Decentralized Identifier Working Group - Activity in 2025
No matches.
TR publications
-
7 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published 3 times as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
DID Methods published twice as a Note. History of DID Methods
-
DID Document Property Extensions published as a Note. History of DID Document Property Extensions
-
Decentralized Identifier Extensions published as a Note. History of Decentralized Identifier Extensions
-
Past meetings
Participants
-
6 participants left.
-
Shaun Conway (W3C Invited Experts) left.
-
Zaïda Rivai (Danube Tech GmbH) left.
-
Ahamed Azeem (Danube Tech GmbH) left.
-
Bernhard Fuchs (Danube Tech GmbH) left.
-
Markus Sabadello (W3C Invited Experts) left.
-
Brent Zundel (Tradeverifyd) left.
-
-
1 organization left.
-
Danube Tech GmbH left.
-
GitHub
w3c/did
-
1 issue opened.
-
1 issue received 2 new comments.
-
PROPOSAL: Universal values for a *null DID* as well as an *empty DID* w3c/did#914 (2 comments by @davidlehn, @mwherman2000)
-
-
1 pull request opened.
-
Export terms from DID Core w3c/did#913, by @ottomorac.
-
-
1 pull request received 4 new comments.
w3c/did-extensions
-
1 issue opened.
-
Add registration rule about metadata to DID Resolution Extensions w3c/did-extensions#655, by @wip-abramson.
-
-
1 issue received 1 new comment.
-
Add registration rule about metadata to DID Resolution Extensions w3c/did-extensions#655 (1 comment by @wip-abramson)
-
-
5 pull requests opened.
-
Add did:kxtid method w3c/did-extensions#660, by @energy-blockchian.
-
Update Editors for Echidna Flow for the other extensions w3c/did-extensions#659, by @ottomorac.
-
Update Editors for Echidna Flow w3c/did-extensions#658, by @ottomorac.
-
Update contact name info for did:nda w3c/did-extensions#657, by @thanhhuykhtn.
-
add did:ckb method w3c/did-extensions#656, by @doitian.
-
-
6 pull requests merged.
-
Update contact name info for did:nda w3c/did-extensions#657.
-
Update Editors for Echidna Flow for the other extensions w3c/did-extensions#659.
-
Update Editors for Echidna Flow w3c/did-extensions#658.
-
add did:ckb method w3c/did-extensions#656.
-
Add did:operon method w3c/did-extensions#653.
-
add did:nda method w3c/did-extensions#649.
-
-
4 pull requests received 5 new comments.
w3c/did-resolution
-
3 issues opened.
-
DID URL Derefencing and Fragments: The role of a DID Resolver w3c/did-resolution#259, by @swcurran.
-
Untestable normative requirement for proof w3c/did-resolution#252, by @wip-abramson.
-
Remove untestable normative requirement on the DID Resolution Extensions w3c/did-resolution#251, by @wip-abramson.
-
-
1 issue closed.
-
Consider adding "Design Goals and Rationale" section w3c/did-resolution#208.
-
-
22 issues received 46 new comments.
-
Unclear definition of "Read" operation for DID methods w3c/did-resolution#230 (14 comments by @jandrieu, @jyasskin, @msporny, @peacekeeper, @w3cbot, @wip-abramson)
-
Rework the abstract to be more grounded w3c/did-resolution#225 (4 comments by @jenniemeier, @w3cbot, @wip-abramson)
-
DID URL Derefencing and Fragments: The role of a DID Resolver w3c/did-resolution#259 (3 comments by @peacekeeper, @w3cbot, @wip-abramson)
-
Reference either DID v1.0 or v1.1 throughout the specification w3c/did-resolution#224 (2 comments by @w3cbot, @wip-abramson)
-
Remove "client" from identifying an error in the path handling w3c/did-resolution#244 (2 comments by @swcurran, @wip-abramson)
-
Do we need to include iterating over extensions in the DID resolution algorithm? w3c/did-resolution#238 (2 comments by @peacekeeper, @wip-abramson)
-
Fill out the Security and Privacy self review questionnaire w3c/did-resolution#191 (2 comments by @ottomorac, @peacekeeper)
-
Fix bug in implementer overview description w3c/did-resolution#228 (2 comments by @peacekeeper, @w3cbot)
-
Remove unnecessary text "against the input verifiable data registry" from DID Resolution Algorithm w3c/did-resolution#236 (1 comment by @msporny)
-
Specify the algorithm for processing the hl DID parameter. w3c/did-resolution#209 (1 comment by @msporny)
-
Use character reference notation and Unicode names for references to specific characters w3c/did-resolution#202 (1 comment by @peacekeeper)
-
Confusing error language in algorithms leading to misimplementation w3c/did-resolution#240 (1 comment by @wip-abramson)
-
need some language about implementing https within private IP range w3c/did-resolution#173 (1 comment by @wip-abramson)
-
Add DID Resolution architecture security and privacy considerations w3c/did-resolution#133 (1 comment by @wip-abramson)
-
Conflicting normative statements about conformant representation of DID document and the accept input w3c/did-resolution#237 (1 comment by @wip-abramson)
-
Can we avoid term definition duplication across DID specs? w3c/did-resolution#232 (1 comment by @w3cbot)
-
Conflicting normative statements about didDocument representation w3c/did-resolution#234 (1 comment by @w3cbot)
-
-
13 pull requests opened.
-
Remove unnecessary normative text from DID Resolution Algorithm. w3c/did-resolution#263, by @msporny.
-
Remove `hl` (hashlink) parameter w3c/did-resolution#262, by @msporny.
-
Remove trailing spaces. w3c/did-resolution#261, by @msporny.
-
Add DID URL Path Handling w3c/did-resolution#260, by @swcurran.
-
Fix section hierarchy bug w3c/did-resolution#258, by @wip-abramson.
-
Clarify DID document representation in relation to accept header w3c/did-resolution#257, by @wip-abramson.
-
Fix section hierarchy bug w3c/did-resolution#256, by @wip-abramson.
-
Add introduction to privacy and security consideration section w3c/did-resolution#255, by @wip-abramson.
-
Note Markus as former editor to fix echidna w3c/did-resolution#254, by @wip-abramson.
-
Clean untestable and duplicate normative statements in spec w3c/did-resolution#253, by @wip-abramson.
-
Clarify proof property definition w3c/did-resolution#250, by @wip-abramson.
-
Update didDocument definition to remove ambiguous use of match and reference the DID data model section w3c/did-resolution#249, by @wip-abramson.
-
Define generic datetime format for DID resolution and use throughout spec w3c/did-resolution#248, by @wip-abramson.
-
-
6 pull requests merged.
-
Add warning about self attested DID document metadata w3c/did-resolution#206.
-
Fix section hierarchy bug w3c/did-resolution#258.
-
Fix section hierarchy bug w3c/did-resolution#256.
-
Note Markus as former editor to fix echidna w3c/did-resolution#254.
-
Clean up old issue flags w3c/did-resolution#242.
-
Fix broken links in common.js w3c/did-resolution#219.
-
-
1 pull request closed.
-
Update DID URL Dereferencing Section with Deterministic Path Handling w3c/did-resolution#221.
-
-
15 pull requests received 81 new comments.
-
Add DID URL Path Handling w3c/did-resolution#260 (48 comments by @msporny, @peacekeeper, @swcurran, @TallTed, @wip-abramson)
-
Prefer UTF-8 for DID Parameters w3c/did-resolution#217 (5 comments by @jandrieu, @swcurran, @w3cbot, @wip-abramson)
-
Define network based conformance classes for resolver and dereferencer w3c/did-resolution#243 (3 comments by @w3cbot, @wip-abramson)
-
Standardize error responses per id (#212) w3c/did-resolution#215 (2 comments by @w3cbot, @wip-abramson)
-
Add warning about self attested DID document metadata w3c/did-resolution#206 (2 comments by @w3cbot, @wip-abramson)
-
Remove unnecessary normative text from DID Resolution Algorithm. w3c/did-resolution#263 (1 comment by @msporny)
-
Clean untestable and duplicate normative statements in spec w3c/did-resolution#253 (1 comment by @TallTed)
-
Clarify DID document representation in relation to accept header w3c/did-resolution#257 (1 comment by @wip-abramson)
-
Update DID URL Dereferencing Section with Deterministic Path Handling w3c/did-resolution#221 (1 comment by @swcurran)
-
w3c/did-rubric
-
1 issue opened.
-
Refactor Many Eyes w3c/did-rubric#76, by @jandrieu.
-
w3c/did-test-suite
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
DID Methods published as a Note. History of DID Methods
Past meetings
Participants
-
2 participants left.
-
Gabe Cohen (W3C Invited Experts) left.
-
Mic Bowman (Intel Corporation) left.
-
-
1 organization joined.
-
Chinese Academy of Sciences joined.
-
GitHub
w3c/did-extensions
-
1 issue opened.
-
Inconsistencies in § 3.1.6 PgpVerificationKey2021 of did-extensions-properties w3c/did-extensions#654, by @pchampin.
-
-
5 pull requests opened.
-
Add did:operon method w3c/did-extensions#653, by @operonmaster.
-
Add did:drop method w3c/did-extensions#652, by @tenman1739-alt.
-
add ConditionalProof2022 as verification method type w3c/did-extensions#651, by @jrayback.
-
update contact website for did:webs w3c/did-extensions#650, by @jrayback.
-
add did:nda method w3c/did-extensions#649, by @thanhhuykhtn.
-
-
1 pull request merged.
-
update contact website for did:webs w3c/did-extensions#650.
-
-
6 pull requests received 14 new comments.
-
add ConditionalProof2022 as verification method type w3c/did-extensions#651 (2 comments by @jrayback, @kentbull)
w3c/did-resolution
-
3 issues opened.
-
Identify unthrown errors in the spec. w3c/did-resolution#247, by @wip-abramson.
-
Clarify the distinction between DID Resolution and DID URL Dereferencing w3c/did-resolution#246, by @wip-abramson.
-
Remove "client" from identifying an error in the path handling w3c/did-resolution#244, by @swcurran.
-
-
5 issues closed.
-
Unaddressed denial of service vector w3c/did-resolution#172.
-
HTTP POST method binding w3c/did-resolution#161.
-
Create NO_CACHE_DISALLOWED error w3c/did-resolution#174.
-
Prepare for DID Resolution v1.0 TAG Review w3c/did-resolution#177.
-
Error codes for unsupported DID features w3c/did-resolution#190.
-
-
30 issues received 65 new comments.
-
Address confusing note about the difference between "resolving" a DID and "dereferencing" a DID URL w3c/did-resolution#227 (7 comments by @ottomorac, @peacekeeper, @swcurran, @w3cbot, @wip-abramson)
-
Unclear definition of "Read" operation for DID methods w3c/did-resolution#230 (6 comments by @w3cbot, @wip-abramson)
-
Address reference to internet draft [HASHLINK] w3c/did-resolution#229 (6 comments by @TallTed, @w3cbot, @wip-abramson)
-
Remove "client" from identifying an error in the path handling w3c/did-resolution#244 (5 comments by @msporny, @peacekeeper, @w3cbot)
-
Duplicate normative requirements around implementing DID resolution algorithm w3c/did-resolution#239 (3 comments by @peacekeeper, @w3cbot, @wip-abramson)
-
Fix bug in implementer overview description w3c/did-resolution#228 (3 comments by @ottomorac, @swcurran, @w3cbot)
-
Clean up duplicate normative requirement statement for error property in didResolutionMetadata w3c/did-resolution#222 (2 comments by @w3cbot, @wip-abramson)
-
w3c/did-resolution#38 (2 comments by @w3cbot)
-
Add examples to illustrate different DID Resolution Architectures w3c/did-resolution#131 (2 comments by @w3cbot, @wip-abramson)
-
Add DID Resolution architecture security and privacy considerations w3c/did-resolution#133 (2 comments by @w3cbot, @wip-abramson)
-
Complete threat modelling analysis for different DID Resolution architectures w3c/did-resolution#132 (2 comments by @w3cbot, @wip-abramson)
-
Consider adding "Design Goals and Rationale" section w3c/did-resolution#208 (2 comments by @msporny, @w3cbot)
-
Confusing error language in algorithms leading to misimplementation w3c/did-resolution#240 (2 comments by @msporny, @w3cbot)
-
Conflicting normative statements about conformant representation of DID document and the accept input w3c/did-resolution#237 (2 comments by @msporny, @w3cbot)
-
Avoid ambiguous use of 'match' in specification w3c/did-resolution#233 (2 comments by @w3cbot, @wip-abramson)
-
Can we avoid term definition duplication across DID specs? w3c/did-resolution#232 (2 comments by @msporny, @w3cbot)
-
Remove normative statement around passing resolution options to the Read operation w3c/did-resolution#223 (1 comment by @w3cbot)
-
Standardize error responses with RFC9457ProblemDetails w3c/did-resolution#212 (1 comment by @w3cbot)
-
Reference either DID v1.0 or v1.1 throughout the specification w3c/did-resolution#224 (1 comment by @w3cbot)
-
Do we need to include iterating over extensions in the DID resolution algorithm? w3c/did-resolution#238 (1 comment by @w3cbot)
-
Remove unnecessary text "against the input verifiable data registry" from DID Resolution Algorithm w3c/did-resolution#236 (1 comment by @w3cbot)
-
Confusing proof property in metadata returned by DID Resolver w3c/did-resolution#235 (1 comment by @w3cbot)
-
Conflicting normative statements about didDocument representation w3c/did-resolution#234 (1 comment by @wip-abramson)
-
`relativeRef` should prefer UTF-8 for percent encoding w3c/did-resolution#201 (1 comment by @w3cbot)
-
-
1 pull request opened.
-
Remove note about did resolution and de-referencing w3c/did-resolution#245, by @ottomorac.
-
-
1 pull request merged.
-
Remove note about did resolution and de-referencing w3c/did-resolution#245.
-
-
5 pull requests received 14 new comments.
-
Define network based conformance classes for resolver and dereferencer w3c/did-resolution#243 (5 comments by @jandrieu, @w3cbot, @wip-abramson)
-
Update DID URL Dereferencing Section with Deterministic Path Handling w3c/did-resolution#221 (5 comments by @dlongley, @peacekeeper, @swcurran, @w3cbot)
-
Remove note about did resolution and de-referencing w3c/did-resolution#245 (1 comment by @peacekeeper)
-
w3c/did-test-suite
-
1 issue opened.
-
Numbers now allowed in DID Resolution Metadata -- test suite needs to allow that w3c/did-test-suite#230, by @swcurran.
-
-
1 pull request opened.
-
feat: did:webs added to test suite w3c/did-test-suite#229, by @kentbull.
-
-
2 pull requests received 2 new comments.
w3c/did
-
1 issue received 1 new comment.
-
Language clarification "A DID document is a representation of information describing a DID subject." w3c/did#912 (1 comment by @TallTed)
-
TR publications
-
5 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published 4 times as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
DID Methods published as a Note. History of DID Methods
-
Past meetings
-
7 meetings.
Participants
-
1 participant left.
-
Kazuyuki Ashimura (W3C) left.
-
GitHub
w3c/did-resolution
-
27 issues opened.
-
Reference DID Core Security and Privacy considerations sections w3c/did-resolution#241, by @wip-abramson.
-
Confusing error language in algorithms leading to misimplementation w3c/did-resolution#240, by @wip-abramson.
-
Duplicate normative requirements around implementing DID resolution algorithm w3c/did-resolution#239, by @wip-abramson.
-
Do we need to include iterating over extensions in the DID resolution algorithm? w3c/did-resolution#238, by @wip-abramson.
-
Conflicting normative statements about conformant representation of DID document and the accept input w3c/did-resolution#237, by @wip-abramson.
-
Remove unnecessary text "against the input verifiable data registry" from DID Resolution Algorithm w3c/did-resolution#236, by @wip-abramson.
-
Confusing proof property in metadata returned by DID Resolver w3c/did-resolution#235, by @wip-abramson.
-
Conflicting normative statements about didDocument representation w3c/did-resolution#234, by @wip-abramson.
-
Avoid ambiguous use of 'match' in specification w3c/did-resolution#233, by @wip-abramson.
-
Can we avoid term definition duplication across DID specs? w3c/did-resolution#232, by @wip-abramson.
-
didDocument definition should refer to DID Data Model w3c/did-resolution#231, by @wip-abramson.
-
Unclear definition of "Read" operation for DID methods w3c/did-resolution#230, by @wip-abramson.
-
Address reference to internet draft [HASHLINK] w3c/did-resolution#229, by @wip-abramson.
-
Fix bug in implementer overview description w3c/did-resolution#228, by @wip-abramson.
-
Address confusing note about the difference between "resolving" a DID and "dereferencing" a DID URL w3c/did-resolution#227, by @wip-abramson.
-
Inconsistent use of resolution? w3c/did-resolution#226, by @wip-abramson.
-
Rework the abstract to be more grounded w3c/did-resolution#225, by @wip-abramson.
-
Reference either DID v1.0 or v1.1 throughout the specification w3c/did-resolution#224, by @wip-abramson.
-
Remove normative statement around passing resolution options to the Read operation w3c/did-resolution#223, by @wip-abramson.
-
Clean up duplicate normative requirement statement for error property in didResolutionMetadata w3c/did-resolution#222, by @wip-abramson.
-
Review ISSUE flags throughout the specification w3c/did-resolution#220, by @wip-abramson.
-
Add rules for DID URL query normalization w3c/did-resolution#218, by @msporny.
-
Broken links w3c/did-resolution#214, by @FabioPinheiro.
-
Make conformance statements concretely testable w3c/did-resolution#213, by @wip-abramson.
-
Standardize error responses with RFC9457ProblemDetails w3c/did-resolution#212, by @erdemonal.
-
Specify the algorithm for processing the hl DID parameter. w3c/did-resolution#209, by @wip-abramson.
-
Consider adding "Design Goals and Rationale" section w3c/did-resolution#208, by @ottomorac.
-
-
8 issues closed.
-
Horizontal Review for DID Resolution v1.0 w3c/did-resolution#139.
-
Update references to DID Specification Registries throughout w3c/did-resolution#148.
-
Broken links in Decentralized Identifier Resolution (DID Resolution) v0.3 w3c/did-resolution#193.
-
TAG Review: Add a description of the problems that end-users were facing before this proposal w3c/did-resolution#185.
-
TAG Review: List alternatives to DID resolution considered w3c/did-resolution#186.
-
Tag Review: Add examples of how to use DID resolution to solve the end-users' problems w3c/did-resolution#187.
-
TAG Review: What do the end-users experience with DID resolution w3c/did-resolution#188.
-
TAG Review: User research you did to validate the problem and/or design, if any w3c/did-resolution#189.
-
-
19 issues received 29 new comments.
-
Make conformance statements concretely testable w3c/did-resolution#213 (3 comments by @msporny, @ottomorac, @w3cbot)
-
Standardize error responses with RFC9457ProblemDetails w3c/did-resolution#212 (3 comments by @erdemonal, @peacekeeper, @w3cbot)
-
Prepare for DID Resolution v1.0 TAG Review w3c/did-resolution#177 (3 comments by @w3cbot, @wip-abramson)
-
Review ISSUE flags throughout the specification w3c/did-resolution#220 (2 comments by @ottomorac, @w3cbot)
-
Add rules for DID URL query normalization w3c/did-resolution#218 (2 comments by @msporny, @swcurran)
-
Reference either DID v1.0 or v1.1 throughout the specification w3c/did-resolution#224 (1 comment by @w3cbot)
-
Confusing proof property in metadata returned by DID Resolver w3c/did-resolution#235 (1 comment by @peacekeeper)
-
Complete threat modelling analysis for different DID Resolution architectures w3c/did-resolution#132 (1 comment by @w3cbot)
-
Specify the algorithm for processing the hl DID parameter. w3c/did-resolution#209 (1 comment by @w3cbot)
-
TAG Review: Add a description of the problems that end-users were facing before this proposal w3c/did-resolution#185 (1 comment by @peacekeeper)
-
Tag Review: Add examples of how to use DID resolution to solve the end-users' problems w3c/did-resolution#187 (1 comment by @peacekeeper)
-
Fill out the Security and Privacy self review questionnaire w3c/did-resolution#191 (1 comment by @ottomorac)
-
-
10 pull requests opened.
-
Define network based conformance classes for resolver and dereferencer w3c/did-resolution#243, by @wip-abramson.
-
Clean up old issue flags w3c/did-resolution#242, by @wip-abramson.
-
Update DID URL Dereferencing Section with Deterministic Path Handling w3c/did-resolution#221, by @swcurran.
-
Fix broken links in common.js w3c/did-resolution#219, by @wip-abramson.
-
Prefer UTF-8 for DID Parameters w3c/did-resolution#217, by @ottomorac.
-
Prefer UTF-8 for DID Parameters w3c/did-resolution#216, by @ottomorac.
-
Standardize error responses per id (#212) w3c/did-resolution#215, by @erdemonal.
-
Create generic FEATURE_NOT_SUPPORTED error w3c/did-resolution#211, by @ottomorac.
-
Editorial: fix bug in heading id w3c/did-resolution#210, by @wip-abramson.
-
TAG Review: Add examples of how to use DID resolution to solve the end-users' problems w3c/did-resolution#207, by @ottomorac.
-
-
8 pull requests merged.
-
Create generic FEATURE_NOT_SUPPORTED error w3c/did-resolution#211.
-
Security Consideration -- DID Resolver Clients should detect resolution cycles w3c/did-resolution#204.
-
Define HTTP POST binding w3c/did-resolution#196.
-
Editorial: fix bug in heading id w3c/did-resolution#210.
-
Remove auto-publication of pull requests. w3c/did-resolution#205.
-
Add usecases section for TAG w3c/did-resolution#194.
-
TAG Review: Add examples of how to use DID resolution to solve the end-users' problems w3c/did-resolution#207.
-
Add "Relationship to Other Technologies" section. w3c/did-resolution#199.
-
-
2 pull requests closed.
-
Prefer UTF-8 for DID Parameters w3c/did-resolution#216.
-
Add NO_CACHE_DISALLOWED error w3c/did-resolution#183.
-
-
14 pull requests received 127 new comments.
-
Update DID URL Dereferencing Section with Deterministic Path Handling w3c/did-resolution#221 (55 comments by @ankurdotb, @dmitrizagidulin, @ottomorac, @peacekeeper, @swcurran, @TallTed, @tweeddalex, @w3cbot, @wip-abramson)
-
TAG Review: Add examples of how to use DID resolution to solve the end-users' problems w3c/did-resolution#207 (17 comments by @ottomorac, @peacekeeper, @TallTed, @wip-abramson)
-
Security Consideration -- DID Resolver Clients should detect resolution cycles w3c/did-resolution#204 (15 comments by @peacekeeper, @swcurran, @TallTed, @w3cbot)
-
Make https binding mandatory w3c/did-resolution#182 (12 comments by @msporny, @ottomorac, @peacekeeper, @w3cbot, @wip-abramson)
-
Create generic FEATURE_NOT_SUPPORTED error w3c/did-resolution#211 (8 comments by @msporny, @ottomorac, @peacekeeper, @w3cbot, @wip-abramson)
-
Require HTTP GET binding and allow HTTP POST w3c/did-resolution#192 (6 comments by @dlongley, @msporny, @ottomorac, @w3cbot, @wip-abramson)
-
Standardize error responses per id (#212) w3c/did-resolution#215 (5 comments by @erdemonal, @peacekeeper)
-
Add warning about self attested DID document metadata w3c/did-resolution#206 (3 comments by @msporny, @w3cbot, @wip-abramson)
-
Define network based conformance classes for resolver and dereferencer w3c/did-resolution#243 (1 comment by @peacekeeper)
-
Add "Relationship to Other Technologies" section. w3c/did-resolution#199 (1 comment by @peacekeeper)
-
w3c/did-extensions
-
1 pull request opened.
-
add did:swtc method w3c/did-extensions#648, by @GinMu.
-
-
1 pull request merged.
-
Add did:andorra method to DID Method Registry w3c/did-extensions#647.
-
-
3 pull requests received 18 new comments.
-
Add did:andorra method to DID Method Registry w3c/did-extensions#647 (13 comments by @davidgbvargroup, @msporny, @ottomorac, @swcurran)
-
w3c/did
-
4 issues opened.
-
Add reference to living threat model document w3c/did#910, by @msporny.
-
Harden change-notification guidance w3c/did#909, by @msporny.
-
4 issues received 4 new comments.
-
Clarify that context integrity protection happens when fetching/caching w3c/did#908 (1 comment by @msporny)
-
1 pull request received 2 new comments.
w3c/did-test-suite
-
1 pull request opened.
-
Added did-webplus-ledgerdomain.json to test suite. w3c/did-test-suite#228, by @vdods.
-
TR publications
-
11 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published 3 times as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
Decentralized Identifiers (DIDs) v1.1 published 4 times as a Working Draft. History of Decentralized Identifiers (DIDs) v1.1
-
DID Methods published 4 times as a Note. History of DID Methods
-
Past meetings
Participants
-
1 chair appointed.
-
Will Abramson became a chair.
-
-
1 chair stepped down.
-
Will Abramson stepped down as a chair.
-
-
3 participants joined.
-
Shaun Conway (W3C Invited Experts) joined.
-
Will Abramson (Legendary Requirements) joined.
-
Parth Bhatt (Digital Bazaar) joined.
-
-
3 participants left.
-
Will Abramson (Legendary Requirements) left.
-
Alan Snyder (Deronyan, LLC) left.
-
Ned Smith (Intel Corporation) left.
-
-
1 organization left.
-
Deronyan, LLC left.
-
GitHub
w3c/did-resolution
-
12 issues opened.
-
Define timestamp format carefully w3c/did-resolution#203, by @aphillips.
-
Use character reference notation and Unicode names for references to specific characters w3c/did-resolution#202, by @aphillips.
-
`relativeRef` should prefer UTF-8 for percent encoding w3c/did-resolution#201, by @aphillips.
-
DID parameters require ASCII-only w3c/did-resolution#200, by @aphillips.
-
Broken links in Decentralized Identifier Resolution (DID Resolution) v0.3 w3c/did-resolution#193, by @dontcallmedom-bot.
-
Fill out the Security and Privacy self review questionnaire w3c/did-resolution#191, by @wip-abramson.
-
Error codes for unsupported DID features w3c/did-resolution#190, by @jandrieu.
-
TAG Review: User research you did to validate the problem and/or design, if any w3c/did-resolution#189, by @wip-abramson.
-
TAG Review: What do the end-users experience with DID resolution w3c/did-resolution#188, by @wip-abramson.
-
Tag Review: Add examples of how to use DID resolution to solve the end-users' problems w3c/did-resolution#187, by @wip-abramson.
-
TAG Review: List alternatives to DID resolution considered w3c/did-resolution#186, by @wip-abramson.
-
TAG Review: Add a description of the problems that end-users were facing before this proposal w3c/did-resolution#185, by @wip-abramson.
-
-
10 issues closed.
-
Is the openAPI spec (eventually) normative or informative? w3c/did-resolution#118.
-
Support numbers in metadata structures w3c/did-resolution#166.
-
Validate signatures/proofs of DID Document w3c/did-resolution#13.
-
Signing validation is not defined. w3c/did-resolution#22.
-
'remote' vs 'local' DID Resolvers w3c/did-resolution#28.
-
DID Resolution: Proof of inclusion of DID document in state of Verifiable Data Registry w3c/did-resolution#102.
-
How to use DID resolution metadata to propagate provenance from other Resolvers w3c/did-resolution#159.
-
Document how DID Resolvers can attest to the resolution results they provide w3c/did-resolution#160.
-
Explain that the HTTP(S) binding can also be used locally w3c/did-resolution#111.
-
-
30 issues received 65 new comments.
-
Fill out the Security and Privacy self review questionnaire w3c/did-resolution#191 (13 comments by @mccown, @msporny, @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Create syntactic sugar for `relativeRef` feature w3c/did-resolution#181 (7 comments by @dlongley, @msporny, @peacekeeper, @w3cbot)
-
Prepare for DID Resolution v1.0 TAG Review w3c/did-resolution#177 (4 comments by @w3cbot, @wip-abramson)
-
Error codes for unsupported DID features w3c/did-resolution#190 (4 comments by @peacekeeper, @w3cbot, @wip-abramson)
-
TAG Review: Add a description of the problems that end-users were facing before this proposal w3c/did-resolution#185 (4 comments by @peacekeeper, @w3cbot, @wip-abramson)
-
Define timestamp format carefully w3c/did-resolution#203 (3 comments by @aphillips, @w3cbot, @wip-abramson)
-
Tag Review: Add examples of how to use DID resolution to solve the end-users' problems w3c/did-resolution#187 (2 comments by @ottomorac, @w3cbot)
-
TAG Review: User research you did to validate the problem and/or design, if any w3c/did-resolution#189 (2 comments by @msporny, @w3cbot)
-
TAG Review: What do the end-users experience with DID resolution w3c/did-resolution#188 (2 comments by @msporny, @w3cbot)
-
TAG Review: List alternatives to DID resolution considered w3c/did-resolution#186 (2 comments by @msporny, @w3cbot)
-
Broken links in Decentralized Identifier Resolution (DID Resolution) v0.3 w3c/did-resolution#193 (1 comment by @peacekeeper)
-
Is the openAPI spec (eventually) normative or informative? w3c/did-resolution#118 (1 comment by @peacekeeper)
-
`relativeRef` should prefer UTF-8 for percent encoding w3c/did-resolution#201 (1 comment by @w3cbot)
-
Use character reference notation and Unicode names for references to specific characters w3c/did-resolution#202 (1 comment by @w3cbot)
-
w3c/did-resolution#38 (1 comment by @w3cbot)
-
Document how DID Resolvers can attest to the resolution results they provide w3c/did-resolution#160 (1 comment by @peacekeeper)
-
w3c/did-resolution#28 (1 comment by @peacekeeper)
-
How to use DID resolution metadata to propagate provenance from other Resolvers w3c/did-resolution#159 (1 comment by @peacekeeper)
-
DID Resolution: Proof of inclusion of DID document in state of Verifiable Data Registry w3c/did-resolution#102 (1 comment by @peacekeeper)
-
w3c/did-resolution#13 (1 comment by @peacekeeper)
-
w3c/did-resolution#22 (1 comment by @peacekeeper)
-
Explain that the HTTP(S) binding can also be used locally w3c/did-resolution#111 (1 comment by @peacekeeper)
-
Define how DID Methods can specify paths and their dereferencing rules w3c/did-resolution#156 (1 comment by @w3cbot)
-
-
13 pull requests opened.
-
Add warning about self attested DID document metadata w3c/did-resolution#206, by @wip-abramson.
-
Remove auto-publication of pull requests. w3c/did-resolution#205, by @msporny.
-
Security Consideration -- DID Resolver Clients should detect resolution cycles w3c/did-resolution#204, by @swcurran.
-
Add "Relationship to Other Technologies" section. w3c/did-resolution#199, by @msporny.
-
Fix/improve references to INFRA specs w3c/did-resolution#198, by @peacekeeper.
-
Fix DID document media types application/did+ld+json -> application/did w3c/did-resolution#197, by @peacekeeper.
-
Define HTTP POST binding w3c/did-resolution#196, by @peacekeeper.
-
Fix quotes in Accept header value w3c/did-resolution#195, by @peacekeeper.
-
Add usecases section for TAG w3c/did-resolution#194, by @wip-abramson.
-
Require HTTP GET binding and allow HTTP POST w3c/did-resolution#192, by @ottomorac.
-
Add direct links to did extensions w3c/did-resolution#184, by @ottomorac.
-
Add NO_CACHE_DISALLOWED error w3c/did-resolution#183, by @ottomorac.
-
Make https binding mandatory w3c/did-resolution#182, by @ottomorac.
-
-
7 pull requests merged.
-
Fix DID document media types application/did+ld+json -> application/did w3c/did-resolution#197.
-
Add direct links to did extensions w3c/did-resolution#184.
-
Fix quotes in Accept header value w3c/did-resolution#195.
-
Fix/improve references to INFRA specs w3c/did-resolution#198.
-
Update the Metadata Structure to include numbers with a caveat about representations w3c/did-resolution#180.
-
Improve "Method Architectures" section w3c/did-resolution#178.
-
Improve "Resolver Architectures" section w3c/did-resolution#179.
-
-
16 pull requests received 75 new comments.
-
Make https binding mandatory w3c/did-resolution#182 (16 comments by @iherman, @msporny, @ottomorac, @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Security Consideration -- DID Resolver Clients should detect resolution cycles w3c/did-resolution#204 (16 comments by @msporny, @swcurran, @w3cbot, @wip-abramson)
-
Add NO_CACHE_DISALLOWED error w3c/did-resolution#183 (7 comments by @ottomorac, @w3cbot, @wip-abramson)
-
Require HTTP GET binding and allow HTTP POST w3c/did-resolution#192 (4 comments by @ottomorac, @peacekeeper, @TallTed, @w3cbot)
-
Remove auto-publication of pull requests. w3c/did-resolution#205 (3 comments by @msporny, @pchampin)
-
Add warning about self attested DID document metadata w3c/did-resolution#206 (1 comment by @TallTed)
-
Fix DID document media types application/did+ld+json -> application/did w3c/did-resolution#197 (1 comment by @peacekeeper)
-
Update the Metadata Structure to include numbers with a caveat about representations w3c/did-resolution#180 (1 comment by @peacekeeper)
-
w3c/did-extensions
-
1 issue closed.
-
Requested changes in review but no re-review w3c/did-extensions#635.
-
-
1 issue received 2 new comments.
-
Requested changes in review but no re-review w3c/did-extensions#635 (2 comments by @rajiv-ishare, @wip-abramson)
-
-
1 pull request opened.
-
Add did:andorra method to DID Method Registry w3c/did-extensions#647, by @davidgbvargroup.
-
-
11 pull requests merged.
-
Update DID:BSV method, company rename and contact update. w3c/did-extensions#646.
-
Add `did:jwks` method w3c/did-extensions#645.
-
Added the registration JSON file for "webplus" DID method. w3c/did-extensions#640.
-
Create midnight.json w3c/did-extensions#627.
-
add did method wba w3c/did-extensions#607.
-
Create tr.json w3c/did-extensions#606.
-
Add did:dime method w3c/did-extensions#596.
-
Update did:iota method spec link w3c/did-extensions#637.
-
Add did:os method w3c/did-extensions#636.
-
add methods/ni.json w3c/did-extensions#633.
-
request addition of ishare DID method w3c/did-extensions#600.
-
-
6 pull requests closed.
-
sql.json w3c/did-extensions#617.
-
Add method `rad` w3c/did-extensions#631.
-
Add did:shanghai method w3c/did-extensions#613.
-
Add did:china method w3c/did-extensions#612.
-
Create velocity did method w3c/did-extensions#583.
-
Create hrdkorea.json w3c/did-extensions#554.
-
-
18 pull requests received 30 new comments.
-
Update DID:BSV method, company rename and contact update. w3c/did-extensions#646 (4 comments by @msporny, @ThomasM2b, @w3cbot)
-
Added the registration JSON file for "webplus" DID method. w3c/did-extensions#640 (3 comments by @swcurran, @vdods)
-
w3c/did-test-suite
-
1 pull request opened.
-
Implement DID v1.1 tests. w3c/did-test-suite#227, by @msporny.
-
-
3 pull requests merged.
-
add did:rm method into test suite w3c/did-test-suite#214.
-
Add Data-Alliance DID Method - dxd w3c/did-test-suite#213.
-
Implement DID v1.1 tests. w3c/did-test-suite#227.
-
-
1 pull request closed.
-
Update codeowners w3c/did-test-suite#226.
-
-
2 pull requests received 6 new comments.
w3c/did
-
2 issues opened.
-
Method specs need further scrutiny or review after re-charter w3c/did#907, by @kdenhartog.
-
Finalize JSON-LD context files for REC w3c/did#906, by @msporny.
-
-
3 issues closed.
-
@context is missing JsonWebKey and Multikey w3c/did#903.
-
3 issues received 7 new comments.
-
@context URL in the spec: https://www.w3.org/ns/did/v1.1 does not resolve w3c/did#901 (5 comments by @msporny, @pchampin)
-
Is percent encoding the fragment (#) really conformant with the URI RFC? w3c/did#898 (1 comment by @msporny)
-
-
2 pull requests merged.
-
Add missing context files for DID. w3c/did#905.
-
Fix DID fragment examples. w3c/did#904.
-
-
2 pull requests received 2 new comments.
TR publications
-
3 documents published.
-
Decentralized Identifiers (DIDs) v1.1 published as a Working Draft. History of Decentralized Identifiers (DIDs) v1.1
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published twice as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
Past meetings
-
6 meetings.
GitHub
w3c/did-resolution
-
3 issues opened.
-
Create syntactic sugar for `relativeRef` feature w3c/did-resolution#181, by @msporny.
-
Prepare for DID Resolution v1.0 TAG Review w3c/did-resolution#177, by @msporny.
-
Create NO_CACHE_DISALLOWED error w3c/did-resolution#174, by @wip-abramson.
-
-
7 issues closed.
-
Should spec conformance statements be understandable as sentences out of context? w3c/did-resolution#162.
-
Minimizing the extent of profiling of requestors w3c/did-resolution#95.
-
Update future work section w3c/did-resolution#134.
-
Discover DIDs from other identifiers w3c/did-resolution#8.
-
Use SVG images instead of PNG w3c/did-resolution#128.
-
-
20 issues received 49 new comments.
-
Support numbers in metadata structures w3c/did-resolution#166 (12 comments by @msporny, @peacekeeper, @swcurran, @TallTed, @w3cbot)
-
Create syntactic sugar for `relativeRef` feature w3c/did-resolution#181 (8 comments by @dlongley, @msporny, @wip-abramson)
-
need some language about implementing https within private IP range w3c/did-resolution#173 (2 comments by @TallTed, @w3cbot)
-
Define how DID Methods can specify paths and their dereferencing rules w3c/did-resolution#156 (2 comments by @msporny, @w3cbot)
-
DID Document Metadata `created` property w3c/did-resolution#163 (2 comments by @peacekeeper, @wip-abramson)
-
Should spec conformance statements be understandable as sentences out of context? w3c/did-resolution#162 (2 comments by @peacekeeper, @wip-abramson)
-
Add DID Resolution architecture security and privacy considerations w3c/did-resolution#133 (1 comment by @w3cbot)
-
Add examples to illustrate different DID Resolution Architectures w3c/did-resolution#131 (1 comment by @w3cbot)
-
Update references to DID Specification Registries throughout w3c/did-resolution#148 (1 comment by @w3cbot)
-
How to use DID resolution metadata to propagate provenance from other Resolvers w3c/did-resolution#159 (1 comment by @peacekeeper)
-
Explain that the HTTP(S) binding can also be used locally w3c/did-resolution#111 (1 comment by @wip-abramson)
-
w3c/did-resolution#22 (1 comment by @wip-abramson)
-
Proposal: Define DDO as "DID Descriptor Object" that can bootstrap into EDO "Entity Descriptor Object" w3c/did-resolution#45 (1 comment by @peacekeeper)
-
-
5 pull requests opened.
-
Update the Metadata Structure to include numbers with a caveat about representations w3c/did-resolution#180, by @swcurran.
-
Improve "Resolver Architectures" section w3c/did-resolution#179, by @peacekeeper.
-
Improve "Method Architectures" section w3c/did-resolution#178, by @peacekeeper.
-
Reference RFC9110 which obsoletes RFC7231. w3c/did-resolution#176, by @peacekeeper.
-
Add more details to OpenAPI definition w3c/did-resolution#175, by @peacekeeper.
-
-
5 pull requests merged.
-
Reference RFC9110 which obsoletes RFC7231. w3c/did-resolution#176.
-
Add more details to OpenAPI definition w3c/did-resolution#175.
-
Consolidate and align sections about metadata. w3c/did-resolution#164.
-
Add OpenAPI definition as an informative resource. w3c/did-resolution#165.
-
8 pull requests received 72 new comments.
-
Improve "Method Architectures" section w3c/did-resolution#178 (26 comments by @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Update the Metadata Structure to include numbers with a caveat about representations w3c/did-resolution#180 (24 comments by @iherman, @msporny, @swcurran, @TallTed, @w3cbot, @wip-abramson)
-
Improve "Resolver Architectures" section w3c/did-resolution#179 (13 comments by @peacekeeper, @TallTed, @wip-abramson)
-
add security consideration about how noCache can lead to DDOS so clients should expect that servers may deny cache bypass w3c/did-resolution#171 (3 comments by @peacekeeper, @w3cbot, @wip-abramson)
-
Reference RFC9110 which obsoletes RFC7231. w3c/did-resolution#176 (2 comments by @peacekeeper, @w3cbot)
-
Add OpenAPI definition as an informative resource. w3c/did-resolution#165 (1 comment by @peacekeeper)
-
w3c/did
-
2 issues opened.
-
@context is missing JsonWebKey and Multikey w3c/did#903, by @peacekeeper.
-
-
1 issue closed.
-
Ambiguity regarding PATH and DID URLs w3c/did#821.
-
-
5 issues received 12 new comments.
-
Is percent encoding the fragment (#) really conformant with the URI RFC? w3c/did#898 (4 comments by @msporny, @w3cbot)
-
@context URL in the spec: https://www.w3.org/ns/did/v1.1 does not resolve w3c/did#901 (2 comments by @msporny, @w3cbot)
-
Language clarification "A DID document is a representation of information describing a DID subject." w3c/did#912 (2 comments by @peacekeeper, @TallTed)
-
-
3 pull requests opened.
-
Add missing context files for DID. w3c/did#905, by @msporny.
-
Fix DID fragment examples. w3c/did#904, by @msporny.
-
Reference RFC9110 which obsoletes RFC7230 and RFC7231. w3c/did#902, by @peacekeeper.
-
-
1 pull request merged.
-
1 pull request received 2 new comments.
w3c/did-extensions
-
3 issues received 5 new comments.
-
Proposed DID parameter: returnDeactivatedDidDocument (Discuss how to treat deactivated DIDs) w3c/did-extensions#622 (3 comments by @peacekeeper, @swcurran)
-
Define DID document metadata property for providing proofs of correctness w3c/did-extensions#632 (1 comment by @peacekeeper)
-
-
2 pull requests opened.
-
Update DID:BSV method, company rename and contact update. w3c/did-extensions#646, by @thebrickman.
-
Add `did:jwks` method w3c/did-extensions#645, by @venables.
-
-
1 pull request received 1 new comment.
-
Added the registration JSON file for "webplus" DID method. w3c/did-extensions#640 (1 comment by @w3cbot)
-
TR publications
-
5 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published 3 times as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
Decentralized Identifiers (DIDs) v1.1 published twice as a Working Draft. History of Decentralized Identifiers (DIDs) v1.1
-
Past meetings
-
7 meetings.
Participants
-
4 participants joined.
-
Junlin He (Ant Group Co., Ltd.) joined.
-
Jim Peng (Ant Group Co., Ltd.) joined.
-
Mitsuhide Matsuda (Frourio, Inc.) joined.
-
Michiko Kuriyama (Originator Profile CIP) joined.
-
-
1 participant left.
-
Sebastian Elfors (IDnow GmbH) left.
-
-
4 organizations joined.
-
Holopin joined.
-
Ant Group Co., Ltd. joined.
-
Frourio, Inc. joined.
-
Originator Profile CIP joined.
-
-
1 organization left.
-
IDnow GmbH left.
-
GitHub
w3c/did-resolution
-
2 issues opened.
-
need some language about implementing https within private IP range w3c/did-resolution#173, by @TallTed.
-
Support numbers in metadata structures w3c/did-resolution#166, by @peacekeeper.
-
-
6 issues closed.
-
Handling DID resolution after a distributed system fork w3c/did-resolution#43.
-
Disallow JSON-LD remote context retrieval w3c/did-resolution#53.
-
Is it graph merge or graph equivalence? w3c/did-resolution#115.
-
Should we use JSON or JSON-LD for the resolution spec? w3c/did-resolution#137.
-
[Introduction] Clarify the role of the DID Resolution spec relative to other DID specs w3c/did-resolution#18.
-
Is DID Resolution a layer defined on top of the DID layers? w3c/did-resolution#17.
-
-
2 issues reopened.
-
DID Document Metadata `created` property w3c/did-resolution#163, by @wip-abramson.
-
27 issues received 57 new comments.
-
HTTP POST method binding w3c/did-resolution#161 (14 comments by @mccown, @peacekeeper, @sloops77, @TallTed, @w3cbot, @wip-abramson)
-
DID Document Metadata `created` property w3c/did-resolution#163 (5 comments by @peacekeeper, @w3cbot, @wip-abramson)
-
Add Security Consideration about turning caching off w3c/did-resolution#149 (5 comments by @gobengo, @msporny, @w3cbot)
-
Add DID Resolution architecture security and privacy considerations w3c/did-resolution#133 (2 comments by @w3cbot)
-
Proposal: Define DDO as "DID Descriptor Object" that can bootstrap into EDO "Entity Descriptor Object" w3c/did-resolution#45 (2 comments by @peacekeeper, @w3cbot)
-
Is the openAPI spec (eventually) normative or informative? w3c/did-resolution#118 (2 comments by @peacekeeper, @w3cbot)
-
w3c/did-resolution#22 (1 comment by @w3cbot)
-
Scope of sub-topics: trust in did resolution / authentication / encryption / selective disclosure w3c/did-resolution#79 (1 comment by @w3cbot)
-
Complete threat modelling analysis for different DID Resolution architectures w3c/did-resolution#132 (1 comment by @w3cbot)
-
Should spec conformance statements be understandable as sentences out of context? w3c/did-resolution#162 (1 comment by @gobengo)
-
w3c/did-resolution#8 (1 comment by @peacekeeper)
-
Add examples to illustrate different DID Resolution Architectures w3c/did-resolution#131 (1 comment by @w3cbot)
-
Should we use JSON or JSON-LD for the resolution spec? w3c/did-resolution#137 (1 comment by @peacekeeper)
-
w3c/did-resolution#43 (1 comment by @wip-abramson)
-
-
7 pull requests opened.
-
Remove "Future Work" section w3c/did-resolution#170, by @peacekeeper.
-
Remove a few issue markers w3c/did-resolution#169, by @peacekeeper.
-
Write examples as text instead of PNG images. w3c/did-resolution#168, by @peacekeeper.
-
Clarify that the HTTP(S) binding can also be local. w3c/did-resolution#167, by @peacekeeper.
-
Add OpenAPI definition as an informative resource. w3c/did-resolution#165, by @peacekeeper.
-
Consolidate and align sections about metadata. w3c/did-resolution#164, by @peacekeeper.
-
7 pull requests merged.
-
Clarify that the HTTP(S) binding can also be local. w3c/did-resolution#167.
-
Add privacy consideration on profiling of requestors w3c/did-resolution#157.
-
Write examples as text instead of PNG images. w3c/did-resolution#168.
-
Remove "Future Work" section w3c/did-resolution#170.
-
Remove a few issue markers w3c/did-resolution#169.
-
Remove language about "graph merge" for equivalentId and canonicalId. w3c/did-resolution#158.
-
Define resolution results as JSON, not JSON-LD. w3c/did-resolution#152.
-
-
10 pull requests received 42 new comments.
-
Consolidate and align sections about metadata. w3c/did-resolution#164 (13 comments by @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Clarify that the HTTP(S) binding can also be local. w3c/did-resolution#167 (7 comments by @peacekeeper, @TallTed, @w3cbot)
-
add security consideration about how noCache can lead to DDOS so clients should expect that servers may deny cache bypass w3c/did-resolution#171 (6 comments by @gobengo, @msporny, @w3cbot, @wip-abramson)
-
Add OpenAPI definition as an informative resource. w3c/did-resolution#165 (4 comments by @peacekeeper, @TallTed, @w3cbot)
-
Add privacy consideration on profiling of requestors w3c/did-resolution#157 (3 comments by @mccown, @peacekeeper, @w3cbot)
-
Remove "Future Work" section w3c/did-resolution#170 (3 comments by @ChristopherA, @peacekeeper, @w3cbot)
-
Write examples as text instead of PNG images. w3c/did-resolution#168 (2 comments by @peacekeeper, @w3cbot)
-
Remove language about "graph merge" for equivalentId and canonicalId. w3c/did-resolution#158 (1 comment by @peacekeeper)
-
w3c/did-extensions
-
1 issue opened.
-
Add extension limitations property w3c/did-extensions#644, by @jandrieu.
-
-
1 issue received 1 new comment.
-
Proposed DID parameter: returnDeactivatedDidDocument (Discuss how to treat deactivated DIDs) w3c/did-extensions#622 (1 comment by @ottomorac)
-
-
5 pull requests opened.
-
Add mana DID method definition w3c/did-extensions#643, by @dx-manacore.
-
Add new DID Method: `mana` w3c/did-extensions#642, by @dx-manacore.
-
Add mana DID method (DX-MANA CORE) w3c/did-extensions#641, by @dx-manacore.
-
Added the registration JSON file for "webplus" DID method. w3c/did-extensions#640, by @vdods.
-
Create amt.json w3c/did-extensions#639, by @solufa.
-
-
3 pull requests closed.
-
Add mana DID method definition w3c/did-extensions#643.
-
Add mana DID method (DX-MANA CORE) w3c/did-extensions#641.
-
Add new DID Method: `mana` w3c/did-extensions#642.
-
-
4 pull requests received 9 new comments.
-
Added the registration JSON file for "webplus" DID method. w3c/did-extensions#640 (3 comments by @vdods)
w3c/did
-
3 issues closed.
-
Relative DID URLs w3c/did#880.
-
Question about query parameter ordering w3c/did#865.
-
-
5 issues received 8 new comments.
-
Is percent encoding the fragment (#) really conformant with the URI RFC? w3c/did#898 (4 comments by @dlongley, @peacekeeper)
-
Verification method controller property when working with intermediate DID document representations w3c/did#866 (1 comment by @msporny)
-
-
1 pull request opened.
-
Add comment about intermediate DID documents w3c/did#900, by @peacekeeper.
-
-
4 pull requests merged.
-
Add comment about intermediate DID documents w3c/did#900.
-
-
4 pull requests received 8 new comments.
-
Clarify that temporary `id` values might be used during operations. w3c/did#894 (5 comments by @msporny, @peacekeeper, @wip-abramson)
-
Clarify that relative URLs are allowed for verification method identifiers. w3c/did#893 (1 comment by @msporny)
-
Add warning about comparing DID URLs containing query parameters. w3c/did#895 (1 comment by @msporny)
-
TR publications
-
2 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published twice as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
Past meetings
Participants
-
1 participant joined.
-
Benjamin Goering (W3C Invited Experts) joined.
-
GitHub
w3c/did-test-suite
-
2 pull requests opened.
-
Update codeowners w3c/did-test-suite#226, by @OR13.
-
Add DID WebVH implementation w3c/did-test-suite#225, by @PatStLouis.
-
-
1 pull request merged.
-
Add DID WebVH implementation w3c/did-test-suite#225.
-
w3c/did
-
2 issues opened.
-
DID Core 1.0 Metadata Structure values data types w3c/did#899, by @PatStLouis.
-
-
1 issue closed.
-
DID Core 1.0 Metadata Structure values data types w3c/did#899.
-
-
6 issues received 11 new comments.
-
Is percent encoding the fragment (#) really conformant with the URI RFC? w3c/did#898 (1 comment by @w3cbot)
-
Language clarification "A DID document is a representation of information describing a DID subject." w3c/did#912 (1 comment by @w3cbot)
-
3 pull requests received 7 new comments.
-
Add warning about comparing DID URLs containing query parameters. w3c/did#895 (3 comments by @dlongley, @TallTed, @w3cbot)
-
Clarify that temporary `id` values might be used during operations. w3c/did#894 (2 comments by @dlongley, @wip-abramson)
-
Clarify that relative URLs are allowed for verification method identifiers. w3c/did#893 (2 comments by @TallTed, @wip-abramson)
-
w3c/did-resolution
-
6 issues opened.
-
DID Document Metadata `created` property w3c/did-resolution#163, by @wip-abramson.
-
Should spec conformance statements be understandable as sentences out of context? w3c/did-resolution#162, by @wip-abramson.
-
HTTP POST method binding w3c/did-resolution#161, by @sloops77.
-
Document how DID Resolvers can attest to the resolution results they provide w3c/did-resolution#160, by @wip-abramson.
-
How to use DID resolution metadata to propagate provenance from other Resolvers w3c/did-resolution#159, by @wip-abramson.
-
Unaddressed denial of service vector w3c/did-resolution#172, by @vdods.
-
-
3 issues closed.
-
Define invalidDidDocument error w3c/did-resolution#136.
-
Define invalidResolutionOptions error w3c/did-resolution#140.
-
Consider use of "Problem Details" in case of errors w3c/did-resolution#87.
-
-
9 issues received 19 new comments.
-
Is it graph merge or graph equivalence? w3c/did-resolution#115 (5 comments by @iherman, @peacekeeper, @TallTed, @w3cbot)
-
Should the HTTPS binding be mandatory? w3c/did-resolution#93 (3 comments by @jandrieu, @TallTed, @w3cbot)
-
Should spec conformance statements be understandable as sentences out of context? w3c/did-resolution#162 (1 comment by @wip-abramson)
-
Document how DID Resolvers can attest to the resolution results they provide w3c/did-resolution#160 (1 comment by @wip-abramson)
-
w3c/did-resolution#18 (1 comment by @peacekeeper)
-
w3c/did-resolution#17 (1 comment by @peacekeeper)
-
w3c/did-resolution#28 (1 comment by @ottomorac)
-
-
2 pull requests opened.
-
Remove language about "graph merge" for equivalentId and canonicalId. w3c/did-resolution#158, by @peacekeeper.
-
Add privacy consideration on profiling of requestors w3c/did-resolution#157, by @wip-abramson.
-
-
3 pull requests merged.
-
Issue #17 - Relationship between DID Resolution spec and DID Core w3c/did-resolution#151.
-
Add security consideration about JSON-LD Context Integrity w3c/did-resolution#147.
-
Add VDR forks Security consideration w3c/did-resolution#155.
-
-
5 pull requests received 15 new comments.
-
Add VDR forks Security consideration w3c/did-resolution#155 (5 comments by @ottomorac, @peacekeeper, @TallTed, @wip-abramson)
-
Add security consideration about JSON-LD Context Integrity w3c/did-resolution#147 (3 comments by @peacekeeper, @TallTed)
-
Define resolution results as JSON, not JSON-LD. w3c/did-resolution#152 (3 comments by @peacekeeper, @TallTed)
-
Issue #17 - Relationship between DID Resolution spec and DID Core w3c/did-resolution#151 (2 comments by @peacekeeper)
-
Add privacy consideration on profiling of requestors w3c/did-resolution#157 (2 comments by @TallTed, @w3cbot)
-
w3c/did-extensions
-
1 issue opened.
-
Requested changes in review but no re-review w3c/did-extensions#635, by @rajiv-ishare.
-
-
3 pull requests opened.
-
Add XRPL DID Method and Schema Enhancements w3c/did-extensions#638, by @popoashley.
-
Update did:iota method spec link w3c/did-extensions#637, by @eike-hass.
-
Add did:os method w3c/did-extensions#636, by @dnpotter.
-
-
1 pull request closed.
-
Add XRPL DID Method and Schema Enhancements w3c/did-extensions#638.
-
-
4 pull requests received 10 new comments.
TR publications
-
3 documents published.
-
Decentralized Identifiers (DIDs) v1.1 published as a Working Draft. History of Decentralized Identifiers (DIDs) v1.1
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published twice as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
Past meetings
GitHub
w3c/did
-
1 issue opened.
-
Privacy and Security Self-Review for DIDs w3c/did#891, by @msporny.
-
-
5 issues closed.
-
DID needs a proper vocabulary specification w3c/did#884.
-
[Question] What type is a DID w3c/did#889.
-
Service Endpoint Media Types/Behavior/Security w3c/did#849.
-
How to Understand the DID Identification w3c/did#844.
-
-
11 issues received 29 new comments.
-
Relative DID URLs w3c/did#880 (9 comments by @FabioPinheiro, @msporny, @peacekeeper, @w3cbot, @wip-abramson)
-
DID needs a proper vocabulary specification w3c/did#884 (7 comments by @iherman, @msporny, @ottomorac, @w3cbot, @wip-abramson)
-
Request for Guidance on Normalization Rules Enforcement w3c/did#842 (2 comments by @ankurdotb, @w3cbot)
-
Allow verification method identifiers in DID Documents to be HTTPS URLs? w3c/did#879 (2 comments by @msporny, @wip-abramson)
-
Verification method controller property when working with intermediate DID document representations w3c/did#866 (1 comment by @msporny)
-
-
4 pull requests opened.
-
Added the necessary files for vocabulary deployment w3c/did#892, by @iherman.
-
1 pull request merged.
-
Added the necessary files for vocabulary deployment w3c/did#892.
-
-
1 pull request received 1 new comment.
w3c/did-extensions
-
2 pull requests opened.
-
add methods/ni.json w3c/did-extensions#633, by @gobengo.
-
Add method `rad` w3c/did-extensions#631, by @lorenzleutgeb.
-
-
1 pull request received 1 new comment.
w3c/did-resolution
-
5 issues opened.
-
Define how DID Methods can specify paths and their dereferencing rules w3c/did-resolution#156, by @wip-abramson.
-
Address incompatible entries in extensions registry w3c/did-resolution#150, by @jandrieu.
-
Add Security Consideration about turning caching off w3c/did-resolution#149, by @msporny.
-
Update references to DID Specification Registries throughout w3c/did-resolution#148, by @wip-abramson.
-
-
4 issues closed.
-
Separate "Security and Privacy Considerations" w3c/did-resolution#91.
-
https://w3c.github.io/did-resolution/contexts/did-resolution-v1.json may not be correct w3c/did-resolution#117.
-
Summary of actions on a number of enhancements w3c/did-resolution#121.
-
More advanced DID URL dereferencing for verificationMethods? w3c/did-resolution#90.
-
-
14 issues received 38 new comments.
-
Address incompatible entries in extensions registry w3c/did-resolution#150 (7 comments by @ig-shaun, @jandrieu, @peacekeeper, @wip-abramson)
-
Should we use JSON or JSON-LD for the resolution spec? w3c/did-resolution#137 (4 comments by @iherman, @pchampin, @TallTed, @w3cbot)
-
DID Resolution: Proof of inclusion of DID document in state of Verifiable Data Registry w3c/did-resolution#102 (2 comments by @w3cbot, @wip-abramson)
-
Consider use of "Problem Details" in case of errors w3c/did-resolution#87 (1 comment by @peacekeeper)
-
w3c/did-resolution#17 (1 comment by @w3cbot)
-
w3c/did-resolution#22 (1 comment by @w3cbot)
-
5 pull requests opened.
-
Add VDR forks Security consideration w3c/did-resolution#155, by @ottomorac.
-
Sync from Main w3c/did-resolution#154, by @ottomorac.
-
Define resolution results as JSON, not JSON-LD. w3c/did-resolution#152, by @peacekeeper.
-
Issue #17 - Relationship between DID Resolution spec and DID Core w3c/did-resolution#151, by @mccown.
-
Add security consideration about JSON-LD Context Integrity w3c/did-resolution#147, by @ottomorac.
-
-
4 pull requests merged.
-
Migrate errors to use problem details w3c/did-resolution#146.
-
Sync from Main w3c/did-resolution#154.
-
Update examples and diagrams in section 7. w3c/did-resolution#143.
-
Update examples and diagrams in section 5. w3c/did-resolution#142.
-
-
7 pull requests received 55 new comments.
-
Add security consideration about JSON-LD Context Integrity w3c/did-resolution#147 (16 comments by @danpape, @dlongley, @msporny, @ottomorac, @peacekeeper, @w3cbot, @wip-abramson)
-
Migrate errors to use problem details w3c/did-resolution#146 (15 comments by @msporny, @peacekeeper, @w3cbot, @wip-abramson)
-
Add VDR forks Security consideration w3c/did-resolution#155 (9 comments by @ottomorac, @peacekeeper, @w3cbot, @wip-abramson)
-
Update examples and diagrams in section 7. w3c/did-resolution#143 (7 comments by @peacekeeper, @w3cbot, @wip-abramson)
-
Issue #17 - Relationship between DID Resolution spec and DID Core w3c/did-resolution#151 (4 comments by @ottomorac, @peacekeeper, @wip-abramson)
-
Define resolution results as JSON, not JSON-LD. w3c/did-resolution#152 (2 comments by @ottomorac, @peacekeeper)
-
Update examples and diagrams in section 5. w3c/did-resolution#142 (2 comments by @peacekeeper, @w3cbot)
-
TR publications
-
5 documents published.
-
Decentralized Identifiers (DIDs) v1.1 published as a Working Draft. History of Decentralized Identifiers (DIDs) v1.1
-
DID Methods published 3 times as a Note. History of DID Methods
Past meetings
Participants
-
1 participant left.
-
Rod Waltermann (Lenovo) left.
-
-
1 organization joined.
-
Oracle Corporation joined.
-
-
2 organizations left.
-
Oracle Corporation left.
-
Lenovo left.
-
GitHub
w3c/did-extensions
-
2 issues received 4 new comments.
-
Proposed DID document metadata property: network w3c/did-extensions#628 (2 comments by @melvincarvalho, @peacekeeper)
-
3 pull requests merged.
-
Add did:cn Method w3c/did-extensions#623.
-
Add did:cndid method w3c/did-extensions#629.
-
Add did:nostr method. w3c/did-extensions#630.
-
-
4 pull requests received 5 new comments.
w3c/did-resolution
-
3 issues opened.
-
Horizontal Review: Accessibility self test w3c/did-resolution#145, by @wip-abramson.
-
Horizontal Review: Internationalization self test w3c/did-resolution#144, by @wip-abramson.
-
Define invalidResolutionOptions error w3c/did-resolution#140, by @wip-abramson.
-
-
5 issues closed.
-
Can we simplify the API to remove resolveRespresentation? w3c/did-resolution#114.
-
Service Endpoint Construction inconsistency w3c/did-resolution#61.
-
DID Parameters: Service - only fragment or complete id? w3c/did-resolution#130.
-
Request service by type w3c/did-resolution#85.
-
-
16 issues received 34 new comments.
-
Should we use JSON or JSON-LD for the resolution spec? w3c/did-resolution#137 (9 comments by @iherman, @msporny, @pchampin, @peacekeeper, @w3cbot)
-
Define invalidResolutionOptions error w3c/did-resolution#140 (4 comments by @peacekeeper, @wip-abramson)
-
Consider use of "Problem Details" in case of errors w3c/did-resolution#87 (3 comments by @peacekeeper, @w3cbot, @wip-abramson)
-
Explain that the HTTP(S) binding can also be used locally w3c/did-resolution#111 (3 comments by @ottomorac, @pchampin, @TallTed)
-
Add DID Resolution architecture security and privacy considerations w3c/did-resolution#133 (1 comment by @w3cbot)
-
Complete threat modelling analysis for different DID Resolution architectures w3c/did-resolution#132 (1 comment by @w3cbot)
-
Add examples to illustrate different DID Resolution Architectures w3c/did-resolution#131 (1 comment by @w3cbot)
-
Scope of sub-topics: trust in did resolution / authentication / encryption / selective disclosure w3c/did-resolution#79 (1 comment by @w3cbot)
-
Horizontal Review: Internationalization self test w3c/did-resolution#144 (1 comment by @wip-abramson)
-
More advanced DID URL dereferencing for verificationMethods? w3c/did-resolution#90 (1 comment by @peacekeeper)
-
https://w3c.github.io/did-resolution/contexts/did-resolution-v1.json may not be correct w3c/did-resolution#117 (1 comment by @peacekeeper)
-
-
4 pull requests opened.
-
Migrate errors to use problem details w3c/did-resolution#146, by @wip-abramson.
-
Update examples and diagrams in section 7. w3c/did-resolution#143, by @peacekeeper.
-
Update examples and diagrams in section 5. w3c/did-resolution#142, by @peacekeeper.
-
Update examples and diagrams in section 5. w3c/did-resolution#141, by @peacekeeper.
-
-
3 pull requests merged.
-
Separate security and privacy considerations sections w3c/did-resolution#138.
-
Define verificationRelationship as a dereferencing option w3c/did-resolution#122.
-
Fix definition of "didDocument" in JSON-LD context w3c/did-resolution#135.
-
-
1 pull request closed.
-
Update examples and diagrams in section 5. w3c/did-resolution#141.
-
-
5 pull requests received 10 new comments.
-
Separate security and privacy considerations sections w3c/did-resolution#138 (3 comments by @peacekeeper)
-
Define verificationRelationship as a dereferencing option w3c/did-resolution#122 (3 comments by @peacekeeper, @wip-abramson)
-
Update examples and diagrams in section 5. w3c/did-resolution#142 (2 comments by @peacekeeper, @wip-abramson)
-
Fix definition of "didDocument" in JSON-LD context w3c/did-resolution#135 (1 comment by @peacekeeper)
-
w3c/did
-
1 issue opened.
-
[Question] What type is a DID w3c/did#889, by @melvincarvalho.
-
-
8 issues closed.
-
Simplify abstract data model to be more concrete w3c/did#855.
-
broken links in the specification w3c/did#853.
-
Broken links w3c/did#832.
-
How to apply new DID Method Specification? w3c/did#827.
-
DID Spec PDF? w3c/did#828.
-
When should did parameters be dropped? w3c/did#337.
-
-
14 issues received 27 new comments.
-
Request for Guidance on Normalization Rules Enforcement w3c/did#842 (5 comments by @KDean-Dolphin, @msporny, @w3cbot, @wip-abramson)
-
Service Endpoint Media Types/Behavior/Security w3c/did#849 (4 comments by @ottomorac, @pchampin, @sondreb, @TallTed)
-
Allow verification method identifiers in DID Documents to be HTTPS URLs? w3c/did#879 (2 comments by @franca6, @w3cbot)
-
Should we restrict the value of `id` when used to identify a subject? w3c/did#217 (2 comments by @melvincarvalho, @msporny)
-
Add short semantic descriptions to improve readability of the spec w3c/did#805 (1 comment by @msporny)
-
-
2 pull requests opened.
-
Add missing diagram source files. w3c/did#890, by @peacekeeper.
-
re-enable Echidna w3c/did#888, by @pchampin.
-
-
4 pull requests merged.
-
Add missing diagram source files. w3c/did#890.
-
re-enable Echidna w3c/did#888.
-
-
4 pull requests received 22 new comments.
-
Simplify abstract data model and specify one concrete representation w3c/did#887 (15 comments by @iherman, @jandrieu, @msporny, @pchampin, @peacekeeper, @TallTed, @w3cbot)
-
Clarify restrictions on identifiers used in DID documents. w3c/did#886 (2 comments by @msporny, @pchampin)
-
TR publications
-
3 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published 3 times as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
Past meetings
Participants
-
1 chair appointed.
-
Otto Mora became a chair.
-
-
1 chair stepped down.
-
Daniel Burnett stepped down as a chair.
-
GitHub
w3c/did
-
2 issues opened.
-
Horizontal Review for DID v1.1 w3c/did#885, by @msporny.
-
DID needs a proper vocabulary specification w3c/did#884, by @iherman.
-
-
3 issues closed.
-
Clean up herd privacy issues w3c/did#539.
-
Confusion regarding threshold for DID controllers w3c/did#839.
-
-
10 issues received 21 new comments.
-
Allow verification method identifiers in DID Documents to be HTTPS URLs? w3c/did#879 (1 comment by @franca6)
-
4 pull requests opened.
-
Clarify restrictions on identifiers used in DID documents. w3c/did#886, by @msporny.
-
Add text clarifying where group controllers might be listed. w3c/did#883, by @msporny.
-
Add link to fragment resolution algorithm. w3c/did#882, by @msporny.
-
2 pull requests merged.
-
Add link to fragment resolution algorithm. w3c/did#882.
-
1 pull request closed.
-
5 pull requests received 32 new comments.
-
Clarify restrictions on identifiers used in DID documents. w3c/did#886 (11 comments by @deniak, @iherman, @msporny, @TallTed)
-
Simplify abstract data model and specify one concrete representation w3c/did#887 (9 comments by @iherman, @msporny, @TallTed)
-
Add text clarifying where group controllers might be listed. w3c/did#883 (8 comments by @msporny, @TallTed, @w3cbot, @wip-abramson)
-
w3c/did-resolution
-
7 issues opened.
-
Horizontal Review for DID Resolution v1.0 w3c/did-resolution#139, by @peacekeeper.
-
Should we use JSON or JSON-LD for the resolution spec? w3c/did-resolution#137, by @iherman.
-
Define invalidDidDocument error w3c/did-resolution#136, by @peacekeeper.
-
Update future work section w3c/did-resolution#134, by @wip-abramson.
-
Add DID Resolution architecture security and privacy considerations w3c/did-resolution#133, by @wip-abramson.
-
Complete threat modelling analysis for different DID Resolution architectures w3c/did-resolution#132, by @wip-abramson.
-
Add examples to illustrate different DID Resolution Architectures w3c/did-resolution#131, by @wip-abramson.
-
-
11 issues closed.
-
Should the network be returned in the resolutionResults object? w3c/did-resolution#52.
-
DID URL dereferencing algorithm should pass options through to DID resolution w3c/did-resolution#127.
-
Discuss how to treat deactivated DIDs w3c/did-resolution#5.
-
Expand referenced keys to inline keys w3c/did-resolution#39.
-
Expand relative URLs to absolute URLs in "id" fields w3c/did-resolution#40.
-
`versionId`/`versionTime` are not defined for DID resolution w3c/did-resolution#66.
-
Use made-up example URLs for resolver endpoints w3c/did-resolution#109.
-
Add support for JWKS w3c/did-resolution#46.
-
Design versioning features w3c/did-resolution#12.
-
Support DIDs as serviceEndpoint? w3c/did-resolution#7.
-
DID method governance w3c/did-resolution#6.
-
-
23 issues received 38 new comments.
-
Consider use of "Problem Details" in case of errors w3c/did-resolution#87 (5 comments by @peacekeeper, @wip-abramson)
-
Scope of sub-topics: trust in did resolution / authentication / encryption / selective disclosure w3c/did-resolution#79 (4 comments by @ChristopherA, @w3cbot, @wip-abramson)
-
DID Parameters: Service - only fragment or complete id? w3c/did-resolution#130 (3 comments by @peacekeeper, @wip-abramson)
-
Should we use JSON or JSON-LD for the resolution spec? w3c/did-resolution#137 (3 comments by @iherman, @peacekeeper)
-
DID `service` parameter does not account for cases where `id` of `service` is a full IRI external to the DID document w3c/did-resolution#97 (2 comments by @peacekeeper)
-
Should the network be returned in the resolutionResults object? w3c/did-resolution#52 (2 comments by @peacekeeper)
-
DID URL dereferencing algorithm should pass options through to DID resolution w3c/did-resolution#127 (2 comments by @peacekeeper)
-
w3c/did-resolution#38 (2 comments by @wip-abramson)
-
Can we simplify the API to remove resolveRespresentation? w3c/did-resolution#114 (1 comment by @wip-abramson)
-
w3c/did-resolution#5 (1 comment by @peacekeeper)
-
w3c/did-resolution#39 (1 comment by @peacekeeper)
-
w3c/did-resolution#40 (1 comment by @peacekeeper)
-
`versionId`/`versionTime` are not defined for DID resolution w3c/did-resolution#66 (1 comment by @peacekeeper)
-
w3c/did-resolution#12 (1 comment by @peacekeeper)
-
w3c/did-resolution#7 (1 comment by @peacekeeper)
-
w3c/did-resolution#6 (1 comment by @peacekeeper)
-
w3c/did-resolution#28 (1 comment by @ChristopherA)
-
Proposal: Define DDO as "DID Descriptor Object" that can bootstrap into EDO "Entity Descriptor Object" w3c/did-resolution#45 (1 comment by @wip-abramson)
-
-
2 pull requests opened.
-
Separate security and privacy considerations sections w3c/did-resolution#138, by @wip-abramson.
-
Fix definition of "didDocument" in JSON-LD context w3c/did-resolution#135, by @peacekeeper.
-
-
4 pull requests merged.
-
Add serviceType parameter, and update service construction algorithm. w3c/did-resolution#125.
-
Remove resolveRepresentation() function w3c/did-resolution#123.
-
Add expandRelativeUrls DID resolution option w3c/did-resolution#126.
-
Pass all dereferencing options to resolution algorithm. w3c/did-resolution#129.
-
-
5 pull requests received 24 new comments.
-
Add serviceType parameter, and update service construction algorithm. w3c/did-resolution#125 (11 comments by @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Define verificationRelationship as a dereferencing option w3c/did-resolution#122 (7 comments by @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Fix definition of "didDocument" in JSON-LD context w3c/did-resolution#135 (4 comments by @iherman, @peacekeeper, @w3cbot)
-
w3c/did-extensions
-
1 issue opened.
-
Proposed DID document metadata property: network w3c/did-extensions#628, by @peacekeeper.
-
-
1 issue received 1 new comment.
-
7 pull requests opened.
-
Add did:nostr method. w3c/did-extensions#630, by @melvincarvalho.
-
Add did:cndid method w3c/did-extensions#629, by @teleinfo-bif.
-
Create midnight.json w3c/did-extensions#627, by @Maetti79.
-
Create midnight.json w3c/did-extensions#626, by @Maetti79.
-
add did:dsr method w3c/did-extensions#625, by @iamstd-zch.
-
Feature zch w3c/did-extensions#624, by @iamstd-zch.
-
Add did:cn Method w3c/did-extensions#623, by @caict-develop-zhangbo.
-
-
2 pull requests closed.
-
Create midnight.json w3c/did-extensions#626.
-
Feature zch w3c/did-extensions#624.
-
-
1 pull request reopened.
-
Create midnight.json w3c/did-extensions#626, by @Maetti79.
-
-
3 pull requests received 5 new comments.
-
Add did:tdw, did:keys, did:svc, and did:proof plus DID Categories (13x) (Trusted Digital Web / Web 7.0). Remove bluetoque*.json (4x) w3c/did-extensions#603 (3 comments by @mwherman2000, @peacekeeper, @swcurran)
-
TR publications
-
7 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published 4 times as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
DID Document Property Extensions published as a Note. History of DID Document Property Extensions
-
DID Methods published as a Note. History of DID Methods
-
Decentralized Identifier Extensions published as a Note. History of Decentralized Identifier Extensions
-
Past meetings
Participants
-
1 participant joined.
-
Otto Mora (W3C Invited Experts) joined.
-
GitHub
w3c/did-resolution
-
3 issues opened.
-
Use SVG images instead of PNG w3c/did-resolution#128, by @peacekeeper.
-
DID URL dereferencing algorithm should pass options through to DID resolution w3c/did-resolution#127, by @wip-abramson.
-
Summary of actions on a number of enhancements w3c/did-resolution#121, by @peacekeeper.
-
-
4 issues closed.
-
Various issues with links to DID core w3c/did-resolution#112.
-
[Introduction] Clarify who is the Primary Target Audience for the DID Resolution spec w3c/did-resolution#19.
-
DID Resolution Result for DID URL Dereferencing w3c/did-resolution#69.
-
Percent-encode reserved characters in HTTP Binding w3c/did-resolution#50.
-
-
24 issues received 37 new comments.
-
Summary of actions on a number of enhancements w3c/did-resolution#121 (5 comments by @msporny, @peacekeeper, @w3cbot, @wip-abramson)
-
Is the openAPI spec (eventually) normative or informative? w3c/did-resolution#118 (3 comments by @iherman, @peacekeeper, @w3cbot)
-
https://w3c.github.io/did-resolution/contexts/did-resolution-v1.json may not be correct w3c/did-resolution#117 (3 comments by @iherman, @msporny)
-
Various issues with links to DID core w3c/did-resolution#112 (2 comments by @msporny, @wip-abramson)
-
Proposal: Define DDO as "DID Descriptor Object" that can bootstrap into EDO "Entity Descriptor Object" w3c/did-resolution#45 (2 comments by @w3cbot, @wip-abramson)
-
w3c/did-resolution#7 (1 comment by @peacekeeper)
-
w3c/did-resolution#39 (1 comment by @peacekeeper)
-
w3c/did-resolution#5 (1 comment by @peacekeeper)
-
w3c/did-resolution#6 (1 comment by @w3cbot)
-
w3c/did-resolution#28 (1 comment by @w3cbot)
-
w3c/did-resolution#37 (1 comment by @w3cbot)
-
`versionId`/`versionTime` are not defined for DID resolution w3c/did-resolution#66 (1 comment by @wip-abramson)
-
Can we simplify the API to remove resolveRespresentation? w3c/did-resolution#114 (1 comment by @peacekeeper)
-
More advanced DID URL dereferencing for verificationMethods? w3c/did-resolution#90 (1 comment by @wip-abramson)
-
w3c/did-resolution#40 (1 comment by @jandrieu)
-
Percent-encode reserved characters in HTTP Binding w3c/did-resolution#50 (1 comment by @peacekeeper)
-
w3c/did-resolution#19 (1 comment by @peacekeeper)
-
-
7 pull requests opened.
-
Pass all dereferencing options to resolution algorithm. w3c/did-resolution#129, by @peacekeeper.
-
Add expandRelativeUrls DID resolution option w3c/did-resolution#126, by @peacekeeper.
-
Add serviceType parameter, and update service construction algorithm. w3c/did-resolution#125, by @peacekeeper.
-
Minor editorial changes w3c/did-resolution#124, by @iherman.
-
Remove resolveRepresentation() function w3c/did-resolution#123, by @peacekeeper.
-
Define verificationRelationship as a dereferencing option w3c/did-resolution#122, by @wip-abramson.
-
Address 109 -- changing example uniresolver references to be an to an example uniresolver w3c/did-resolution#120, by @swcurran.
-
-
4 pull requests merged.
-
Add versionId and versionTime to DID resolution options w3c/did-resolution#119.
-
Minor editorial changes w3c/did-resolution#124.
-
Address 109 -- changing example uniresolver references to be an to an example uniresolver w3c/did-resolution#120.
-
add audience section to introduction w3c/did-resolution#107.
-
-
8 pull requests received 45 new comments.
-
Add serviceType parameter, and update service construction algorithm. w3c/did-resolution#125 (11 comments by @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Define verificationRelationship as a dereferencing option w3c/did-resolution#122 (9 comments by @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Add versionId and versionTime to DID resolution options w3c/did-resolution#119 (8 comments by @ankurdotb, @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Add expandRelativeUrls DID resolution option w3c/did-resolution#126 (6 comments by @peacekeeper, @w3cbot, @wip-abramson)
-
Remove resolveRepresentation() function w3c/did-resolution#123 (4 comments by @w3cbot, @wip-abramson)
-
Minor editorial changes w3c/did-resolution#124 (4 comments by @iherman, @peacekeeper, @wip-abramson)
-
Address 109 -- changing example uniresolver references to be an to an example uniresolver w3c/did-resolution#120 (2 comments by @peacekeeper, @swcurran)
-
w3c/did-extensions
-
4 issues opened.
-
Proposed DID parameter: returnDeactivatedDidDocument (Discuss how to treat deactivated DIDs) w3c/did-extensions#622, by @peacekeeper.
-
Proposed DID parameter: followServiceDid (Support DIDs as serviceEndpoint?) w3c/did-extensions#620, by @peacekeeper.
-
Proposed DID parameter: expandReferencedVerificationMethods (Expand referenced keys to inline keys) w3c/did-extensions#621, by @peacekeeper.
-
Integrate DID Traits Schema w3c/did-extensions#619, by @jceb.
-
-
19 issues closed.
-
Should registry track how to contact DID method authors? w3c/did-extensions#174.
-
DID Method Registration Resolution #2 on 2021-03-16 w3c/did-extensions#271.
-
Consider allowing multiple registrations by the same "name" in a given category w3c/did-extensions#304.
-
blockchainAccountId example to support cosmos blockchains w3c/did-extensions#347.
-
Raising the quality bar for registry changes w3c/did-extensions#348.
-
Changing requirements for new did method registry entries w3c/did-extensions#362.
-
Outdated naming for a DID public keys w3c/did-extensions#365.
-
DID specifications registration request w3c/did-extensions#396.
-
Creating a new 'service' type w3c/did-extensions#437.
-
Update CCF registry details w3c/did-extensions#492.
-
How to handle duplicates w3c/did-extensions#569.
-
Why isn't the lint workflow progressing? w3c/did-extensions#572.
-
The link to the Property and Value Extensions listing returns 404 w3c/did-extensions#575.
-
DID spec registry gives 404 error w3c/did-extensions#576.
-
Clarify the registration process wrt. trademarks and copyrights w3c/did-extensions#595.
-
README.md: link missing for the DID implementers guide at the bottom of this page w3c/did-extensions#384.
-
Something goofy happening with the URL to the Extensions parent document w3c/did-extensions#588.
-
Discussion: Circle of Competence w3c/did-extensions#599.
-
-
2 issues received 2 new comments.
-
Requesting contact information for Jsong1230, MetadiumRelease w3c/did-extensions#216 (1 comment by @wip-abramson)
-
-
3 pull requests merged.
-
updates my w3id in 3 html files w3c/did-extensions#616.
-
Add my w3cid w3c/did-extensions#614.
-
Add fox did method w3c/did-extensions#592.
-
-
2 pull requests received 5 new comments.
w3c/did
-
1 issue opened.
-
Relative DID URLs w3c/did#880, by @FabioPinheiro.
-
-
2 issues received 3 new comments.
-
Add short semantic descriptions to improve readability of the spec w3c/did#805 (2 comments by @w3cbot, @wip-abramson)
-
-
1 pull request opened.
-
Update did-core to did for github and editor draft links w3c/did#881, by @wip-abramson.
-
-
1 pull request received 1 new comment.
w3c/did-use-cases
-
1 pull request opened.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/did-use-cases#153, by @deniak.
-
w3c/did-rubric
-
1 pull request opened.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/did-rubric#75, by @deniak.
-
w3c/did-imp-guide
-
1 pull request opened.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/did-imp-guide#43, by @deniak.
-
TR publications
-
7 documents published.
-
Decentralized Identifier Resolution (DID Resolution) v0.3 published twice as a Working Draft. History of Decentralized Identifier Resolution (DID Resolution) v0.3
-
Decentralized Identifiers (DIDs) v1.1 published as a First Public Working Draft. History of Decentralized Identifiers (DIDs) v1.1
-
DID Methods published as a Note. History of DID Methods
-
Decentralized Identifier Extensions published 3 times as a Note. History of Decentralized Identifier Extensions
-
Past meetings
Participants
-
1 chair stepped down.
-
Gabe Cohen stepped down as a chair.
-
-
5 participants joined.
-
Ruoxi Ran (W3C) joined.
-
ChangYun LEE (CREATIVECODE) joined.
-
Daehyun Kim (CREATIVECODE) joined.
-
Hyeri Kim (CREATIVECODE) joined.
-
Taehyoung Shim (Electronics and Telecommunications Research Institute (ETRI)) joined.
-
-
4 participants left.
-
Ruoxi Ran (W3C) left.
-
Juan Caballero (Protocol Labs) left.
-
Benjamin Goering (W3C Invited Experts) left.
-
Sungpil Shin (Electronics and Telecommunications Research Institute (ETRI)) left.
-
-
1 organization joined.
-
CREATIVECODE joined.
-
-
1 organization left.
-
Protocol Labs left.
-
GitHub
w3c/did-resolution
-
8 issues opened.
-
Is the openAPI spec (eventually) normative or informative? w3c/did-resolution#118, by @iherman.
-
https://w3c.github.io/did-resolution/contexts/did-resolution-v1.json may not be correct w3c/did-resolution#117, by @iherman.
-
Model accept as the HTTP accept header w3c/did-resolution#116, by @iherman.
-
Is it graph merge or graph equivalence? w3c/did-resolution#115, by @iherman.
-
Can we simplify the API to remove resolveRespresentation? w3c/did-resolution#114, by @wip-abramson.
-
Various issues with links to DID core w3c/did-resolution#112, by @wip-abramson.
-
Explain that the HTTP(S) binding can also be used locally w3c/did-resolution#111, by @peacekeeper.
-
Use made-up example URLs for resolver endpoints w3c/did-resolution#109, by @peacekeeper.
-
-
3 issues closed.
-
Select top-level properties from Resolver w3c/did-resolution#59.
-
Find better terms than "primary resource" and "secondary resource" w3c/did-resolution#94.
-
DID resolution context is not accessible w3c/did-resolution#78.
-
-
26 issues received 49 new comments.
-
Can we simplify the API to remove resolveRespresentation? w3c/did-resolution#114 (3 comments by @peacekeeper, @wip-abramson)
-
Select top-level properties from Resolver w3c/did-resolution#59 (3 comments by @BernhardFuchs, @peacekeeper, @w3cbot)
-
`versionId`/`versionTime` are not defined for DID resolution w3c/did-resolution#66 (2 comments by @peacekeeper, @w3cbot)
-
Service Endpoint Construction inconsistency w3c/did-resolution#61 (2 comments by @peacekeeper, @w3cbot)
-
Find better terms than "primary resource" and "secondary resource" w3c/did-resolution#94 (2 comments by @peacekeeper, @wip-abramson)
-
DID Resolution Result for DID URL Dereferencing w3c/did-resolution#69 (2 comments by @pchampin, @wip-abramson)
-
Should the network be returned in the resolutionResults object? w3c/did-resolution#52 (2 comments by @pchampin, @wip-abramson)
-
Consider use of "Problem Details" in case of errors w3c/did-resolution#87 (2 comments by @pchampin, @peacekeeper)
-
DID Resolution: Proof of inclusion of DID document in state of Verifiable Data Registry w3c/did-resolution#102 (2 comments by @w3cbot, @wip-abramson)
-
https://w3c.github.io/did-resolution/contexts/did-resolution-v1.json may not be correct w3c/did-resolution#117 (1 comment by @peacekeeper)
-
More advanced DID URL dereferencing for verificationMethods? w3c/did-resolution#90 (1 comment by @w3cbot)
-
w3c/did-resolution#8 (1 comment by @w3cbot)
-
Scope of sub-topics: trust in did resolution / authentication / encryption / selective disclosure w3c/did-resolution#79 (1 comment by @w3cbot)
-
DID Parameters: Service - only fragment or complete id? w3c/did-resolution#130 (1 comment by @wip-abramson)
-
3 pull requests opened.
-
Add versionId and versionTime to DID resolution options w3c/did-resolution#119, by @wip-abramson.
-
Add details about HTTPS binding. w3c/did-resolution#108, by @peacekeeper.
-
add audience section to introduction w3c/did-resolution#107, by @wip-abramson.
-
-
4 pull requests merged.
-
Add details about HTTPS binding. w3c/did-resolution#108.
-
Add more details about how to dereference path and query of a DID URL. w3c/did-resolution#104.
-
Add details to results of the dereferencing algorithm. w3c/did-resolution#103.
-
Move DID Parameters section from did-core to did-resolution. w3c/did-resolution#106.
-
-
5 pull requests received 16 new comments.
-
Add details about HTTPS binding. w3c/did-resolution#108 (7 comments by @msporny, @peacekeeper, @w3cbot, @wip-abramson)
-
Move DID Parameters section from did-core to did-resolution. w3c/did-resolution#106 (3 comments by @msporny, @peacekeeper, @w3cbot)
-
Add more details about how to dereference path and query of a DID URL. w3c/did-resolution#104 (2 comments by @peacekeeper, @w3cbot)
-
Add details to results of the dereferencing algorithm. w3c/did-resolution#103 (2 comments by @peacekeeper, @w3cbot)
-
w3c/did
-
2 issues opened.
-
6 issues closed.
-
Normatively reference Controller Document w3c/did#854.
-
Introduction: who is the Intended Audience? w3c/did#870.
-
Add example for Verification Method ID as a fragment w3c/did#860.
-
9 issues received 17 new comments.
-
Language clarification "A DID document is a representation of information describing a DID subject." w3c/did#912 (4 comments by @dlongley, @jandrieu, @wip-abramson)
-
Should we be allowed to multi-reference keys through did documents? w3c/did#878 (4 comments by @ankurdotb, @msporny, @pchampin)
-
New verification material property supporting JWK sets by reference w3c/did#811 (1 comment by @msporny)
-
-
4 pull requests opened.
-
Add dependency on CID spec. w3c/did#877, by @msporny.
-
Add audience section to the spec w3c/did#876, by @wip-abramson.
-
Improve capability delegation example and explanation w3c/did#875, by @wip-abramson.
-
Add relative DID URL DID Document example w3c/did#874, by @wip-abramson.
-
-
5 pull requests merged.
-
Add dependency on CID spec. w3c/did#877.
-
Add audience section to the spec w3c/did#876.
-
Add relative DID URL DID Document example w3c/did#874.
-
-
5 pull requests received 45 new comments.
-
Add dependency on CID spec. w3c/did#877 (27 comments by @jandrieu, @msporny, @pchampin, @peacekeeper, @TallTed, @w3cbot, @wip-abramson)
-
Improve capability delegation example and explanation w3c/did#875 (8 comments by @dlongley, @msporny, @TallTed, @w3cbot, @wip-abramson)
-
Add audience section to the spec w3c/did#876 (7 comments by @danpape, @msporny, @TallTed, @w3cbot, @wip-abramson)
-
w3c/did-extensions
-
3 issues opened.
-
Update DID methods list to allow multiple registrations per resolution w3c/did-extensions#618, by @wip-abramson.
-
Define DID document metadata property for providing proofs of correctness w3c/did-extensions#632, by @wip-abramson.
-
Add new list to the DID Resolution Extensions for tracking DID URL Path parameters w3c/did-extensions#615, by @wip-abramson.
-
-
2 issues closed.
-
Why is there a difference between the editor's draft and the latest published version? w3c/did-extensions#420.
-
Reformat table definitions in DID Spec Registries w3c/did-extensions#160.
-
-
22 issues received 28 new comments.
-
Why is there a difference between the editor's draft and the latest published version? w3c/did-extensions#420 (4 comments by @msporny, @wip-abramson)
-
RSASignature2018 suite needs to be independently defined w3c/did-extensions#370 (2 comments by @kdenhartog, @wip-abramson)
-
Reformat table definitions in DID Spec Registries w3c/did-extensions#160 (2 comments by @msporny, @wip-abramson)
-
Consider allowing multiple registrations by the same "name" in a given category w3c/did-extensions#304 (1 comment by @wip-abramson)
-
Something goofy happening with the URL to the Extensions parent document w3c/did-extensions#588 (1 comment by @wip-abramson)
-
Planning of merging editor's draft with published version w3c/did-extensions#487 (1 comment by @wip-abramson)
-
README.md: link missing for the DID implementers guide at the bottom of this page w3c/did-extensions#384 (1 comment by @wip-abramson)
-
Changing requirements for new did method registry entries w3c/did-extensions#362 (1 comment by @wip-abramson)
-
Clarify the registration process wrt. trademarks and copyrights w3c/did-extensions#595 (1 comment by @wip-abramson)
-
-
3 pull requests opened.
-
sql.json w3c/did-extensions#617, by @StellarQuantaLabs.
-
updates my w3id in 3 html files w3c/did-extensions#616, by @gatemezing.
-
Add my w3cid w3c/did-extensions#614, by @MizukiSonoko.
-
-
3 pull requests merged.
-
Add did:webvh DID Method to the Registry -- did:webvh is `did:web` + Verifiable History w3c/did-extensions#581.
-
Updated the copyright, trademark, or any intellectual property rights section w3c/did-extensions#610.
-
Update outdated "official repository" language. w3c/did-extensions#593.
-
-
5 pull requests received 15 new comments.
-
Add did:webvh DID Method to the Registry -- did:webvh is `did:web` + Verifiable History w3c/did-extensions#581 (2 comments by @msporny, @swcurran)