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.

Sign up for GitHub

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

Jump to bottom

Fill or remove section on DID URL Dereferencing #364

Closed
peacekeeper opened this issue Jul 30, 2020 · 3 comments
Closed

Fill or remove section on DID URL Dereferencing #364

peacekeeper opened this issue Jul 30, 2020 · 3 comments
Assignees
@peacekeeper
Labels
pr exists There is an open PR to address this issue

Comments

@peacekeeper
Copy link
Contributor

A section on DID Resolution has been added (#331). A section on Metadata Structure has also been added (#347).

We also have an empty placeholder section on DID URL Dereferencing, which we should either fill, or remove. Let's discuss in this new issue.

If there is support for having this section, we should be able to re-use content from existing PRs such as #253.

For example, an abstract DID URL dereferencing function could look like this (analogous to the resolveStream function):

dereferenceStream ( did-url, did-url-dereferencing-input-metadata ) ->
    ( did-url-dereferencing-metadata, content-stream, did-document-metadata )
@peacekeeper peacekeeper self-assigned this Jul 30, 2020
This was referenced Jul 30, 2020
Closed
Closed
@wyc
Copy link
Contributor

wyc commented Aug 18, 2020

@peacekeeper how does your work found in the CCG relate to this section?
https://w3c-ccg.github.io/did-resolution/

I have been reviewing #253

@wyc wyc mentioned this issue Aug 18, 2020
Closed
@peacekeeper
Copy link
Contributor Author

@wyc the idea is that DID Core will only contain definitions of abstract functions with their inputs and outputs. The resolve() function has already been added in https://w3c.github.io/did-core/#did-resolution. This issue is now about adding the dereference() function in a similar way.

DID Core however would leave out implementation details such as resolver architectures, protocols, metadata data formats, algorithms, etc.. The DID Resolution spec in the CCG is meant to be the place for such content that goes beyond the abstract function definition.

@wyc wyc mentioned this issue Aug 26, 2020
Closed
wyc added a commit to wyc/did-core that referenced this issue Aug 26, 2020
@wyc
Fill DID URL Dereferencing Section
a646c95 
As per: w3c#364

- Fill the DID URL Dereferencing section with abstract function, function
  parameters, return values, and their definitions, using language and format
  consistent to (and drawn from) the DID Resolution section.
- Delegate the handling of DID URLs which are also DIDs to the DID Resolution
  process, thereby ensuring that DID URL Dereferencing is a superset of DID
  Resolution, just as DID URLs are a superset of DIDs.
@wyc wyc mentioned this issue Aug 26, 2020
Merged
@peacekeeper peacekeeper added the pr exists There is an open PR to address this issue label Sep 3, 2020
msporny pushed a commit that referenced this issue Sep 14, 2020
@wyc @msporny
Fill DID URL Dereferencing Section
8bfe90e 
As per: #364

- Fill the DID URL Dereferencing section with abstract function, function
  parameters, return values, and their definitions, using language and format
  consistent to (and drawn from) the DID Resolution section.
- Delegate the handling of DID URLs which are also DIDs to the DID Resolution
  process, thereby ensuring that DID URL Dereferencing is a superset of DID
  Resolution, just as DID URLs are a superset of DIDs.
@peacekeeper
Copy link
Contributor Author

This was addressed by #381. Closing.

msporny pushed a commit to w3c/cid that referenced this issue Jun 2, 2024
@wyc @msporny
Fill DID URL Dereferencing Section
46c4bb7 
As per: w3c/did-core#364

- Fill the DID URL Dereferencing section with abstract function, function
  parameters, return values, and their definitions, using language and format
  consistent to (and drawn from) the DID Resolution section.
- Delegate the handling of DID URLs which are also DIDs to the DID Resolution
  process, thereby ensuring that DID URL Dereferencing is a superset of DID
  Resolution, just as DID URLs are a superset of DIDs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@peacekeeper peacekeeper

Labels
pr exists There is an open PR to address this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@peacekeeper @wyc