-
Notifications
You must be signed in to change notification settings - Fork 8
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
Make credential-context resolvable #26
Comments
@jimmarino - is this on your roadmap? If no, I could pick this up. EDC doesn't need it but I think there's value in it. Note: The original issue mentions |
@arnoweiss If you could pick this up it would be much appreciated. |
Created a PR in the |
Hey @arnoweiss thanks! Just a small comment for the links. I would use the published on in GH pages, You can find the published one here: Policy Context Credentials Context |
Thanks, I wasn't aware that exists. As the documents you linked mirror |
The respective PRs are merged and resolve correctly AFAICT. Please check and close if confirmed. |
Thanks @arnoweiss LGTM! |
Description
As Operator or Enablement Service Provider for a CX-0018 compliant service,
I want to read the expanded JSON-LD of VCs,
so that I can reliably process and understand their content.
Acceptance Criteria
https://w3id.org/catenax/credentials/v1.0.0
is resolvable to a JSON-LD context.Additional Information
Currently, the samples'
@context
in the credentials-folder rely on thehttps://w3id.org/catenax/credentials/v1.0.0
context. It currently resolves to the default path specified in the redirects. The credential-context included in this repository is already in v1.1 so I'm unsure whether it's an appropriate target. Its content would be affected if issue #25 is accepted with further implications for versioning.I'd be willing to contribute if there's an aligned concept.
The text was updated successfully, but these errors were encountered: