Closed sgillies closed 8 years ago
I'd vote against merging this as:
@values
in JSON-LD, which describes the values of multidimensional arrays.I suggest waiting for https://github.com/json-ld/json-ld.org/issues/397. If this proposal gets shot by the JSON-LD community, you can go ahead and merge this.
@pietercolpaert thank you very much! I'll follow that issue.
@sgillies Thanks for trying to resolve these difficult and often controversial issues!
I don't understand how the @type
is a WKT Literal, as it isn't: it's a JSON array. No?
@pietercolpaert my intent is that @type would trigger coercion to WKT as in http://www.w3.org/TR/json-ld/#type-coercion. Am I misreading that section?
@sgillies No, you aren't. My bad!
@pietercolpaert I'm glad to get second opinions. Sometimes I feel lost without a compass in JSON-LD!
@pietercolpaert it looks like we should merge and continue without creation of a new media type. Agreed?
Related: I've read the discussion in https://github.com/jasnell/w3c-socialwg-activitystreams/issues/52 and have a better understanding of where many commenters here are coming from.
Closing.
Towards closing https://github.com/geojson/geojson-ld/issues/32.
This helps RDF users get usable RDF by coercion of GeoJSON geometry to WKT.
It does nothing for RDF -> GeoJSON, but I don't think this lack has to be a blocker for a first release of GeoJSON-LD on the web.
Definition of a new container types specific to GeoJSON geometry objects and N-D arrays could assist with RDF -> GeoJSON conversions as well as serialization of geometries to pure RDF, but let's defer work on those.
Reviews welcome!