- From: Nicolas Chauvat <nicolas.chauvat@logilab.fr>
- Date: Thu, 16 Jul 2020 11:14:35 +0200
- To: "Cox, Simon (L&W, Clayton)" <Simon.Cox@csiro.au>
- Cc: Jeen Broekstra <jeen@fastmail.com>, "semantic-web@w3.org" <semantic-web@w3.org>
Hi Simon, I find these examples and links useful. Thank you. On Mon, Jul 13, 2020 at 01:46:56AM +0000, Cox, Simon (L&W, Clayton) wrote: > 1. JSON literals is specified in > https://w3c.github.io/json-ld-syntax/#the-rdf-json-datatype - the > `rdf:JSON` datatypes When using json-ld that would be like embedding a graph in a literal, wouldn't it ? > The argument for moving some kinds structured data over to the other > side of the RDF|Data boundary is that the operations that are > generally carried out on those are (in this case) > geometric/algebraic rather than logical, and thus use different > engines. If in general the operations carried out on RDF are logical and the operations carried out on geo:gmlLiteral are geometric/algebraic, can GeoSPARQL be considered a proof that at times, you need to operate on both sides in the same query ? Are there other similar extensions to sparql, JsonSparql or DateTimeSparql maybe ? -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances
Received on Thursday, 16 July 2020 09:14:51 UTC