-
Notifications
You must be signed in to change notification settings - Fork 156
JSON-LD version on playground #589
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
Comments
Wouldn't the easiest be if we would simply have two HTML pages for the two versions and make them include different versions?
|
We have two versions now. There's the main one with 0.5.x lib, and dev one with ~0.6.x lib. But as I was saying, there is no fully conforming 1.0 lib available. I doubt anyone wants to spend effort to make that happen vs just using 1.1 in 1.0 mode and accept the issues. I'm not too convinced it's even a real issue that people would want a 1.0 only playground. |
Regarding having multiple playgrounds, here are my thoughts: At a minimum, the main playground should have a toggle for processing mode (1.0 vs. 1.1 vs. experimental) and it should use the same (most recent) lib. If people feel a need for a second playground that will process things using some older version of the library (i.e. pre-1.1 ... but even here expectations about what it will do may be off) then it can be a separate HTML page that loads that older version. |
We do have multiple playgrounds, and it does allow selecting the processing mode. Closing. |
During the last meeting it was resolved to have one playground for 1.0 and 1.1 processing. Some notes on that related to jsonld.js:
@graph
handling and a bit of@version
handlingFrom an ease of site development viewpoint, I think we should just put the most recent jsonld.js on the playground and add a UI control to pick the
processingMode
API option. Due to practicalities of jsonld.js not having a full correct 1.0 only lib, it seems not worth the effort to try and deal with this any other way. There are edge cases where a 1.1 lib in 1.0 mode will produce different results than a 1.0 lib. My guess is that in practice this really doesn't matter. Or in any case, is not worth handling on the playground.The text was updated successfully, but these errors were encountered: