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

Context resolution #68

Open
clehner opened this issue Oct 29, 2020 · 0 comments
Open

Context resolution #68

clehner opened this issue Oct 29, 2020 · 0 comments

Comments

@clehner
Copy link
Member

clehner commented Oct 29, 2020

The security context references https://w3id.org/security#. But https://w3id.org/security redirects to https://w3id.org/security/, which redirects to https://w3c-ccg.github.io/security-vocab/, which does not return JSON-LD - even if the HTTP Accept header is set to application/ld+json or application/json (since it is served by GitHub Pages). How is the security vocab context supposed to be referenced and resolved?

These URLs do return JSON-LD and seem to be the actual context documents, but internally they reference https://w3id.org/security:

The redirects appear to be set here: https://github.com/perma-id/w3id.org/blob/master/security/.htaccess

This is the reference I am looking at for how to load a JSON-LD document for resolving a context:
https://www.w3.org/TR/json-ld-api/#remote-document-and-context-retrieval

Should w3id.org be updated to point https://w3id.org/security to https://w3c-ccg.github.io/security-vocab/contexts/security-v2.jsonld? Or should index.html in this repo be updated to embed the JSON-LD context? Or am I misunderstanding how these things are supposed to work?

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

No branches or pull requests

1 participant