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

feat: add did contexts #712

Merged
merged 3 commits into from
Feb 7, 2023
Merged

feat: add did contexts #712

merged 3 commits into from
Feb 7, 2023

Conversation

rflechtner
Copy link
Contributor

fixes https://github.com/KILTprotocol/ticket/issues/1999

Adds static copies of json-ld context files relevant to KILT DID documents to the sdk, as well as the respective URI to DID documents exported to the conformant json-ld representation.

How to test:

n/a

Checklist:

  • I have verified that the code works
  • I have verified that the code is easy to understand
    • If not, I have left a well-balanced amount of inline comments
  • I have left the code in a better state
  • I have documented the changes (where applicable)

@rflechtner rflechtner requested a review from ntn-x2 February 6, 2023 17:31
@rflechtner rflechtner changed the base branch from develop to release-0.31.0 February 6, 2023 19:42
@rflechtner rflechtner changed the base branch from release-0.31.0 to develop February 6, 2023 19:54
Copy link
Member

@ntn-x2 ntn-x2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

* See https://w3c-ccg.github.io/security-vocab/.
* This document is extended by the context file available under the [[KILT_DID_CONTEXT_URL]].
*/
export const W3C_SECURITY_CONTEXT_URI = 'https://w3id.org/security/v2'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also a URL tho, right? What about renaming them all to URI? Since the IPFS link is definitely not a URL.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually I think I wanted to name it "URL" bc last thing I heard was that the distinction IRI / URI / URL is being abandoned in favour of calling everything "URL". Why is an ipfs link not a URL? It does resolve and thus let you locate a resource, no?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I know, URL is only used for web resources.

@ntn-x2
Copy link
Member

ntn-x2 commented Feb 7, 2023

@rflechtner I'm merging the PR since I will build on top of this to tackle https://github.com/KILTprotocol/ticket/issues/2093.

@ntn-x2 ntn-x2 merged commit 8eeedfc into develop Feb 7, 2023
@ntn-x2 ntn-x2 deleted the rf-did-context branch February 7, 2023 09:23
rflechtner added a commit that referenced this pull request Feb 7, 2023
* feat: static copy of DID json-ld contexts

* test: update tests

* chore: use shorter ipfs URL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants