-
Notifications
You must be signed in to change notification settings - Fork 81
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
doi.org serving JSON-LD documents breaks Codemeta's context file #278
Comments
actually, the issue is caused by doi.org now serving its own JSON-LD documents (via a redirect to Datacite). https://doi.org/10.5063/schema/codemeta-2.0 is supposed to redirect to https://raw.githubusercontent.com/codemeta/codemeta/2.0/codemeta.jsonld , and it still does when used in a browser or with default curl for example:
however, when the
(thanks to @puckipedia for figuring this out) |
That is an issue...and I'm not sure how we would work around it. DataCite used to allow you have custom content negotiation, but now they provide content negotiation to the medatata. This makes sense in most cases....but not if you want to serve your own jsonld. |
Can we close this with the w3id change? |
Yup! It actually looks like DataCite changed their content negotiation again so the DOI does work now....but w3id is going to be much more sustainable. |
@tmorrell Did it? I still get their own JSON-LD instead of the Codemeta context:
|
Huh...playground is working and I thought the content negotiation was too...but now it's not. In any event w3id will solve this. |
Hi,
(ignore this paragraph, see the first comment)
It looks like thehttp://schema.org
now redirects tohttps://schema.org
, even with aAccept: application/ld+json
header; and neither PyLD nor jsonld.js seem to handle this gracefully.Applications which hardcode context files (as they should) are not affected, but this causes issues with the JSON-LD playground for example: https://json-ld.org/playground/#startTab=tab-expanded&json-ld=%7B%22%40context%22%3A%22https%3A%2F%2Fdoi.org%2F10.5063%2Fschema%2Fcodemeta-2.0%22%2C%22license%22%3A%22https%3A%2F%2Fspdx.org%2Flicenses%2FGPL-3.0%22%2C%22name%22%3A%22test%20software%22%7D shows:
I don't know what should be done about this, any idea? (hot-patch the codemeta context? report the issue to
schema.orgdoi.org?)The text was updated successfully, but these errors were encountered: