-
Notifications
You must be signed in to change notification settings - Fork 14
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
Remove outstanding issue with release of JSON-LD 1.1 #49
Conversation
With the release of [JSON-LD 1.1](https://www.w3.org/TR/json-ld11/) is this still an issue? Looking at this comment as a reference w3c/json-ld-syntax#7 (comment)
@mejackreed I haven't been able to follow JSON-LD very closely in the past 3 years. I'll need to rely on someone else to say whether it is still an issue. |
As I understand, it is solved with this construction: |
@azaroth42 would you be able to confirm this isn't an issue anymore in JSON-LD 1.1 ? |
Yes, arrays of arrays work as expected in JSON-LD 1.1 :) That said, there's also a native JSON datatype that would potentially obviate the need for GeoJSON-LD completely ... unless you want to do semantic processing of the geoJson structure. So it depends on what the intent is ... if it's to embed GeoJSON as a blob, then use JSON datatype. If it's to enrich GeoJSON with additional semantics, then use the array of arrays. |
of JSON-LD 1.0. There are no current best practices for addressing this issue. | ||
Applications that process GeoJSON as JSON-LD using the GeoJSON-LD 1.0 context | ||
must take extra steps not defined here to ensure that geometric coordinates | ||
are processed appropriately. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mejackreed @azaroth42 what would you think about, instead of removing this entire paragraph, leaving the first sentence (still true for JSON-LD 1.0) and adding another sentence explaining that it is no longer a problem with JSON-LD 1.1?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mejackreed @azaroth42 ping?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That seems ok to me! Would you like me to make that change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please 🙏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermind.
With the release of JSON-LD 1.1 is this still an issue?
Looking at this comment as a reference w3c/json-ld-syntax#7 (comment)