Comments (13)
We have a candidate for publication at https://w3c.github.io/did-use-cases/FPWD/2019-11-21/index.html
Once that is approved by the working group, we'll close out this issue.
from did-use-cases.
The only place that phrase is used is in Section 3 https://w3c.github.io/did-use-cases/#create:
These DIDs may be recorded in a registry in such a manner as to be able to resolve to a DID Document. The DID Document may be dynamically and deterministically generated through resolution or it may be explicitly constructed as a stand-alone resource and either stored or referenced in the registry. In this scenario, the process will need access to any registry, ideally a decentralized system, and like the rest of the DID actions, it should be possible to create the DID without interaction with any particular authority.
This is an accurate statement. It doesn't assert that all DID methods record to a registry. In fact, the paragraph makes it clear that, for example, documents may be deterministically generated instead.
I do expect there is language in the did-core that refers to DID registries as an implied requirement (just because the language is out of date with some of the newer methods). However, the use case document itself avoids discussing the specifics of the design choices such as Methods and Registries as these are means to realize the use cases but not required for understanding the use.
@selfissued Does this address your concern?
I'd like to close this if it does.
from did-use-cases.
I'll try to clean this up in the FPWD, but might not be able to.
from did-use-cases.
I would suggest removing the term registry parts. There are lots of methods such as did:key
and did:ethr
, did:peer
, and non anchored sidetree dids don't require any registration.
from did-use-cases.
We need to consider did:peer and did:key as well.
from did-use-cases.
It's entirely likely that "registry" isn't the right word for this piece of functionality. I don't have a better term off hand. But fundamentally it's about how a DID is tied to a DID document, which is part of the resolution process.
from did-use-cases.
This deserves further discussion. We'll flag this term as under discussion for the FPWD.
from did-use-cases.
This issue is explicitly referenced from the current draft https://w3c.github.io/did-use-cases/#issue-container-number-14
from did-use-cases.
@jandrieu's last comment, from 2019-11-14, says we'll close this issue when FPWD is published - which happened. So I'm closing this!
from did-use-cases.
Closed by mistake. Apologies.
from did-use-cases.
The question at the moment is where is the term "registry" in terms of the DID Document? Is that still a term in use? @msporny @talltree ? I see "DID Registry" is still a term in use, is that stable or still in discussion?
from did-use-cases.
The question at the moment is where is the term "registry" in terms of the DID Document? Is that still a term in use? @msporny @talltree ? I see "DID Registry" is still a term in use, is that stable or still in discussion?
There is a PR in to change "DID Registry" to "Verifiable Data Registry". We plan to no longer use the term "DID Registry". The two terms that will be left in the spec after the most recent PRs go in are:
- Verifiable Data Registry (the place where DIDs are recorded)
- DID Specifications Registries (the place where developers go to find out what properties can be used in a DID Document, what DID Methods are available, etc.)
from did-use-cases.
Closing per WG conversation.
from did-use-cases.
Related Issues (20)
- Add Focal Use-Case for human-centered DID interoperability: Alice Rents a Car HOT 8
- Add use case for DIDs+eIDAS HOT 24
- Add human story for 2.1 online shopper HOT 1
- Add human story for 2.1 Vehicle assemblies HOT 1
- Add human story for 2.3 Encrypted Data Vault HOT 1
- Consider removing use case 2.4 HOT 2
- Add human story to 2.5 Identifiers in an ecosystem of verifiable credentials (VCs): HOT 1
- Add a human story to use case 2.6 Sharing opted-in information across platforms HOT 1
- Psuedonymity rather than anonymity in Use Case 2.8 HOT 1
- Add Use-Case for Ambient Surveillance HOT 15
- Interop with the web platform
- Possibility to add a use case
- Add Domain Map for use cases HOT 6
- rename master branch HOT 11
- Add M-of-N use case HOT 1
- Add WebAuthN use case HOT 5
- Add non-public key verification HOT 1
- DIDComm and serviceEndpoints HOT 12
- Package Manager / App Store and Service Endpoints HOT 5
- Service Endpoints & Private Data Exchange without Publishing to a Blockchain / VDR HOT 12
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from did-use-cases.