Decentralized Identifier Working Group - Activity
No matches.
TR publications
-
2 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v1 published as a Candidate Recommendation Draft. History of Decentralized Identifier Resolution (DID Resolution) v1
-
DID Methods published as a Note. History of DID Methods
-
GitHub
w3c/did-extensions
-
1 pull request merged.
-
Add did:agentid method registration w3c/did-extensions#762.
-
-
1 pull request received 1 new comment.
-
Give each error entry the URL its defining specification defines w3c/did-extensions#767 (1 comment by @MizukiSonoko)
-
w3c/did-resolution
-
1 issue received 1 new comment.
-
Consider revising / removing DID Resolution Architecture w3c/did-resolution#347 (1 comment by @TallTed)
-
-
1 pull request merged.
-
Remove DID Resolution Architectures section w3c/did-resolution#390.
-
-
1 pull request received 1 new comment.
Lifecycle
TR publications
-
6 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v1 published 5 times as a Candidate Recommendation Draft. History of Decentralized Identifier Resolution (DID Resolution) v1
-
DID Methods published as a Note. History of DID Methods
-
Past meetings
Participants
-
1 participant joined.
-
Juan Caballero (Decentralized Identity Foundation (DIF)) joined.
-
-
2 participants left.
-
Rob De Feo (Vidos) left.
-
Misha Deville (Vidos) left.
-
-
1 organization joined.
-
Decentralized Identity Foundation (DIF) joined.
-
-
1 organization left.
-
Vidos left.
-
GitHub
w3c/did-extensions
-
5 pull requests opened.
-
Give each error entry the URL its defining specification defines w3c/did-extensions#767, by @danpape.
-
Register did:aroha w3c/did-extensions#766, by @rajganesan-aroha-labs.
-
Register did:cde method w3c/did-extensions#765, by @OlivierTiratCDE.
-
Register did:sigelo w3c/did-extensions#764, by @csigelo.
-
-
1 pull request merged.
-
Register did:aria DID method w3c/did-extensions#714.
-
-
1 pull request closed.
-
Register the did:at DID method w3c/did-extensions#732.
-
-
4 pull requests received 9 new comments.
w3c/did-resolution
-
14 issues opened.
-
post-344: Problematic definitions of “client” and “DID-enabled application” w3c/did-resolution#387, by @peacekeeper.
-
post-344: Confusion about performing HTTP GET on service endpoints as part of DID URL dereferencing w3c/did-resolution#386, by @peacekeeper.
-
post-344: Open questions about `did:ex:123?service=DIDCommMessaging` example w3c/did-resolution#385, by @peacekeeper.
-
post-344: Open questions about `did:ex:123#key-1` example w3c/did-resolution#384, by @peacekeeper.
-
post-344: Open questions about `relativeRef`, `PathHandler`, `PathService` w3c/did-resolution#383, by @peacekeeper.
-
post-344: Unclear how “serviceType” could be supported w3c/did-resolution#382, by @peacekeeper.
-
post-344: Dereferencing algorithm should not depend on configuration of its implementation w3c/did-resolution#381, by @peacekeeper.
-
post-344: Dereferencing algorithm should not depend on context in which it is executed w3c/did-resolution#380, by @peacekeeper.
-
post-344: Unclear why dereferencing metadata was removed w3c/did-resolution#379, by @peacekeeper.
-
post-344: Unclear why dereferencing options were removed w3c/did-resolution#378, by @peacekeeper.
-
post-344: Dereferencing algorithm defines no results w3c/did-resolution#377, by @peacekeeper.
-
@jandrieu fears we are rehashing the same issue again. w3c/did-resolution#367, by @TallTed.
-
`contentType` returned in the wrong metadata structure (Sections 4.4 and 5.4.1) w3c/did-resolution#366, by @danpape.
-
Section 12.1: no status code or `Content-Type` rule for a complete DID resolution result w3c/did-resolution#365, by @danpape.
-
-
16 issues closed.
-
Address incompatible entries in extensions registry w3c/did-resolution#150.
-
Define how DID Methods can specify paths and their dereferencing rules w3c/did-resolution#156.
-
Create syntactic sugar for `relativeRef` feature w3c/did-resolution#181.
-
Should support for DID Parameters be OPTIONAL? w3c/did-resolution#289.
-
Reconsider accept as parameter for dereferencing rather than resolution w3c/did-resolution#303.
-
Consider replacing "dereferencer" with "resolving client" w3c/did-resolution#310.
-
How does a registered error type become a URL? w3c/did-resolution#359.
-
Section 12.1: no status code or `Content-Type` rule for a complete DID resolution result w3c/did-resolution#365.
-
`contentType` returned in the wrong metadata structure (Sections 4.4 and 5.4.1) w3c/did-resolution#366.
-
Potentially drop HTTP binding for "dereferencers"? w3c/did-resolution#306.
-
Add examples to illustrate different DID Resolution Architectures w3c/did-resolution#131.
-
Fill out the Security and Privacy self review questionnaire w3c/did-resolution#191.
-
@jandrieu fears we are rehashing the same issue again. w3c/did-resolution#367.
-
Horizontal Reviews for DID Resolution v1.0 w3c/did-resolution#349.
-
Registered and method-defined error types have no HTTP status mapping w3c/did-resolution#355.
-
24 issues received 37 new comments.
-
Consider revising / removing DID Resolution Architecture w3c/did-resolution#347 (6 comments by @ottomorac, @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
post-344: Confusion about performing HTTP GET on service endpoints as part of DID URL dereferencing w3c/did-resolution#386 (3 comments by @peacekeeper, @swcurran, @wip-abramson)
-
post-344: Open questions about `did:ex:123?service=DIDCommMessaging` example w3c/did-resolution#385 (3 comments by @peacekeeper, @swcurran, @wip-abramson)
-
Experiments with service, serviceType, relativeRef vs. PathService w3c/did-resolution#332 (3 comments by @peacekeeper, @wip-abramson)
-
Reconsider expandRelativeURLs as part of dereferencing instead of resolution w3c/did-resolution#302 (2 comments by @peacekeeper, @wip-abramson)
-
Potentially drop HTTP binding for "dereferencers"? w3c/did-resolution#306 (2 comments by @swcurran, @wip-abramson)
-
post-344: Unclear how “serviceType” could be supported w3c/did-resolution#382 (1 comment by @wip-abramson)
-
post-344: Open questions about `relativeRef`, `PathHandler`, `PathService` w3c/did-resolution#383 (1 comment by @wip-abramson)
-
post-344: Open questions about `did:ex:123#key-1` example w3c/did-resolution#384 (1 comment by @wip-abramson)
-
post-344: Problematic definitions of “client” and “DID-enabled application” w3c/did-resolution#387 (1 comment by @wip-abramson)
-
Consider replacing "dereferencer" with "resolving client" w3c/did-resolution#310 (1 comment by @wip-abramson)
-
MUST implement the exact function signature for DID Resolution? w3c/did-resolution#363 (1 comment by @w3cbot)
-
Add examples to illustrate different DID Resolution Architectures w3c/did-resolution#131 (1 comment by @wip-abramson)
-
Reconsider accept as parameter for dereferencing rather than resolution w3c/did-resolution#303 (1 comment by @wip-abramson)
-
Fill out the Security and Privacy self review questionnaire w3c/did-resolution#191 (1 comment by @wip-abramson)
-
Create syntactic sugar for `relativeRef` feature w3c/did-resolution#181 (1 comment by @wip-abramson)
-
Define how DID Methods can specify paths and their dereferencing rules w3c/did-resolution#156 (1 comment by @wip-abramson)
-
Address incompatible entries in extensions registry w3c/did-resolution#150 (1 comment by @wip-abramson)
-
@jandrieu fears we are rehashing the same issue again. w3c/did-resolution#367 (1 comment by @wip-abramson)
-
Section 12.1: no status code or `Content-Type` rule for a complete DID resolution result w3c/did-resolution#365 (1 comment by @peacekeeper)
-
`contentType` returned in the wrong metadata structure (Sections 4.4 and 5.4.1) w3c/did-resolution#366 (1 comment by @peacekeeper)
-
Registered and method-defined error types have no HTTP status mapping w3c/did-resolution#355 (1 comment by @danpape)
-
-
13 pull requests opened.
-
Remove DID Resolution Architectures section w3c/did-resolution#390, by @swcurran.
-
Remove broken links to deleted dereferencing metadata sections w3c/did-resolution#389, by @JinDX.
-
Percent-encode the service parameter in the Default Service Handler example w3c/did-resolution#388, by @shlee1223.
-
Localized fixes to address broken links from 344 and 371 w3c/did-resolution#376, by @swcurran.
-
Fix additional post-ReSpec errors that prevent Echidna Auto-publish GHAction completing w3c/did-resolution#375, by @swcurran.
-
Fix ReSpec errors that prevent Echidna Auto-publish GHAction completing w3c/did-resolution#374, by @swcurran.
-
Remove DID URL Dereferencing Result section w3c/did-resolution#373, by @swcurran.
-
Remove DID URL dereferencing from the HTTP(S) binding w3c/did-resolution#372, by @danpape.
-
Replace DID URL Dereferencing algorithm with provisional one w3c/did-resolution#371, by @wip-abramson.
-
Require a specification that defines an error type to define its URL w3c/did-resolution#370, by @danpape.
-
Give a complete result a status code in the HTTP(S) binding w3c/did-resolution#369, by @danpape.
-
Return contentType in the metadata structures that define it w3c/did-resolution#368, by @danpape.
-
Mostly replace "client" with "DID-enabled application" w3c/did-resolution#364, by @peacekeeper.
-
-
11 pull requests merged.
-
Remove DID URL Dereferencing Result section w3c/did-resolution#373.
-
Require a specification that defines an error type to define its URL w3c/did-resolution#370.
-
Give a complete result a status code in the HTTP(S) binding w3c/did-resolution#369.
-
Localized fixes to address broken links from 344 and 371 w3c/did-resolution#376.
-
Fix additional post-ReSpec errors that prevent Echidna Auto-publish GHAction completing w3c/did-resolution#375.
-
Fix ReSpec errors that prevent Echidna Auto-publish GHAction completing w3c/did-resolution#374.
-
Return contentType in the metadata structures that define it w3c/did-resolution#368.
-
Remove DID URL dereferencing from the HTTP(S) binding w3c/did-resolution#372.
-
Replace DID URL Dereferencing algorithm with provisional one w3c/did-resolution#371.
-
full pass at DID URL dereferencing algorithm (isolated) w3c/did-resolution#344.
-
Map error types not defined in this specification to HTTP status codes w3c/did-resolution#358.
-
-
8 pull requests closed.
-
Remove broken links to deleted dereferencing metadata sections w3c/did-resolution#389.
-
Explain that DID URL dereferencer acts as client of a DID resolver w3c/did-resolution#319.
-
Andrieu/did parameter guidance w3c/did-resolution#325.
-
Emphasize DID URL dereferencing "algorithm" over "function" w3c/did-resolution#362.
-
Andrieu/remove dereferencing function w3c/did-resolution#326.
-
major rewrite to address resolution/dereferencing confusion. take 2 w3c/did-resolution#315.
-
first complete pass at resolution/dereference clean up. still draft. w3c/did-resolution#311.
-
shifts from resolving "DIDs" to "DID URLs" w3c/did-resolution#324.
-
-
21 pull requests received 128 new comments.
-
full pass at DID URL dereferencing algorithm (isolated) w3c/did-resolution#344 (74 comments by @frmoretto, @jandrieu, @ottomorac, @peacekeeper, @swcurran, @TallTed, @wip-abramson)
-
Mostly replace "client" with "DID-enabled application" w3c/did-resolution#364 (13 comments by @danpape, @mccown, @peacekeeper, @TallTed, @w3cbot)
-
Replace DID URL Dereferencing algorithm with provisional one w3c/did-resolution#371 (6 comments by @ottomorac, @peacekeeper, @w3cbot, @wip-abramson)
-
Explain better that function signatures are abstract w3c/did-resolution#356 (5 comments by @peacekeeper, @wip-abramson)
-
Require a specification that defines an error type to define its URL w3c/did-resolution#370 (4 comments by @danpape, @TallTed, @wip-abramson)
-
Give a complete result a status code in the HTTP(S) binding w3c/did-resolution#369 (4 comments by @danpape, @wip-abramson)
-
Return contentType in the metadata structures that define it w3c/did-resolution#368 (4 comments by @danpape, @peacekeeper, @w3cbot)
-
Explain that DID URL dereferencer acts as client of a DID resolver w3c/did-resolution#319 (3 comments by @peacekeeper, @wip-abramson)
-
Remove broken links to deleted dereferencing metadata sections w3c/did-resolution#389 (2 comments by @JinDX, @swcurran)
-
Emphasize DID URL dereferencing "algorithm" over "function" w3c/did-resolution#362 (2 comments by @TallTed, @wip-abramson)
-
Percent-encode the service parameter in the Default Service Handler example w3c/did-resolution#388 (1 comment by @swcurran)
-
Localized fixes to address broken links from 344 and 371 w3c/did-resolution#376 (1 comment by @swcurran)
-
Fix additional post-ReSpec errors that prevent Echidna Auto-publish GHAction completing w3c/did-resolution#375 (1 comment by @swcurran)
-
Fix ReSpec errors that prevent Echidna Auto-publish GHAction completing w3c/did-resolution#374 (1 comment by @swcurran)
-
Remove DID URL dereferencing from the HTTP(S) binding w3c/did-resolution#372 (1 comment by @danpape)
-
major rewrite to address resolution/dereferencing confusion. take 2 w3c/did-resolution#315 (1 comment by @wip-abramson)
-
first complete pass at resolution/dereference clean up. still draft. w3c/did-resolution#311 (1 comment by @wip-abramson)
-
w3c/did-threat-model
-
3 issues opened.
-
Proposed Threat w3c/did-threat-model#11, by @TomCJones.
-
Threat Model covers a subset of possible DID Resolution architectures w3c/did-threat-model#9, by @peacekeeper.
-
Fix language about "resolving DID URLs" w3c/did-threat-model#8, by @peacekeeper.
-
-
1 pull request opened.
-
Updated threat model to address both DIDs and DID Resolution w3c/did-threat-model#10, by @jandrieu.
-
-
1 pull request merged.
-
Updated threat model to address both DIDs and DID Resolution w3c/did-threat-model#10.
-
w3c/did
-
2 issues opened.
-
Clean up ids and add explanation w3c/did#937, by @jandrieu.
-
1 issue closed.
-
CSOAI — did:web AI governance identity w3c/did#935.
-
-
1 issue received 2 new comments.
w3c/did-wg-charter
-
1 issue received 3 new comments.
w3c/did-resolution-threat-model
-
2 issues opened.
-
Threat Model covers a subset of possible DID Resolution architectures w3c/did-resolution-threat-model#9, by @peacekeeper.
-
Fix language about "resolving DID URLs" w3c/did-resolution-threat-model#8, by @peacekeeper.
-
TR publications
-
5 documents published.
-
DID Methods published 3 times as a Note. History of DID Methods
-
DID Method Rubric v2.0 published twice as a Note. History of DID Method Rubric v2.0
-
Past meetings
-
6 meetings.
GitHub
w3c/did-resolution
-
3 issues opened.
-
MUST implement the exact function signature for DID Resolution? w3c/did-resolution#363, by @peacekeeper.
-
How to express inputs and results of the algorithms? w3c/did-resolution#361, by @peacekeeper.
-
-
5 issues received 16 new comments.
-
How to express inputs and results of the algorithms? w3c/did-resolution#361 (6 comments by @msporny, @peacekeeper, @swcurran, @wip-abramson)
-
HTTP(S) Binding's GET and TLS requirements apply to all conforming DID resolvers, not only network-based ones w3c/did-resolution#360 (4 comments by @danpape, @fabianekc, @peacekeeper, @wip-abramson)
-
Treat deactivated DID resolution state as an error code w3c/did-resolution#353 (3 comments by @filip26, @peacekeeper)
-
How does a registered error type become a URL? w3c/did-resolution#359 (2 comments by @danpape, @wip-abramson)
-
MUST implement the exact function signature for DID Resolution? w3c/did-resolution#363 (1 comment by @TallTed)
-
-
1 pull request opened.
-
Emphasize DID URL dereferencing "algorithm" over "function" w3c/did-resolution#362, by @peacekeeper.
-
-
5 pull requests received 87 new comments.
-
full pass at DID URL dereferencing algorithm (isolated) w3c/did-resolution#344 (60 comments by @jandrieu, @peacekeeper, @swcurran, @TallTed, @w3cbot, @wip-abramson)
-
Emphasize DID URL dereferencing "algorithm" over "function" w3c/did-resolution#362 (15 comments by @peacekeeper, @TallTed, @wip-abramson)
-
Explain better that function signatures are abstract w3c/did-resolution#356 (7 comments by @peacekeeper, @TallTed, @wip-abramson)
-
Map error types not defined in this specification to HTTP status codes w3c/did-resolution#358 (4 comments by @danpape, @peacekeeper, @TallTed)
-
w3c/did-wg-charter
-
1 issue opened.
-
Use of LLMs in standards work? w3c/did-wg-charter#39, by @peacekeeper.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Add CID to list of charter deliverables. w3c/did-wg-charter#37, by @msporny.
-
-
1 pull request merged.
-
Add CID to list of charter deliverables. w3c/did-wg-charter#37.
-
-
1 pull request received 12 new comments.
-
Add CID to list of charter deliverables. w3c/did-wg-charter#37 (12 comments by @brentzundel, @iherman, @jeswr, @msporny)
-
w3c/did-extensions
-
2 issues opened.
-
Registration process clarification for did:maatara: metadata entry and IP commitments w3c/did-extensions#759, by @Rob142857.
-
Link to `webs` method is broken w3c/did-extensions#754, by @jeswr.
-
-
1 issue closed.
-
Four error entries reference public key errors that DID Resolution removed w3c/did-extensions#747.
-
-
1 issue received 1 new comment.
-
11 pull requests opened.
-
Add did:agentid method registration w3c/did-extensions#762, by @haroldmalikfrimpong-ops.
-
Register did:avtr w3c/did-extensions#761, by @amoddange.
-
Deprecate four error entries whose DID Resolution definitions were removed w3c/did-extensions#760, by @danpape.
-
Register did:youling and did:myco methods w3c/did-extensions#758, by @cjfan.
-
Register did:rodit method w3c/did-extensions#757, by @discernible-io.
-
Add did:vireo method w3c/did-extensions#755, by @serhohro.
-
Register did:aaid DID method - Agentic AI Identifier for A2A and MCP agents w3c/did-extensions#753, by @shlee1223.
-
Add contact email and website for did:meta w3c/did-extensions#752, by @jsong1230.
-
Register did:epn w3c/did-extensions#751, by @ansikmahapatra.
-
Update did:aip registration to v2 (Solana to ERC-8004) w3c/did-extensions#750, by @dr-wilson-empty.
-
-
9 pull requests merged.
-
Add did:vireo method w3c/did-extensions#755.
-
Register did:cha2a method w3c/did-extensions#744.
-
Add contact email and website for did:meta w3c/did-extensions#752.
-
Deprecate four error entries whose DID Resolution definitions were removed w3c/did-extensions#760.
-
Register did:epn w3c/did-extensions#751.
-
Fix case-mismatched links to DID Resolution error definitions w3c/did-extensions#746.
-
Register did:educreds method w3c/did-extensions#749.
-
Register did:julia w3c/did-extensions#748.
-
-
2 pull requests closed.
-
Register did:aaid DID method - Agentic AI Identifier for A2A and MCP agents w3c/did-extensions#753.
-
Update did:ma url to version 1.0.0 final w3c/did-extensions#745.
-
-
1 pull request reopened.
-
Update did:aip registration to v2 (Solana to ERC-8004) w3c/did-extensions#750, by @dr-wilson-empty.
-
-
8 pull requests received 17 new comments.
-
Register did:aaid DID method - Agentic AI Identifier for A2A and MCP agents w3c/did-extensions#753 (2 comments by @shlee1223)
-
Register did:cimd - a DID method for AI agents and MCP clients (resolved from the OAuth Client ID Metadata Document, no ledger) w3c/did-extensions#756 (1 comment by @shlee1223)
w3c/did-cbor-note
-
1 issue opened.
-
07503531977 w3c/did-cbor-note#9, by @ll6065412-bit.
-
-
1 issue closed.
-
07503531977 w3c/did-cbor-note#9.
-
w3c/did-rubric
-
1 issue closed.
-
Move "Retired Criteria" and "Possible additional criteria" from main spec w3c/did-rubric#109.
-
-
1 pull request opened.
-
remove possible additional criteria w3c/did-rubric#117, by @wip-abramson.
-
-
1 pull request merged.
-
remove possible additional criteria w3c/did-rubric#117.
-
w3c/did
-
2 issues opened.
-
CSOAI — did:web AI governance identity w3c/did#935, by @CSOAI-ORG.