search

geojson / geojson-ld

GeoJSON in JSON-LD contexts
Other
131 stars 13 forks source link

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

Closed mejackreed closed 3 years ago

mejackreed commented 4 years ago

With the release of JSON-LD 1.1 is this still an issue?

Looking at this comment as a reference https://github.com/w3c/json-ld-syntax/issues/7#issuecomment-421084641

sgillies commented 4 years ago

@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 commented 4 years ago

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 commented 4 years ago

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

azaroth42 commented 4 years ago

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.