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

Remove outstanding issue with release of JSON-LD 1.1 #49

Merged
merged 1 commit into from
Nov 5, 2020

Conversation

mejackreed
Copy link
Contributor

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)

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)
@sgillies
Copy link
Contributor

@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.

@kgeographer
Copy link

As I understand, it is solved with this construction:
"coordinates": {"@container": "@list"}
but I have yet to test e.g. by round-tripping to/from rdf/xml in #LinkedPlaces format implementations

@mejackreed
Copy link
Contributor Author

@azaroth42 would you be able to confirm this isn't an issue anymore in JSON-LD 1.1 ?

@azaroth42
Copy link

Yes, arrays of arrays work as expected in JSON-LD 1.1 :)
https://www.w3.org/TR/json-ld11/#example-83-coordinates-expressed-in-geojson

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.
https://www.w3.org/TR/json-ld11/#json-literals

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.
Copy link
Contributor

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?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

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?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes please 🙏

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nevermind.

@sgillies sgillies merged commit d60125c into geojson:gh-pages Nov 5, 2020
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

Successfully merging this pull request may close these issues.

4 participants