For that to happen, the implementation in question would have to be able to infer that the SELECT statement in question was sure to produce _only_ legitimate
triples. In other words, not only that the form was a simple 3-tuple, but that neither the first nor second positions would ever contain literals and that the
second position would never contain bnodes. That's not impossible, but it would be extremely difficult.
Remember, an RDF triple is _not_ just a 3-tuple. It is specifically a tuple of
IRI-or-bnode, IRI, IRI-or-bnode-or-literal. [1]
---
A. Soroka
[1] https://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/#section-triples
Laura Morales wrote on 5/12/17 3:24 PM:
JSON-LD is an RDF syntax for graphs and datasets so it will need to be a
CONSTRUCT or DESCRIBE query.
XML/JSON/CSV/TSV are result set format for SELECT.
OK perhaps this is a noob question, but I don't understand why there is this
distinction between formats...
If results are returned in the form of "s p o" triples anyway, regardless of
XML/JSON/CSV/TSV, why can't the same output be formatted as n-triples, turtle, or json-ld?
