Decentralized Identifier Working Group - Activity in 2019
No matches.
TR publications
-
2 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
-
Participants
-
4 organizations joined.
-
Baidu, Inc. joined.
-
LG Electronics joined.
-
Thomson Reuters Corp. joined.
-
Viacom inc. joined.
-
GitHub
w3c/did
-
5 issues opened.
-
Should we support multiple encodings of DID docs? w3c/did#140, by @talltree.
-
Should the DID parameters be normative in the spec? w3c/did#137, by @iherman.
-
Inconsistent normative language around `id` on public keys w3c/did#134, by @rhiaro.
-
3 issues closed.
-
Supported public key formats? w3c/did#67.
-
DID Method discovery mechanism requirement w3c/did#12.
-
-
14 issues received 106 new comments.
-
DID Doc Encoding: Abstract Data Model in JSON w3c/did#128 (35 comments by @darrellodonnell, @dhh1128, @dlongley, @ewelton, @iherman, @mikelodder7, @msporny, @OR13, @peacekeeper, @selfissued, @SmithSamuelM, @TallTed, @talltree)
-
Should the DID parameters be normative in the spec? w3c/did#137 (19 comments by @dlongley, @iherman, @msporny, @peacekeeper, @selfissued, @TallTed, @talltree)
-
Should we support multiple encodings of DID docs? w3c/did#140 (11 comments by @brentzundel, @darrellodonnell, @ewelton, @msporny, @peacekeeper, @selfissued, @TallTed)
-
Enable instant DID use/resolution for DID Methods that include a propagation delay w3c/did#70 (9 comments by @cboscolo, @csuwildcat, @OR13, @peacekeeper)
-
inconsistent mental model connecting id, kid, and references inside a DID doc w3c/did#131 (5 comments by @awoie, @dlongley, @kdenhartog, @peacekeeper)
-
Consider adding a well-defined method-specific section to the DID Document w3c/did#143 (4 comments by @cboscolo, @OR13, @talltree)
-
Add CBOR a valid type of DID document syntax similar to JSON and on par with JSON-LD w3c/did#92 (1 comment by @burnburn)
-
-
10 pull requests opened.
-
Simplifies spec by using pure JSON instead of JSON-LD w3c/did#146, by @mikelodder7.
-
removed "context" from requirements w3c/did#145, by @jricher.
-
Clarify when DID parameters should (not) be used. w3c/did#144, by @peacekeeper.
-
Enable pure JSON processing of DID Documents w3c/did#142, by @msporny.
-
DID Documents section editorial re-review w3c/did#141, by @grantnoble.
-
Add "id" DID parameter instead of "service". w3c/did#139, by @peacekeeper.
-
Add "transform-keys" matrix parameter. w3c/did#138, by @peacekeeper.
-
Fix markup issue w3c/did#136, by @deniak.
-
Update index.html w3c/did#135, by @iherman.
-
Editorial review of Privacy Considerations section w3c/did#133, by @grantnoble.
-
-
13 pull requests merged.
-
Editorial Security Considerations section review w3c/did#132.
-
Fix markup issue w3c/did#136.
-
Add key expression formats for secp256k1. w3c/did#101.
-
Add key expression formats for ed25519. w3c/did#102.
-
Add key expression formats for secp256r1. w3c/did#109.
-
Add key expression formats for Curve25519. w3c/did#110.
-
Update index.html w3c/did#135.
-
Fix typo in index.html w3c/did#129.
-
DID resolvers section review w3c/did#127.
-
DID methods section review w3c/did#126.
-
DID Document Syntax section review w3c/did#125.
-
Data Model section editorial review w3c/did#114.
-
3 pull requests closed.
-
DID Documents section review w3c/did#117.
-
Add "key" DID URL matrix parameter. w3c/did#59.
-
23 pull requests received 225 new comments.
-
Enable pure JSON processing of DID Documents w3c/did#142 (102 comments by @burnburn, @cboscolo, @csuwildcat, @dhh1128, @dlongley, @iherman, @jricher, @mavarley, @mikelodder7, @msporny, @OR13, @peacekeeper, @selfissued, @SmithSamuelM, @TallTed, @talltree)
-
removed "context" from requirements w3c/did#145 (23 comments by @cboscolo, @dlongley, @iherman, @jricher, @peacekeeper, @selfissued, @SmithSamuelM, @TallTed)
-
Add `initial-values` matrix parameter to Generic DID Parameters w3c/did#84 (7 comments by @cboscolo, @csuwildcat, @OR13, @peacekeeper, @TallTed)
-
Add key expression formats for Curve25519. w3c/did#110 (7 comments by @dlongley, @msporny, @TallTed)
-
Add key expression formats for secp256r1. w3c/did#109 (6 comments by @kdenhartog, @msporny, @TallTed)
-
Add "key" DID URL matrix parameter. w3c/did#59 (6 comments by @dmitrizagidulin, @iherman, @msporny, @OR13, @peacekeeper)
-
Simplifies spec by using pure JSON instead of JSON-LD w3c/did#146 (5 comments by @iherman, @mikelodder7, @TallTed, @talltree)
-
Add "id" DID parameter instead of "service". w3c/did#139 (4 comments by @dlongley, @msporny, @peacekeeper)
-
Add "transform-keys" matrix parameter. w3c/did#138 (4 comments by @awoie, @dlongley, @msporny, @peacekeeper)
-
Add "content-type" and "content-id" DID URL matrix parameters. w3c/did#61 (3 comments by @brentzundel, @peacekeeper)
-
Move DID method security & privacy into normative section w3c/did#130 (2 comments by @msporny, @rhiaro)
-
w3c/did-use-cases
-
3 issues opened.
-
Jargon from VCDM and crypto w3c/did-use-cases#62, by @TzviyaSiegman.
-
DID CRUD is a confusing term w3c/did-use-cases#61, by @TzviyaSiegman.
-
Use Case Pile-up w3c/did-use-cases#60, by @bumblefudge.
-
-
1 issue closed.
-
Tiny (mostly editorial) comments. w3c/did-use-cases#49.
-
-
5 issues received 13 new comments.
-
Decentralized Identities are simply Credentials and should be defined/called out as such... w3c/did-use-cases#56 (4 comments by @mwherman2000, @TallTed)
-
Suggestion: Better partitioning of "DID" actions w3c/did-use-cases#58 (3 comments by @mwherman2000, @TallTed)
-
New Use Case Proposal: Blending DIDs with X.509 w3c/did-use-cases#59 (3 comments by @cstoecker, @dlongley, @TallTed)
-
New Use Case Proposals: 1) FMCG Intelligent Serial Number, 2) VIN DID, 3)Circular Economy w3c/did-use-cases#55 (2 comments by @bumblefudge, @cstoecker)
-
-
2 pull requests merged.
-
Editorial changes. Will Fix #49 w3c/did-use-cases#54.
-
Echidna setup w3c/did-use-cases#53.
-
-
1 pull request closed.
-
Add Terminology section. Fixes #12. w3c/did-use-cases#33.
-
-
2 pull requests received 3 new comments.
w3c/did-resolution
-
1 pull request merged.
-
Add details about resolver architectures w3c/did-resolution#44.
-
TR publications
-
5 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 as a First Public Working Draft. History of Use Cases and Requirements for Decentralized Identifiers
-
Decentralized Identifiers (DIDs) v1.0 published as a First Public Working Draft. History of Decentralized Identifiers (DIDs) v1.0
-
Participants
-
1 participant joined.
-
Jonathan Holt (Consensys) joined.
-
GitHub
w3c/did-use-cases
-
15 issues opened.
-
New Use Case Proposal: Blending DIDs with X.509 w3c/did-use-cases#59, by @cstoecker.
-
Suggestion: Better partitioning of "DID" actions w3c/did-use-cases#58, by @mwherman2000.
-
Confusion about what a "DID" is throughout the document [DID Credentials] w3c/did-use-cases#57, by @mwherman2000.
-
Decentralized Identities are simply Credentials and should be defined/called out as such... w3c/did-use-cases#56, by @mwherman2000.
-
New Use Case Proposals: 1) FMCG Intelligent Serial Number, 2) VIN DID, 3)Circular Economy w3c/did-use-cases#55, by @cstoecker.
-
Consider use cases from key representation discussion in did-core w3c/did-use-cases#52, by @jandrieu.
-
Focal use cases: more emphasis on DID-s? w3c/did-use-cases#50, by @iherman.
-
Tiny (mostly editorial) comments. w3c/did-use-cases#49, by @iherman.
-
Terminology section issues w3c/did-use-cases#48, by @iherman.
-
Term 'Relying party' w3c/did-use-cases#40, by @philarcher.
-
Relying Party terminology could confuse things w3c/did-use-cases#39, by @msporny.
-
Title of the document w3c/did-use-cases#28, by @iherman.
-
Language usage in the use cases w3c/did-use-cases#27, by @iherman.
-
General comment on the document structure w3c/did-use-cases#26, by @iherman.
-
"Surveillance capitalism" terminology? w3c/did-use-cases#25, by @iherman.
-
-
10 issues closed.
-
Use Cases document missing Terminology section w3c/did-use-cases#12.
-
Synchronize DID role terminology between Use Cases and Core specs w3c/did-use-cases#10.
-
Should "Althea" be "Alice" in the Prescriptions example? w3c/did-use-cases#22.
-
Don't use actual domain names in examples w3c/did-use-cases#18.
-
Term 'Relying party' w3c/did-use-cases#40.
-
Rotate operation section missing its section number w3c/did-use-cases#16.
-
Use Cases document missing References section w3c/did-use-cases#11.
-
No reference for "the DID Resolution specification" w3c/did-use-cases#15.
-
Clarify intent behind he language "When a DID contains a service name" w3c/did-use-cases#17.
-
Title of the document w3c/did-use-cases#28.
-
-
23 issues received 54 new comments.
-
When do we publish a FPWD of the Use Cases document? w3c/did-use-cases#8 (7 comments by @brentzundel, @burnburn, @iherman, @jandrieu, @philarcher)
-
What does it mean for a DID to be "recorded in a registry"? w3c/did-use-cases#14 (7 comments by @jandrieu, @jricher, @ken-ebert, @OR13, @philarcher)
-
Should "Althea" be "Alice" in the Prescriptions example? w3c/did-use-cases#22 (6 comments by @agropper, @iherman, @jandrieu, @philarcher, @selfissued)
-
Confusion about what a "DID" is throughout the document [DID Credentials] w3c/did-use-cases#57 (3 comments by @mwherman2000)
-
Language usage in the use cases w3c/did-use-cases#27 (3 comments by @iherman, @jandrieu, @philarcher)
-
"Surveillance capitalism" terminology? w3c/did-use-cases#25 (3 comments by @bumblefudge, @iherman, @jandrieu)
-
Don't use actual domain names in examples w3c/did-use-cases#18 (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)
-
General comment on the document structure w3c/did-use-cases#26 (2 comments by @iherman, @philarcher)
-
No reference for "the DID Resolution specification" w3c/did-use-cases#15 (2 comments by @jandrieu, @peacekeeper)
-
Clarify intent behind he language "When a DID contains a service name" w3c/did-use-cases#17 (2 comments by @jandrieu, @peacekeeper)
-
Synchronize DID role terminology between Use Cases and Core specs w3c/did-use-cases#10 (1 comment by @philarcher)
-
Describe relationship between DID Methods and DID Authentication in Use Cases document w3c/did-use-cases#13 (1 comment by @jandrieu)
-
Background statement in Decentralized Corporate Identifiers description not obvious w3c/did-use-cases#19 (1 comment by @jandrieu)
-
Supply chain validation mechanisms not obvious in Decentralized Corporate Identifiers description w3c/did-use-cases#20 (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 @jandrieu)
-
-
21 pull requests opened.
-
Editorial changes. Will Fix #49 w3c/did-use-cases#54, by @philarcher.
-
Echidna setup w3c/did-use-cases#53, by @iherman.
-
Updating link to Generic DID Parameter Names w3c/did-use-cases#51, by @philarcher.
-
Updated the ReSpec header: noRecTrack w3c/did-use-cases#47, by @iherman.
-
Snapshot for FPWD w3c/did-use-cases#46, by @rhiaro.
-
replaced revoke with deactivate in did_actions.png w3c/did-use-cases#45, by @jandrieu.
-
Deleting duplicate revoke section w3c/did-use-cases#44, by @philarcher.
-
Import terms from did-core w3c/did-use-cases#43, by @rhiaro.
-
Referring to correct Issue no w3c/did-use-cases#42, by @philarcher.
-
Updates and flags for terminology section w3c/did-use-cases#41, by @philarcher.
-
replaced joe@aol.com with joe@example.com w3c/did-use-cases#38, by @jandrieu.
-
switched Alice/Bob/Charlie to Alicia/Barkley/Connor w3c/did-use-cases#37, by @jandrieu.
-
New intro & terminology w3c/did-use-cases#36, by @philarcher.
-
Fixing my errors w3c/did-use-cases#35, by @philarcher.
-
Shift to problem statement w3c/did-use-cases#34, by @philarcher.
-
Add Terminology section. Fixes #12. w3c/did-use-cases#33, by @peacekeeper.
-
Clarify dereferencing of DID URLs with "service" parameter. Fixes #17. w3c/did-use-cases#32, by @peacekeeper.
-
Add References section. Fixes #11. Fixes #15. w3c/did-use-cases#31, by @peacekeeper.
-
Change "revoke" to "deactivate". w3c/did-use-cases#30, by @peacekeeper.
-
Add "requirements" to title of document w3c/did-use-cases#29, by @brentzundel.
-
FPWD static ready w3c/did-use-cases#24, by @rhiaro.
-
-
18 pull requests merged.
-
Updating link to Generic DID Parameter Names w3c/did-use-cases#51.
-
Updated the ReSpec header: noRecTrack w3c/did-use-cases#47.
-
Snapshot for FPWD w3c/did-use-cases#46.
-
Import terms from did-core w3c/did-use-cases#43.
-
replaced revoke with deactivate in did_actions.png w3c/did-use-cases#45.
-
Deleting duplicate revoke section w3c/did-use-cases#44.
-
Referring to correct Issue no w3c/did-use-cases#42.
-
Updates and flags for terminology section w3c/did-use-cases#41.
-
switched Alice/Bob/Charlie to Alicia/Barkley/Connor w3c/did-use-cases#37.
-
replaced joe@aol.com with joe@example.com w3c/did-use-cases#38.
-
New intro & terminology w3c/did-use-cases#36.
-
Change "revoke" to "deactivate". w3c/did-use-cases#30.
-
Add References section. Fixes #11. Fixes #15. w3c/did-use-cases#31.
-
Clarify dereferencing of DID URLs with "service" parameter. Fixes #17. w3c/did-use-cases#32.
-
Fixing my errors w3c/did-use-cases#35.
-
Shift to problem statement w3c/did-use-cases#34.
-
Add "requirements" to title of document w3c/did-use-cases#29.
-
FPWD static ready w3c/did-use-cases#24.
-
-
6 pull requests received 21 new comments.
-
Add Terminology section. Fixes #12. w3c/did-use-cases#33 (9 comments by @jandrieu, @peacekeeper, @philarcher, @tplooker)
-
w3c/did
-
15 issues opened.
-
DID Doc Encoding: Abstract Data Model in JSON w3c/did#128, by @SmithSamuelM.
-
Regarding PII Embedded in Key Formats w3c/did#124, by @OR13.
-
When is a DID subject not a DID controller (if ever)? w3c/did#122, by @rhiaro.
-
Horizontal Review: offer review opportunity to TAG w3c/did#119, by @burnburn.
-
Specification needs to be compliant with WCAG 2.0 w3c/did#118, by @burnburn.
-
undecipherable sentence w3c/did#115, by @TallTed.
-
Normative language in Security Considerations w3c/did#107, by @rhiaro.
-
Add contributing.md with specific support for JSON-LD contribution w3c/did#106, by @OR13.
-
Horizontal Review: Accessibility self test w3c/did#105, by @iherman.
-
Horizontal Review: Internationalization self test w3c/did#104, by @iherman.
-
Separating abstract data model from syntaxes w3c/did#103, by @talltree.
-
Document Structure w3c/did#95, by @jricher.
-
Create DID explainer w3c/did#94, by @burnburn.
-
1 issue closed.
-
When do we publish a FPWD? w3c/did#68.
-
-
24 issues received 186 new comments.
-
DID Doc Encoding: Abstract Data Model in JSON w3c/did#128 (45 comments by @awoie, @darrellodonnell, @dhh1128, @dlongley, @dmitrizagidulin, @ewelton, @iherman, @jandrieu, @msporny, @OR13, @peacekeeper, @pelle, @SmithSamuelM, @talltree)
-
Does DID Document metadata belong in the Document? w3c/did#65 (33 comments by @dlongley, @dmitrizagidulin, @iherman, @jandrieu, @jonnycrunch, @msporny, @peacekeeper, @selfissued, @TallTed)
-
Where will the DID contexts(s) live? w3c/did#5 (21 comments by @brentzundel, @burnburn, @dmitrizagidulin, @iherman, @msporny, @peacekeeper, @rhiaro, @yancyribbens)
-
Supported public key formats? w3c/did#67 (16 comments by @awoie, @csuwildcat, @msporny, @OR13, @peacekeeper, @selfissued, @TallTed, @tplooker)
-
Separating abstract data model from syntaxes w3c/did#103 (15 comments by @dhuseby, @jricher, @selfissued, @SmithSamuelM, @talltree)
-
Enable instant DID use/resolution for DID Methods that include a propagation delay w3c/did#70 (8 comments by @csuwildcat, @iherman, @jonnycrunch, @OR13, @yancyribbens)
-
Standardize the key revocation list w3c/did#14 (8 comments by @csuwildcat, @dhh1128, @msporny, @OR13, @peacekeeper, @selfissued)
-
Clarification of other verification methods in authentication section missing w3c/did#57 (5 comments by @awoie, @dhh1128, @dlongley)
-
Inconsistant namspace for `method` and/or `method-specific-id` w3c/did#98 (4 comments by @mitfik, @peacekeeper, @talltree)
-
inconsistent mental model connecting id, kid, and references inside a DID doc w3c/did#131 (2 comments by @awoie, @selfissued)
-
Add support for ethereumAddress public key type in @context w3c/did#55 (2 comments by @awoie, @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)
-
-
25 pull requests opened.
-
Editorial Security Considerations section review w3c/did#132, by @grantnoble.
-
Move DID method security & privacy into normative section w3c/did#130, by @rhiaro.
-
Fix typo in index.html w3c/did#129, by @melvincarvalho.
-
DID resolvers section review w3c/did#127, by @grantnoble.
-
DID methods section review w3c/did#126, by @grantnoble.
-
DID Document Syntax section review w3c/did#125, by @grantnoble.
-
Rewrite authentication section w3c/did#123, by @rhiaro.
-
Fix respec errors on local links w3c/did#121, by @rhiaro.
-
Comment the date so it's always today w3c/did#120, by @rhiaro.
-
DID Documents section review w3c/did#117, by @grantnoble.
-
Decentralized Identifiers (DIDs) section review w3c/did#116, by @grantnoble.
-
Data Model section editorial review w3c/did#114, by @grantnoble.
-
Terminology section editorial updates w3c/did#113, by @grantnoble.
-
Move security and privacy requirements into DID methods w3c/did#112, by @rhiaro.
-
Intro editorial review w3c/did#111, by @grantnoble.
-
Add key expression formats for Curve25519. w3c/did#110, by @msporny.
-
Add key expression formats for secp256r1. w3c/did#109, by @msporny.
-
Editorial pass through latter half w3c/did#108, by @rhiaro.
-
Add key expression formats for ed25519. w3c/did#102, by @msporny.
-
Add key expression formats for secp256k1. w3c/did#101, by @msporny.
-
Initial setup for echidna w3c/did#99, by @iherman.
-
DID-METHOD-REGISTRY is published by CCG, not DVCG w3c/did#97, by @peacekeeper.
-
Update @context URI w3c/did#96, by @rhiaro.
-
Fixed hyperlink w3c/did#93, by @jernst.
-
-
10 pull requests merged.
-
Fix respec errors on local links w3c/did#121.
-
Decentralized Identifiers (DIDs) section review w3c/did#116.
-
Terminology section editorial updates w3c/did#113.
-
Intro editorial review w3c/did#111.
-
Editorial pass through latter half w3c/did#108.
-
Comment the date so it's always today w3c/did#120.
-
Initial setup for echidna w3c/did#99.
-
Update @context URI w3c/did#96.
-
Fixed hyperlink w3c/did#93.
-
-
2 pull requests closed.
-
Remove "Proof" property section. w3c/did#26.
-
23 pull requests received 166 new comments.
-
Add key expression formats for ed25519. w3c/did#102 (25 comments by @dlongley, @kdenhartog, @msporny, @OR13, @selfissued, @TallTed, @tplooker, @troyronda, @yancyribbens)
-
Terminology section editorial updates w3c/did#113 (19 comments by @grantnoble, @iherman, @rhiaro, @TallTed)
-
Add key expression formats for secp256k1. w3c/did#101 (12 comments by @ChristopherA, @dlongley, @msporny, @OR13, @selfissued, @yancyribbens)
-
Add `initial-values` matrix parameter to Generic DID Parameters w3c/did#84 (8 comments by @msporny, @OR13, @peacekeeper, @TallTed)
-
Move security and privacy requirements into DID methods w3c/did#112 (7 comments by @rhiaro, @TallTed)
-
Data Model section editorial review w3c/did#114 (7 comments by @grantnoble, @msporny, @rhiaro, @TallTed)
-
Decentralized Identifiers (DIDs) section review w3c/did#116 (6 comments by @grantnoble, @rhiaro, @TallTed)
-
Move DID method security & privacy into normative section w3c/did#130 (3 comments by @rhiaro, @TallTed)
-
w3c/did-extensions
-
1 issue opened.
-
Resolver descriptions w3c/did-extensions#634, by @philarcher.
-
-
1 issue received 1 new comment.
w3c/did-resolution
-
2 issues opened.
-
Should the network be returned in the resolutionResults object? w3c/did-resolution#52, by @kdenhartog.
-
Percent-encode reserved characters in HTTP Binding w3c/did-resolution#50, by @peacekeeper.
-
-
2 issues received 2 new comments.
-
Should the network be returned in the resolutionResults object? w3c/did-resolution#52 (1 comment by @peacekeeper)
-
Percent-encode reserved characters in HTTP Binding w3c/did-resolution#50 (1 comment by @peacekeeper)
-
-
1 pull request received 2 new comments.
-
Issue#48 fix Capitalization fix for DID spec w3c/did-resolution#49 (2 comments by @mskuybeda, @peacekeeper)
-
Participants
-
1 participant joined.
-
Yancy Ribbens (W3C Invited Experts) joined.
-
-
8 organizations joined.
-
J. Paul Getty Trust joined.
-
Jolocom GmbH joined.
-
Learning Machine, Inc. joined.
-
MITRE Corporation joined.
-
Onfido joined.
-
Mattr Limited joined.
-
Wikimedia Foundation joined.
-
globaliD joined.
-
GitHub
w3c/did-resolution
-
1 issue opened.
-
Change key terms to lowercase w3c/did-resolution#48, by @peacekeeper.
-
-
2 issues closed.
-
DID Resolver Logic Discards DIDs with Query Strings that are not Service Endpoints w3c/did-resolution#42.
-
[Abstract] DID Subject: There's issues with DID Subject not being well defined w3c/did-resolution#16.
-
-
6 issues received 10 new comments.
-
w3c/did-resolution#43 (1 comment by @burnburn)
-
w3c/did-resolution#6 (1 comment by @peacekeeper)
-
w3c/did-resolution#16 (1 comment by @peacekeeper)
-
w3c/did-resolution#40 (1 comment by @peacekeeper)
-
2 pull requests opened.
-
Issue#48 fix Capitalization fix for DID spec w3c/did-resolution#49, by @mskuybeda.
-
Account for fragments in algorithm. w3c/did-resolution#47, by @peacekeeper.
-
-
1 pull request merged.
-
Account for fragments in algorithm. w3c/did-resolution#47.
-
-
2 pull requests received 6 new comments.
w3c/did-use-cases
-
15 issues opened.
-
Describe the relationship between the Single Sign On example and WebAuthn w3c/did-use-cases#23, by @selfissued.
-
Should "Althea" be "Alice" in the Prescriptions example? w3c/did-use-cases#22, by @selfissued.
-
Supply chain validation mechanisms not obvious in Decentralized Corporate Identifiers description w3c/did-use-cases#20, by @selfissued.
-
Background statement in Decentralized Corporate Identifiers description not obvious w3c/did-use-cases#19, by @selfissued.
-
Don't use actual domain names in examples w3c/did-use-cases#18, by @selfissued.
-
Clarify intent behind he language "When a DID contains a service name" w3c/did-use-cases#17, by @selfissued.
-
Rotate operation section missing its section number w3c/did-use-cases#16, by @selfissued.
-
No reference for "the DID Resolution specification" w3c/did-use-cases#15, by @selfissued.
-
What does it mean for a DID to be "recorded in a registry"? w3c/did-use-cases#14, by @selfissued.
-
Describe relationship between DID Methods and DID Authentication in Use Cases document w3c/did-use-cases#13, by @selfissued.
-
Use Cases document missing Terminology section w3c/did-use-cases#12, by @selfissued.
-
Use Cases document missing References section w3c/did-use-cases#11, by @selfissued.
-
Synchronize DID role terminology between Use Cases and Core specs w3c/did-use-cases#10, by @selfissued.
-
When do we publish a FPWD of the Use Cases document? w3c/did-use-cases#8, by @selfissued.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
add links to other DID-WG repositories w3c/did-use-cases#9, by @TallTed.
-
-
1 pull request merged.
-
add links to other DID-WG repositories w3c/did-use-cases#9.
-
w3c/did
-
14 issues opened.
-
Bikeshed the DID specification short name w3c/did#76, by @msporny.
-
tracking revocation of public keys w3c/did#75, by @TallTed.
-
List of authors is broken w3c/did#74, by @peacekeeper.
-
Privacy Considerations - Specifically call out GDPR w3c/did#72, by @msporny.
-
How to integrate certificates with DIDs? w3c/did#69, by @OR13.
-
When do we publish a FPWD? w3c/did#68, by @msporny.
-
Supported public key formats? w3c/did#67, by @msporny.
-
Does DID Document metadata belong in the Document? w3c/did#65, by @dmitrizagidulin.
-
Encrypted serviceEndpoint values? w3c/did#64, by @dmitrizagidulin.
-
Registry handling w3c/did#58, by @iherman.
-
11 issues closed.
-
Bikeshed the DID specification short name w3c/did#76.
-
[Abstract] Clarification... w3c/did#40.
-
Add "DID controller" to "Terminology" section. w3c/did#37.
-
[Introduction] Clarify... w3c/did#42.
-
List of authors is broken w3c/did#74.
-
[Introduction] Doesn't read well... w3c/did#43.
-
-
50 issues received 268 new comments.
-
Supported public key formats? w3c/did#67 (31 comments by @ChristopherA, @dlongley, @gjgd, @iherman, @kdenhartog, @msporny, @OR13, @peacekeeper, @selfissued, @TallTed)
-
Fragment identifier semantics are independent of URI scheme w3c/did#1 (23 comments by @azaroth42, @brentzundel, @dlongley, @iherman, @msporny, @peacekeeper, @TallTed)
-
Enable instant DID use/resolution for DID Methods that include a propagation delay w3c/did#70 (21 comments by @cboscolo, @csuwildcat, @OR13, @peacekeeper, @talltree, @thehenrytsai)
-
Bikeshed the DID specification short name w3c/did#76 (18 comments by @brentzundel, @burnburn, @dlongley, @iherman, @kdenhartog-sybil1, @kimdhamilton, @msporny, @TallTed)
-
Standardize the key revocation list w3c/did#14 (18 comments by @brentzundel, @ChristopherA, @csuwildcat, @dhh1128, @msporny, @OR13, @selfissued, @thereisnogabe)
-
Where will the DID contexts(s) live? w3c/did#5 (17 comments by @dmitrizagidulin, @iherman, @msporny, @OR13, @TallTed)
-
Rewrite Authentication section - controller is wrong w3c/did#2 (11 comments by @ChristopherA, @dhh1128, @dlongley, @msporny, @OR13)
-
Are service endpoints transport layer or application layer specific? w3c/did#16 (11 comments by @ChristopherA, @kdenhartog, @msporny, @peacekeeper, @talltree)
-
need rationale in spec for fully qualified DID references as the value of "id" fields w3c/did#15 (11 comments by @csuwildcat, @dhh1128, @dlongley, @msporny, @peacekeeper)
-
tracking revocation of public keys w3c/did#75 (8 comments by @ChristopherA, @csuwildcat, @dlongley, @msporny, @selfissued, @TallTed)
-
Figure out three fundamental roles of DIDs (controller, subject, XXX) w3c/did#4 (7 comments by @dlongley, @jandrieu, @peacekeeper, @tplooker)
-
Should "id" be mandatory for "service" and "publicKey"? w3c/did#47 (7 comments by @dhh1128, @dlongley, @peacekeeper, @selfissued)
-
Syntactially differentiate data about the DID versus application data w3c/did#85 (5 comments by @dlongley, @iherman, @OR13, @peacekeeper, @selfissued)
-
Leverage existing RFC7517 to specify cryptographic key w3c/did#7 (4 comments by @awoie, @iherman, @msporny, @selfissued)
-
Encrypted serviceEndpoint values? w3c/did#64 (4 comments by @dlongley, @dmitrizagidulin, @peacekeeper)
-
Random capitalization of "key terms" ...those that appear in the Terminology section w3c/did#50 (3 comments by @brentzundel, @peacekeeper)
-
[Overview] "Because DIDs reside on a distributed ledger" - not true? w3c/did#17 (3 comments by @msporny, @rhiaro)
-
[Absract] "proof purposes" is a new term but is not defined anywhere in the document w3c/did#39 (2 comments by @dlongley, @rhiaro)
-
It would be useful to have `services` as a mapping instead of an `array` w3c/did#46 (2 comments by @dlongley)
-
Details on the use of method-specific DID parameters w3c/did#36 (2 comments by @selfissued, @talltree)
-
publicKeyJwk, publicKeyHex, publicKeyBase64, publicKeyBase58 missing from context. w3c/did#23 (2 comments by @selfissued, @tplooker)
-
make publicKey section more explicit for understanding of DIDs reliance on public keys w3c/did#24 (2 comments by @ChristopherA, @jandrieu)
-
[Public Keys] re: referenced keys: Is multiple level recursion allowed? w3c/did#20 (1 comment by @selfissued)
-
Clarification of other verification methods in authentication section missing w3c/did#57 (1 comment by @dlongley)
-
Cheap DIDs and the option to migrate DIDs between ledgers using standard DID Deprecation Registries w3c/did#33 (1 comment by @dlongley)
-
[Authentication] Is Authentication the correct mechanism for specifying the ownership of a Thing? w3c/did#22 (1 comment by @msporny)
-
-
21 pull requests opened.
-
Add README for context directory. w3c/did#91, by @msporny.
-
add links to other DID-WG repositories w3c/did#90, by @TallTed.
-
Admin changes in the respec setting w3c/did#89, by @iherman.
-
Fix grammar in DID path and fragment sentence. w3c/did#88, by @peacekeeper.
-
Ready a First Public Working Draft for the DID specification w3c/did#87, by @msporny.
-
Editorial updates w3c/did#86, by @rhiaro.
-
add `did controller(s)` to matching terms w3c/did#83, by @TallTed.
-
Add "DID resolver" to terminology w3c/did#82, by @peacekeeper.
-
Fix DID query term definition w3c/did#81, by @peacekeeper.
-
restore author list w3c/did#78, by @brentzundel.
-
Ensure DID Controller is used consistently. Fix #37. w3c/did#77, by @msporny.
-
Change capitalization of key terms to lowercase. w3c/did#73, by @peacekeeper.
-
Make "id" optional for services and public keys. w3c/did#66, by @peacekeeper.
-
Add publicKeyHex as a valid publicKey format w3c/did#63, by @gjgd.
-
Add "service-type" DID URL matrix parameter. w3c/did#62, by @peacekeeper.
-
Add "key-type" DID URL matrix parameter. w3c/did#60, by @peacekeeper.
-
Add "key" DID URL matrix parameter. w3c/did#59, by @peacekeeper.
-
-
18 pull requests merged.
-
add links to other DID-WG repositories w3c/did#90.
-
Editorial updates w3c/did#86.
-
Admin changes in the respec setting w3c/did#89.
-
Fix grammar in DID path and fragment sentence. w3c/did#88.
-
Fix DID query term definition w3c/did#81.
-
Add "DID resolver" to terminology w3c/did#82.
-
Make "id" optional for services and public keys. w3c/did#66.
-
Change capitalization of key terms to lowercase. w3c/did#73.
-
restore author list w3c/did#78.
-
Add section on services to data model section. w3c/did#32.
-
Add section on cryptographic keys. w3c/did#31.
-
Add initial text to DID Document section. w3c/did#30.
-
Minor, essentially editorial changes w3c/did#54.
-
1 pull request closed.
-
add `did controller(s)` to matching terms w3c/did#83.
-
-
26 pull requests received 180 new comments.
-
Make "id" optional for services and public keys. w3c/did#66 (21 comments by @msporny, @peacekeeper, @selfissued, @TallTed)
-
Ensure DID Controller is used consistently. Fix #37. w3c/did#77 (14 comments by @dlongley, @jandrieu, @msporny, @peacekeeper, @rhiaro, @TallTed)
-
Change capitalization of key terms to lowercase. w3c/did#73 (14 comments by @dlongley, @msporny, @peacekeeper)
-
Remove "Proof" property section. w3c/did#26 (14 comments by @ChristopherA, @dlongley, @dmitrizagidulin, @iherman, @msporny, @peacekeeper, @TallTed)
-
Remove "Created" property section. w3c/did#28 (13 comments by @ChristopherA, @dlongley, @dmitrizagidulin, @iherman, @msporny, @peacekeeper, @TallTed)
-
Ready a First Public Working Draft for the DID specification w3c/did#87 (12 comments by @iherman, @msporny, @peacekeeper)
-
Add "DID resolver" to terminology w3c/did#82 (10 comments by @msporny, @peacekeeper, @rhiaro, @TallTed)
-
Add section on identifiers to Data Model section. w3c/did#29 (7 comments by @ken-ebert, @msporny, @TallTed)
-
Add `initial-values` matrix parameter to Generic DID Parameters w3c/did#84 (6 comments by @csuwildcat, @peacekeeper)
-
Add publicKeyHex as a valid publicKey format w3c/did#63 (6 comments by @dlongley, @mikelodder7, @msporny, @selfissued)
-
PR to fix issue #42—clarifying meaning of a sentence in intro w3c/did#79 (5 comments by @iherman, @msporny, @peacekeeper, @talltree)
-
Clarify text about actions defined for DID Registry. Fix #43. w3c/did#71 (4 comments by @msporny, @peacekeeper, @TallTed)
-
Add "service-type" DID URL matrix parameter. w3c/did#62 (3 comments by @dlongley, @msporny, @peacekeeper)
-
Add "content-type" and "content-id" DID URL matrix parameters. w3c/did#61 (3 comments by @dlongley, @msporny, @peacekeeper)
-
Add "key-type" DID URL matrix parameter. w3c/did#60 (3 comments by @dlongley, @msporny, @peacekeeper)
-
w3c/did-test-suite
-
1 pull request opened.
-
add links to other DID-WG repositories w3c/did-test-suite#1, by @TallTed.
-
-
1 pull request merged.
-
add links to other DID-WG repositories w3c/did-test-suite#1.
-
w3c/did-rubric
-
1 pull request opened.
-
add links to other DID-WG repositories w3c/did-rubric#1, by @TallTed.
-
-
1 pull request merged.
-
add links to other DID-WG repositories w3c/did-rubric#1.
-
Lifecycle
-
1 charter started.
-
Chartered until 14 December 2020. Participants had to rejoin under this charter.
-
Participants
-
5 participants joined.
-
Kim Duffy (W3C Invited Experts) joined.
-
Adrian Gropper (W3C Invited Experts) joined.
-
Christopher Allen (W3C Invited Experts) joined.
-
Joe Andrieu (Legendary Requirements) joined.
-
Ivan Herman (W3C) joined.
-
-
20 organizations joined.
-
China Academy of Information and Communications Technology (CAICT) joined.
-
OpenLink Software Inc. joined.
-
Microsoft Corporation joined.
-
BrightLink joined.
-
SURF bv joined.
-
Sovrin Foundation joined.
-
AKASHA Foundation joined.
-
Universities Admissions Centre joined.
-
Transmute joined.
-
SecureKey joined.
-
Credly joined.
-
Conexxus joined.
-
Digital Bazaar joined.
-
The Scottish Government joined.
-
GS1 joined.
-
Evernym joined.
-
Wiley joined.
-
Consensys joined.
-
Electronics and Telecommunications Research Institute (ETRI) joined.
-
Danube Tech GmbH joined.
-
GitHub
w3c/did
-
48 issues opened.
-
Add support for ethereumAddress public key type in @context w3c/did#55, by @awoie.
-
Normative vs. non-normative references w3c/did#53, by @iherman.
-
(Minor note) update the IANA file w3c/did#52, by @iherman.
-
Some comments by Steven Rowat w3c/did#48, by @brentzundel.
-
Should "id" be mandatory for "service" and "publicKey"? w3c/did#47, by @brentzundel.
-
DID Test Suite and untestable normative statements w3c/did#44, by @brentzundel.
-
[Introduction] Doesn't read well... w3c/did#43, by @brentzundel.
-
[Introduction] Clarify... w3c/did#42, by @brentzundel.
-
[Introduction] Clarification... w3c/did#41, by @brentzundel.
-
[Abstract] Clarification... w3c/did#40, by @brentzundel.
-
Add "DID controller" to "Terminology" section. w3c/did#37, by @brentzundel.
-
Details on the use of method-specific DID parameters w3c/did#36, by @brentzundel.
-
Should DID syntax allow an empty "method-specific-id"? w3c/did#34, by @brentzundel.
-
(Partially) Encrypting DID Documents w3c/did#25, by @brentzundel.
-
Standardize the key revocation list w3c/did#14, by @brentzundel.
-
Allow DID documents to be retrieved using any URI scheme w3c/did#13, by @brentzundel.
-
DID Method discovery mechanism requirement w3c/did#12, by @brentzundel.
-
What happens when you feed a did: URL to a URL resolver? w3c/did#11, by @brentzundel.
-
Explain RsaSignature2018 w3c/did#10, by @brentzundel.
-
Replace RsaSignature2017 by a standard JWA signature w3c/did#9, by @brentzundel.
-
Leverage RFC7518 to specify cryptographic algorithms w3c/did#8, by @brentzundel.
-
What happened to the "old" list of did-spec issues? w3c/did#6, by @mwherman2000.
-
Where will the DID contexts(s) live? w3c/did#5, by @dmitrizagidulin.
-
Rewrite Authentication section - controller is wrong w3c/did#2, by @msporny.
-
1 issue closed.
-
[Introduction] Clarification... w3c/did#41.
-
-
8 issues received 20 new comments.
-
Rewrite Authentication section - controller is wrong w3c/did#2 (8 comments by @dhh1128, @dlongley, @peacekeeper)
-
publicKeyJwk, publicKeyHex, publicKeyBase64, publicKeyBase58 missing from context. w3c/did#23 (3 comments by @awoie, @dmitrizagidulin, @OR13)
-
Figure out three fundamental roles of DIDs (controller, subject, XXX) w3c/did#4 (3 comments by @brentzundel, @RieksJ)
-
Are service endpoints transport layer or application layer specific? w3c/did#16 (1 comment by @kdenhartog)
-
make publicKey section more explicit for understanding of DIDs reliance on public keys w3c/did#24 (1 comment by @jandrieu)
-
-
9 pull requests opened.
-
Added support for ethereumAddress in context - fixed #55 w3c/did#56, by @awoie.
-
Minor, essentially editorial changes w3c/did#54, by @iherman.
-
Add section on services to data model section. w3c/did#32, by @msporny.
-
Add section on cryptographic keys. w3c/did#31, by @msporny.
-
Add initial text to DID Document section. w3c/did#30, by @msporny.
-
Add section on identifiers to Data Model section. w3c/did#29, by @msporny.
-
Remove "Created" property section. w3c/did#28, by @msporny.
-
Remove "Updated" property section. w3c/did#27, by @msporny.
-
Remove "Proof" property section. w3c/did#26, by @msporny.
-
-
9 pull requests received 21 new comments.
w3c/did-resolution
-
2 issues opened.
-
Add support for JWKS w3c/did-resolution#46, by @awoie.
-
-
2 issues received 6 new comments.
-
1 pull request opened.
-
Add details about resolver architectures w3c/did-resolution#44, by @kdenhartog.
-
w3c/did-use-cases
-
2 issues opened.
-
Need to add coverage of portability/substitutability w3c/did-use-cases#2, by @burnburn.
-
Time Stamp Proofs w3c/did-use-cases#1, by @burnburn.
-
-
1 issue received 1 new comment.