-
Notifications
You must be signed in to change notification settings - Fork 154
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
Playground is down #728
Comments
The playground is up. It's a problem with schema.org. Their context isn't being served properly (it is ignoring a request for JSON-LD and only serving HTML): Run:
You'll see the output is HTML. |
Closing since the issue is elsewhere. Feel free to reopen/open another issue if there's an issue with the playground. |
It was a combination schema.org and jsonld.js problem. Should be fixed now. |
Thanks, @davidlehn. As I recall, there's no test infrastructure for the xhr document loader. |
@gkellogg The playground users are the test infrastructure. They found a bug, we fixed it. ;-) But yes, that should be addressed at some point. |
See: https://tinyurl.com/kk7k5qt (A link to the JSON-LD playground)
jsonld.InvalidUrl: Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.
And that is just the tip of the iceberg of a lot of json-ld services being impacted. See also RDFLib/rdflib-jsonld#84
The text was updated successfully, but these errors were encountered: