> 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]
I also don't understand why this would be necessary. Mainly because, as far as I can see, triples are already validated before inserting them into the dataset (for example when using tdbloader). Are all triples checked for correctness before outputting any of XML/JSON/CSV/TSV? If they do, it would seem very strange to me.
