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

Use rfc7807bis JSON-LD Context #224

Open
asbjornu opened this issue Feb 10, 2021 · 6 comments
Open

Use rfc7807bis JSON-LD Context #224

asbjornu opened this issue Feb 10, 2021 · 6 comments

Comments

@asbjornu
Copy link
Member

Work has begun updating RFC 7807 with rfc7807bis. With the opportunity this gives, I've suggested in ietf-wg-httpapi/rfc7807bis#10 to create an official JSON-LD context for application/problem+json. If that is implemented, we should consider replacing Hydra's JSON-LD Context for problem+json defined in #178 with the one defined by rfc7807bis.

@alien-mcl
Copy link
Member

Once it is there we could use it. We'll see how it will end, but I believe the status is the only missing piece.

@asbjornu
Copy link
Member Author

Public accessible hosting of the problem-context.jsonld would be nice too, no?

@alien-mcl
Copy link
Member

I can see three solutions here, all fine to me:

  • Hydra CG's location
  • JSON-LD related location
  • problem/json related location

@tpluscode
Copy link
Contributor

Public accessible hosting of the problem-context.jsonld would be nice too, no?

We should have the context dereferancable directly from hydra too.

@asbjornu
Copy link
Member Author

We should have the context dereferancable directly from hydra too.

Even though no terms within it are defined by Hydra? Why can't we refer to rfc7808bis' location?

@tpluscode
Copy link
Contributor

We can, when it arrives but I don't expect that too soon

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

3 participants