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

Expand DID Configuration to handle more DID-related config items #37

Open
csuwildcat opened this issue Jul 22, 2020 · 9 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@csuwildcat
Copy link
Member

As we look at how to make Credential Manifests discoverable, we have an opportunity to reuse the DID Configuration resource as the place to do that, as well as the things related to it. This might include a list of CMs (or references to them), details about issuance protocols (OIDC endpoints, DIDComms connection details, etc.). I think reusing this for more config stuff makes sense, given it is appropriately named/situated.

@OR13
Copy link
Contributor

OR13 commented Jul 22, 2020

The current resource structure:

{
  "@context": "https://identity.foundation/.well-known/contexts/did-configuration-v0.0.jsonld",
  "entries": [ VC_DATA_MODELs ]
}

Proposed structure:

{
  "@context": "https://identity.foundation/.well-known/contexts/did-configuration-v0.0.jsonld",
  "linked_dids": [ VC_DATA_MODELs ],
  "supported_protocols": [ PROTOCOLs],
  "credential_manifests": [ CREDENTIAL_MANIFESTS]
}

@OR13
Copy link
Contributor

OR13 commented Jul 22, 2020

potential issue is that the supported protocols implicitly apply to all linked dids...

@OR13
Copy link
Contributor

OR13 commented Jul 22, 2020

Link to related hackmd...https://hackmd.io/QCJ3WDcLSXWp8t3hAQ387A

@csuwildcat
Copy link
Member Author

potential issue is that the supported protocols implicitly apply to all linked dids...

Good point - I wonder if there would need to be something in the issuance flow that specifies which DID the user wants to have a given cred issued from?

@OR13
Copy link
Contributor

OR13 commented Jul 22, 2020

We can resolve this issue by adding a member of the supported_protocols objects called linked_dids... which tells you which linked did support which protocols... in the future... this kind of thing should be discoverable from the DID... not some well known centralized resource...

@OR13
Copy link
Contributor

OR13 commented Aug 15, 2020

protocol data model...

name: string
documentation: URI
version: string

additional properties false, really don't want people to overload that object.

@csuwildcat
Copy link
Member Author

Resolved:

  • Other specs will define the schema-based objects this spec contains, and we need to define those objects before we start adding them to this spec
  • Work on Credential Manifest spec
  • Work on PE supported formats feature for inclusion as supported_formats

@OR13
Copy link
Contributor

OR13 commented Aug 17, 2020

well known did configuration now blocked by:

decentralized-identity/presentation-exchange#94

@OR13 OR13 added the enhancement New feature or request label Dec 4, 2020
@OR13
Copy link
Contributor

OR13 commented Dec 4, 2020

I would only be in favor of adding URLs at this time, this issue is going to stick aroudn until we decide which URLs to add or we close this issue :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants