Decentralized Identifier Working Group - Activity in 2020
No matches.
Lifecycle
-
1 charter started.
-
Chartered until 30 September 2021. Participants had to rejoin under this charter.
-
TR publications
-
8 documents published.
-
Decentralized Identifiers (DIDs) v1.0 published 3 times as a Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
Use Cases and Requirements for Decentralized Identifiers published 3 times as a Working Draft. History of Use Cases and Requirements for Decentralized Identifiers
-
DID Specification Registries published twice as a Note. History of DID Specification Registries
-
Participants
-
8 participants joined.
-
TK HO (Digital Policy Office, The Government of the Hong Kong Special Administrative Region of the People's Republic of China) joined.
-
Adrien Wartel (Indeed) joined.
-
Adam Lake (Digital Bazaar) joined.
-
Andrew Jones (Digital Bazaar) joined.
-
Mina Soliman (Jolocom GmbH) joined.
-
Joachim Lohkamp (Jolocom GmbH) joined.
-
Rouven Heck (Consensys) joined.
-
jonathan holt (TranSendX) joined.
-
-
5 participants left.
-
Haiguang Wang (Huawei) left.
-
Siyu Zhu (China Academy of Information and Communications Technology (CAICT)) left.
-
Joachim Lohkamp (Jolocom GmbH) left.
-
Rouven Heck (Consensys) left.
-
Rouven Heck (Consensys) left.
-
-
17 organizations joined.
-
Electronics and Telecommunications Research Institute (ETRI) joined.
-
OpenLink Software Inc. joined.
-
Digital Policy Office, The Government of the Hong Kong Special Administrative Region of the People's Republic of China joined.
-
Indeed joined.
-
Keio University joined.
-
China Academy of Information and Communications Technology (CAICT) joined.
-
Digital Bazaar joined.
-
Evernym joined.
-
GS1 joined.
-
Jolocom GmbH joined.
-
Microsoft Corporation joined.
-
Transmute joined.
-
Mattr Limited joined.
-
Consensys joined.
-
Google LLC joined.
-
Wiley joined.
-
Danube Tech GmbH joined.
-
-
52 organizations left.
-
Universidad Politécnica de Madrid left.
-
Intel Corporation left.
-
Rakuten Group, Inc. left.
-
Torus left.
-
ZIIOT left.
-
TranSendX left.
-
Gooroomee Inc. left.
-
Pundi X left.
-
Ripple left.
-
Spruce Systems, Inc. left.
-
Keio University left.
-
Fiserv left.
-
Huawei left.
-
Cisco left.
-
Data Society Alliance left.
-
Hedera Hashgraph left.
-
USAA left.
-
Digital Policy Office, The Government of the Hong Kong Special Administrative Region of the People's Republic of China left.
-
Google LLC left.
-
Wireline left.
-
Baidu, Inc. left.
-
LG Electronics left.
-
Thomson Reuters Corp. left.
-
Viacom inc. left.
-
J. Paul Getty Trust left.
-
Jolocom GmbH left.
-
Learning Machine, Inc. left.
-
MITRE Corporation left.
-
Onfido left.
-
Mattr Limited left.
-
Wikimedia Foundation left.
-
globaliD left.
-
China Academy of Information and Communications Technology (CAICT) left.
-
OpenLink Software Inc. left.
-
Microsoft Corporation left.
-
BrightLink left.
-
SURF bv left.
-
Sovrin Foundation left.
-
AKASHA Foundation left.
-
Universities Admissions Centre left.
-
Transmute left.
-
SecureKey left.
-
Credly left.
-
Conexxus left.
-
Digital Bazaar left.
-
The Scottish Government left.
-
GS1 left.
-
Evernym left.
-
Wiley left.
-
Consensys left.
-
Electronics and Telecommunications Research Institute (ETRI) left.
-
Danube Tech GmbH left.
-
GitHub
w3c/did
-
15 issues opened.
-
Issues in "Note on Persistence" in DID Syntax section w3c/did#504, by @shigeya.
-
`Decentralized extension` is not discussed w3c/did#502, by @shigeya.
-
Representation property or representation-specific property ? w3c/did#500, by @shigeya.
-
Datetime data type missing timezone and precision w3c/did#498, by @msporny.
-
`updated` property's initial value is not defined clearly w3c/did#495, by @shigeya.
-
DID method name should be ASCII alphanumeric in lowercase w3c/did#491, by @shigeya.
-
Issue with using `version-id` and key revocation w3c/did#483, by @oed.
-
Section 6.3.3.1 DAG CBOR spec link w3c/did#481, by @manicprogrammer.
-
Provide better service.type examples w3c/did#479, by @OR13.
-
34 issues closed.
-
Issue with using `version-id` and key revocation w3c/did#483.
-
How should resolvers handle the accept header? w3c/did#417.
-
Datetime data type missing timezone and precision w3c/did#498.
-
Should did-core restrict the use of JWK? w3c/did#240.
-
Move Issues from Spec Registries to DID Core w3c/did#367.
-
Representations need explicit type conversion rules w3c/did#462.
-
application/did+json should be marked at risk w3c/did#439.
-
Abstract data model is not secure w3c/did#398.
-
rename master branch w3c/did#332.
-
Remove publicKeyPem from did core and did spec tests w3c/did#374.
-
Section 6.3.3.1 DAG CBOR spec link w3c/did#481.
-
How to treat unknown properties w3c/did#205.
-
Ordered set of links for controllers? w3c/did#411.
-
Additional information/proxy service type w3c/did#329.
-
DID Core editorial review (2) w3c/did#403.
-
DID Core editorial review (1) w3c/did#401.
-
62 issues received 213 new comments.
-
IETF did+ld+json media type registration w3c/did#208 (11 comments by @iherman, @msporny, @rhiaro, @TallTed)
-
application/did+json should be marked at risk w3c/did#439 (11 comments by @ChristopherA, @csuwildcat, @iherman, @OR13, @selfissued)
-
Clarification on what DIDs might identify w3c/did#199 (11 comments by @agropper, @brentzundel, @dlongley, @iherman, @jandrieu, @kdenhartog, @peacekeeper)
-
Precise specification of the DID Core Vocabulary w3c/did#404 (10 comments by @iherman, @msporny, @OR13, @rhiaro, @selfissued)
-
Normative statements review w3c/did#384 (9 comments by @brentzundel, @jricher, @kdenhartog, @msporny, @OR13, @rhiaro, @selfissued)
-
Issue with using `version-id` and key revocation w3c/did#483 (8 comments by @awoie, @msporny, @oed, @OR13, @peacekeeper)
-
Provide better service.type examples w3c/did#479 (7 comments by @agropper, @ChristopherA, @msporny, @OR13)
-
Service Endpoints in the DID Doc might be an anti-pattern w3c/did#382 (7 comments by @agropper, @dhh1128, @msporny, @tahpot)
-
`Decentralized extension` is not discussed w3c/did#502 (6 comments by @kdenhartog, @msporny, @peacekeeper, @shigeya)
-
`updated` property's initial value is not defined clearly w3c/did#495 (5 comments by @peacekeeper, @shigeya)
-
How should contributors register the same DID Method on multiple networks? w3c/did#478 (5 comments by @kdenhartog, @msporny, @OR13, @peacekeeper)
-
Minor editorial issue: discrepancy between alsoKnownAs and others w3c/did#518 (4 comments by @csuwildcat, @iherman, @TallTed)
-
Representation property or representation-specific property ? w3c/did#500 (4 comments by @kdenhartog, @peacekeeper, @shigeya)
-
Define serializations for Numbers, Dates, other properties w3c/did#361 (4 comments by @dlongley, @msporny)
-
Issues in "Note on Persistence" in DID Syntax section w3c/did#504 (3 comments by @kdenhartog, @shigeya)
-
The definition of "the top-level" of the abstract data model is unclear w3c/did#505 (3 comments by @msporny, @shigeya)
-
Inconsistent definition/name of DID Document (or abstract data model?) w3c/did#496 (3 comments by @msporny, @shigeya)
-
DID method name should be ASCII alphanumeric in lowercase w3c/did#491 (3 comments by @msporny, @peacekeeper, @shigeya)
-
According to the working draft as of 8 June 2020, raw secp256r1 public keys must be 32-byte long w3c/did#325 (3 comments by @msporny)
-
DID Core must define how to compute the digest to secure did spec registry entries contexts w3c/did#464 (3 comments by @msporny)
-
DID Spec Registries needs to specify registration process wrt. restrictions. w3c/did#425 (3 comments by @iherman, @wseltzer)
-
Remove publicKeyPem from did core and did spec tests w3c/did#374 (3 comments by @brentzundel, @kdenhartog, @TallTed)
-
Metadata properties don't define data model and serialization format w3c/did#499 (2 comments by @msporny, @peacekeeper)
-
Correct the serviceEndpoint property to allow for a string or array of strings w3c/did#506 (2 comments by @msporny)
-
JSON-LD context specific questions about DID Core specification w3c/did#416 (2 comments by @msporny, @OR13)
-
Discussion on "localized rules for handling properties" not described anywhere w3c/did#494 (1 comment by @msporny)
-
Public key "id" and "type" members duplicate JWK "kid" and "kty" members w3c/did#170 (1 comment by @msporny)
-
Enable instant DID use/resolution for DID Methods that include a propagation delay w3c/did#70 (1 comment by @msporny)
-
Ability for DID in a Method to be known as more than one ID, with a canonical selection w3c/did#368 (1 comment by @msporny)
-
Current language around equivalent canonical DIDs increases signature verification complexity w3c/did#421 (1 comment by @msporny)
-
Section "Authentication and Verifiable Claims": Add language about legal identity w3c/did#390 (1 comment by @peacekeeper)
-
Uses of terms defined in the specification should be links to their definitions w3c/did#163 (1 comment by @msporny)
-
32 pull requests opened.
-
Added an appendix as a vocabulary overview w3c/did#519, by @iherman.
-
(editorial) fix plural terms w3c/did#517, by @TallTed.
-
Add section on service privacy w3c/did#515, by @dhh1128.
-
rewords usage of decentralized extensions w3c/did#514, by @kdenhartog.
-
Add SVIP contract number. w3c/did#513, by @peacekeeper.
-
Add StandICT.eu contract number. w3c/did#512, by @peacekeeper.
-
Add section on "Service Privacy" to Privacy Considerations. w3c/did#511, by @msporny.
-
Allow serviceEndpoint to be an array. Address #506. w3c/did#510, by @msporny.
-
Specify datetime precision for serializations. w3c/did#509, by @msporny.
-
Add additional Metadata properties, fix #483 w3c/did#508, by @oed.
-
changes usage of localized rules to previously used language w3c/did#507, by @kdenhartog.
-
Minor cross reference fixes to the terminology section w3c/did#503, by @shigeya.
-
Adding '-specific' to 'representation property' w3c/did#501, by @shigeya.
-
Minor typo fixes to Sec. 1, 6 and 7 w3c/did#497, by @shigeya.
-
markup: Fix bugs w3c/did#493, by @rhiaro.
-
Refactor verification methods section w3c/did#490, by @OR13.
-
Add LinkedDomain example w3c/did#489, by @OR13.
-
Remove reference to @base issue discussion. w3c/did#488, by @OR13.
-
Define representation-not-supported error w3c/did#487, by @OR13.
-
Add note on representation properties lexical and value space w3c/did#486, by @OR13.
-
Add advisement on computing the cryptographic hash of a context w3c/did#485, by @OR13.
-
Update main from master w3c/did#482, by @brentzundel.
-
Remove duplicate data conversion section. w3c/did#475, by @msporny.
-
Add JSON-LD Production and Consumption rules. w3c/did#474, by @msporny.
-
Add equivalence properties. w3c/did#473, by @msporny.
-
(editorial) minor language refinement w3c/did#472, by @TallTed.
-
-
32 pull requests merged.
-
Add SVIP contract number. w3c/did#513.
-
Add StandICT.eu contract number. w3c/did#512.
-
Allow serviceEndpoint to be an array. Address #506. w3c/did#510.
-
Specify datetime precision for serializations. w3c/did#509.
-
Add additional Metadata properties, fix #483 w3c/did#508.
-
Add LinkedDomain example w3c/did#489.
-
Minor typo fixes to Sec. 1, 6 and 7 w3c/did#497.
-
Refactor verification methods section w3c/did#490.
-
Remove reference to @base issue discussion. w3c/did#488.
-
Define representation-not-supported error w3c/did#487.
-
markup: Fix bugs w3c/did#493.
-
Remove duplicate data conversion section. w3c/did#475.
-
Add JSON-LD Production and Consumption rules. w3c/did#474.
-
Change MUST to SHOULD for lossless conversion w3c/did#465.
-
(editorial) minor language refinement w3c/did#472.
-
Add equivalence properties. w3c/did#473.
-
updated cbor section w3c/did#420.
-
Minor editorial reshuffling in Core Properties w3c/did#471.
-
methods: remove untestable normative statement w3c/did#470.
-
respec: fix restrictReferences w3c/did#467.
-
Add considerations about real-world identity. w3c/did#466.
-
editorial: remove biometrics examples w3c/did#459.
-
-
6 pull requests closed.
-
Update main from master w3c/did#482.
-
add discussion on unknown and reserved properties w3c/did#394.
-
41 pull requests received 222 new comments.
-
Add DID parameter for dereferencing an information resource identified by a DID w3c/did#480 (32 comments by @agropper, @brentzundel, @dlongley, @iherman, @kdenhartog, @msporny, @OR13, @peacekeeper, @rhiaro, @talltree)
-
Refactor verification methods section w3c/did#490 (21 comments by @dlongley, @kdenhartog, @msporny, @OR13, @rhiaro, @TallTed)
-
Add LinkedDomain example w3c/did#489 (20 comments by @awoie, @csuwildcat, @dlongley, @kdenhartog, @msporny, @OR13, @tplooker)
-
DIDs as Enhanced URNs w3c/did#457 (10 comments by @agropper, @brentzundel, @kdenhartog, @msporny, @shigeya, @TallTed, @talltree)
-
Simplify id property via separation of deterministic equivalence functionality w3c/did#431 (9 comments by @csuwildcat, @msporny, @OR13)
-
Add advisement on computing the cryptographic hash of a context w3c/did#485 (8 comments by @davidlehn, @msporny, @OR13, @TallTed)
-
Add section on "Service Privacy" to Privacy Considerations. w3c/did#511 (7 comments by @agropper, @dhh1128, @dlongley, @msporny)
-
Changing DID method name description to match the ABNF definition to allow digits w3c/did#492 (6 comments by @brentzundel, @iherman, @msporny, @shigeya)
-
rewords usage of decentralized extensions w3c/did#514 (5 comments by @brentzundel, @kdenhartog, @msporny)
-
Align CBOR production/consumption rules with rest of specification. w3c/did#476 (5 comments by @jonnycrunch, @msporny, @OR13)
-
Add additional Metadata properties, fix #483 w3c/did#508 (4 comments by @jonnycrunch, @msporny, @oed)
-
At Risk statement for ABNF not allowing an empty method-id-string w3c/did#477 (4 comments by @jandrieu, @peacekeeper, @talltree)
-
Allow serviceEndpoint to be an array. Address #506. w3c/did#510 (3 comments by @csuwildcat, @msporny)
-
changes usage of localized rules to previously used language w3c/did#507 (2 comments by @brentzundel, @msporny)
-
At Risk statement for ABNF not allowing an empty method-id-string w3c/did#484 (2 comments by @msporny)
-
Add representation language to address syntax and "unknown" properties. w3c/did#454 (2 comments by @iherman, @msporny)
-
Define the JSON representation as JSON (without excluding directives) w3c/did#396 (1 comment by @msporny)
-
Add concrete serialization rules for JSON based on new data types section. w3c/did#469 (1 comment by @msporny)
-
w3c/did-use-cases
-
1 issue closed.
-
Auto-inclusion of glossary from DID-Core w3c/did-use-cases#75.
-
-
1 issue received 1 new comment.
-
12 pull requests opened.
-
Adding Crypto Auth Com to EDV Use Case w3c/did-use-cases#134, by @philarcher.
-
Nits & typos w3c/did-use-cases#133, by @philarcher.
-
Update challenges section of messaging use case w3c/did-use-cases#132, by @creatornader.
-
Triggering publication w3c/did-use-cases#131, by @philarcher.
-
Adding SVG diagrams w3c/did-use-cases#130, by @philarcher.
-
Additional context for messaging use cases w3c/did-use-cases#129, by @creatornader.
-
ReSpec config using 'group' w3c/did-use-cases#128, by @philarcher.
-
Cleaning up the terminology section w3c/did-use-cases#127, by @philarcher.
-
Duplicate of PR 122 Will fix #97 w3c/did-use-cases#126, by @philarcher.
-
Improving requirements table w3c/did-use-cases#125, by @philarcher.
-
Removing repeated Feature Coverage section w3c/did-use-cases#124, by @philarcher.
-
Removing erroneous duplicate sections w3c/did-use-cases#123, by @philarcher.
-
-
10 pull requests merged.
-
Adding Crypto Auth Com to EDV Use Case w3c/did-use-cases#134.
-
Nits & typos w3c/did-use-cases#133.
-
Triggering publication w3c/did-use-cases#131.
-
Adding SVG diagrams w3c/did-use-cases#130.
-
Additional context for messaging use cases w3c/did-use-cases#129.
-
ReSpec config using 'group' w3c/did-use-cases#128.
-
Cleaning up the terminology section w3c/did-use-cases#127.
-
Improving requirements table w3c/did-use-cases#125.
-
Removing repeated Feature Coverage section w3c/did-use-cases#124.
-
Removing erroneous duplicate sections w3c/did-use-cases#123.
-
-
2 pull requests closed.
-
Add messaging focal use case (didcomm). Will fix issue #97 w3c/did-use-cases#122.
-
Add didcomm usecase w3c/did-use-cases#100.
-
-
4 pull requests received 21 new comments.
-
Duplicate of PR 122 Will fix #97 w3c/did-use-cases#126 (11 comments by @creatornader, @dhh1128, @jandrieu, @philarcher, @TelegramSam)
-
Update challenges section of messaging use case w3c/did-use-cases#132 (5 comments by @creatornader, @jandrieu)
-
Add messaging focal use case (didcomm). Will fix issue #97 w3c/did-use-cases#122 (4 comments by @creatornader, @philarcher)
-
w3c/did-extensions
-
8 issues opened.
-
Should registry track how to contact DID method authors? w3c/did-extensions#174, by @dhh1128.
-
Human readable docs in the DID ns w3c/did-extensions#173, by @rhiaro.
-
LinkedDomains IRI is not stable w3c/did-extensions#167, by @OR13.
-
blockchainAccountId has no CDDL w3c/did-extensions#165, by @OR13.
-
X25519KeyAgreementKey2019 has no normative definition w3c/did-extensions#164, by @OR13.
-
How to register did method w3c/did-extensions#161, by @niyuelin1990.
-
Reformat table definitions in DID Spec Registries w3c/did-extensions#160, by @msporny.
-
Remove proxy service from registry or define it. w3c/did-extensions#157, by @OR13.
-
-
3 issues closed.
-
How to register did method w3c/did-extensions#161.
-
Should we redirect publicKeyHex to the CCG security vocab? w3c/did-extensions#65.
-
Remove publicKeyPem w3c/did-extensions#126.
-
-
8 issues received 15 new comments.
-
Should registry track how to contact DID method authors? w3c/did-extensions#174 (6 comments by @dhh1128, @OR13, @peacekeeper, @talltree)
-
Can we add date added/deprecated or version added/deprecated to track addition of properties? w3c/did-extensions#143 (2 comments by @kdenhartog, @OR13)
-
Should we redirect publicKeyHex to the CCG security vocab? w3c/did-extensions#65 (2 comments by @kdenhartog, @OR13)
-
Management Process for DID Spec Registries after DID WG ends w3c/did-extensions#149 (1 comment by @iherman)
-
-
15 pull requests opened.
-
namespace: Add html terms list, fixes #173 w3c/did-extensions#179, by @rhiaro.
-
Add note about desirability of author email w3c/did-extensions#178, by @dhh1128.
-
Add Korea Mobile Identity System DID method Spec w3c/did-extensions#177, by @identify202020.
-
Add email address for DID method spec author w3c/did-extensions#176, by @peacekeeper.
-
Add Future DID method specification w3c/did-extensions#175, by @niyuelin1990.
-
contexts: Explain which terms aren't in DID Core Spec w3c/did-extensions#172, by @rhiaro.
-
markup: Fix typo w3c/did-extensions#171, by @rhiaro.
-
contexts: Remove terms not in DID Core Spec w3c/did-extensions#170, by @rhiaro.
-
fix did namespace in contexts w3c/did-extensions#169, by @rhiaro.
-
Add LinkedDomains service type w3c/did-extensions#168, by @OR13.
-
Add @BlockchainCommons/did-method-onion w3c/did-extensions#163, by @ChristopherA.
-
MONiD DID method specification w3c/did-extensions#162, by @ilovelili.
-
Add signed-ietf-json-patch parameter w3c/did-extensions#159, by @peacekeeper.
-
fix: update publicKeyHex definition and JSON-LD context w3c/did-extensions#158, by @kdenhartog.
-
-
6 pull requests merged.
-
Add Future DID method specification w3c/did-extensions#175.
-
markup: Fix typo w3c/did-extensions#171.
-
MONiD DID method specification w3c/did-extensions#162.
-
fix: update publicKeyHex definition and JSON-LD context w3c/did-extensions#158.
-
Add signed-ietf-json-patch parameter w3c/did-extensions#159.
-
-
13 pull requests received 59 new comments.
-
contexts: Remove terms not in DID Core Spec w3c/did-extensions#170 (26 comments by @iherman, @OR13, @rhiaro)
-
contexts: Explain which terms aren't in DID Core Spec w3c/did-extensions#172 (8 comments by @iherman, @kdenhartog, @msporny, @OR13, @rhiaro)
-
Add email address for DID method spec author w3c/did-extensions#176 (2 comments by @frozeman, @OR13)
-
fix: update publicKeyHex definition and JSON-LD context w3c/did-extensions#158 (2 comments by @kdenhartog, @OR13)
-
Added CDDL as data definition syntax for parts of the Abstract Data Model of DID Document and registry items w3c/did-extensions#138 (1 comment by @OR13)
-
w3c/did-rubric
-
1 pull request received 2 new comments.
w3c/did-test-suite
-
2 issues opened.
-
Tests are confusing, consider refactoring w3c/did-test-suite#17, by @OR13.
-
Unclear how to run the tests w3c/did-test-suite#15, by @csuwildcat.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Initial equivalence test w3c/did-test-suite#16, by @csuwildcat.
-
-
2 pull requests merged.
-
Initial equivalence test w3c/did-test-suite#16.
-
Add scenarios for DID syntax w3c/did-test-suite#12.
-
-
2 pull requests received 7 new comments.
TR publications
-
7 documents published.
-
Decentralized Identifiers (DIDs) v1.0 published 3 times as a Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
DID Specification Registries published 4 times as a Note. History of DID Specification Registries
-
Participants
-
6 participants joined.
-
Joaquin Salvachua (Universidad Politécnica de Madrid) joined.
-
Kaliya Young (Evernym) joined.
-
Ned Smith (Intel Corporation) joined.
-
Ned Smith (Intel Corporation) joined.
-
Keiko Itakura (Rakuten Group, Inc.) joined.
-
Leonard Tan (Torus) joined.
-
-
2 participants left.
-
Lovesh Harchandani (Evernym) left.
-
Ned Smith (Intel Corporation) left.
-
-
4 organizations joined.
-
Universidad Politécnica de Madrid joined.
-
Intel Corporation joined.
-
Rakuten Group, Inc. joined.
-
Torus joined.
-
GitHub
w3c/did-extensions
-
6 issues opened.
-
DID Spec Registries needs terminological criteria w3c/did-extensions#156, by @rhiaro.
-
Provide an example of registering a new representation w3c/did-extensions#154, by @OR13.
-
Management Process for DID Spec Registries after DID WG ends w3c/did-extensions#149, by @msporny.
-
Review DID Methods for Conformance with DID Core w3c/did-extensions#148, by @OR13.
-
-
4 issues closed.
-
DID Resolution Response Metadata: "invalid-did" is undefined w3c/did-extensions#111.
-
Remove CBOR `equivalence` mappings w3c/did-extensions#82.
-
Add a CBOR Registry definition for id w3c/did-extensions#5.
-
8 issues received 15 new comments.
-
JsonWebKey2020 might get renamed in the future w3c/did-extensions#101 (3 comments by @kdenhartog, @OR13)
-
Management Process for DID Spec Registries after DID WG ends w3c/did-extensions#149 (3 comments by @iherman, @jonnycrunch, @msporny)
-
Discuss schema.org, activitypub, VC and DID JSON-LD overlap w3c/did-extensions#92 (2 comments by @kdenhartog, @OR13)
-
Should CDDL be used as the Data Definition Language to formalize the constraints of the Abstract Data Model? w3c/did-extensions#153 (1 comment by @jonnycrunch)
-
DID Resolution Response Metadata: "unauthorized" is undefined w3c/did-extensions#112 (1 comment by @peacekeeper)
-
-
3 pull requests opened.
-
docs: removes publicKeyPem to address issue #126 w3c/did-extensions#155, by @kdenhartog.
-
Update list of error values. w3c/did-extensions#151, by @peacekeeper.
-
Add Panacea DID method specification w3c/did-extensions#150, by @youngjoon-lee.
-
-
6 pull requests merged.
-
Update list of error values. w3c/did-extensions#151.
-
docs: removes publicKeyPem to address issue #126 w3c/did-extensions#155.
-
Add Panacea DID method specification w3c/did-extensions#150.
-
Added `alsoKnownAs` to the context w3c/did-extensions#133.
-
uns DID method specification w3c/did-extensions#145.
-
methods: Add link to normative requirements of DID method specs w3c/did-extensions#147.
-
-
8 pull requests received 52 new comments.
-
Added CDDL as data definition syntax for parts of the Abstract Data Model of DID Document and registry items w3c/did-extensions#138 (36 comments by @cabo, @jonnycrunch, @msporny, @OR13, @peacekeeper)
-
Remove @context as Core Property w3c/did-extensions#139 (8 comments by @kdenhartog, @msporny, @OR13, @peacekeeper)
-
methods: Add link to normative requirements of DID method specs w3c/did-extensions#147 (2 comments by @OR13)
-
w3c/did
-
7 issues opened.
-
Should "deactivated" be an error code? w3c/did#468, by @peacekeeper.
-
Naming classes of properties and syntax w3c/did#463, by @peacekeeper.
-
Representations need explicit type conversion rules w3c/did#462, by @jricher.
-
Data Model and Representations "Value and Lexical Space" w3c/did#456, by @OR13.
-
Updating architecture overview diagrams w3c/did#453, by @shigeya.
-
-
12 issues closed.
-
Are we okay with not testing DID URL's query? w3c/did#385.
-
Incompatibilities in the fragment definitions w3c/did#400.
-
Underspecified semantics of "updated" property w3c/did#174.
-
Include discussion of eIDAS levels-of-assurance w3c/did#151.
-
DID Document vs. DID Subject w3c/did#413.
-
Restrict the number of key representation members w3c/did#356.
-
54 issues received 182 new comments.
-
When should did parameters be dropped? w3c/did#337 (18 comments by @dhh1128, @kdenhartog, @msporny, @OR13, @peacekeeper)
-
How should resolvers handle the accept header? w3c/did#417 (14 comments by @kdenhartog, @msporny, @OR13, @peacekeeper)
-
Service Endpoints in the DID Doc might be an anti-pattern w3c/did#382 (12 comments by @agropper, @dhh1128, @jandrieu, @msporny, @OR13, @tahpot, @TelegramSam)
-
Clarification on what DIDs might identify w3c/did#199 (10 comments by @agropper, @brentzundel, @msporny, @rxgrant)
-
application/did+json should be marked at risk w3c/did#439 (7 comments by @msporny, @OR13, @talltree, @txalkan)
-
Define serializations for Numbers, Dates, other properties w3c/did#361 (6 comments by @jonnycrunch, @msporny, @rhiaro)
-
Remove publicKeyPem from did core and did spec tests w3c/did#374 (6 comments by @kdenhartog, @msporny, @OR13, @peacekeeper)
-
IETF did+ld+json media type registration w3c/did#208 (5 comments by @gkellogg, @iherman, @msporny, @rhiaro)
-
Incompatibilities in the fragment definitions w3c/did#400 (5 comments by @brentzundel, @iherman, @msporny, @OR13)
-
Naming classes of properties and syntax w3c/did#463 (4 comments by @iherman, @OR13, @peacekeeper, @talltree)
-
Ability for DID in a Method to be known as more than one ID, with a canonical selection w3c/did#368 (4 comments by @msporny, @peacekeeper)
-
DID Spec Registries needs to specify registration process wrt. restrictions. w3c/did#425 (3 comments by @jandrieu, @msporny, @shigeya)
-
Data Model and Representations "Value and Lexical Space" w3c/did#456 (3 comments by @OR13, @peacekeeper)
-
Include discussion of eIDAS levels-of-assurance w3c/did#151 (3 comments by @kdenhartog, @msporny, @peacekeeper)
-
constraints on assertionMethod? Or a different verification purpose? w3c/did#375 (3 comments by @dhh1128, @kdenhartog, @msporny)
-
Public key "id" and "type" members duplicate JWK "kid" and "kty" members w3c/did#170 (3 comments by @msporny, @OR13, @selfissued)
-
Precise specification of the DID Core Vocabulary w3c/did#404 (3 comments by @iherman, @msporny, @pukkamustard)
-
CBOR core representation is solid and should NOT be marked as at-risk w3c/did#339 (2 comments by @jonnycrunch, @msporny)
-
Enable instant DID use/resolution for DID Methods that include a propagation delay w3c/did#70 (2 comments by @msporny)
-
Should we rename "verification relationships" to "authorization relationships"? w3c/did#318 (2 comments by @brentzundel, @msporny)
-
How to mitigate the single source of failure wrt/ "Trust into the Universal Resolver"? w3c/did#249 (2 comments by @brentzundel, @msporny)
-
Cheap DIDs and the option to migrate DIDs between ledgers using standard DID Deprecation Registries w3c/did#33 (2 comments by @kdenhartog, @msporny)
-
Handling additional errors in resolution/dereferencing w3c/did#402 (2 comments by @kdenhartog, @msporny)
-
Consider EFF / ACLU objections by distinguaishing accountable vs. voluntary DIDs w3c/did#370 (2 comments by @agropper, @msporny)
-
Proposed Appendices on DID Identification Architecture w3c/did#373 (2 comments by @msporny, @talltree)
-
Current language around equivalent canonical DIDs increases signature verification complexity w3c/did#421 (1 comment by @msporny)
-
Section "Authentication and Verifiable Claims": Add subsection about key security w3c/did#391 (1 comment by @peacekeeper)
-
How should contributors register the same DID Method on multiple networks? w3c/did#478 (1 comment by @kdenhartog)
-
Section "Authentication and Verifiable Claims": Add language about legal identity w3c/did#390 (1 comment by @msporny)
-
-
12 pull requests opened.
-
Minor editorial reshuffling in Core Properties w3c/did#471, by @rhiaro.
-
methods: remove untestable normative statement w3c/did#470, by @rhiaro.
-
respec: fix restrictReferences w3c/did#467, by @rhiaro.
-
Add considerations about real-world identity. w3c/did#466, by @peacekeeper.
-
Change MUST to SHOULD for lossless conversion w3c/did#465, by @peacekeeper.
-
appendix text added w3c/did#460, by @talltree.
-
editorial: remove biometrics examples w3c/did#459, by @rhiaro.
-
Marks did+ld+json media type at risk w3c/did#458, by @rhiaro.
-
DIDs as Enhanced URNs w3c/did#457, by @talltree.
-
Rework Data Model section. w3c/did#455, by @msporny.
-
-
13 pull requests merged.
-
Marks did+ld+json media type at risk w3c/did#458.
-
terms: add 'immutable' to DLT definition w3c/did#450.
-
Rework Data Model section. w3c/did#455.
-
Condense Verification Relationships sections w3c/did#451.
-
references: DID Spec Registries informative w3c/did#448.
-
editorial: Remove closed issues w3c/did#445.
-
Editorial updates from Ivan, #2 w3c/did#441.
-
editorial: fix stray link to issues w3c/did#442.
-
-
1 pull request closed.
-
Add `type` property w3c/did#410.
-
-
24 pull requests received 228 new comments.
-
Simplify id property via separation of deterministic equivalence functionality w3c/did#431 (54 comments by @csuwildcat, @iherman, @msporny, @OR13, @peacekeeper, @selfissued, @TomCJones, @tplooker, @troyronda)
-
Rework Data Model section. w3c/did#455 (33 comments by @brentzundel, @dlongley, @iherman, @jricher, @kdenhartog, @msporny, @OR13, @talltree)
-
appendix text added w3c/did#460 (33 comments by @brentzundel, @iherman, @jandrieu, @kdenhartog, @rhiaro, @talltree)
-
Add representation language to address syntax and "unknown" properties. w3c/did#454 (26 comments by @brentzundel, @burnburn, @dlongley, @iherman, @jonnycrunch, @jricher, @msporny, @OR13, @selfissued, @TallTed)
-
terms: add 'immutable' to DLT definition w3c/did#450 (16 comments by @iherman, @jandrieu, @msporny, @peacekeeper, @rhiaro)
-
Add concrete serialization rules for JSON based on new data types section. w3c/did#469 (12 comments by @iherman, @jricher, @msporny)
-
updated cbor section w3c/did#420 (8 comments by @cabo, @jonnycrunch, @msporny, @OR13, @peacekeeper, @talltree)
-
editorial: remove biometrics examples w3c/did#459 (8 comments by @kdenhartog, @msporny, @peacekeeper, @rhiaro)
-
Change MUST to SHOULD for lossless conversion w3c/did#465 (4 comments by @jricher, @msporny, @peacekeeper)
-
Define the JSON representation as JSON (without excluding directives) w3c/did#396 (2 comments by @peacekeeper, @rhiaro)
-
editorial: Clarify that id is only for DID subject when at top level w3c/did#449 (1 comment by @msporny)
-
privacy: Add privacy concerns about 'type' (and similar) property. w3c/did#444 (1 comment by @msporny)
-
w3c/did-resolution
-
1 issue opened.
-
Select top-level properties from Resolver w3c/did-resolution#59, by @BernhardFuchs.
-
-
1 pull request opened.
-
Propose Authentication allowed on DID resolution w3c/did-resolution#58, by @jose-gataca.
-
-
1 pull request received 2 new comments.
-
Propose Authentication allowed on DID resolution w3c/did-resolution#58 (2 comments by @jose-gataca, @TomCJones)
-
w3c/did-use-cases
-
10 issues closed.
-
Add Focal Use-Case for human-centered DID interoperability: Alice Rents a Car w3c/did-use-cases#101.
-
Consider removing use case 2.4 w3c/did-use-cases#108.
-
Suggestion: Better partitioning of "DID" actions w3c/did-use-cases#58.
-
Add a human story to use case 2.6 Sharing opted-in information across platforms w3c/did-use-cases#110.
-
Psuedonymity rather than anonymity in Use Case 2.8 w3c/did-use-cases#111.
-
Add human story for 2.1 Vehicle assemblies w3c/did-use-cases#106.
-
Add human story for 2.1 online shopper w3c/did-use-cases#105.
-
Add use case for DIDs+eIDAS w3c/did-use-cases#102.
-
Add human story for 2.3 Encrypted Data Vault w3c/did-use-cases#107.
-
Add human story to 2.5 Identifiers in an ecosystem of verifiable credentials (VCs): w3c/did-use-cases#109.
-
-
12 issues received 18 new comments.
-
Add Use-Case for Ambient Surveillance w3c/did-use-cases#113 (5 comments by @agropper, @jandrieu, @philarcher)
-
Add Focal Use-Case for human-centered DID interoperability: Alice Rents a Car w3c/did-use-cases#101 (1 comment by @philarcher)
-
Add a human story to use case 2.6 Sharing opted-in information across platforms w3c/did-use-cases#110 (1 comment by @philarcher)
-
Add human story to 2.5 Identifiers in an ecosystem of verifiable credentials (VCs): w3c/did-use-cases#109 (1 comment by @philarcher)
-
-
9 pull requests opened.
-
Add messaging focal use case (didcomm). Will fix issue #97 w3c/did-use-cases#122, by @creatornader.
-
Archaic yellow highlighting removed w3c/did-use-cases#121, by @philarcher.
-
Alice rents a car will fix #101 w3c/did-use-cases#120, by @philarcher.
-
Psuedonymity not anonymity. Will fix Issue #111 w3c/did-use-cases#119, by @philarcher.
-
Human story for UC 5. Will fix Issue #110 w3c/did-use-cases#118, by @philarcher.
-
Human story for VCs ecosystem. Will fix #109 w3c/did-use-cases#117, by @philarcher.
-
Human story for encrypted data vault. Will fx issue #107 w3c/did-use-cases#116, by @philarcher.
-
Human story for vehicle assembly. Will fix issue #106 w3c/did-use-cases#115, by @philarcher.
-
Human story for online shopper. Fixes Issue #105 w3c/did-use-cases#114, by @philarcher.
-
-
9 pull requests merged.
-
Alice rents a car will fix #101 w3c/did-use-cases#120.
-
Archaic yellow highlighting removed w3c/did-use-cases#121.
-
Psuedonymity not anonymity. Will fix Issue #111 w3c/did-use-cases#119.
-
Human story for encrypted data vault. Will fx issue #107 w3c/did-use-cases#116.
-
Adds use case "Public authority identity credentials (eIDAS)" w3c/did-use-cases#112.
-
Human story for online shopper. Fixes Issue #105 w3c/did-use-cases#114.
-
Human story for vehicle assembly. Will fix issue #106 w3c/did-use-cases#115.
-
Human story for VCs ecosystem. Will fix #109 w3c/did-use-cases#117.
-
Human story for UC 5. Will fix Issue #110 w3c/did-use-cases#118.
-
-
6 pull requests received 34 new comments.
-
Human story for encrypted data vault. Will fx issue #107 w3c/did-use-cases#116 (13 comments by @agropper, @dlongley, @jandrieu, @OR13, @philarcher)
-
Adds use case "Public authority identity credentials (eIDAS)" w3c/did-use-cases#112 (6 comments by @ewagner70, @jandrieu, @peacekeeper, @philarcher)
-
Psuedonymity not anonymity. Will fix Issue #111 w3c/did-use-cases#119 (4 comments by @agropper, @jandrieu, @philarcher)
-
Human story for UC 5. Will fix Issue #110 w3c/did-use-cases#118 (2 comments by @agropper, @philarcher)
-
w3c/did-rubric
-
6 pull requests opened.
-
(DO NOT MERGE) Sample PR showing how to submit info about arbitrary methods w3c/did-rubric#12, by @dhh1128.
-
Add draft of security and privacy sections w3c/did-rubric#11, by @dhh1128.
-
add draft of security and privacy sections w3c/did-rubric#10, by @dhh1128.
-
editorial: break monolithic index.html into subfiles w3c/did-rubric#9, by @dhh1128.
-
minor editorial changes w3c/did-rubric#8, by @dhh1128.
-
editorial: title change w3c/did-rubric#7, by @dhh1128.
-
-
2 pull requests merged.
-
minor editorial changes w3c/did-rubric#8.
-
editorial: title change w3c/did-rubric#7.
-
-
2 pull requests closed.
-
add draft of security and privacy sections w3c/did-rubric#10.
-
editorial: break monolithic index.html into subfiles w3c/did-rubric#9.
-
-
2 pull requests received 61 new comments.
w3c/did-imp-guide
-
1 issue received 1 new comment.
w3c/did-test-suite
-
2 issues opened.
-
Danube Tech is testing these sections of the spec w3c/did-test-suite#14, by @peacekeeper.
-
Transmute is testing the entire specification w3c/did-test-suite#13, by @OR13.
-
-
2 pull requests opened.
-
Add scenarios for DID syntax w3c/did-test-suite#12, by @peacekeeper.
-
Fix link to did-core w3c/did-test-suite#11, by @peacekeeper.
-
-
1 pull request merged.
-
Fix link to did-core w3c/did-test-suite#11.
-
TR publications
-
7 documents published.
-
Decentralized Identifiers (DIDs) v1.0 published 6 times as a Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
DID Specification Registries published as a Note. History of DID Specification Registries
-
Participants
-
6 participants joined.
-
Charles Lehner (W3C Invited Experts) joined.
-
Wayne Chang (Spruce Systems, Inc.) joined.
-
Juan Caballero (Spruce Systems, Inc.) joined.
-
Geunhyung Kim (Sharing Economy Association of Korea (SEAK)) joined.
-
Fei3 Gao (China Academy of Information and Communications Technology (CAICT)) joined.
-
Aanchal Malhotra (Ripple) joined.
-
-
4 participants left.
-
Christian Lundkvist (Consensys) left.
-
Jonathan Holt (Consensys) left.
-
Yurong Li (China Academy of Information and Communications Technology (CAICT)) left.
-
Alex Cai (China Academy of Information and Communications Technology (CAICT)) left.
-
-
5 organizations joined.
-
ZIIOT joined.
-
TranSendX joined.
-
Gooroomee Inc. joined.
-
Pundi X joined.
-
Ripple joined.
-
GitHub
w3c/did-extensions
-
1 issue opened.
-
Align with w3id.org w3c/did-extensions#144, by @OR13.
-
-
2 issues closed.
-
A Cryptographic Golem has been created w3c/did-extensions#79.
-
ECHIDNA is broken w3c/did-extensions#78.
-
-
3 issues received 10 new comments.
-
3 pull requests opened.
-
methods: Add link to normative requirements of DID method specs w3c/did-extensions#147, by @rhiaro.
-
Require hash of JSON-LD context w3c/did-extensions#146, by @rhiaro.
-
uns DID method specification w3c/did-extensions#145, by @SophieDM.
-
-
2 pull requests merged.
-
Change created/updated examples to match DID Core examples. w3c/did-extensions#136.
-
Fix links to created and updated in DID Core w3c/did-extensions#135.
-
-
1 pull request closed.
-
Registry Updates w3c/did-extensions#132.
-
-
4 pull requests received 34 new comments.
-
Added CDDL as data definition syntax for parts of the Abstract Data Model of DID Document and registry items w3c/did-extensions#138 (24 comments by @anweiss, @cabo, @jonnycrunch, @OR13, @peacekeeper)
-
w3c/did
-
7 issues opened.
-
Differentiate external properties in examples w3c/did#447, by @rhiaro.
-
application/did+json should be marked at risk w3c/did#439, by @OR13.
-
Lack of clarity regarding Numbers in the Abstract Data Model w3c/did#435, by @jonnycrunch.
-
Restrictions on `@context` property values in DID Documents w3c/did#432, by @OR13.
-
7 issues closed.
-
Create DID explainer w3c/did#94.
-
Define DID Document Metadata w3c/did#203.
-
Discoverability of `version-id` w3c/did#419.
-
2 issues reopened.
-
35 issues received 156 new comments.
-
How should resolvers handle the accept header? w3c/did#417 (23 comments by @mooreT1881, @OR13, @peacekeeper, @TomCJones)
-
need to clarify revocation vs. rotation w3c/did#386 (20 comments by @agropper, @dhh1128, @dlongley, @jandrieu, @SmithSamuelM)
-
Restrictions on `@context` property values in DID Documents w3c/did#432 (19 comments by @dhh1128, @dlongley, @msporny, @OR13, @peacekeeper)
-
Current language around equivalent canonical DIDs increases signature verification complexity w3c/did#421 (18 comments by @csuwildcat, @dlongley, @msporny, @OR13, @timcappalli, @troyronda)
-
Should we rename "verification relationships" to "authorization relationships"? w3c/did#318 (11 comments by @csuwildcat, @dlongley, @kdenhartog, @mprorock, @OR13)
-
Proposed Appendices on DID Identification Architecture w3c/did#373 (9 comments by @kdenhartog, @OR13)
-
JSON-LD context specific questions about DID Core specification w3c/did#416 (8 comments by @dlongley, @OR13, @veikkoeeva)
-
Lack of clarity regarding Numbers in the Abstract Data Model w3c/did#435 (2 comments by @jonnycrunch, @rhiaro)
-
Ability for DID in a Method to be known as more than one ID, with a canonical selection w3c/did#368 (2 comments by @csuwildcat, @OR13)
-
Compound key is not clear and points to wikipedia not a normative definition w3c/did#452 (1 comment by @OR13)
-
Public key "id" and "type" members duplicate JWK "kid" and "kty" members w3c/did#170 (1 comment by @msporny)
-
Enable instant DID use/resolution for DID Methods that include a propagation delay w3c/did#70 (1 comment by @csuwildcat)
-
Cheap DIDs and the option to migrate DIDs between ledgers using standard DID Deprecation Registries w3c/did#33 (1 comment by @OR13)
-
-
23 pull requests opened.
-
Condense Verification Relationships sections w3c/did#451, by @rhiaro.
-
terms: add 'immutable' to DLT definition w3c/did#450, by @rhiaro.
-
references: DID Spec Registries informative w3c/did#448, by @rhiaro.
-
methods: Remove 2 normative requirements about methods w3c/did#446, by @rhiaro.
-
editorial: Remove closed issues w3c/did#445, by @rhiaro.
-
editorial: Clarify importance of ordering of property values w3c/did#443, by @rhiaro.
-
editorial: fix stray link to issues w3c/did#442, by @rhiaro.
-
Editorial updates from Ivan, #2 w3c/did#441, by @rhiaro.
-
Remove "unauthorized" and add "deactivated" error code. w3c/did#440, by @peacekeeper.
-
normative statements: Security considerations / methods sections w3c/did#438, by @rhiaro.
-
normative statements: Resolution section w3c/did#437, by @rhiaro.
-
normative statements: JSON and JSON-LD representations sections w3c/did#436, by @rhiaro.
-
normative statements: Representations section w3c/did#434, by @rhiaro.
-
fix a minor typo w3c/did#433, by @qpakzk.
-
Fix JSON-LD object in the spec w3c/did#430, by @gjgd.
-
normative statements: Core properties section w3c/did#429, by @rhiaro.
-
editorial: Remove duplicate subsection; fix line lengths w3c/did#428, by @rhiaro.
-
normative statements: Identifier section w3c/did#427, by @rhiaro.
-
normative statements: Conformance section w3c/did#426, by @rhiaro.
-
Rename resolveStream to resolveRepresentation w3c/did#424, by @peacekeeper.
-
-
18 pull requests merged.
-
normative statements: Identifier section w3c/did#427.
-
Fix JSON-LD object in the spec w3c/did#430.
-
normative statements: Resolution section w3c/did#437.
-
normative statements: Representations section w3c/did#434.
-
normative statements: Core properties section w3c/did#429.
-
normative statements: Conformance section w3c/did#426.
-
Editorial updates from Ivan w3c/did#414.
-
Rename resolveStream to resolveRepresentation w3c/did#424.
-
Add JSON-LD Producer / Consumer details w3c/did#408.
-
Cleanup key representations w3c/did#407.
-
Allow fragments to be applied to secondary resources w3c/did#409.
-
Fix echidna w3c/did#422.
-
-
2 pull requests closed.
-
fix a minor typo w3c/did#433.
-
add representation property w3c/did#348.
-
-
30 pull requests received 302 new comments.
-
updated cbor section w3c/did#420 (69 comments by @brentzundel, @burnburn, @cabo, @jonnycrunch, @msporny, @OR13, @peacekeeper)
-
Add `type` property w3c/did#410 (59 comments by @agropper, @brentzundel, @ChristopherA, @dhh1128, @dmitrizagidulin, @iherman, @jandrieu, @jonnycrunch, @melvincarvalho, @msporny, @OR13, @peacekeeper, @philarcher, @talltree)
-
Simplify id property via separation of deterministic equivalence functionality w3c/did#431 (54 comments by @csuwildcat, @dlongley, @dmitrizagidulin, @jandrieu, @msporny, @OR13, @peacekeeper, @tplooker, @troyronda)
-
Add JSON-LD Producer / Consumer details w3c/did#408 (28 comments by @csuwildcat, @dlongley, @gkellogg, @msporny, @OR13, @peacekeeper)
-
Fix JSON-LD object in the spec w3c/did#430 (15 comments by @gjgd, @jonnycrunch, @msporny, @OR13, @peacekeeper)
-
normative statements: Identifier section w3c/did#427 (9 comments by @iherman, @msporny, @peacekeeper, @rhiaro)
-
normative statements: JSON and JSON-LD representations sections w3c/did#436 (7 comments by @brentzundel, @kdenhartog, @msporny, @OR13, @rhiaro)
-
normative statements: Core properties section w3c/did#429 (5 comments by @kdenhartog, @msporny, @rhiaro)
-
Remove "unauthorized" and add "deactivated" error code. w3c/did#440 (4 comments by @agropper, @peacekeeper)
-
respec: replace WG info with 'group' property and fix internal refs w3c/did#412 (4 comments by @brentzundel, @msporny)
-
privacy: Add privacy concerns about 'type' (and similar) property. w3c/did#444 (1 comment by @brentzundel)
-
normative statements: Security considerations / methods sections w3c/did#438 (1 comment by @msporny)
-
Define the JSON representation as JSON (without excluding directives) w3c/did#396 (1 comment by @msporny)
-
w3c/did-rubric
-
1 issue closed.
-
Need initial content w3c/did-rubric#2.
-
-
2 pull requests opened.
-
various minor editorial changes (must merge after #5, instead of #5, or rebase) w3c/did-rubric#6, by @dhh1128.
-
Tweak editor/author info per comments in PR 4 w3c/did-rubric#5, by @dhh1128.
-
-
3 pull requests merged.
-
Tweak editor/author info per comments in PR 4 w3c/did-rubric#5.
-
Initialize with content from first draft w3c/did-rubric#4.
-
2 pull requests received 8 new comments.
-
various minor editorial changes (must merge after #5, instead of #5, or rebase) w3c/did-rubric#6 (1 comment by @jandrieu)
w3c/did-use-cases
-
8 issues opened.
-
Add Use-Case for Ambient Surveillance w3c/did-use-cases#113, by @agropper.
-
Psuedonymity rather than anonymity in Use Case 2.8 w3c/did-use-cases#111, by @jandrieu.
-
Add a human story to use case 2.6 Sharing opted-in information across platforms w3c/did-use-cases#110, by @jandrieu.
-
Add human story to 2.5 Identifiers in an ecosystem of verifiable credentials (VCs): w3c/did-use-cases#109, by @jandrieu.
-
Consider removing use case 2.4 w3c/did-use-cases#108, by @jandrieu.
-
Add human story for 2.3 Encrypted Data Vault w3c/did-use-cases#107, by @jandrieu.
-
Add human story for 2.1 Vehicle assemblies w3c/did-use-cases#106, by @jandrieu.
-
Add human story for 2.1 online shopper w3c/did-use-cases#105, by @jandrieu.
-
-
1 issue closed.
-
Package Manager / App Store and Service Endpoints w3c/did-use-cases#98.
-
-
5 issues received 25 new comments.
-
Add use case for DIDs+eIDAS w3c/did-use-cases#102 (16 comments by @agropper, @ewagner70, @jandrieu, @peacekeeper, @philarcher)
-
Add Focal Use-Case for human-centered DID interoperability: Alice Rents a Car w3c/did-use-cases#101 (4 comments by @agropper, @jandrieu, @philarcher)
-
Package Manager / App Store and Service Endpoints w3c/did-use-cases#98 (2 comments by @jandrieu, @OR13)
-
Service Endpoints & Private Data Exchange without Publishing to a Blockchain / VDR w3c/did-use-cases#99 (2 comments by @jandrieu, @OR13)
-
-
2 pull requests opened.
-
Adds use case "Public authority identity credentials (eIDAS)" w3c/did-use-cases#112, by @peacekeeper.
-
Fix USCIS name w3c/did-use-cases#104, by @peacekeeper.
-
-
2 pull requests merged.
-
Updated the respec reference w3c/did-use-cases#103.
-
Fix USCIS name w3c/did-use-cases#104.
-
-
2 pull requests received 12 new comments.
-
Adds use case "Public authority identity credentials (eIDAS)" w3c/did-use-cases#112 (4 comments by @agropper, @ewagner70, @jandrieu, @peacekeeper)
w3c/did-test-suite
-
5 issues closed.
-
PROPOSAL: The test suite will be dockerized w3c/did-test-suite#3.
-
PROPOSAL: the test suite will support strings first and callback second. w3c/did-test-suite#5.
-
Validate command cli w3c/did-test-suite#7.
-
Can we remove the BSD Digital Bazaar License? w3c/did-test-suite#8.
-
I request to be made an editor of this repo w3c/did-test-suite#10.
-
-
6 issues received 8 new comments.
-
PROPOSAL: the test suite will support strings first and callback second. w3c/did-test-suite#5 (1 comment by @OR13)
-
1 pull request merged.
-
Setup w3c/did-test-suite#9.
-
-
1 pull request received 5 new comments.
w3c/did-resolution
-
2 issues received 3 new comments.
-
w3c/did-resolution#9 (2 comments by @peacekeeper)
-
TR publications
-
3 documents published.
-
Decentralized Identifiers (DIDs) v1.0 published as a Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
Use Cases and Requirements for Decentralized Identifiers published as a Working Draft. History of Use Cases and Requirements for Decentralized Identifiers
-
DID Specification Registries published as a Note. History of DID Specification Registries
-
Participants
-
1 participant joined.
-
Shigeya Suzuki (Keio University) joined.
-
-
1 participant left.
-
Wayne Chang (Spruce Systems, Inc.) left.
-
-
2 organizations joined.
-
Spruce Systems, Inc. joined.
-
Keio University joined.
-
GitHub
w3c/did-use-cases
-
2 issues opened.
-
Add use case for DIDs+eIDAS w3c/did-use-cases#102, by @peacekeeper.
-
Add Focal Use-Case for human-centered DID interoperability: Alice Rents a Car w3c/did-use-cases#101, by @agropper.
-
-
1 issue closed.
-
Need to add coverage of portability/substitutability w3c/did-use-cases#2.
-
-
5 issues received 12 new comments.
-
Add use case for DIDs+eIDAS w3c/did-use-cases#102 (6 comments by @agropper, @ewagner70, @peacekeeper, @philarcher)
-
Add Focal Use-Case for human-centered DID interoperability: Alice Rents a Car w3c/did-use-cases#101 (3 comments by @agropper, @philarcher)
-
-
1 pull request opened.
-
Updated the respec reference w3c/did-use-cases#103, by @iherman.
-
-
2 pull requests merged.
-
Fix typos. w3c/did-use-cases#93.
-
Adding UC/Req matrix w3c/did-use-cases#92.
-
-
1 pull request received 6 new comments.
w3c/did-extensions
-
5 issues opened.
-
Can we add date added/deprecated or version added/deprecated to track addition of properties? w3c/did-extensions#143, by @kdenhartog.
-
publicKeyGpg is missing w3c/did-extensions#137, by @jonnycrunch.
-
@context should be removed from the list of properties w3c/did-extensions#131, by @peacekeeper.
-
Remove publicKeyPem w3c/did-extensions#126, by @OR13.
-
Registry should not contain service endpoint types w3c/did-extensions#125, by @peacekeeper.
-
-
4 issues closed.
-
Respec / Disambiguate "service" param from "service" prop w3c/did-extensions#113.
-
DID Resolution Request Metadata "accept" is undefined w3c/did-extensions#108.
-
DID Resolution Response Metadata: "content-type" is not defined w3c/did-extensions#109.
-
DID Resolution Response Metadata: "error" is undefined w3c/did-extensions#110.
-
-
3 issues received 11 new comments.
-
@context should be removed from the list of properties w3c/did-extensions#131 (8 comments by @jricher, @OR13, @talltree)
-
Respec / Disambiguate "service" param from "service" prop w3c/did-extensions#113 (1 comment by @OR13)
-
-
15 pull requests opened.
-
chore: test w3c/did-extensions#142, by @OR13.
-
chore: test ECHIDNA w3c/did-extensions#140, by @OR13.
-
Remove @context as Core Property w3c/did-extensions#139, by @peacekeeper.
-
Change created/updated examples to match DID Core examples. w3c/did-extensions#136, by @peacekeeper.
-
Fix links to created and updated in DID Core w3c/did-extensions#135, by @rhiaro.
-
respec: fix config for updated respec w3c/did-extensions#134, by @rhiaro.
-
Added `alsoKnownAs` to the context w3c/did-extensions#133, by @iherman.
-
Registry Updates w3c/did-extensions#132, by @OR13.
-
Corda DID method specification w3c/did-extensions#130, by @pranavkirtani88.
-
Update respec reference w3c/did-extensions#129, by @iherman.
-
tyronZIL DID-Method w3c/did-extensions#128, by @txalkan.
-
add a new did method, did:key w3c/did-extensions#127, by @brentzundel.
-
Tidy up section headings and ids w3c/did-extensions#124, by @rhiaro.
-
-
13 pull requests merged.
-
chore: test w3c/did-extensions#142.
-
Test w3c/did-extensions#141.
-
chore: test ECHIDNA w3c/did-extensions#140.
-
Corda DID method specification w3c/did-extensions#130.
-
tyronZIL DID-Method w3c/did-extensions#128.
-
respec: fix config for updated respec w3c/did-extensions#134.
-
Tidy up section headings and ids w3c/did-extensions#124.
-
Update respec reference w3c/did-extensions#129.
-
add new did method, did:grg w3c/did-extensions#119.
-
add a new did method, did:key w3c/did-extensions#127.
-
Add the Blockcore DID Method to registry list w3c/did-extensions#122.
-
Update entries for metadata properties w3c/did-extensions#120.
-
Add relative-ref DID URL parameter. w3c/did-extensions#118.
-
-
1 pull request closed.
-
Harmonize JSON and JSON-LD Registration Process w3c/did-extensions#115.
-
-
12 pull requests received 71 new comments.
-
Added `alsoKnownAs` to the context w3c/did-extensions#133 (20 comments by @iherman, @msporny, @OR13, @rhiaro)
-
Added CDDL as data definition syntax for parts of the Abstract Data Model of DID Document and registry items w3c/did-extensions#138 (10 comments by @iherman, @jonnycrunch, @OR13, @peacekeeper, @rhiaro)
-
Change created/updated examples to match DID Core examples. w3c/did-extensions#136 (10 comments by @msporny, @OR13, @peacekeeper)
-
w3c/did
-
18 issues opened.
-
Discoverability of `version-id` w3c/did#419, by @oed.
-
How should resolvers handle the accept header? w3c/did#417, by @OR13.
-
DID Document vs. DID Subject w3c/did#413, by @burnburn.
-
Ordered set of links for controllers? w3c/did#411, by @iherman.
-
Is this a misspelling? 32 vs. 33 bit for publicKeyBase58 w3c/did#405, by @iherman.
-
Precise specification of the DID Core Vocabulary w3c/did#404, by @iherman.
-
DID Core editorial review (2) w3c/did#403, by @iherman.
-
Handling additional errors in resolution/dereferencing w3c/did#402, by @clehner.
-
DID Core editorial review (1) w3c/did#401, by @iherman.
-
Incompatibilities in the fragment definitions w3c/did#400, by @iherman.
-
DID Fragment semantics cleanup needed w3c/did#399, by @iherman.
-
Abstract data model is not secure w3c/did#398, by @OR13.
-
need to clarify revocation vs. rotation w3c/did#386, by @dhh1128.
-
Are we okay with not testing DID URL's query? w3c/did#385, by @wyc.
-
16 issues closed.
-
Add public key examples using JWKs w3c/did#171.
-
Fill or remove section on DID URL Dereferencing w3c/did#364.
-
Should the DID parameters be normative in the spec? w3c/did#137.
-
Should DID support self-signed certificates? w3c/did#266.
-
Supported ciphers in a DID document w3c/did#185.
-
JSON-LD Contexts in Registry w3c/did#202.
-
Remove proof and service example from CBOR section w3c/did#338.
-
67 issues received 359 new comments.
-
Service Endpoints in the DID Doc might be an anti-pattern w3c/did#382 (71 comments by @agropper, @csuwildcat, @dhh1128, @dlongley, @jandrieu, @msporny, @OR13, @peacekeeper, @SmithSamuelM, @talltree, @wyc)
-
need to clarify revocation vs. rotation w3c/did#386 (48 comments by @agropper, @brentzundel, @dhh1128, @jandrieu, @OR13, @SmithSamuelM, @TelegramSam)
-
Proposed Appendices on DID Identification Architecture w3c/did#373 (29 comments by @dlongley, @iherman, @jandrieu, @melvincarvalho, @msporny, @peacekeeper, @rhiaro, @talltree)
-
Current language around equivalent canonical DIDs increases signature verification complexity w3c/did#421 (24 comments by @csuwildcat, @dlongley, @kdenhartog, @OR13, @peacekeeper, @tplooker, @troyronda)
-
How should resolvers handle the accept header? w3c/did#417 (18 comments by @dlongley, @iherman, @OR13, @peacekeeper)
-
DID Document vs. DID Subject w3c/did#413 (10 comments by @iherman, @melvincarvalho, @rhiaro, @talltree)
-
How to treat unknown properties w3c/did#205 (10 comments by @iherman, @jonnycrunch, @jricher, @OR13, @selfissued)
-
Should did-core restrict the use of JWK? w3c/did#240 (7 comments by @iherman, @jonnycrunch, @kdenhartog, @msporny, @OR13)
-
Getting IANA Registration for some additional CBOR Tags w3c/did#341 (5 comments by @brentzundel, @msporny, @selfissued, @wolfmcnally)
-
constraints on assertionMethod? Or a different verification purpose? w3c/did#375 (4 comments by @dhh1128, @dlongley, @talltree)
-
Is this a misspelling? 32 vs. 33 bit for publicKeyBase58 w3c/did#405 (4 comments by @iherman, @OR13)
-
Change serviceEndpoint from string-or-object to array-or-object, or just an object with a URI array property w3c/did#359 (4 comments by @csuwildcat, @msporny, @OR13)
-
Definition of the term "client" in regard to SSI principles w3c/did#261 (3 comments by @marceljay, @peacekeeper)
-
Should the DID parameters be normative in the spec? w3c/did#137 (3 comments by @iherman, @peacekeeper)
-
Specify date and time format of version-time DID parameter value w3c/did#379 (2 comments by @peacekeeper)
-
Consider EFF / ACLU objections by distinguaishing accountable vs. voluntary DIDs w3c/did#370 (2 comments by @agropper, @brentzundel)
-
Privacy Considerations - Specifically call out GDPR w3c/did#72 (2 comments by @peacekeeper, @talltree)
-
According to the working draft as of 8 June 2020, raw secp256r1 public keys must be 32-byte long w3c/did#325 (2 comments by @brentzundel, @msporny)
-
Section "Authentication and Verifiable Claims": Add language about legal identity w3c/did#390 (2 comments by @Oskar-van-Deventer, @peacekeeper)
-
Syntactially differentiate data about the DID versus application data w3c/did#85 (2 comments by @brentzundel)
-
Does DID Document metadata belong in the Document? w3c/did#65 (2 comments by @brentzundel, @peacekeeper)
-
Details on the use of method-specific DID parameters w3c/did#36 (2 comments by @brentzundel, @peacekeeper)
-
Define serializations for Numbers, Dates, other properties w3c/did#361 (2 comments by @iherman, @jonnycrunch)
-
How should contributors register the same DID Method on multiple networks? w3c/did#478 (2 comments by @OR13, @peacekeeper)
-
transfer of controllership and it's intersection with the subject of an identifier w3c/did#269 (1 comment by @kdenhartog)
-
Public key "id" and "type" members duplicate JWK "kid" and "kty" members w3c/did#170 (1 comment by @OR13)
-
Should we rename "verification relationships" to "authorization relationships"? w3c/did#318 (1 comment by @dlongley)
-
publicKeyJwk, publicKeyHex, publicKeyBase64, publicKeyBase58 missing from context. w3c/did#23 (1 comment by @OR13)
-
Section "Authentication and Verifiable Claims": Add subsection about key security w3c/did#391 (1 comment by @peacekeeper)
-
CBOR core representation is solid and should NOT be marked as at-risk w3c/did#339 (1 comment by @msporny)
-
Ability for DID in a Method to be known as more than one ID, with a canonical selection w3c/did#368 (1 comment by @csuwildcat)
-
How to mitigate the single source of failure wrt/ "Trust into the Universal Resolver"? w3c/did#249 (1 comment by @peacekeeper)
-
-
20 pull requests opened.
-
Fix echidna w3c/did#422, by @OR13.
-
updated cbor section w3c/did#420, by @jonnycrunch.
-
edit terms.html file w3c/did#418, by @anjaleeishara.
-
Forbid multiple key formats in the same verification method w3c/did#415, by @OR13.
-
Editorial updates from Ivan w3c/did#414, by @rhiaro.
-
Add `type` property w3c/did#410, by @rhiaro.
-
Allow fragments to be applied to secondary resources w3c/did#409, by @OR13.
-
Add JSON-LD Producer / Consumer details w3c/did#408, by @OR13.
-
Cleanup key representations w3c/did#407, by @OR13.
-
Add JsonWebKey2020 (JWK) key representation to did core. w3c/did#406, by @OR13.
-
Make alsoKnownAs a subsection of DID Subject. w3c/did#397, by @peacekeeper.
-
Updated the respec reference w3c/did#395, by @iherman.
-
add discussion on unknown and reserved properties w3c/did#394, by @jricher.
-
Replace "client" with more appropriate terms w3c/did#393, by @peacekeeper.
-
Specify format of version-time DID parameter value. w3c/did#392, by @peacekeeper.
-
Define alsoKnownAs property w3c/did#389, by @rhiaro.
-
Address Unknown Properties in JSON-LD w3c/did#388, by @OR13.
-
Re-add language about colons in DID syntax w3c/did#387, by @peacekeeper.
-
-
13 pull requests merged.
-
Make alsoKnownAs a subsection of DID Subject. w3c/did#397.
-
Replace "client" with more appropriate terms w3c/did#393.
-
Specify format of version-time DID parameter value. w3c/did#392.
-
Updated the respec reference w3c/did#395.
-
Define alsoKnownAs property w3c/did#389.
-
Re-add language about colons in DID syntax w3c/did#387.
-
Fill DID URL Dereferencing Section w3c/did#381.
-
Markup / structural fixes w3c/did#383.
-
Remove method-specific DID parameters w3c/did#378.
-
Update note about controller value w3c/did#371.
-
URI not URL in section 1.1 w3c/did#351.
-
Add reqlist JS for listing normative statements w3c/did#372.
-
-
4 pull requests closed.
-
edit terms.html file w3c/did#418.
-
Address Unknown Properties in JSON-LD w3c/did#388.
-
Add alsoKnownAs property w3c/did#355.
-
-
26 pull requests received 220 new comments.
-
Address Unknown Properties in JSON-LD w3c/did#388 (41 comments by @jricher, @msporny, @OR13, @peacekeeper, @selfissued, @tplooker)
-
add discussion on unknown and reserved properties w3c/did#394 (37 comments by @jricher, @msporny, @OR13)
-
Add `type` property w3c/did#410 (26 comments by @agropper, @brentzundel, @dhh1128, @jandrieu, @jonnycrunch, @kdenhartog, @melvincarvalho, @msporny, @talltree)
-
updated cbor section w3c/did#420 (15 comments by @iherman, @jonnycrunch, @OR13, @peacekeeper, @rhiaro)
-
Define the JSON representation as JSON (without excluding directives) w3c/did#396 (15 comments by @jricher, @msporny, @OR13, @peacekeeper)
-
Forbid multiple key formats in the same verification method w3c/did#415 (8 comments by @iherman, @msporny, @OR13)
-
Add JsonWebKey2020 (JWK) key representation to did core. w3c/did#406 (6 comments by @msporny, @OR13)
-
Adds a note about controllership and and ownership of the identifier w3c/did#352 (4 comments by @kdenhartog, @msporny)
-
Update context requirements for JSON-LD producers/consumers. w3c/did#362 (4 comments by @dlongley, @msporny)
-
respec: replace WG info with 'group' property and fix internal refs w3c/did#412 (1 comment by @iherman)
-
w3c/did-test-suite
-
2 issues opened.
-
I request to be made an editor of this repo w3c/did-test-suite#10, by @OR13.
-
Can we remove the BSD Digital Bazaar License? w3c/did-test-suite#8, by @OR13.
-
-
3 issues received 3 new comments.
-
PROPOSAL: the test suite will support strings first and callback second. w3c/did-test-suite#5 (1 comment by @peacekeeper)
-
-
1 pull request received 6 new comments.
w3c/did-resolution
-
1 issue opened.
-
Streaming resolution w3c/did-resolution#57, by @clehner.
-
-
1 issue closed.
-
DID resolution context URL does not exist w3c/did-resolution#54.
-
-
2 issues received 3 new comments.
-
1 pull request opened.
-
Add context w3c/did-resolution#56, by @OR13.
-
-
1 pull request merged.
-
Add context w3c/did-resolution#56.
-
-
2 pull requests received 5 new comments.
w3c/did-imp-guide
-
1 issue opened.
-
Add implementation details for DIDs+eIDAS w3c/did-imp-guide#2, by @peacekeeper.
-
-
1 issue received 1 new comment.
Participants
-
3 participants joined.
-
Ahamed Azeem (Danube Tech GmbH) joined.
-
Cihan Saglam (Danube Tech GmbH) joined.
-
Bernhard Fuchs (Danube Tech GmbH) joined.
-
GitHub
w3c/did
-
12 issues opened.
-
Normative statements review w3c/did#384, by @rhiaro.
-
Service Endpoints in the DID Doc might be an anti-pattern w3c/did#382, by @msporny.
-
Why DID Document streaming (`resolveStream`)? w3c/did#380, by @wyc.
-
Remove publicKeyPem from did core and did spec tests w3c/did#374, by @OR13.
-
Proposed Appendices on DID Identification Architecture w3c/did#373, by @talltree.
-
Move Issues from Spec Registries to DID Core w3c/did#367, by @OR13.
-
Verifiable credential creation flow implementation w3c/did#366, by @mehranshakeri.
-
-
10 issues closed.
-
Verifiable credential creation flow implementation w3c/did#366.
-
Add sections on DID Resolution w3c/did#198.
-
Add relative-ref DID URL parameter w3c/did#349.
-
46 issues received 254 new comments.
-
Service Endpoints in the DID Doc might be an anti-pattern w3c/did#382 (56 comments by @agropper, @bumblefudge, @csuwildcat, @dhh1128, @dlongley, @jonnycrunch, @msporny, @mwklein, @OR13, @peacekeeper, @wyc)
-
Change serviceEndpoint from string-or-object to array-or-object, or just an object with a URI array property w3c/did#359 (36 comments by @agropper, @csuwildcat, @dhh1128, @dlongley, @OR13)
-
Supported ciphers in a DID document w3c/did#185 (20 comments by @baha-ai, @dlongley, @llorllale, @OR13)
-
Proposed Appendices on DID Identification Architecture w3c/did#373 (17 comments by @agropper, @iherman, @kdenhartog, @msporny, @peacekeeper, @talltree)
-
How should contributors register the same DID Method on multiple networks? w3c/did#478 (16 comments by @dhh1128, @msporny, @OR13, @peacekeeper, @rhiaro, @talltree)
-
Ability for DID in a Method to be known as more than one ID, with a canonical selection w3c/did#368 (13 comments by @csuwildcat, @msporny, @OR13, @peacekeeper, @philarcher)
-
Public key "id" and "type" members duplicate JWK "kid" and "kty" members w3c/did#170 (7 comments by @kdenhartog, @OR13, @selfissued)
-
Specifications needed for supported key representations publicKeyJwk, publcKeyPem, and publicKeyBase58 w3c/did#281 (5 comments by @brentzundel, @msporny, @OR13)
-
Create a seperate top level block for defining proof purposes w3c/did#294 (4 comments by @brentzundel, @dlongley, @kdenhartog, @tplooker)
-
According to the working draft as of 8 June 2020, raw secp256r1 public keys must be 32-byte long w3c/did#325 (4 comments by @msporny, @OR13, @sammotic)
-
Consider EFF / ACLU objections by distinguaishing accountable vs. voluntary DIDs w3c/did#370 (3 comments by @agropper, @wyc)
-
Privacy Considerations - Specifically call out GDPR w3c/did#72 (3 comments by @iherman, @rhiaro, @selfissued)
-
Impossible DID URL ABNF using eager evaluation without backtracking? w3c/did#344 (2 comments by @peacekeeper, @wyc)
-
publicKeyJwk, publicKeyHex, publicKeyBase64, publicKeyBase58 missing from context. w3c/did#23 (2 comments by @OR13)
-
Verifiable credential creation flow implementation w3c/did#366 (2 comments by @mehranshakeri, @peacekeeper)
-
transfer of controllership and it's intersection with the subject of an identifier w3c/did#269 (1 comment by @kdenhartog)
-
Syntactially differentiate data about the DID versus application data w3c/did#85 (1 comment by @peacekeeper)
-
Clear explanation on how can A DID have more than one controller w3c/did#260 (1 comment by @talltree)
-
Should we rename "verification relationships" to "authorization relationships"? w3c/did#318 (1 comment by @dlongley)
-
CBOR core representation is solid and should NOT be marked as at-risk w3c/did#339 (1 comment by @OR13)
-
Inconsistency between using key or value to define different types w3c/did#358 (1 comment by @brentzundel)
-
Update data model parts of spec to refer to Infra specification w3c/did#328 (1 comment by @brentzundel)
-
-
8 pull requests opened.
-
Markup / structural fixes w3c/did#383, by @rhiaro.
-
Fill DID URL Dereferencing Section w3c/did#381, by @wyc.
-
Remove method-specific DID parameters w3c/did#378, by @peacekeeper.
-
Add examples w3c/did#377, by @OR13.
-
Clarify id prop language to allow equivalent DID values w3c/did#376, by @csuwildcat.
-
Add reqlist JS for listing normative statements w3c/did#372, by @rhiaro.
-
Update note about controller value w3c/did#371, by @rhiaro.
-
-
7 pull requests merged.
-
Add examples w3c/did#377.
-
Simplify DID URL ABNF w3c/did#360.
-
Add 'relative-ref' DID URL parameter. Fixes #349. w3c/did#357.
-
Restructure Core Properties section w3c/did#345.
-
-
2 pull requests closed.
-
Added DID resolution and dereferencing contracts. w3c/did#253.
-
1 pull request reopened.
-
Clarify id prop language to allow equivalent DID values w3c/did#376, by @csuwildcat.
-
-
18 pull requests received 111 new comments.
-
Update note about controller value w3c/did#371 (35 comments by @agropper, @brentzundel, @dlongley, @jandrieu, @msporny, @rhiaro)
-
Clarify id prop language to allow equivalent DID values w3c/did#376 (20 comments by @brentzundel, @csuwildcat, @dlongley, @kdenhartog, @msporny, @OR13, @peacekeeper)
-
Restructure Core Properties section w3c/did#345 (11 comments by @dlongley, @Fak3, @msporny, @rhiaro)
-
Move "created" and "updated" from Core Properties to DID document metadata w3c/did#365 (7 comments by @msporny, @peacekeeper)
-
Update context requirements for JSON-LD producers/consumers. w3c/did#362 (6 comments by @dlongley, @msporny, @OR13, @peacekeeper)
-
Adds a note about controllership and and ownership of the identifier w3c/did#352 (4 comments by @kdenhartog, @msporny)
-
Define resolution function with data types, property values, and full metadata structures w3c/did#299 (2 comments by @msporny)
-
Remove unsubstantiated statement about protecting against attacks when compromised w3c/did#369 (1 comment by @msporny)
-
w3c/did-extensions
-
8 issues opened.
-
Respec / Disambiguate "service" param from "service" prop w3c/did-extensions#113, by @OR13.
-
DID Resolution Response Metadata: "unauthorized" is undefined w3c/did-extensions#112, by @OR13.
-
DID Resolution Response Metadata: "invalid-did" is undefined w3c/did-extensions#111, by @OR13.
-
DID Resolution Response Metadata: "error" is undefined w3c/did-extensions#110, by @OR13.
-
DID Resolution Response Metadata: "content-type" is not defined w3c/did-extensions#109, by @OR13.
-
DID Resolution Request Metadata "accept" is undefined w3c/did-extensions#108, by @OR13.
-
Unresolved issues from CCG did-method-registry repo w3c/did-extensions#105, by @kimdhamilton.
-
JsonWebKey2020 might get renamed in the future w3c/did-extensions#101, by @OR13.
-
-
7 issues closed.
-
Merge W3C CCG DID Method Registry history into this repo w3c/did-extensions#72.
-
Need a statement about lack of curation w3c/did-extensions#56.
-
Define sidetree context w3c/did-extensions#19.
-
Add Example to The Properties Extension Registry w3c/did-extensions#31.
-
Add JsonWebKey2020 to allow for algorithm agnostic key usage in did documents w3c/did-extensions#46.
-
The property "jws" in the input was not defined in the context. w3c/did-extensions#55.
-
Set up Echidna for auto-publication of DID Spec Registries w3c/did-extensions#68.
-
-
24 issues received 41 new comments.
-
Respec / Disambiguate "service" param from "service" prop w3c/did-extensions#113 (5 comments by @OR13, @rhiaro)
-
Merge W3C CCG DID Method Registry history into this repo w3c/did-extensions#72 (4 comments by @msporny, @OR13)
-
Explanation on the DID Methods in the registries' document w3c/did-extensions#83 (4 comments by @iherman, @OR13)
-
Discuss schema.org, activitypub, VC and DID JSON-LD overlap w3c/did-extensions#92 (2 comments by @OR13, @rhiaro)
-
JsonWebKey2020 might get renamed in the future w3c/did-extensions#101 (2 comments by @msporny, @OR13)
-
Add JsonWebKey2020 to allow for algorithm agnostic key usage in did documents w3c/did-extensions#46 (1 comment by @OR13)
-
Add note about deprecating publicKey in favor of verificationMethod w3c/did-extensions#54 (1 comment by @OR13)
-
The property "jws" in the input was not defined in the context. w3c/did-extensions#55 (1 comment by @OR13)
-
Set up Echidna for auto-publication of DID Spec Registries w3c/did-extensions#68 (1 comment by @OR13)
-
These registries needs and Expert Review Required section. w3c/did-extensions#81 (1 comment by @OR13)
-
Add a column for third party security audit to DID Method Registry? w3c/did-extensions#91 (1 comment by @OR13)
-
-
16 pull requests opened.
-
add a new DID method did:schema to main index.html w3c/did-extensions#123, by @MajdT51.
-
Add the Blockcore DID Method to registry list w3c/did-extensions#122, by @sondreb.
-
Fix broken link w3c/did-extensions#121, by @ilanolkies.
-
Update entries for metadata properties w3c/did-extensions#120, by @peacekeeper.
-
add new did method, did:grg w3c/did-extensions#119, by @GrgChain.
-
Add relative-ref DID URL parameter. w3c/did-extensions#118, by @peacekeeper.
-
add a new DID method did:schema w3c/did-extensions#117, by @MajdT51.
-
Remove proof property from did document w3c/did-extensions#116, by @OR13.
-
Harmonize JSON and JSON-LD Registration Process w3c/did-extensions#115, by @OR13.
-
Cleaning / html bugs w3c/did-extensions#114, by @OR13.
-
update Jolocom spec link w3c/did-extensions#107, by @PeterTheOne.
-
Add five DID methods w3c/did-extensions#106, by @OntologyTech.
-
Add commit history from ccg w3c/did-extensions#104, by @OR13.
-
Add bba DID method w3c/did-extensions#103, by @atz3n.
-
add did:morpheus: method w3c/did-extensions#100, by @mudlee.
-
Add X25519KeyAgreementKey2019 to did-v1.jsonld w3c/did-extensions#99, by @OR13.
-
-
14 pull requests merged.
-
add a new DID method did:schema to main index.html w3c/did-extensions#123.
-
add a new DID method did:schema w3c/did-extensions#117.
-
Fix broken link w3c/did-extensions#121.
-
Remove proof property from did document w3c/did-extensions#116.
-
Add five DID methods w3c/did-extensions#106.
-
update Jolocom spec link w3c/did-extensions#107.
-
Add commit history from ccg w3c/did-extensions#104.
-
Cleaning / html bugs w3c/did-extensions#114.
-
Add bba DID method w3c/did-extensions#103.
-
add did:morpheus: method w3c/did-extensions#100.
-
Add X25519KeyAgreementKey2019 to did-v1.jsonld w3c/did-extensions#99.
-
add did:vaa: method w3c/did-extensions#98.
-
Add NEAR DID Method w3c/did-extensions#97.
-
Add support for JsonWebKey2020 and JsonWebSignature2020 w3c/did-extensions#96.
-
-
1 pull request reopened.
-
add a new DID method did:schema w3c/did-extensions#117, by @MajdT51.
-
-
15 pull requests received 124 new comments.
-
Harmonize JSON and JSON-LD Registration Process w3c/did-extensions#115 (58 comments by @bumblefudge, @csuwildcat, @dhh1128, @msporny, @OR13, @selfissued, @SmithSamuelM, @talltree, @thereisnogabe)
-
Add support for JsonWebKey2020 and JsonWebSignature2020 w3c/did-extensions#96 (28 comments by @dlongley, @gjgd, @msporny, @OR13, @peacekeeper, @tplooker)
-
add a new DID method did:schema w3c/did-extensions#117 (11 comments by @csuwildcat, @dhh1128, @jonnycrunch, @jpbu, @kdenhartog, @MajdT51, @OR13, @thereisnogabe)
-
Add relative-ref DID URL parameter. w3c/did-extensions#118 (6 comments by @msporny, @OR13, @peacekeeper)
-
Add X25519KeyAgreementKey2019 to did-v1.jsonld w3c/did-extensions#99 (2 comments by @msporny, @OR13)
-
w3c/did-test-suite
-
2 issues opened.
-
Validate command cli w3c/did-test-suite#7, by @gspmishra.
-
Test suite URL is not correct w3c/did-test-suite#6, by @OR13.
-
-
2 issues closed.
-
Test suite URL is not correct w3c/did-test-suite#6.
-
-
3 issues received 3 new comments.
-
PROPOSAL: The test suite structured input will be in yaml and structured output will be in json w3c/did-test-suite#4 (1 comment by @OR13)
w3c/did-use-cases
-
6 issues opened.
-
Service Endpoints & Private Data Exchange without Publishing to a Blockchain / VDR w3c/did-use-cases#99, by @OR13.
-
Package Manager / App Store and Service Endpoints w3c/did-use-cases#98, by @OR13.
-
DIDComm and serviceEndpoints w3c/did-use-cases#97, by @OR13.
-
Add non-public key verification w3c/did-use-cases#96, by @jandrieu.
-
Add WebAuthN use case w3c/did-use-cases#95, by @jandrieu.
-
Add M-of-N use case w3c/did-use-cases#94, by @jandrieu.
-
-
1 issue closed.
-
Consider use cases from key representation discussion in did-core w3c/did-use-cases#52.
-
-
6 issues received 27 new comments.
-
Service Endpoints & Private Data Exchange without Publishing to a Blockchain / VDR w3c/did-use-cases#99 (8 comments by @agropper, @dlongley, @OR13)
-
Package Manager / App Store and Service Endpoints w3c/did-use-cases#98 (3 comments by @bumblefudge, @OR13)
-
Consider use cases from key representation discussion in did-core w3c/did-use-cases#52 (1 comment by @jandrieu)
-
1 pull request opened.
-
Add didcomm usecase w3c/did-use-cases#100, by @OR13.
-
-
3 pull requests received 13 new comments.
w3c/did-rubric
-
1 issue received 1 new comment.
TR publications
-
8 documents published.
-
Decentralized Identifiers (DIDs) v1.0 published 7 times as a Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
Use Cases and Requirements for Decentralized Identifiers published as a Working Draft. History of Use Cases and Requirements for Decentralized Identifiers
-
Participants
-
1 chair appointed.
-
Daniel Burnett became a chair.
-
-
1 chair stepped down.
-
Daniel Burnett stepped down as a chair.
-
-
3 participants joined.
-
Lucian Lauritz (Fiserv) joined.
-
Kristina Yasuda (Microsoft Corporation) joined.
-
Daniel Burnett (W3C Invited Experts) joined.
-
-
2 participants left.
-
Sam Curren (Sovrin Foundation) left.
-
Daniel Burnett (W3C Invited Experts) left.
-
-
1 organization joined.
-
Fiserv joined.
-
GitHub
w3c/did
-
13 issues opened.
-
Fill or remove section on DID URL Dereferencing w3c/did#364, by @peacekeeper.
-
Clarify Authorization requirements. w3c/did#363, by @Fak3.
-
Define serializations for Numbers, Dates, other properties w3c/did#361, by @jricher.
-
Restrict the number of key representation members w3c/did#356, by @OR13.
-
Add relative-ref DID URL parameter w3c/did#349, by @peacekeeper.
-
Impossible DID URL ABNF using eager evaluation without backtracking? w3c/did#344, by @wyc.
-
Getting IANA Registration for some additional CBOR Tags w3c/did#341, by @ChristopherA.
-
Add COSE key format example into CBOR section w3c/did#340, by @jonnycrunch.
-
Remove proof and service example from CBOR section w3c/did#338, by @jonnycrunch.
-
-
13 issues closed.
-
DID Syntax w3c/did#333.
-
Need term for relying party w3c/did#248.
-
Use case for service endpoints / did parameters w3c/did#327.
-
Document Structure w3c/did#95.
-
List of early implementations conforming to spec? w3c/did#258.
-
tracking revocation of public keys w3c/did#75.
-
Standardize the key revocation list w3c/did#14.
-
When should did parameters be dropped? w3c/did#336.
-
-
50 issues received 175 new comments.
-
Should did-core restrict the use of JWK? w3c/did#240 (16 comments by @baha-ai, @dlongley, @kdenhartog, @msporny, @OR13)
-
Cheap DIDs and the option to migrate DIDs between ledgers using standard DID Deprecation Registries w3c/did#33 (16 comments by @dmitrizagidulin, @iherman, @msporny, @OR13, @peacekeeper, @rhiaro)
-
Impossible DID URL ABNF using eager evaluation without backtracking? w3c/did#344 (12 comments by @jonnycrunch, @peacekeeper, @wyc)
-
When is a DID subject not a DID controller (if ever)? w3c/did#122 (8 comments by @dlongley, @dmitrizagidulin, @jandrieu, @msporny, @rhiaro, @talltree)
-
Privacy Considerations for service endpoints w3c/did#324 (7 comments by @agropper, @kdenhartog, @OR13, @talltree)
-
Getting IANA Registration for some additional CBOR Tags w3c/did#341 (6 comments by @ChristopherA, @jonnycrunch, @msporny, @selfissued)
-
Define serializations for Numbers, Dates, other properties w3c/did#361 (5 comments by @jricher, @msporny, @OR13)
-
Should the DID parameters be normative in the spec? w3c/did#137 (5 comments by @iherman, @msporny, @peacekeeper)
-
When should did parameters be dropped? w3c/did#337 (5 comments by @brentzundel, @OR13, @peacekeeper, @tplooker, @wyc)
-
According to the working draft as of 8 June 2020, raw secp256r1 public keys must be 32-byte long w3c/did#325 (5 comments by @msporny, @OR13, @selfissued)
-
CBOR core representation is solid and should NOT be marked as at-risk w3c/did#339 (4 comments by @burnburn, @msporny, @OR13)
-
Unclear which verification methods are authorized for did document operations w3c/did#195 (4 comments by @dlongley, @OR13, @peacekeeper, @tplooker)
-
Does DID Document metadata belong in the Document? w3c/did#65 (2 comments by @msporny, @peacekeeper)
-
How to mitigate the single source of failure wrt/ "Trust into the Universal Resolver"? w3c/did#249 (2 comments by @msporny, @peacekeeper)
-
Update data model parts of spec to refer to Infra specification w3c/did#328 (2 comments by @msporny, @rhiaro)
-
Inconsistency between using key or value to define different types w3c/did#358 (2 comments by @dlongley, @msporny)
-
transfer of controllership and it's intersection with the subject of an identifier w3c/did#269 (2 comments by @jandrieu, @kdenhartog)
-
Confusing example in the section 3.2.1 - DID parameters are URI query strings w3c/did#353 (1 comment by @peacekeeper)
-
-
15 pull requests opened.
-
Update context requirements for JSON-LD producers/consumers. w3c/did#362, by @dlongley.
-
Simplify DID URL ABNF w3c/did#360, by @wyc.
-
Add 'relative-ref' DID URL parameter. Fixes #349. w3c/did#357, by @peacekeeper.
-
Add alsoKnownAs property w3c/did#355, by @talltree.
-
Remove obsolete sentence w3c/did#354, by @Fak3.
-
URI not URL in section 1.1 w3c/did#351, by @philarcher.
-
Swap relying party for requesting party Will fix #248 w3c/did#350, by @philarcher.
-
add representation property w3c/did#348, by @talltree.
-
Add Metadata section based on infra data structures. w3c/did#347, by @msporny.
-
Fix spelling. w3c/did#346, by @davidlehn.
-
Restructure Core Properties section w3c/did#345, by @rhiaro.
-
Added missing reference to the diagram in ECHIDNA w3c/did#343, by @iherman.
-
[WIP] Update specification to use INFRA w3c/did#342, by @msporny.
-
12 pull requests merged.
-
Add Metadata section based on infra data structures. w3c/did#347.
-
Remove obsolete sentence w3c/did#354.
-
Fix spelling. w3c/did#346.
-
[WIP] Update specification to use INFRA w3c/did#342.
-
full editing pass on all terms w3c/did#335.
-
Added missing reference to the diagram in ECHIDNA w3c/did#343.
-
Fixed ABNF for method-specific-id of DID Syntax w3c/did#334.
-
Put key points up front w3c/did#267.
-
Support resolve() and resolveStream() functions w3c/did#331.
-
minor editorial fixes to VR examples w3c/did#330.
-
4 pull requests closed.
-
Define simple type-less resolution function w3c/did#295.
-
1 pull request reopened.
-
Simplify DID URL ABNF w3c/did#360, by @wyc.
-
-
22 pull requests received 131 new comments.
-
add representation property w3c/did#348 (34 comments by @brentzundel, @iherman, @kdenhartog, @msporny, @OR13, @peacekeeper, @talltree)
-
Add alsoKnownAs property w3c/did#355 (19 comments by @ChristopherA, @dlongley, @dmitrizagidulin, @iherman, @kdenhartog, @msporny, @OR13, @talltree)
-
Add Metadata section based on infra data structures. w3c/did#347 (18 comments by @jricher, @msporny, @selfissued)
-
URI not URL in section 1.1 w3c/did#351 (10 comments by @dlongley, @iherman, @jonnycrunch, @msporny, @philarcher, @talltree)
-
Adds a note about controllership and and ownership of the identifier w3c/did#352 (8 comments by @Fak3, @jandrieu, @kdenhartog, @msporny)
-
[WIP] Update specification to use INFRA w3c/did#342 (6 comments by @dlongley, @dmitrizagidulin, @iherman, @msporny)
-
Update context requirements for JSON-LD producers/consumers. w3c/did#362 (4 comments by @dlongley, @jricher)
-
Define resolution function with data types, property values, and full metadata structures w3c/did#299 (3 comments by @msporny, @peacekeeper, @selfissued)
-
Added DID resolution and dereferencing contracts. w3c/did#253 (2 comments by @msporny, @peacekeeper)
-
Define resolution function with data types and property values w3c/did#297 (2 comments by @msporny, @peacekeeper)
-
Define resolution function with data types, property values, and simple metadata structures w3c/did#298 (1 comment by @msporny)
-
w3c/did-extensions
-
9 issues opened.
-
`did:github` has been removed from the registry w3c/did-extensions#94, by @OR13.
-
Define Trademarked and Branded DID Method Registry Policy w3c/did-extensions#93, by @OR13.
-
Discuss schema.org, activitypub, VC and DID JSON-LD overlap w3c/did-extensions#92, by @OR13.
-
Add a column for third party security audit to DID Method Registry? w3c/did-extensions#91, by @OR13.
-
Explanation on the DID Methods in the registries' document w3c/did-extensions#83, by @iherman.
-
Remove CBOR `equivalence` mappings w3c/did-extensions#82, by @jonnycrunch.
-
These registries needs and Expert Review Required section. w3c/did-extensions#81, by @jonnycrunch.
-
Define sameAs w3c/did-extensions#80, by @OR13.
-
A Cryptographic Golem has been created w3c/did-extensions#79, by @jonnycrunch.
-
-
4 issues closed.
-
Add Example to The Parameters Extension Registry w3c/did-extensions#30.
-
URLs and references in schemas cannot be resolved w3c/did-extensions#70.
-
It is not possible to checkout did-spec-registries on a Windows machine w3c/did-extensions#71.
-
Fix JSON-LD Context Links w3c/did-extensions#3.
-
-
8 issues received 20 new comments.
-
URLs and references in schemas cannot be resolved w3c/did-extensions#70 (6 comments by @OR13, @veikkoeeva)
-
Add transform-keys=jwks parameter for use with OIDC SIOP w3c/did-extensions#66 (5 comments by @awoie, @OR13, @peacekeeper)
-
Add a column for third party security audit to DID Method Registry? w3c/did-extensions#91 (2 comments by @OR13, @peacekeeper)
-
It is not possible to checkout did-spec-registries on a Windows machine w3c/did-extensions#71 (1 comment by @OR13)
-
-
11 pull requests opened.
-
add did:vaa: method w3c/did-extensions#98, by @caict-develop-zhangbo.
-
Add NEAR DID Method w3c/did-extensions#97, by @OntologyTech.
-
Add support for JsonWebKey2020 and JsonWebSignature2020 w3c/did-extensions#96, by @OR13.
-
Update README.md: fix draft link w3c/did-extensions#95, by @davidlj95.
-
Add did:twit method w3c/did-extensions#90, by @thereisnogabe.
-
Change "resolution options" to "resolution input metadata" w3c/did-extensions#89, by @peacekeeper.
-
Remove json schema requirement for registries w3c/did-extensions#88, by @OR13.
-
Try to fix echidna w3c/did-extensions#87, by @OR13.
-
Fix windows pathing issue w3c/did-extensions#86, by @OR13.
-
Add initial-state and transform-keys DID parameters. Fixes #30. w3c/did-extensions#85, by @peacekeeper.
-
Limit JSON Schema requirement to properties w3c/did-extensions#84, by @peacekeeper.
-
-
8 pull requests merged.
-
Add did:twit method w3c/did-extensions#90.
-
Update README.md: fix draft link w3c/did-extensions#95.
-
added `blockchainAccountId` to core context w3c/did-extensions#73.
-
Change "resolution options" to "resolution input metadata" w3c/did-extensions#89.
-
Remove json schema requirement for registries w3c/did-extensions#88.
-
Add initial-state and transform-keys DID parameters. Fixes #30. w3c/did-extensions#85.
-
Try to fix echidna w3c/did-extensions#87.
-
Fix windows pathing issue w3c/did-extensions#86.
-
-
2 pull requests closed.
-
Limit JSON Schema requirement to properties w3c/did-extensions#84.
-
OMN DID Method w3c/did-extensions#74.
-
-
7 pull requests received 73 new comments.
-
added `blockchainAccountId` to core context w3c/did-extensions#73 (36 comments by @awoie, @burnburn, @csuwildcat, @kenhuangus, @kimdhamilton, @msporny, @oed, @OR13, @peacekeeper, @pedrouid, @talltree, @Therecanbeonlyone1969)
-
Add did:twit method w3c/did-extensions#90 (18 comments by @msporny, @OR13, @peacekeeper, @talltree, @thereisnogabe)
-
Add support for JsonWebKey2020 and JsonWebSignature2020 w3c/did-extensions#96 (8 comments by @kdenhartog, @msporny, @OR13, @tplooker)
-
Limit JSON Schema requirement to properties w3c/did-extensions#84 (3 comments by @OR13, @peacekeeper)
-
Remove json schema requirement for registries w3c/did-extensions#88 (2 comments by @OR13, @peacekeeper)
-
w3c/did-use-cases
-
4 issues closed.
-
Describe relationship between DID Methods and DID Authentication in Use Cases document w3c/did-use-cases#13.
-
Add DHS use case(s) w3c/did-use-cases#81.
-
Relying Party terminology could confuse things w3c/did-use-cases#39.
-
New Use Case Proposal: Blending DIDs with X.509 w3c/did-use-cases#59.
-
-
1 issue reopened.
-
rename master branch w3c/did-use-cases#88, by @brentzundel.
-
-
6 issues received 9 new comments.
-
Describe relationship between DID Methods and DID Authentication in Use Cases document w3c/did-use-cases#13 (2 comments by @jandrieu, @philarcher)
-
-
2 pull requests opened.
-
Fix typos. w3c/did-use-cases#93, by @davidlehn.
-
Adding UC/Req matrix w3c/did-use-cases#92, by @philarcher.
-
-
2 pull requests merged.
-
Relying Party -> Requesting Party w3c/did-use-cases#84.
-
Andrieu dhs use cases w3c/did-use-cases#91.
-
-
1 pull request closed.
-
A new IoT usecase w3c/did-use-cases#70.
-
-
3 pull requests received 9 new comments.
w3c/did-resolution
-
1 issue closed.
-
Change key terms to lowercase w3c/did-resolution#48.
-
w3c/did-rubric
-
2 issues received 3 new comments.
-
1 pull request opened.
-
Initialize with content from first draft w3c/did-rubric#4, by @rhiaro.
-
-
1 pull request received 2 new comments.
w3c/did-test-suite
-
3 issues opened.
-
PROPOSAL: the test suite will support strings first and callback second. w3c/did-test-suite#5, by @OR13.
-
PROPOSAL: The test suite structured input will be in yaml and structured output will be in json w3c/did-test-suite#4, by @OR13.
-
PROPOSAL: The test suite will be dockerized w3c/did-test-suite#3, by @OR13.
-
-
1 issue received 2 new comments.
-
PROPOSAL: The test suite structured input will be in yaml and structured output will be in json w3c/did-test-suite#4 (2 comments by @iherman, @OR13)
-
TR publications
-
7 documents published.
-
Use Cases and Requirements for Decentralized Identifiers published 3 times as a Working Draft. History of Use Cases and Requirements for Decentralized Identifiers
-
Decentralized Identifiers (DIDs) v1.0 published 3 times as a Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
DID Specification Registries published as a Note. History of DID Specification Registries
-
Participants
-
5 participants joined.
-
Junjie QU (W3C Invited Experts) joined.
-
Namseok Ko (Electronics and Telecommunications Research Institute (ETRI)) joined.
-
Xin Kang (Huawei) joined.
-
Haiguang Wang (Huawei) joined.
-
Wayne Chang (Spruce Systems, Inc.) joined.
-
-
1 organization joined.
-
Huawei joined.
-
GitHub
w3c/did
-
14 issues opened.
-
When should did parameters be dropped? w3c/did#337, by @OR13.
-
When should did parameters be dropped? w3c/did#336, by @OR13.
-
DID Syntax w3c/did#333, by @Crenshinibon.
-
rename master branch w3c/did#332, by @brentzundel.
-
Additional information/proxy service type w3c/did#329, by @dlongley.
-
Update data model parts of spec to refer to Infra specification w3c/did#328, by @msporny.
-
Use case for service endpoints / did parameters w3c/did#327, by @OR13.
-
Privacy Considerations for service endpoints w3c/did#324, by @agropper.
-
Add links to the definition of "lowercase" w3c/did#313, by @xfq.
-
Move term definitions into the term document w3c/did#311, by @jandrieu.
-
-
26 issues closed.
-
Remove uses of publicKeyHex w3c/did#280.
-
Decoupling DID Core spec from LD-Proof / LDS specs w3c/did#154.
-
Explain RsaSignature2018 w3c/did#10.
-
Move term definitions into the term document w3c/did#311.
-
Define terminology for properties and values w3c/did#204.
-
Add links to the definition of "lowercase" w3c/did#313.
-
publicKeyHex format unused by spec currently w3c/did#236.
-
Add section on extensibility and conformance w3c/did#207.
-
Where will the DID contexts(s) live? w3c/did#5.
-
Remove `proof` w3c/did#293.
-
did parameter equivilance w3c/did#270.
-
72 issues received 267 new comments.
-
Need term for relying party w3c/did#248 (17 comments by @agropper, @brentzundel, @ChristopherA, @Identitywoman, @jandrieu, @msporny, @OR13, @philarcher, @talltree)
-
Create a seperate top level block for defining proof purposes w3c/did#294 (17 comments by @dlongley, @kdenhartog, @OR13, @rhiaro, @tplooker)
-
Add support for ethereumAddress public key type in @context w3c/did#55 (12 comments by @awoie, @brentzundel, @jonnycrunch, @msporny, @OR13)
-
Details on the use of method-specific DID parameters w3c/did#36 (8 comments by @csuwildcat, @kdenhartog, @OR13, @peacekeeper, @talltree)
-
Decoupling DID Core spec from LD-Proof / LDS specs w3c/did#154 (8 comments by @awoie, @brentzundel, @jonnycrunch, @msporny, @OR13)
-
Clarification on what DIDs might identify w3c/did#199 (8 comments by @brentzundel, @dlongley, @peacekeeper, @talltree)
-
tracking revocation of public keys w3c/did#75 (8 comments by @awoie, @burnburn, @dlongley, @msporny, @OR13, @selfissued)
-
How to treat unknown properties w3c/did#205 (8 comments by @dlongley, @jonnycrunch, @OR13, @Oskar-van-Deventer, @rhiaro, @selfissued)
-
Horizontal Review: Internationalization self test w3c/did#104 (6 comments by @brentzundel, @iherman, @xfq)
-
Should DID support self-signed certificates? w3c/did#266 (6 comments by @DurandA, @kdenhartog, @OR13, @selfissued, @tplooker)
-
How to mitigate the single source of failure wrt/ "Trust into the Universal Resolver"? w3c/did#249 (6 comments by @OR13, @peacekeeper, @SmithSamuelM)
-
Should we rename "verification relationships" to "authorization relationships"? w3c/did#318 (6 comments by @csuwildcat, @dlongley, @OR13, @peacekeeper)
-
Privacy Considerations - Specifically call out GDPR w3c/did#72 (6 comments by @agropper, @rhiaro, @talltree)
-
Should we be allowed to multi-reference keys through did documents? w3c/did#301 (5 comments by @kdenhartog, @peacekeeper)
-
invert mapping between proof purposes and verification methods? w3c/did#273 (5 comments by @brentzundel, @dhh1128, @kdenhartog, @OR13)
-
Unclear which verification methods are authorized for did document operations w3c/did#195 (5 comments by @dlongley, @kdenhartog, @msporny, @peacekeeper)
-
Include discussion of eIDAS levels-of-assurance w3c/did#151 (4 comments by @awoie, @nalamillo, @OR13, @peacekeeper)
-
publicKeyJwk, publicKeyHex, publicKeyBase64, publicKeyBase58 missing from context. w3c/did#23 (4 comments by @kdenhartog, @msporny, @OR13, @rhiaro)
-
publicKeyHex format unused by spec currently w3c/did#236 (4 comments by @kdenhartog, @msporny, @OR13)
-
How are we distinguishing "core" properties vs "extension" properties? w3c/did#317 (3 comments by @brentzundel, @kdenhartog, @rhiaro)
-
Underspecified statement on combining timestamps with signatures w3c/did#178 (3 comments by @brentzundel, @rhiaro, @yancyribbens)
-
DIDs and JOSE: publicKey.id and publicKey.publicKeyJwk.kid w3c/did#259 (3 comments by @brentzundel, @msporny, @OR13)
-
Cheap DIDs and the option to migrate DIDs between ledgers using standard DID Deprecation Registries w3c/did#33 (3 comments by @iherman, @OR13)
-
We should find a better term than "DID Registry" and better define what it refers to w3c/did#162 (2 comments by @brentzundel, @rhiaro)
-
Replace RsaSignature2017 by a standard JWA signature w3c/did#9 (2 comments by @brentzundel, @msporny)
-
Specifications needed for supported key representations publicKeyJwk, publcKeyPem, and publicKeyBase58 w3c/did#281 (2 comments by @OR13)
-
Should the DID parameters be normative in the spec? w3c/did#137 (2 comments by @kdenhartog, @peacekeeper)
-
Clear explanation on how can A DID have more than one controller w3c/did#260 (2 comments by @jandrieu, @talltree)
-
Clarification of other verification methods in authentication section missing w3c/did#57 (2 comments by @brentzundel, @rhiaro)
-
Syntactially differentiate data about the DID versus application data w3c/did#85 (2 comments by @jricher, @selfissued)
-
transfer of controllership and it's intersection with the subject of an identifier w3c/did#269 (1 comment by @jandrieu)
-
Uses of terms defined in the specification should be links to their definitions w3c/did#163 (1 comment by @talltree)
-
What degree should proof purposes be defined for specific application layer usages? w3c/did#268 (1 comment by @kdenhartog)
-
Public key "id" and "type" members duplicate JWK "kid" and "kty" members w3c/did#170 (1 comment by @OR13)
-
Ambiguity around necessity of populated top-level DID Document 'id' property w3c/did#274 (1 comment by @csuwildcat)
-
What is being discussed in issue 4 (clarification of TERMX via use-cases, spec pointers, and PR) w3c/did#190 (1 comment by @brentzundel)
-
Unsubstantiated statement about protecting against attacks when compromised w3c/did#176 (1 comment by @burnburn)
-
-
19 pull requests opened.
-
full editing pass on all terms w3c/did#335, by @talltree.
-
Fixed ABNF for method-specific-id of DID Syntax w3c/did#334, by @Crenshinibon.
-
Support resolve() and resolveStream() functions w3c/did#331, by @peacekeeper.
-
minor editorial fixes to VR examples w3c/did#330, by @kdenhartog.
-
Relationship between `controller` property and DID controller w3c/did#326, by @rhiaro.
-
Allow resolve() to return abstract DID document (option 2) w3c/did#323, by @peacekeeper.
-
Allow resolve() to return abstract DID document (option 1) w3c/did#322, by @peacekeeper.
-
Put all term dfns in terms.html w3c/did#321, by @rhiaro.
-
Makes use of property/name/value consistent w3c/did#320, by @rhiaro.
-
Editorial: Identifier and Methods sections w3c/did#319, by @rhiaro.
-
Remove largely ficticious real world example. w3c/did#316, by @msporny.
-
Remove interop registries appendix. w3c/did#315, by @msporny.
-
Move Future Work section to implementation guide. w3c/did#314, by @msporny.
-
add core properties verifiable relationship sections w3c/did#312, by @kdenhartog.
-
Fix typos. w3c/did#310, by @davidlehn.
-
clarify use practice of using a timestamp with signatures w3c/did#309, by @yancyribbens.
-
Replace RsaVerificationKey2018 examples w3c/did#307, by @rhiaro.
-
Add DID parameter examples. w3c/did#306, by @peacekeeper.
-
-
18 pull requests merged.
-
Put all term dfns in terms.html w3c/did#321.
-
Makes use of property/name/value consistent w3c/did#320.
-
Editorial: Identifier and Methods sections w3c/did#319.
-
Remove largely ficticious real world example. w3c/did#316.
-
Remove interop registries appendix. w3c/did#315.
-
Move Future Work section to implementation guide. w3c/did#314.
-
add core properties verifiable relationship sections w3c/did#312.
-
Define resolution function with data types w3c/did#296.
-
Added CBOR section w3c/did#282.
-
Fix typos. w3c/did#310.
-
Add DID parameter examples. w3c/did#306.
-
Add verificationMethod as a DID document property. w3c/did#304.
-
Replace RsaVerificationKey2018 examples w3c/did#307.
-
-
2 pull requests closed.
-
29 pull requests received 166 new comments.
-
add core properties verifiable relationship sections w3c/did#312 (56 comments by @dlongley, @kdenhartog, @msporny, @rhiaro)
-
Add verificationMethod as a DID document property. w3c/did#304 (15 comments by @msporny, @OR13, @peacekeeper, @rhiaro)
-
Support resolve() and resolveStream() functions w3c/did#331 (11 comments by @dlongley, @jricher, @msporny, @peacekeeper)
-
Define resolution function with data types w3c/did#296 (7 comments by @jricher, @kdenhartog, @msporny, @peacekeeper)
-
Fixed ABNF for method-specific-id of DID Syntax w3c/did#334 (5 comments by @Crenshinibon, @iherman, @msporny)
-
Allow resolve() to return abstract DID document (option 2) w3c/did#323 (3 comments by @kdenhartog, @msporny, @peacekeeper)
-
clarify use practice of using a timestamp with signatures w3c/did#309 (3 comments by @msporny, @rhiaro, @yancyribbens)
-
Disallow expressing revoked keys using a verification relationship. w3c/did#308 (3 comments by @dlongley, @kdenhartog, @msporny)
-
Remove proof as it is specific to Linked Data Proofs. Fixes #293 w3c/did#305 (3 comments by @msporny, @peacekeeper)
-
Allow resolve() to return abstract DID document (option 1) w3c/did#322 (2 comments by @dlongley, @peacekeeper)
-
Replace links to external registries with the DID Spec Registries w3c/did#303 (1 comment by @msporny)
-
Change 'DID registry' to 'Verifiable data registry', towards #162 w3c/did#302 (1 comment by @msporny)
-
Define resolution function with data types and property values w3c/did#297 (1 comment by @davidlehn)
-
w3c/did-extensions
-
17 issues opened.
-
ECHIDNA is broken w3c/did-extensions#78, by @OR13.
-
Add column for link to implementations for each DID Method w3c/did-extensions#77, by @msporny.
-
rename master branch w3c/did-extensions#76, by @brentzundel.
-
Merge W3C CCG DID Method Registry history into this repo w3c/did-extensions#72, by @msporny.
-
It is not possible to checkout did-spec-registries on a Windows machine w3c/did-extensions#71, by @veikkoeeva.
-
URLs and references in schemas cannot be resolved w3c/did-extensions#70, by @veikkoeeva.
-
How do I get a DID? w3c/did-extensions#69, by @thereisnogabe.
-
Set up Echidna for auto-publication of DID Spec Registries w3c/did-extensions#68, by @msporny.
-
Add transform-keys=jwks parameter for use with OIDC SIOP w3c/did-extensions#66, by @OR13.
-
Should we redirect publicKeyHex to the CCG security vocab? w3c/did-extensions#65, by @kdenhartog.
-
Reference to the core v1 context should use the official URL w3c/did-extensions#62, by @iherman.
-
Need a statement about lack of curation w3c/did-extensions#56, by @dhh1128.
-
The property "jws" in the input was not defined in the context. w3c/did-extensions#55, by @OR13.
-
Add note about deprecating publicKey in favor of verificationMethod w3c/did-extensions#54, by @OR13.
-
Move meta data to meta data section w3c/did-extensions#53, by @OR13.
-
Update proof based on did core spec changes w3c/did-extensions#52, by @OR13.
-
Rename 'verification methods' subsection to 'verification relationships' w3c/did-extensions#49, by @rhiaro.
-
-
6 issues closed.
-
Integrate DID Method Registry w3c/did-extensions#26.
-
Reference to the core v1 context should use the official URL w3c/did-extensions#62.
-
Add Example to The Core Parameters w3c/did-extensions#32.
-
Rename 'verification methods' subsection to 'verification relationships' w3c/did-extensions#49.
-
DID Core Registries -> DID Extension Registries, plus clear inclusion of terms from Core w3c/did-extensions#28.
-
JSON-LD context for extensions - not needed? w3c/did-extensions#40.
-
-
12 issues received 18 new comments.
-
Add JsonWebKey2020 to allow for algorithm agnostic key usage in did documents w3c/did-extensions#46 (3 comments by @OR13)
-
The property "jws" in the input was not defined in the context. w3c/did-extensions#55 (3 comments by @msporny, @OR13)
-
Rename 'verification methods' subsection to 'verification relationships' w3c/did-extensions#49 (2 comments by @dlongley)
-
Set up Echidna for auto-publication of DID Spec Registries w3c/did-extensions#68 (1 comment by @iherman)
-
DID Core Registries -> DID Extension Registries, plus clear inclusion of terms from Core w3c/did-extensions#28 (1 comment by @rhiaro)
-
-
13 pull requests opened.
-
Fix markdown error w3c/did-extensions#75, by @OR13.
-
OMN DID Method w3c/did-extensions#74, by @pleerock.
-
added `blockchainAccountId` to core context w3c/did-extensions#73, by @awoie.
-
Setting up final ECHIDNA data w3c/did-extensions#67, by @iherman.
-
Use real context URL for Core context links w3c/did-extensions#64, by @rhiaro.
-
Fix context links w3c/did-extensions#63, by @rhiaro.
-
Add DID parameter entries. Fixes #32. w3c/did-extensions#61, by @peacekeeper.
-
Add Dock DID method w3c/did-extensions#60, by @lovesh.
-
ProximaX SiriusID DID Method w3c/did-extensions#59, by @alvin-reyes.
-
Cleanups. w3c/did-extensions#58, by @davidlehn.
-
Add statement about lack of curation. w3c/did-extensions#57, by @msporny.
-
Rename verification methods to verification relationships. w3c/did-extensions#51, by @rhiaro.
-
Fix link to issue 240 w3c/did-extensions#50, by @rhiaro.
-
-
10 pull requests merged.
-
Fix markdown error w3c/did-extensions#75.
-
Add Dock DID method w3c/did-extensions#60.
-
Setting up final ECHIDNA data w3c/did-extensions#67.
-
ProximaX SiriusID DID Method w3c/did-extensions#59.
-
Use real context URL for Core context links w3c/did-extensions#64.
-
Add DID parameter entries. Fixes #32. w3c/did-extensions#61.
-
Add statement about lack of curation. w3c/did-extensions#57.
-
Cleanups. w3c/did-extensions#58.
-
Rename verification methods to verification relationships. w3c/did-extensions#51.
-
Fix link to issue 240 w3c/did-extensions#50.
-
-
1 pull request closed.
-
Fix context links w3c/did-extensions#63.
-
-
8 pull requests received 57 new comments.
-
added `blockchainAccountId` to core context w3c/did-extensions#73 (19 comments by @awoie, @csuwildcat, @dlongley, @msporny, @OR13, @Therecanbeonlyone1969, @vongohren)
-
Add Dock DID method w3c/did-extensions#60 (17 comments by @brentzundel, @deniak, @iherman, @lovesh, @msporny, @OR13, @pleerock)
-
Rename verification methods to verification relationships. w3c/did-extensions#51 (9 comments by @msporny, @OR13, @peacekeeper, @rhiaro)
-
w3c/did-rubric
-
1 issue opened.
-
rename master branch w3c/did-rubric#3, by @brentzundel.
-
-
2 issues received 4 new comments.
w3c/did-use-cases
-
2 issues opened.
-
rename master branch w3c/did-use-cases#88, by @brentzundel.
-
Add Domain Map for use cases w3c/did-use-cases#87, by @jandrieu.
-
-
15 issues closed.
-
What does it mean for a DID to be "recorded in a registry"? w3c/did-use-cases#14.
-
Use Case Pile-up w3c/did-use-cases#60.
-
DID CRUD is a confusing term w3c/did-use-cases#61.
-
Background statement in Decentralized Corporate Identifiers description not obvious w3c/did-use-cases#19.
-
Focal use cases: more emphasis on DID-s? w3c/did-use-cases#50.
-
Confusion about what a "DID" is throughout the document [DID Credentials] w3c/did-use-cases#57.
-
General comment on the document structure w3c/did-use-cases#26.
-
Describe the relationship between the Single Sign On example and WebAuthn w3c/did-use-cases#23.
-
Time Stamp Proofs w3c/did-use-cases#1.
-
Terminology section issues w3c/did-use-cases#48.
-
Language usage in the use cases w3c/did-use-cases#27.
-
-
23 issues received 50 new comments.
-
rename master branch w3c/did-use-cases#88 (5 comments by @brentzundel, @dlongley, @iherman, @philarcher, @selfissued)
-
General comment on the document structure w3c/did-use-cases#26 (5 comments by @iherman, @jandrieu, @philarcher)
-
What does it mean for a DID to be "recorded in a registry"? w3c/did-use-cases#14 (4 comments by @jandrieu, @msporny)
-
Auto-inclusion of glossary from DID-Core w3c/did-use-cases#75 (4 comments by @jandrieu, @philarcher)
-
Describe relationship between DID Methods and DID Authentication in Use Cases document w3c/did-use-cases#13 (3 comments by @jandrieu, @philarcher)
-
New Use Case Proposals: 1) FMCG Intelligent Serial Number, 2) VIN DID, 3)Circular Economy w3c/did-use-cases#55 (3 comments by @jandrieu, @philarcher)
-
New Use Case Proposal: Blending DIDs with X.509 w3c/did-use-cases#59 (2 comments by @jandrieu, @philarcher)
-
Confusion about what a "DID" is throughout the document [DID Credentials] w3c/did-use-cases#57 (2 comments by @jandrieu, @philarcher)
-
Describe the relationship between the Single Sign On example and WebAuthn w3c/did-use-cases#23 (2 comments by @jandrieu, @philarcher)
-
Consider use cases from key representation discussion in did-core w3c/did-use-cases#52 (1 comment by @jandrieu)
-
Decentralized Identities are simply Credentials and should be defined/called out as such... w3c/did-use-cases#56 (1 comment by @jandrieu)
-
Long-life, recipient-managed credentials example doesn't say how the recipient can validate the issuer of the diploma w3c/did-use-cases#21 (1 comment by @philarcher)
-
Supply chain validation mechanisms not obvious in Decentralized Corporate Identifiers description w3c/did-use-cases#20 (1 comment by @philarcher)
-
Background statement in Decentralized Corporate Identifiers description not obvious w3c/did-use-cases#19 (1 comment by @philarcher)
-
-
5 pull requests opened.
-
Andrieu dhs use cases w3c/did-use-cases#91, by @jandrieu.
-
Added sentence about circular economy Will Fix #55 w3c/did-use-cases#90, by @philarcher.
-
Added supply chain UC w3c/did-use-cases#89, by @philarcher.
-
Anonymous author short use case Will Fix #60 w3c/did-use-cases#86, by @philarcher.
-
Edits to corporate ID background. Will fix #19 w3c/did-use-cases#85, by @philarcher.
-
-
5 pull requests merged.
-
Anonymous author short use case Will Fix #60 w3c/did-use-cases#86.
-
Improves Actions list Will fix #61 w3c/did-use-cases#73.
-
Edits to corporate ID background. Will fix #19 w3c/did-use-cases#85.
-
Added supply chain UC w3c/did-use-cases#89.
-
Added sentence about circular economy Will Fix #55 w3c/did-use-cases#90.
-
-
5 pull requests received 8 new comments.
-
Edits to corporate ID background. Will fix #19 w3c/did-use-cases#85 (3 comments by @jandrieu, @philarcher)
-
w3c/did-imp-guide
-
1 issue opened.
-
rename master branch w3c/did-imp-guide#1, by @brentzundel.
-
-
1 issue received 1 new comment.
w3c/did-test-suite
-
1 issue opened.
-
rename master branch w3c/did-test-suite#2, by @brentzundel.
-
-
1 issue received 1 new comment.
Participants
-
1 participant joined.
-
Nicholas Steele (Cisco) joined.
-
-
2 participants left.
-
Samuel Smith (Consensys) left.
-
Robert Sanderson (J. Paul Getty Trust) left.
-
GitHub
w3c/did
-
16 issues opened.
-
Create a seperate top level block for defining proof purposes w3c/did#294, by @tplooker.
-
Remove `proof` w3c/did#293, by @rhiaro.
-
Horizontal Review Tracking w3c/did#292, by @brentzundel.
-
PING Horizontal Review w3c/did#291, by @brentzundel.
-
The DID context document is now 404 w3c/did#290, by @troyronda.
-
Should DID Methods expose Proof Purposes for DID Operations? w3c/did#289, by @OR13.
-
Remove uses of publicKeyHex w3c/did#280, by @selfissued.
-
invert mapping between proof purposes and verification methods? w3c/did#273, by @dhh1128.
-
Remove all unspecified properties/functionality from the spec w3c/did#272, by @csuwildcat.
-
did parameter equivilance w3c/did#270, by @kdenhartog.
-
17 issues closed.
-
Who or what can be a DID Controller? w3c/did#210.
-
Remove matrix parameters from the DID specification w3c/did#159.
-
Underspecified semantics of revoked keys w3c/did#168.
-
Allowing embedded custom contexts w3c/did#153.
-
Use of undefined term "verifiable timestamps" w3c/did#181.
-
The DID context document is now 404 w3c/did#290.
-
Normative vs. non-normative references w3c/did#53.
-
Unmotivated statement about JSON pointers w3c/did#164.
-
Use of undefined term "resource" w3c/did#182.
-
-
1 issue reopened.
-
Should DID Methods expose Proof Purposes for DID Operations? w3c/did#289, by @OR13.
-
-
56 issues received 185 new comments.
-
Should DID Methods expose Proof Purposes for DID Operations? w3c/did#289 (42 comments by @ChristopherA, @csuwildcat, @dhh1128, @dlongley, @kdenhartog, @OR13, @peacekeeper, @SmithSamuelM, @troyronda)
-
invert mapping between proof purposes and verification methods? w3c/did#273 (11 comments by @agropper, @dhh1128, @dlongley, @ewelton)
-
Verification method block should be a first citizen like public keys w3c/did#283 (8 comments by @awoie, @kdenhartog, @OR13, @rhiaro)
-
Remove all unspecified properties/functionality from the spec w3c/did#272 (8 comments by @csuwildcat, @dlongley, @kdenhartog, @rhiaro, @selfissued)
-
Is "verification method" relevant to inbound (as opposed to outbound) communication? w3c/did#276 (8 comments by @brentzundel, @dhh1128, @dlongley, @kdenhartog)
-
Do we need a DID method-type feature (capturing new discussion) w3c/did#152 (6 comments by @cboscolo, @dlongley, @msporny, @OR13)
-
Add public key examples using JWKs w3c/did#171 (6 comments by @kdenhartog, @msporny, @OR13, @selfissued)
-
Add support for ethereumAddress public key type in @context w3c/did#55 (6 comments by @awoie, @kdenhartog, @OR13, @selfissued)
-
What are the differences between Verifiable Credentials and DID document? w3c/did#147 (4 comments by @agropper, @haidedang, @peacekeeper, @YueJing95)
-
DID URL dereferencing and its relationship to different encodings/representations w3c/did#200 (3 comments by @burnburn, @kdenhartog, @tplooker)
-
IETF did+ld+json media type registration w3c/did#208 (3 comments by @BigBlueHat, @iherman, @msporny)
-
transfer of controllership and it's intersection with the subject of an identifier w3c/did#269 (3 comments by @jandrieu, @kdenhartog)
-
Unmotivated statement about JSON pointers w3c/did#164 (3 comments by @kdenhartog, @msporny, @SmithSamuelM)
-
When is a DID subject not a DID controller (if ever)? w3c/did#122 (2 comments by @dlongley, @kdenhartog)
-
publicKeyJwk, publicKeyHex, publicKeyBase64, publicKeyBase58 missing from context. w3c/did#23 (2 comments by @OR13)
-
What degree should proof purposes be defined for specific application layer usages? w3c/did#268 (2 comments by @dlongley, @kdenhartog)
-
We should find a better term than "DID Registry" and better define what it refers to w3c/did#162 (2 comments by @rhiaro, @selfissued)
-
Replace registries administered community groups with registries established by this specification w3c/did#169 (2 comments by @OR13, @selfissued)
-
Ambiguity around necessity of populated top-level DID Document 'id' property w3c/did#274 (2 comments by @kdenhartog, @nikosft)
-
What is being discussed in issue 4 (clarification of TERMX via use-cases, spec pointers, and PR) w3c/did#190 (1 comment by @msporny)
-
Is method-specific-id supposed to be equivalent to param-char? w3c/did#45 (1 comment by @peacekeeper)
-
Public key "id" and "type" members duplicate JWK "kid" and "kty" members w3c/did#170 (1 comment by @selfissued)
-
Add CBOR a valid type of DID document syntax similar to JSON and on par with JSON-LD w3c/did#92 (1 comment by @jonnycrunch)
-
Ambiguity around DID controller public key and authentication method w3c/did#275 (1 comment by @nikosft)
-
Seeking clarification around authentication, public keys, and verification apparatus w3c/did#193 (1 comment by @msporny)
-
How to mitigate the single source of failure wrt/ "Trust into the Universal Resolver"? w3c/did#249 (1 comment by @SmithSamuelM)
-
-
20 pull requests opened.
-
Remove proof as it is specific to Linked Data Proofs. Fixes #293 w3c/did#305, by @rhiaro.
-
Add verificationMethod as a DID document property. w3c/did#304, by @rhiaro.
-
Replace links to external registries with the DID Spec Registries w3c/did#303, by @rhiaro.
-
Change 'DID registry' to 'Verifiable data registry', towards #162 w3c/did#302, by @rhiaro.
-
Define resolution function with data types and property values w3c/did#297, by @jricher.
-
Define resolution function with data types w3c/did#296, by @jricher.
-
Define simple type-less resolution function w3c/did#295, by @jricher.
-
Intro re-structure and new content w3c/did#288, by @rhiaro.
-
Trivial nit wrt a reference w3c/did#287, by @philarcher.
-
Add normative DID Resolution section. (option #2) w3c/did#286, by @msporny.
-
Remove matrix parameters, addresses #159. w3c/did#285, by @peacekeeper.
-
Amplify/broaden def of 'verification method' w3c/did#284, by @dhh1128.
-
Added CBOR section w3c/did#282, by @jonnycrunch.
-
Simplify description of revoked keys w3c/did#279, by @selfissued.
-
Remove uses of undefined terms graph-based and tree-based w3c/did#278, by @selfissued.
-
Accurately describe dependence on registries w3c/did#277, by @selfissued.
-
-
11 pull requests merged.
-
Intro re-structure and new content w3c/did#288.
-
Remove matrix parameters, addresses #159. w3c/did#285.
-
Simplify description of revoked keys w3c/did#279.
-
Trivial nit wrt a reference w3c/did#287.
-
Amplify/broaden def of 'verification method' w3c/did#284.
-
Accurately describe dependence on registries w3c/did#277.
-
Remove statement about JSON Pointer. w3c/did#257.
-
initial text for section 6 w3c/did#241.
-
-
5 pull requests closed.
-
Add normative DID URL Dereferencing section. w3c/did#264.
-
Add normative DID Resolution section. (option #2) w3c/did#286.
-
Add normative DID Resolution section. (option #1) w3c/did#263.
-
Add normative DID Resolution Metadata section. w3c/did#265.
-
Add "id" DID parameter instead of "service". w3c/did#139.
-
-
21 pull requests received 137 new comments.
-
Added CBOR section w3c/did#282 (31 comments by @iherman, @jonnycrunch, @jricher, @msporny, @OR13, @peacekeeper)
-
Add normative DID Resolution section. (option #1) w3c/did#263 (15 comments by @dlongley, @jricher, @msporny, @OR13)
-
Intro re-structure and new content w3c/did#288 (15 comments by @iherman, @kdenhartog, @msporny, @rhiaro, @yancyribbens)
-
Define resolution function with data types, property values, and full metadata structures w3c/did#299 (10 comments by @dlongley, @dmitrizagidulin, @jricher, @llorllale, @OR13)
-
Add normative DID Resolution section. (option #2) w3c/did#286 (10 comments by @jricher, @kdenhartog, @msporny, @peacekeeper, @talltree, @tplooker)
-
Accurately describe dependence on registries w3c/did#277 (7 comments by @msporny, @peacekeeper, @selfissued)
-
Add normative DID URL Dereferencing section. w3c/did#264 (6 comments by @jandrieu, @jricher, @msporny, @OR13, @peacekeeper)
-
Define resolution function with data types, property values, and simple metadata structures w3c/did#298 (4 comments by @jricher, @OR13)
-
Add "id" DID parameter instead of "service". w3c/did#139 (4 comments by @OR13, @peacekeeper, @SmithSamuelM)
-
Added DID resolution and dereferencing contracts. w3c/did#253 (3 comments by @dmitrizagidulin, @jricher, @msporny)
-
Define resolution function with data types and property values w3c/did#297 (2 comments by @davidlehn, @jricher)
-
w3c/did-rubric
-
1 issue opened.
-
Need initial content w3c/did-rubric#2, by @OR13.
-
-
1 issue received 1 new comment.
w3c/did-extensions
-
3 issues opened.
-
Add JsonWebKey2020 to allow for algorithm agnostic key usage in did documents w3c/did-extensions#46, by @kdenhartog.
-
Rename the repo w3c/did-extensions#45, by @rhiaro.
-
OCAP properties need to be defined or removed w3c/did-extensions#41, by @OR13.
-
-
3 issues closed.
-
Examples in the Registries w3c/did-extensions#39.
-
Rename the repo w3c/did-extensions#45.
-
updated is missing from the json-ld context w3c/did-extensions#29.
-
-
6 issues received 19 new comments.
-
Why are we using didv in our core context? w3c/did-extensions#48 (6 comments by @dlongley, @iherman, @OR13)
-
Add JsonWebKey2020 to allow for algorithm agnostic key usage in did documents w3c/did-extensions#46 (2 comments by @OR13)
-
-
4 pull requests opened.
-
Restructure properties and remove extensions context w3c/did-extensions#47, by @rhiaro.
-
Restructure to use tables for spec links w3c/did-extensions#44, by @rhiaro.
-
rename JwsVerificationKey2020 to JsonWebKey2020 w3c/did-extensions#43, by @kdenhartog.
-
Define did core properties w3c/did-extensions#42, by @OR13.
-
-
4 pull requests merged.
-
Restructure properties and remove extensions context w3c/did-extensions#47.
-
Restructure to use tables for spec links w3c/did-extensions#44.
-
Add `updated` to the JSON-LD context w3c/did-extensions#35.
-
Define did core properties w3c/did-extensions#42.
-
-
1 pull request closed.
-
rename JwsVerificationKey2020 to JsonWebKey2020 w3c/did-extensions#43.
-
-
4 pull requests received 29 new comments.
-
rename JwsVerificationKey2020 to JsonWebKey2020 w3c/did-extensions#43 (21 comments by @kdenhartog, @kimdhamilton, @msporny, @OR13)
-
Restructure to use tables for spec links w3c/did-extensions#44 (5 comments by @msporny, @OR13, @rhiaro)
-
w3c/did-use-cases
-
1 issue closed.
-
When do we publish a FPWD of the Use Cases document? w3c/did-use-cases#8.
-
-
2 issues received 2 new comments.
-
2 pull requests opened.
-
Relying Party -> Requesting Party w3c/did-use-cases#84, by @philarcher.
-
Replace relying party with verifier, will fix #39 w3c/did-use-cases#83, by @philarcher.
-
-
1 pull request closed.
-
Replace relying party with verifier, will fix #39 w3c/did-use-cases#83.
-
-
2 pull requests received 2 new comments.
TR publications
-
7 documents published.
-
Use Cases and Requirements for Decentralized Identifiers published twice as a Working Draft. History of Use Cases and Requirements for Decentralized Identifiers
-
Decentralized Identifiers (DIDs) v1.0 published 5 times as a Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
Participants
-
4 participants joined.
-
Jonathan Holt (Consensys) joined.
-
Nat Holloway (USAA) joined.
-
Sumita Jonak (USAA) joined.
-
Liam Tait (Mattr Limited) joined.
-
-
5 participants left.
-
Wayne Chang (Spruce Systems, Inc.) left.
-
Pelle Braendgaard (Consensys) left.
-
Grant Noble (Consensys) left.
-
Robert Coote (Consensys) left.
-
Jonathan Holt (Consensys) left.
-
-
2 organizations joined.
-
Cisco joined.
-
Data Society Alliance joined.
-
GitHub
w3c/did
-
10 issues opened.
-
Should DID support self-signed certificates? w3c/did#266, by @DurandA.
-
Definition of the term "client" in regard to SSI principles w3c/did#261, by @marceljay.
-
DIDs and JOSE: publicKey.id and publicKey.publicKeyJwk.kid w3c/did#259, by @OR13.
-
List of early implementations conforming to spec? w3c/did#258, by @codi0.
-
MIME Types for DID Documents and Representations w3c/did#255, by @jricher.
-
Need term for relying party w3c/did#248, by @jandrieu.
-
13 issues closed.
-
MIME Types for DID Documents and Representations w3c/did#255.
-
(Partially) Encrypting DID Documents w3c/did#25.
-
Do we really want to recommend polling for changes? w3c/did#179.
-
JSON LD Explanatory Text is extraneous w3c/did#206.
-
45 issues received 128 new comments.
-
Standardize the key revocation list w3c/did#14 (16 comments by @csuwildcat, @dhh1128, @dlongley, @lrosenthol, @msporny, @OR13, @thereisnogabe)
-
Define terminology for properties and values w3c/did#204 (11 comments by @burnburn, @iherman, @jricher, @kdenhartog, @msporny, @peacekeeper)
-
Unmotivated statement about JSON pointers w3c/did#164 (10 comments by @kdenhartog, @msporny, @peacekeeper, @SmithSamuelM)
-
MIME Types for DID Documents and Representations w3c/did#255 (7 comments by @dmitrizagidulin, @iherman, @jricher, @msporny, @peacekeeper)
-
publicKeyHex format unused by spec currently w3c/did#236 (7 comments by @ChristopherA, @kdenhartog, @OR13, @peacekeeper)
-
Can we minimize the footprint of the DID document by removing all delegation w3c/did#194 (5 comments by @brentzundel, @ChristopherA, @ewelton, @msporny)
-
Include discussion of eIDAS levels-of-assurance w3c/did#151 (5 comments by @ewagner70, @nalamillo, @peacekeeper, @veikkoeeva)
-
DIDs and JOSE: publicKey.id and publicKey.publicKeyJwk.kid w3c/did#259 (5 comments by @csuwildcat, @OR13)
-
Can we nuance our mental model on DID control slightly? w3c/did#233 (4 comments by @brentzundel, @kdenhartog, @pknowl)
-
Should DID support self-signed certificates? w3c/did#266 (3 comments by @DurandA, @kdenhartog, @NightBus9)
-
What degree should proof purposes be defined for specific application layer usages? w3c/did#268 (3 comments by @dlongley, @kdenhartog)
-
transfer of controllership and it's intersection with the subject of an identifier w3c/did#269 (3 comments by @jandrieu, @kdenhartog)
-
We should find a better term than "DID Registry" and better define what it refers to w3c/did#162 (3 comments by @kdenhartog, @panickervinod, @peacekeeper)
-
Add CBOR a valid type of DID document syntax similar to JSON and on par with JSON-LD w3c/did#92 (3 comments by @burnburn, @jricher, @kdenhartog)
-
Underspecified statement on combining timestamps with signatures w3c/did#178 (2 comments by @rhiaro, @yancyribbens)
-
How to mitigate the single source of failure wrt/ "Trust into the Universal Resolver"? w3c/did#249 (2 comments by @peacekeeper, @rknobloch)
-
Replace registries administered community groups with registries established by this specification w3c/did#169 (1 comment by @rhiaro)
-
Should we restrict the value of `id` when used to identify a subject? w3c/did#217 (1 comment by @brentzundel)
-
Syntactially differentiate data about the DID versus application data w3c/did#85 (1 comment by @jricher)
-
Correct misleading language about no dependence upon centralized registries or authorities w3c/did#160 (1 comment by @selfissued)
-
Unclear which verification methods are authorized for did document operations w3c/did#195 (1 comment by @OR13)
-
Clear explanation on how can A DID have more than one controller w3c/did#260 (1 comment by @kdenhartog)
-
Clarify language around what the items in `service` should/must be w3c/did#234 (1 comment by @llorllale)
-
-
13 pull requests opened.
-
Put key points up front w3c/did#267, by @CholoTook.
-
Add normative DID Resolution Metadata section. w3c/did#265, by @msporny.
-
Add normative DID URL Dereferencing section. w3c/did#264, by @msporny.
-
Add normative DID Resolution section. (option #1) w3c/did#263, by @msporny.
-
Remove statement about JSON Pointer. w3c/did#257, by @msporny.
-
Remove JSON-LD Appendix (jricher) w3c/did#256, by @msporny.
-
fix typo w3c/did#254, by @llorllale.
-
Added DID resolution and dereferencing contracts. w3c/did#253, by @jricher.
-
Fix typos. w3c/did#252, by @davidlehn.
-
Fix typo: duplicate "are" w3c/did#251, by @PeterTheOne.
-
Remove self-reference to the public keys section w3c/did#250, by @PeterTheOne.
-
Add initial content for DID Resolution. w3c/did#247, by @peacekeeper.
-
-
14 pull requests merged.
-
Working dfn for 'resource', for #182 w3c/did#243.
-
Remove JSON-LD Contexts from DID Core w3c/did#238.
-
Remove suggestion of polling w3c/did#244.
-
Removed JSON-LD explainer. w3c/did#239.
-
Remove JSON-LD Appendix (jricher) w3c/did#256.
-
address privacy concerns with serviceEndpoints w3c/did#232.
-
fix typo w3c/did#254.
-
Clarify id value for json-ld w3c/did#242.
-
Fix typos. w3c/did#252.
-
Fix references that should be non-normative w3c/did#245.
-
Remove self-reference to the public keys section w3c/did#250.
-
Fix typo: duplicate "are" w3c/did#251.
-
Clarify what a DID identifies w3c/did#213.
-
Remove reference to closed issue #35. w3c/did#246.
-
-
3 pull requests closed.
-
Add initial content for DID Resolution. w3c/did#247.
-
Add "service-type" DID URL matrix parameter. w3c/did#62.
-
Add "key-type" DID URL matrix parameter. w3c/did#60.
-
-
22 pull requests received 289 new comments.
-
Added DID resolution and dereferencing contracts. w3c/did#253 (67 comments by @dlongley, @iherman, @jricher, @kdenhartog, @llorllale, @mavarley, @msporny, @peacekeeper, @talltree)
-
Add non-normative DID Resolution and Dereferencing sections to Architecture. w3c/did#262 (56 comments by @iherman, @jricher, @kdenhartog, @msporny, @philarcher)
-
initial text for section 6 w3c/did#241 (42 comments by @burnburn, @iherman, @kdenhartog, @msporny, @peacekeeper, @talltree)
-
Add initial content for DID Resolution. w3c/did#247 (42 comments by @brentzundel, @iherman, @jricher, @kdenhartog, @lrosenthol, @msporny, @OR13, @peacekeeper, @philarcher)
-
Add normative DID URL Dereferencing section. w3c/did#264 (19 comments by @iherman, @jandrieu, @jricher, @peacekeeper, @philarcher)
-
Add normative DID Resolution section. (option #1) w3c/did#263 (12 comments by @jricher, @peacekeeper, @philarcher)
-
Add "key-type" DID URL matrix parameter. w3c/did#60 (5 comments by @kdenhartog, @msporny, @OR13, @peacekeeper)
-
Remove self-reference to the public keys section w3c/did#250 (5 comments by @iherman, @peacekeeper, @PeterTheOne)
-
Add "service-type" DID URL matrix parameter. w3c/did#62 (3 comments by @kdenhartog, @msporny, @peacekeeper)
-
w3c/did-extensions
-
6 issues opened.
-
JSON-LD context for extensions - not needed? w3c/did-extensions#40, by @rhiaro.
-
Examples in the Registries w3c/did-extensions#39, by @rhiaro.
-
Add Example to The Core Parameters w3c/did-extensions#32, by @OR13.
-
Add Example to The Properties Extension Registry w3c/did-extensions#31, by @OR13.
-
Add Example to The Parameters Extension Registry w3c/did-extensions#30, by @OR13.
-
updated is missing from the json-ld context w3c/did-extensions#29, by @rhiaro.
-
-
2 issues closed.
-
Do not permit properties or parameters that duplicate those in DID Core w3c/did-extensions#22.
-
Clarify language around JSON-LD contexts w3c/did-extensions#23.
-
-
5 issues received 27 new comments.
-
DID Core Registries -> DID Extension Registries, plus clear inclusion of terms from Core w3c/did-extensions#28 (19 comments by @msporny, @OR13, @rhiaro, @selfissued, @talltree)
-
Do not permit properties or parameters that duplicate those in DID Core w3c/did-extensions#22 (2 comments by @OR13, @rhiaro)
-
-
6 pull requests opened.
-
Adding wgId field to configuration w3c/did-extensions#38, by @iherman.
-
No duplicating properties and parameters from Core w3c/did-extensions#37, by @rhiaro.
-
Clarify language around JSON-LD contexts in registration process. w3c/did-extensions#36, by @rhiaro.
-
Add `updated` to the JSON-LD context w3c/did-extensions#35, by @rhiaro.
-
Add Spanning Example w3c/did-extensions#34, by @OR13.
-
Add an Example of a Property Extension w3c/did-extensions#33, by @OR13.
-
-
6 pull requests merged.
-
Adding wgId field to configuration w3c/did-extensions#38.
-
No duplicating properties and parameters from Core w3c/did-extensions#37.
-
Add Spanning Example w3c/did-extensions#34.
-
Clarify language around JSON-LD contexts in registration process. w3c/did-extensions#36.
-
Add an Example of a Property Extension w3c/did-extensions#33.
-
Define verification methods w3c/did-extensions#27.
-
-
6 pull requests received 34 new comments.
-
Define verification methods w3c/did-extensions#27 (12 comments by @davidlehn, @dlongley, @gjgd, @OR13)
-
No duplicating properties and parameters from Core w3c/did-extensions#37 (2 comments by @OR13, @rhiaro)
-
w3c/did-resolution
-
1 issue opened.
-
DID resolution context URL does not exist w3c/did-resolution#54, by @troyronda.
-
w3c/did-use-cases
-
2 issues opened.
-
Add DHS use case(s) w3c/did-use-cases#81, by @jandrieu.
-
Auto-inclusion of glossary from DID-Core w3c/did-use-cases#75, by @philarcher.
-
-
2 issues closed.
-
"Surveillance capitalism" terminology? w3c/did-use-cases#25.
-
Decentralised Identity Resolution w3c/did-use-cases#67.
-
-
6 issues received 9 new comments.
-
DID CRUD is a confusing term w3c/did-use-cases#61 (4 comments by @jandrieu, @peacekeeper, @philarcher, @selfissued)
-
-
9 pull requests opened.
-
Added the wgId field to the configuration w3c/did-use-cases#82, by @iherman.
-
Removes "Surveillance capitalism" term Will fix #25 w3c/did-use-cases#80, by @philarcher.
-
Minor change to remove solution before the problem w3c/did-use-cases#79, by @philarcher.
-
Remove CRUD from Create action w3c/did-use-cases#78, by @philarcher.
-
Adding missing </ol> w3c/did-use-cases#77, by @philarcher.
-
Rotate means update w3c/did-use-cases#76, by @philarcher.
-
Putting original authors back in w3c/did-use-cases#74, by @philarcher.
-
Improves Actions list Will fix #61 w3c/did-use-cases#73, by @philarcher.
-
Sharing opted-in information across platforms UC w3c/did-use-cases#72, by @philarcher.
-
-
10 pull requests merged.
-
Added the wgId field to the configuration w3c/did-use-cases#82.
-
Removes "Surveillance capitalism" term Will fix #25 w3c/did-use-cases#80.
-
Minor change to remove solution before the problem w3c/did-use-cases#79.
-
Remove CRUD from Create action w3c/did-use-cases#78.
-
Adding missing </ol> w3c/did-use-cases#77.
-
Rotate means update w3c/did-use-cases#76.
-
Putting original authors back in w3c/did-use-cases#74.
-
Sharing opted-in information across platforms UC w3c/did-use-cases#72.
-
Create CODEOWNERS w3c/did-use-cases#71.
-
Updating 'Accessing Master Data of Entities' UC w3c/did-use-cases#66.
-
-
3 pull requests received 9 new comments.
-
Putting original authors back in w3c/did-use-cases#74 (7 comments by @iherman, @jandrieu, @philarcher)
-
TR publications
-
5 documents published.
-
Decentralized Identifiers (DIDs) v1.0 published 5 times as a Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
Participants
-
6 participants joined.
-
Tim Cappalli (Microsoft Corporation) joined.
-
Troy Ronda (SecureKey) joined.
-
Justin Richer (SecureKey) joined.
-
Tobias Looker (Mattr Limited) joined.
-
Paul Madsen (Hedera Hashgraph) joined.
-
Brett McDowell (Hedera Hashgraph) joined.
-
-
2 participants left.
-
Troy Ronda (SecureKey) left.
-
Justin Richer (SecureKey) left.
-
-
1 organization joined.
-
Hedera Hashgraph joined.
-
GitHub
w3c/did-extensions
-
9 issues opened.
-
DID Core Registries -> DID Extension Registries, plus clear inclusion of terms from Core w3c/did-extensions#28, by @rhiaro.
-
Integrate DID Method Registry w3c/did-extensions#26, by @rhiaro.
-
Clarify language around JSON-LD contexts w3c/did-extensions#23, by @rhiaro.
-
Do not permit properties or parameters that duplicate those in DID Core w3c/did-extensions#22, by @rhiaro.
-
Define sidetree context w3c/did-extensions#19, by @OR13.
-
Define unified versioning system for machine and human readable definitions. w3c/did-extensions#17, by @OR13.
-
Add precommit hook + linter w3c/did-extensions#16, by @OR13.
-
Refactor Github Actions w3c/did-extensions#15, by @OR13.
-
DID Core Registries Stabilization Checklist w3c/did-extensions#13, by @msporny.
-
-
3 issues closed.
-
Add Github actions for testing machine readable definitions of registry w3c/did-extensions#8.
-
Refactor Github Actions w3c/did-extensions#15.
-
Add a JSON-LD Definition for id w3c/did-extensions#6.
-
-
15 issues received 87 new comments.
-
DID Core Registries Stabilization Checklist w3c/did-extensions#13 (19 comments by @dhh1128, @iherman, @JaceHensley, @msporny, @OR13, @rhiaro, @selfissued)
-
Define unified versioning system for machine and human readable definitions. w3c/did-extensions#17 (17 comments by @burnburn, @iherman, @msporny, @OR13, @rhiaro, @selfissued)
-
Add a CBOR Registry definition for id w3c/did-extensions#5 (6 comments by @jonnycrunch, @msporny, @OR13)
-
DID Core Registries -> DID Extension Registries, plus clear inclusion of terms from Core w3c/did-extensions#28 (5 comments by @msporny, @rhiaro, @selfissued)
-
Define sidetree context w3c/did-extensions#19 (5 comments by @msporny, @OR13, @peacekeeper, @selfissued)
-
Fix JSON-LD Context Links w3c/did-extensions#3 (5 comments by @jonnycrunch, @msporny, @OR13, @rhiaro, @selfissued)
-
Clarify language around JSON-LD contexts w3c/did-extensions#23 (3 comments by @dlongley, @OR13, @rhiaro)
-
Why are we using didv in our core context? w3c/did-extensions#48 (3 comments by @iherman, @msporny, @OR13)
-
Do not permit properties or parameters that duplicate those in DID Core w3c/did-extensions#22 (2 comments by @OR13, @rhiaro)
-
Add Github actions for testing machine readable definitions of registry w3c/did-extensions#8 (1 comment by @OR13)
-
-
7 pull requests opened.
-
Define verification methods w3c/did-extensions#27, by @OR13.
-
Create CODEOWNERS w3c/did-extensions#25, by @OR13.
-
Add support for Relative URIs in JSON-LD DID Documents w3c/did-extensions#24, by @OR13.
-
Remove undefined properties from did-v1 context w3c/did-extensions#21, by @OR13.
-
Add Support for publicKeyJwk w3c/did-extensions#20, by @OR13.
-
Refactor Github action w3c/did-extensions#18, by @gjgd.
-
Add initial registration requirements for registries. w3c/did-extensions#14, by @msporny.
-
-
7 pull requests merged.
-
Add support for Relative URIs in JSON-LD DID Documents w3c/did-extensions#24.
-
Create CODEOWNERS w3c/did-extensions#25.
-
Add Support for publicKeyJwk w3c/did-extensions#20.
-
Add CI Tests w3c/did-extensions#11.
-
Add initial registration requirements for registries. w3c/did-extensions#14.
-
Refactor Github action w3c/did-extensions#18.
-
Add Orie Steele as lead editor/author. w3c/did-extensions#10.
-
-
1 pull request closed.
-
Remove undefined properties from did-v1 context w3c/did-extensions#21.
-
-
8 pull requests received 100 new comments.
-
Add CI Tests w3c/did-extensions#11 (42 comments by @csuwildcat, @davidlehn, @gjgd, @iherman, @llorllale, @msporny, @OR13)
-
Add Support for publicKeyJwk w3c/did-extensions#20 (36 comments by @csuwildcat, @dlongley, @gjgd, @kdenhartog, @msporny, @OR13)
-
Add support for Relative URIs in JSON-LD DID Documents w3c/did-extensions#24 (7 comments by @csuwildcat, @iherman, @msporny, @OR13)
-
Remove undefined properties from did-v1 context w3c/did-extensions#21 (6 comments by @msporny, @OR13, @selfissued)
-
Add initial registration requirements for registries. w3c/did-extensions#14 (5 comments by @dlongley, @msporny, @OR13)
-
w3c/did
-
7 issues opened.
-
Should did-core restrict the use of JWK? w3c/did#240, by @OR13.
-
publicKeyHex format unused by spec currently w3c/did#236, by @kdenhartog.
-
Can we nuance our mental model on DID control slightly? w3c/did#233, by @dhh1128.
-
Define proof property of did document w3c/did#223, by @OR13.
-
Change the terminology from "DID URL" to "DID Locator" w3c/did#218, by @iherman.
-
-
17 issues closed.
-
Term "CRUD operations" is used without being defined w3c/did#167.
-
Add usage / key usage for sidetree methods w3c/did#158.
-
Add support for experimental context w3c/did#188.
-
Define proof property of did document w3c/did#223.
-
Statement on stable DID Registries not actionable w3c/did#166.
-
DID, DID-URL, identification (DID view <-> SW view) w3c/did#183.
-
Confusing statement about key revocation on DLTs w3c/did#180.
-
Use of undefined term "object capabilities" w3c/did#177.
-
Add resolution procedure for relative URL references w3c/did#201.
-
Use of undefined term "verification method" w3c/did#172.
-
86 issues received 517 new comments.
-
Can we nuance our mental model on DID control slightly? w3c/did#233 (81 comments by @burnburn, @ChristopherA, @dhh1128, @ewelton, @jandrieu, @kdenhartog, @mitfik, @msporny, @peacekeeper, @pknowl, @talltree)
-
Remove matrix parameters from the DID specification w3c/did#159 (60 comments by @awoie, @burnburn, @csuwildcat, @dlongley, @iherman, @jandrieu, @kdenhartog, @msporny, @OR13, @peacekeeper, @philarcher)
-
Change the terminology from "DID URL" to "DID Locator" w3c/did#218 (25 comments by @iherman, @jonnycrunch, @kdenhartog, @OR13, @peacekeeper, @philarcher, @selfissued, @talltree)
-
Include discussion of eIDAS levels-of-assurance w3c/did#151 (24 comments by @bumblefudge, @ChristopherA, @dlongley, @ewagner70, @kdenhartog, @msporny, @nalamillo, @Oskar-van-Deventer, @peacekeeper)
-
Supported ciphers in a DID document w3c/did#185 (22 comments by @brentzundel, @dhh1128, @dlongley, @kdenhartog, @msporny, @OR13, @selfissued, @tplooker)
-
Clarification on what DIDs might identify w3c/did#199 (13 comments by @brentzundel, @jandrieu, @kdenhartog, @Oskar-van-Deventer, @pknowl, @SmithSamuelM, @talltree)
-
DID, DID-URL, identification (DID view <-> SW view) w3c/did#183 (12 comments by @brentzundel, @dmitrizagidulin, @iherman, @msporny, @peacekeeper, @talltree)
-
publicKeyHex format unused by spec currently w3c/did#236 (11 comments by @csuwildcat, @kdenhartog, @mirceanis, @OR13, @peacekeeper, @selfissued)
-
Underspecified semantics of revoked keys w3c/did#168 (11 comments by @csuwildcat, @jandrieu, @msporny, @OR13)
-
Consider adding a well-defined method-specific section to the DID Document w3c/did#143 (10 comments by @cboscolo, @dlongley, @msporny, @OR13)
-
Underspecified semantics of "updated" property w3c/did#174 (10 comments by @csuwildcat, @jandrieu, @OR13, @peacekeeper, @selfissued)
-
Should we restrict the value of `id` when used to identify a subject? w3c/did#217 (9 comments by @iherman, @kdenhartog, @peacekeeper, @rhiaro)
-
Enable instant DID use/resolution for DID Methods that include a propagation delay w3c/did#70 (9 comments by @csuwildcat, @dlongley, @jandrieu, @kdenhartog, @msporny, @OR13)
-
Clarification of other verification methods in authentication section missing w3c/did#57 (7 comments by @kdenhartog, @msporny, @peacekeeper)
-
Confusing statement about key revocation on DLTs w3c/did#180 (7 comments by @dlongley, @kdenhartog, @msporny, @OR13, @peacekeeper, @selfissued)
-
Does DID Document metadata belong in the Document? w3c/did#65 (7 comments by @burnburn, @jricher, @msporny, @OR13, @peacekeeper)
-
We should find a better term than "DID Registry" and better define what it refers to w3c/did#162 (6 comments by @kdenhartog, @peacekeeper, @rhiaro, @talltree)
-
Do we really want to recommend polling for changes? w3c/did#179 (6 comments by @dlongley, @kdenhartog, @OR13, @rhiaro, @selfissued)
-
Decoupling DID Core spec from LD-Proof / LDS specs w3c/did#154 (5 comments by @iherman, @jonnycrunch, @OR13)
-
JSON LD Explanatory Text is extraneous w3c/did#206 (5 comments by @brentzundel, @jricher, @OR13, @rhiaro)
-
Unmotivated statement about JSON pointers w3c/did#164 (5 comments by @ChristopherA, @iherman, @selfissued, @SmithSamuelM)
-
Should DID syntax allow an empty "method-specific-id"? w3c/did#34 (5 comments by @dlongley, @kdenhartog, @msporny, @peacekeeper)
-
When is a DID subject not a DID controller (if ever)? w3c/did#122 (5 comments by @ChristopherA, @ewelton, @iherman, @jandrieu, @rhiaro)
-
Term "CRUD operations" is used without being defined w3c/did#167 (4 comments by @brentzundel, @peacekeeper, @selfissued)
-
Use colon separator or kebab-case for method-specific DID parameter names? w3c/did#35 (4 comments by @brentzundel, @kdenhartog, @OR13, @peacekeeper)
-
Do we need a DID method-type feature (capturing new discussion) w3c/did#152 (4 comments by @burnburn, @kdenhartog, @peacekeeper, @talltree)
-
Replace registries administered community groups with registries established by this specification w3c/did#169 (4 comments by @iherman, @jandrieu, @OR13, @selfissued)
-
Add support for ethereumAddress public key type in @context w3c/did#55 (4 comments by @awoie, @kdenhartog, @OR13)
-
Syntactially differentiate data about the DID versus application data w3c/did#85 (4 comments by @dlongley, @jricher, @selfissued)
-
Use of undefined terms "graph-based" and "tree-based" w3c/did#161 (3 comments by @kdenhartog, @selfissued)
-
What are entityship and start-of-authority (SOA) problems? w3c/did#165 (3 comments by @kdenhartog, @OR13, @selfissued)
-
Shall we need more words on how DIDs support for a centralized identity systems? w3c/did#211 (3 comments by @kdenhartog, @peacekeeper, @philarcher)
-
Use of undefined term "verifiable timestamps" w3c/did#181 (3 comments by @OR13, @selfissued, @yancyribbens)
-
Uses of terms defined in the specification should be links to their definitions w3c/did#163 (3 comments by @rhiaro, @selfissued, @talltree)
-
Meaning of statement about augmenting X.509 certificates unclear w3c/did#175 (3 comments by @OR13, @rhiaro, @selfissued)
-
Public key "id" and "type" members duplicate JWK "kid" and "kty" members w3c/did#170 (3 comments by @OR13, @selfissued)
-
Inconsistent normative language around `id` on public keys w3c/did#134 (3 comments by @OR13, @peacekeeper, @rhiaro)
-
Move or reference section about extending in 5.1 Contexts to 5.10 Extensibility w3c/did#148 (2 comments by @brentzundel, @rhiaro)
-
Statement on stable DID Registries not actionable w3c/did#166 (2 comments by @kdenhartog, @selfissued)
-
Underspecified statement on combining timestamps with signatures w3c/did#178 (2 comments by @kdenhartog, @OR13)
-
Is method-specific-id supposed to be equivalent to param-char? w3c/did#45 (2 comments by @OR13, @peacekeeper)
-
Unsubstantiated statement about protecting against attacks when compromised w3c/did#176 (2 comments by @OR13, @selfissued)
-
Correct misleading language about no dependence upon centralized registries or authorities w3c/did#160 (2 comments by @jandrieu, @selfissued)
-
Add CBOR a valid type of DID document syntax similar to JSON and on par with JSON-LD w3c/did#92 (2 comments by @jonnycrunch, @msporny)
-
Leverage RFC7518 to specify cryptographic algorithms w3c/did#8 (2 comments by @burnburn, @selfissued)
-
Clarify language around what the items in `service` should/must be w3c/did#234 (1 comment by @rhiaro)
-
DID URL dereferencing and its relationship to different encodings/representations w3c/did#200 (1 comment by @tplooker)
-
inconsistent mental model connecting id, kid, and references inside a DID doc w3c/did#131 (1 comment by @msporny)
-
publicKeyJwk, publicKeyHex, publicKeyBase64, publicKeyBase58 missing from context. w3c/did#23 (1 comment by @OR13)
-
Seeking clarification around authentication, public keys, and verification apparatus w3c/did#193 (1 comment by @ewelton)
-
Are service endpoints transport layer or application layer specific? w3c/did#16 (1 comment by @kdenhartog)
-
[Public Keys] re: referenced keys: Is multiple level recursion allowed? w3c/did#20 (1 comment by @kdenhartog)
-
Inconsistant namspace for `method` and/or `method-specific-id` w3c/did#98 (1 comment by @peacekeeper)
-
Unclear which verification methods are authorized for did document operations w3c/did#195 (1 comment by @msporny)
-
-
27 pull requests opened.
-
Remove reference to closed issue #35. w3c/did#246, by @peacekeeper.
-
Fix references that should be non-normative w3c/did#245, by @rhiaro.
-
Remove suggestion of polling w3c/did#244, by @rhiaro.
-
Working dfn for 'resource', for #182 w3c/did#243, by @rhiaro.
-
Clarify id value for json-ld w3c/did#242, by @rhiaro.
-
initial text for section 6 w3c/did#241, by @talltree.
-
Removed JSON-LD explainer. w3c/did#239, by @jricher.
-
Remove JSON-LD Contexts from DID Core w3c/did#238, by @OR13.
-
Remove closed issues from the list w3c/did#237, by @rhiaro.
-
address privacy concerns with serviceEndpoints w3c/did#232, by @kdenhartog.
-
change example of a revoked key to use a more common example w3c/did#230, by @kdenhartog.
-
remove issue referencing object capabilities w3c/did#229, by @kdenhartog.
-
Section about encrypted data in DID docs w3c/did#228, by @rhiaro.
-
Update broken URL for BIP113 w3c/did#227, by @yancyribbens.
-
Remove the term "CRUD". Addresses #167. w3c/did#226, by @peacekeeper.
-
Make id mandatory for public keys and service endpoints w3c/did#225, by @rhiaro.
-
A DID Document MUST NOT contain revoked keys. w3c/did#224, by @OR13.
-
Attempt to fix ABNF for id-char and param-char w3c/did#222, by @OR13.
-
Add publicKeyJwk with compound key identifier example and note w3c/did#221, by @OR13.
-
Add language regarding DID Method Update Operation w3c/did#220, by @OR13.
-
Add support for relative DID URLs. Fix #201. w3c/did#219, by @msporny.
-
Disallow empty method-specific-id in ABNF. w3c/did#216, by @peacekeeper.
-
Clarify use of colon in method-specific-id. w3c/did#215, by @peacekeeper.
-
Added a (forgotten) section, amending the latest section 5 reorg w3c/did#214, by @iherman.
-
Clarify what a DID identifies w3c/did#213, by @Oskar-van-Deventer.
-
Reorganisation of section 5 w3c/did#212, by @iherman.
-
-
15 pull requests merged.
-
Section about encrypted data in DID docs w3c/did#228.
-
Add language regarding DID Method Update Operation w3c/did#220.
-
Remove closed issues from the list w3c/did#237.
-
remove issue referencing object capabilities w3c/did#229.
-
Update broken URL for BIP113 w3c/did#227.
-
Remove the term "CRUD". Addresses #167. w3c/did#226.
-
Add support for relative DID URLs. Fix #201. w3c/did#219.
-
Clarify use of colon in method-specific-id. w3c/did#215.
-
Disallow empty method-specific-id in ABNF. w3c/did#216.
-
Reorganisation of section 5 w3c/did#212.
-
4 pull requests closed.
-
A DID Document MUST NOT contain revoked keys. w3c/did#224.
-
Add README for context directory. w3c/did#91.
-
Attempt to fix ABNF for id-char and param-char w3c/did#222.
-
26 pull requests received 242 new comments.
-
Clarify what a DID identifies w3c/did#213 (63 comments by @brentzundel, @burnburn, @dlongley, @ewelton, @iherman, @jandrieu, @msporny, @OR13, @Oskar-van-Deventer, @peacekeeper)
-
A DID Document MUST NOT contain revoked keys. w3c/did#224 (26 comments by @ChristopherA, @dhh1128, @jandrieu, @jonnycrunch, @msporny, @OR13)
-
Add language regarding DID Method Update Operation w3c/did#220 (23 comments by @brentzundel, @kdenhartog, @msporny, @OR13)
-
initial text for section 6 w3c/did#241 (20 comments by @brentzundel, @iherman, @jricher, @kdenhartog, @rhiaro, @talltree)
-
Add publicKeyJwk with compound key identifier example and note w3c/did#221 (16 comments by @dhh1128, @dlongley, @msporny, @OR13)
-
Add support for relative DID URLs. Fix #201. w3c/did#219 (12 comments by @csuwildcat, @davidlehn, @dhh1128, @msporny, @OR13)
-
Clarify use of colon in method-specific-id. w3c/did#215 (8 comments by @davidlehn, @msporny, @peacekeeper)
-
address privacy concerns with serviceEndpoints w3c/did#232 (7 comments by @kdenhartog, @msporny, @rhiaro)
-
remove untestable normative statement regarding did method specs w3c/did#231 (6 comments by @brentzundel, @kdenhartog, @msporny, @rhiaro)
-
change example of a revoked key to use a more common example w3c/did#230 (5 comments by @kdenhartog, @msporny, @rhiaro)
-
Remove JSON-LD Contexts from DID Core w3c/did#238 (4 comments by @iherman, @kdenhartog, @msporny, @OR13)
-
Add `initial-values` matrix parameter to Generic DID Parameters w3c/did#84 (3 comments by @csuwildcat, @OR13)
-
w3c/did-use-cases
-
4 pull requests opened.
-
Create CODEOWNERS w3c/did-use-cases#71, by @OR13.
-
A new IoT usecase w3c/did-use-cases#70, by @YueJing95.
-
Update index.html w3c/did-use-cases#68, by @zhanb.
-
-
2 pull requests closed.
-
Case100 w3c/did-use-cases#69.
-
Update index.html w3c/did-use-cases#68.
-
TR publications
-
2 documents published.
-
Decentralized Identifiers (DIDs) v1.0 published twice as a Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
Participants
-
12 participants joined.
-
Likun Gao (China Academy of Information and Communications Technology (CAICT)) joined.
-
Xiaoyu YOU (China Academy of Information and Communications Technology (CAICT)) joined.
-
bo zhang (China Academy of Information and Communications Technology (CAICT)) joined.
-
Jingxuan Li (China Academy of Information and Communications Technology (CAICT)) joined.
-
Siyu Zhu (China Academy of Information and Communications Technology (CAICT)) joined.
-
Yurong Li (China Academy of Information and Communications Technology (CAICT)) joined.
-
Thomas Schwarz (USAA) joined.
-
Margo Johnson (Transmute) joined.
-
Joel Hartshorn (USAA) joined.
-
Eugeniu Rusu (Jolocom GmbH) joined.
-
Rick Chan (Digital Policy Office, The Government of the Hong Kong Special Administrative Region of the People's Republic of China) joined.
-
Jason PUN (Digital Policy Office, The Government of the Hong Kong Special Administrative Region of the People's Republic of China) joined.
-
-
1 participant left.
-
YI LIN ZHANG (China Academy of Information and Communications Technology (CAICT)) left.
-
-
2 organizations joined.
-
USAA joined.
-
Digital Policy Office, The Government of the Hong Kong Special Administrative Region of the People's Republic of China joined.
-
GitHub
w3c/did-extensions
-
7 issues opened.
-
Storing normative properties? w3c/did-extensions#9, by @iherman.
-
Add Github actions for testing machine readable definitions of registry w3c/did-extensions#8, by @OR13.
-
Add strict URI pattern w3c/did-extensions#7, by @OR13.
-
Add a JSON-LD Definition for id w3c/did-extensions#6, by @OR13.
-
Add a CBOR Registry definition for id w3c/did-extensions#5, by @OR13.
-
Fix JSON-LD Context Links w3c/did-extensions#3, by @OR13.
-
Adding things to the registry w3c/did-extensions#1, by @OR13.
-
-
1 issue closed.
-
Adding things to the registry w3c/did-extensions#1.
-
-
3 issues received 15 new comments.
-
5 pull requests opened.
-
Add OR13 w3cid w3c/did-extensions#12, by @OR13.
-
Add CI Tests w3c/did-extensions#11, by @OR13.
-
Add Orie Steele as lead editor/author. w3c/did-extensions#10, by @msporny.
-
Add DID Document JSON Schema w3c/did-extensions#4, by @OR13.
-
Define publicKey w3c/did-extensions#2, by @OR13.
-
-
2 pull requests merged.
-
Add DID Document JSON Schema w3c/did-extensions#4.
-
Define publicKey w3c/did-extensions#2.
-
-
1 pull request closed.
-
Add OR13 w3cid w3c/did-extensions#12.
-
-
3 pull requests received 94 new comments.
-
Add DID Document JSON Schema w3c/did-extensions#4 (45 comments by @davidlehn, @dlongley, @msporny, @OR13)
-
Add Orie Steele as lead editor/author. w3c/did-extensions#10 (7 comments by @iherman, @msporny, @OR13)
-
w3c/did
-
22 issues opened.
-
Who or what can be a DID Controller? w3c/did#210, by @kdenhartog.
-
IETF did+ld+json media type registration w3c/did#208, by @msporny.
-
Add section on extensibility and conformance w3c/did#207, by @jricher.
-
JSON LD Explanatory Text is extraneous w3c/did#206, by @jricher.
-
How to treat unknown properties w3c/did#205, by @jricher.
-
Define terminology for properties and values w3c/did#204, by @jricher.
-
Define DID Document Metadata w3c/did#203, by @jricher.
-
JSON-LD Contexts in Registry w3c/did#202, by @jricher.
-
Add resolution procedure for relative URL references w3c/did#201, by @msporny.
-
Clarification on what DIDs might identify w3c/did#199, by @brentzundel.
-
Add sections on DID Resolution w3c/did#198, by @peacekeeper.
-
Test Issue if I can w3c/did#189, by @nembal.
-
Add support for experimental context w3c/did#188, by @OR13.
-
The did-core registry MUST be machine and human readable. w3c/did#187, by @OR13.
-
Supported ciphers in a DID document w3c/did#185, by @tplooker.
-
DID, DID-URL, identification (DID view <-> SW view) w3c/did#183, by @iherman.
-
32 issues closed.
-
Encrypted serviceEndpoint values? w3c/did#64.
-
Should we support multiple encodings of DID docs? w3c/did#140.
-
DID Doc Encoding: Abstract Data Model in JSON w3c/did#128.
-
Separating abstract data model from syntaxes w3c/did#103.
-
(Minor note) update the IANA file w3c/did#52.
-
Should multiple "controller" values be expressible? w3c/did#173.
-
Some comments by Steven Rowat w3c/did#48.
-
Test Issue if I can w3c/did#189.
-
Regarding PII Embedded in Key Formats w3c/did#124.
-
How to integrate certificates with DIDs? w3c/did#69.
-
undecipherable sentence w3c/did#115.
-
1 issue reopened.
-
83 issues received 322 new comments.
-
Figure out three fundamental roles of DIDs (controller, subject, XXX) w3c/did#4 (30 comments by @ChristopherA, @dlongley, @ewelton, @iherman, @jandrieu, @msporny, @Oskar-van-Deventer, @selfissued, @talltree)
-
Clarification on what DIDs might identify w3c/did#199 (23 comments by @brentzundel, @dlongley, @iherman, @jandrieu, @kdenhartog, @ken-ebert, @Oskar-van-Deventer, @peacekeeper, @talltree)
-
Enable instant DID use/resolution for DID Methods that include a propagation delay w3c/did#70 (23 comments by @csuwildcat, @dmitrizagidulin, @gjgd, @jandrieu, @kdenhartog, @kimdhamilton, @OR13, @peacekeeper)
-
IETF did+ld+json media type registration w3c/did#208 (19 comments by @BigBlueHat, @davidlehn, @iherman, @jasnell, @msporny, @peacekeeper, @rhiaro)
-
Supported ciphers in a DID document w3c/did#185 (11 comments by @dlongley, @msporny, @OR13, @tplooker)
-
Standardize the key revocation list w3c/did#14 (9 comments by @burnburn, @ChristopherA, @csuwildcat, @dhh1128, @jandrieu, @jonnycrunch, @msporny)
-
DID, DID-URL, identification (DID view <-> SW view) w3c/did#183 (9 comments by @dlongley, @iherman, @peacekeeper)
-
How to treat unknown properties w3c/did#205 (8 comments by @davidlehn, @iherman, @jandrieu, @jricher, @Oskar-van-Deventer, @selfissued)
-
Can we minimize the footprint of the DID document by removing all delegation w3c/did#194 (7 comments by @ChristopherA, @dhh1128, @dlongley, @ewelton, @SmithSamuelM)
-
The did-core registry MUST be machine and human readable. w3c/did#187 (7 comments by @msporny, @OR13, @selfissued, @talltree)
-
Include discussion of eIDAS levels-of-assurance w3c/did#151 (7 comments by @awoie, @bumblefudge, @ewagner70, @kimdhamilton, @nalamillo)
-
[Public Keys] re: referenced keys: Is multiple level recursion allowed? w3c/did#20 (5 comments by @brentzundel, @dlongley, @msporny, @peacekeeper, @selfissued)
-
Fragment identifier semantics are independent of URI scheme w3c/did#1 (5 comments by @iherman, @msporny)
-
Encrypted serviceEndpoint values? w3c/did#64 (4 comments by @brentzundel, @dmitrizagidulin, @jonnycrunch)
-
DID Doc Encoding: Abstract Data Model in JSON w3c/did#128 (4 comments by @msporny, @OR13, @SmithSamuelM, @talltree)
-
DID URL dereferencing and its relationship to different encodings/representations w3c/did#200 (4 comments by @msporny, @peacekeeper, @tplooker)
-
make publicKey section more explicit for understanding of DIDs reliance on public keys w3c/did#24 (4 comments by @ChristopherA, @kdenhartog, @msporny)
-
Public key "id" and "type" members duplicate JWK "kid" and "kty" members w3c/did#170 (4 comments by @msporny, @OR13)
-
We should find a better term than "DID Registry" and better define what it refers to w3c/did#162 (4 comments by @peacekeeper, @rhiaro, @selfissued, @talltree)
-
Shall we need more words on how DIDs support for a centralized identity systems? w3c/did#211 (3 comments by @iherman, @YueJing95)
-
Is method-specific-id supposed to be equivalent to param-char? w3c/did#45 (3 comments by @peacekeeper, @talltree)
-
Inconsistent normative language around `id` on public keys w3c/did#134 (3 comments by @msporny, @OR13, @peacekeeper)
-
publicKeyJwk, publicKeyHex, publicKeyBase64, publicKeyBase58 missing from context. w3c/did#23 (3 comments by @msporny, @OR13)
-
Add CBOR a valid type of DID document syntax similar to JSON and on par with JSON-LD w3c/did#92 (3 comments by @jonnycrunch, @msporny, @OR13)
-
Leverage RFC7518 to specify cryptographic algorithms w3c/did#8 (3 comments by @msporny, @selfissued)
-
need rationale in spec for fully qualified DID references as the value of "id" fields w3c/did#15 (2 comments by @brentzundel, @msporny)
-
Inconsistant namspace for `method` and/or `method-specific-id` w3c/did#98 (2 comments by @mitfik, @peacekeeper)
-
Are service endpoints transport layer or application layer specific? w3c/did#16 (2 comments by @kdenhartog, @msporny)
-
inconsistent mental model connecting id, kid, and references inside a DID doc w3c/did#131 (2 comments by @msporny, @OR13)
-
[Authentication] Is Authentication the correct mechanism for specifying the ownership of a Thing? w3c/did#22 (2 comments by @msporny)
-
[DID Operations] "all the operations required of a CKMS" are not specified on the body of this section w3c/did#21 (2 comments by @msporny)
-
Use colon separator or kebab-case for method-specific DID parameter names? w3c/did#35 (2 comments by @OR13, @talltree)
-
Add support for ethereumAddress public key type in @context w3c/did#55 (2 comments by @OR13, @selfissued)
-
Do we need a DID method-type feature (capturing new discussion) w3c/did#152 (1 comment by @kdenhartog)
-
Clarification of other verification methods in authentication section missing w3c/did#57 (1 comment by @dmitrizagidulin)
-
Unclear which verification methods are authorized for did document operations w3c/did#195 (1 comment by @msporny)
-
-
7 pull requests opened.
-
HTML errors w3c/did#209, by @iherman.
-
Add producer/consumer language w3c/did#197, by @jricher.
-
Add IANA Considerations section. Fix #1. w3c/did#196, by @msporny.
-
Add DID Delegate terminology. Remove delegate/dependent. Fix #4. w3c/did#192, by @msporny.
-
Define all conformance classes. Fix #80. w3c/did#191, by @msporny.
-
Refactor DID Core specification based on DID WG F2F consensus. w3c/did#186, by @msporny.
-
Rebased version of rhiaro's other PR #123 w3c/did#184, by @msporny.
-
-
8 pull requests merged.
-
Add producer/consumer language w3c/did#197.
-
Define all conformance classes. Fix #80. w3c/did#191.
-
Add IANA Considerations section. Fix #1. w3c/did#196.
-
Cut down security note; fixes #115 w3c/did#155.
-
Rewrite authentication section w3c/did#123.
-
-
10 pull requests closed.
-
HTML errors w3c/did#209.
-
Add publicKeyHex as a valid publicKey format w3c/did#63.
-
Update did-v0.11.jsonld to match the current spec w3c/did#156.
-
removed "context" from requirements w3c/did#145.
-
Enable pure JSON processing of DID Documents w3c/did#142.
-
Rebased version of rhiaro's other PR #123 w3c/did#184.
-
Remove "Created" property section. w3c/did#28.
-
Remove "Updated" property section. w3c/did#27.
-
-
20 pull requests received 178 new comments.
-
Refactor DID Core specification based on DID WG F2F consensus. w3c/did#186 (21 comments by @iherman, @jandrieu, @jricher, @msporny, @OR13, @selfissued)
-
Add README for context directory. w3c/did#91 (12 comments by @csuwildcat, @msporny, @OR13, @selfissued)
-
Define all conformance classes. Fix #80. w3c/did#191 (10 comments by @dmitrizagidulin, @jricher, @msporny, @peacekeeper)
-
detail how unsupported CRUD operations should be defined w3c/did#150 (4 comments by @kdenhartog, @msporny)
-
Add DID Delegate terminology. Remove delegate/dependent. Fix #4. w3c/did#192 (1 comment by @msporny)
w3c/did-use-cases
-
1 issue opened.
-
Decentralised Identity Resolution w3c/did-use-cases#67, by @ydennisy.
-
w3c/did-resolution
-
1 issue opened.
-
Disallow JSON-LD remote context retrieval w3c/did-resolution#53, by @peacekeeper.
-
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
Use Cases and Requirements for Decentralized Identifiers published as a Working Draft. History of Use Cases and Requirements for Decentralized Identifiers
-
Participants
-
2 participants joined.
-
Dirk Balfanz (Google LLC) joined.
-
Kaliya Young (Wireline) joined.
-
-
2 organizations joined.
-
Google LLC joined.
-
Wireline joined.
-
GitHub
w3c/did
-
31 issues opened.
-
Use of undefined term "resource" w3c/did#182, by @selfissued.
-
Use of undefined term "verifiable timestamps" w3c/did#181, by @selfissued.
-
Confusing statement about key revocation on DLTs w3c/did#180, by @selfissued.
-
Do we really want to recommend polling for changes? w3c/did#179, by @selfissued.
-
Use of undefined term "object capabilities" w3c/did#177, by @selfissued.
-
Underspecified semantics of "updated" property w3c/did#174, by @selfissued.
-
Should multiple "controller" values be expressible? w3c/did#173, by @selfissued.
-
Use of undefined term "verification method" w3c/did#172, by @selfissued.
-
Add public key examples using JWKs w3c/did#171, by @selfissued.
-
Underspecified semantics of revoked keys w3c/did#168, by @selfissued.
-
Term "CRUD operations" is used without being defined w3c/did#167, by @selfissued.
-
Statement on stable DID Registries not actionable w3c/did#166, by @selfissued.
-
What are entityship and start-of-authority (SOA) problems? w3c/did#165, by @selfissued.
-
Unmotivated statement about JSON pointers w3c/did#164, by @selfissued.
-
Use of undefined terms "graph-based" and "tree-based" w3c/did#161, by @selfissued.
-
Remove matrix parameters from the DID specification w3c/did#159, by @selfissued.
-
Add usage / key usage for sidetree methods w3c/did#158, by @OR13.
-
Decoupling DID Core spec from LD-Proof / LDS specs w3c/did#154, by @awoie.
-
Allowing embedded custom contexts w3c/did#153, by @gjgd.
-
Do we need a DID method-type feature (capturing new discussion) w3c/did#152, by @cboscolo.
-
Include discussion of eIDAS levels-of-assurance w3c/did#151, by @Oskar-van-Deventer.
-
Does a did method have to implement all CRUD operations? w3c/did#149, by @gjgd.
-
-
2 issues closed.
-
Normative language in Security Considerations w3c/did#107.
-
-
19 issues received 91 new comments.
-
When is a DID subject not a DID controller (if ever)? w3c/did#122 (19 comments by @cboscolo, @dlongley, @ewelton, @iherman, @jandrieu, @Oskar-van-Deventer)
-
inconsistent mental model connecting id, kid, and references inside a DID doc w3c/did#131 (12 comments by @awoie, @David-Chadwick, @OR13, @tplooker)
-
Include discussion of eIDAS levels-of-assurance w3c/did#151 (10 comments by @awoie, @bumblefudge, @nalamillo, @Oskar-van-Deventer, @talltree)
-
Do we need a DID method-type feature (capturing new discussion) w3c/did#152 (7 comments by @cboscolo, @jricher, @kdenhartog, @OR13, @peacekeeper, @talltree)
-
Enable instant DID use/resolution for DID Methods that include a propagation delay w3c/did#70 (7 comments by @cboscolo, @kdenhartog, @OR13, @talltree)
-
need rationale in spec for fully qualified DID references as the value of "id" fields w3c/did#15 (6 comments by @cboscolo, @csuwildcat, @dhh1128, @msporny, @OR13)
-
Remove matrix parameters from the DID specification w3c/did#159 (4 comments by @peacekeeper, @selfissued)
-
Does a did method have to implement all CRUD operations? w3c/did#149 (4 comments by @gjgd, @iherman, @kdenhartog)
-
Move or reference section about extending in 5.1 Contexts to 5.10 Extensibility w3c/did#148 (2 comments by @gjgd, @OR13)
-
Figure out three fundamental roles of DIDs (controller, subject, XXX) w3c/did#4 (1 comment by @Oskar-van-Deventer)
-
What are the differences between Verifiable Credentials and DID document? w3c/did#147 (1 comment by @aceshim)
-
-
3 pull requests opened.
-
Update did-v0.11.jsonld to match the current spec w3c/did#156, by @OR13.
-
Cut down security note; fixes #115 w3c/did#155, by @rhiaro.
-
detail how unsupported CRUD operations should be defined w3c/did#150, by @kdenhartog.
-
-
4 pull requests merged.
-
DID Documents section editorial re-review w3c/did#141.
-
Editorial review of Privacy Considerations section w3c/did#133.
-
Clarify when DID parameters should (not) be used. w3c/did#144.
-
1 pull request closed.
-
Add "transform-keys" matrix parameter. w3c/did#138.
-
-
8 pull requests received 38 new comments.
-
DID Documents section editorial re-review w3c/did#141 (18 comments by @grantnoble, @msporny, @TallTed)
-
detail how unsupported CRUD operations should be defined w3c/did#150 (9 comments by @gjgd, @kdenhartog, @msporny, @peacekeeper)
-
Move DID method security & privacy into normative section w3c/did#130 (3 comments by @msporny, @rhiaro)
-
w3c/did-use-cases
-
1 issue reopened.
-
What does it mean for a DID to be "recorded in a registry"? w3c/did-use-cases#14, by @philarcher.
-
-
4 issues received 5 new comments.
-
What does it mean for a DID to be "recorded in a registry"? w3c/did-use-cases#14 (2 comments by @philarcher)
-
New Use Case Proposals: 1) FMCG Intelligent Serial Number, 2) VIN DID, 3)Circular Economy w3c/did-use-cases#55 (1 comment by @philarcher)
-
-
4 pull requests opened.
-
Updating 'Accessing Master Data of Entities' UC w3c/did-use-cases#66, by @philarcher.
-
Added three new short UCs w3c/did-use-cases#65, by @philarcher.
-
Proposed credit method for focal use cases w3c/did-use-cases#64, by @philarcher.
-
Addition of vehicle assemblies use case w3c/did-use-cases#63, by @philarcher.
-
-
3 pull requests merged.
-
Added three new short UCs w3c/did-use-cases#65.
-
Proposed credit method for focal use cases w3c/did-use-cases#64.
-
Addition of vehicle assemblies use case w3c/did-use-cases#63.
-
-
2 pull requests received 5 new comments.
w3c/did-extensions
-
1 issue opened.
-
Why are we using didv in our core context? w3c/did-extensions#48, by @OR13.
-
-
1 issue received 1 new comment.
w3c/did-resolution
-
1 issue received 1 new comment.
-
w3c/did-resolution#36 (1 comment by @vongohren)
-