Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should the DID Document data model be moved to the DID Resolution spec? #15

Closed
mwherman2000 opened this issue Feb 7, 2019 · 9 comments
Labels
pending-close Issue will be closed shortly if no objections

Comments

@mwherman2000
Copy link

mwherman2000 commented Feb 7, 2019

[Duplicate of DID spec comment: https://github.com/w3c-ccg/did-spec/issues/151#issuecomment-461417659]

Where should DID Documents be defined/spec'ed out? ...given that they are exclusively an output of the DID Resolution process?

Digging deeper...

  1. Is there an analogy/are there parallels between:

    • the DID and DID Document "information architecture", and
    • the IP Address/TCP-IP/DNS information architecture?
  2. Is the IP Address/TCP/IP information architecture analogous to DIDs?
    ...similar to the way DID Documents are to DNS entries?

  3. If it doesn't make sense to spec DNS entries in the IP/TCP-IP specs, why are we trying to spec DID Documents in the DID spec (instead of the DID Resolution spec)?

Reference: Here's a DNS primer that some people might find helpful (DNS is much more than a domain name => IP address resolver):
https://hyperonomy.com/2019/01/02/dns-domain-name-service-a-detailed-high-level-overview/

Here's an updated version of the DID 6-Layer Model to illustrate the above point...

image

@mwherman2000
Copy link
Author

Cross-reference: w3c-ccg/community#20 - DID Resolution spec "charter"

@mwherman2000
Copy link
Author

The DID Document data model being defined by the DID Resolution spec is supported by the following statement in the Introduction https://w3c-ccg.github.io/did-resolution/#introduction. It states...

This specification defines common requirements, input parameters and output data, architectural options, and various considerations for the DID Resolution process.

@mwherman2000
Copy link
Author

Being discussed/answered here: #18 (comment)

@peacekeeper
Copy link
Collaborator

@mwherman2000 I think the consensus was that the DID (Document) data model would NOT be moved to the DID Resolution spec. Is there any reason why you re-opened this issue?

@mwherman2000
Copy link
Author

mwherman2000 commented Feb 8, 2019

@peacekeeper ...only because I had clicked on the Close and comment button by mistake (before we discussed this on the call).

Did I capture the ideas discussed on yesterday's call properly in this diagram? #18 (comment)

@peacekeeper
Copy link
Collaborator

Okay I see. How about then we close this issue now and discuss the diagram on the other open issue #18 ?

@peacekeeper
Copy link
Collaborator

@mwherman2000 considering this thread, and this comment #18 (comment), and this thread w3c-ccg/did-spec#167, I believe the consensus is that the DID Document data model will NOT be moved to the DID Resolution spec. So we can close this issue, do you agree?

@peacekeeper
Copy link
Collaborator

I think this issue can be closed, since it's clear that the DID document data model will not be moved to the DID Resolution spec.

In fact, there is an ongoing discussion now whether DID Core should be updated to reference the Controller Document Specification:

w3c/did-core#854

@peacekeeper peacekeeper added the pending-close Issue will be closed shortly if no objections label Sep 5, 2024
@peacekeeper
Copy link
Collaborator

Closing, as discussed in today's DID WG meeting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-close Issue will be closed shortly if no objections
Projects
None yet
Development

No branches or pull requests

2 participants