- From: Kjetil Kjernsmo <kjetil@kjernsmo.net>
- Date: Tue, 16 Jun 2015 12:37:36 +0200
- To: public-hydra@w3.org
- Cc: Gregory Williams <greg@evilfunhouse.com>
On Tuesday 16. June 2015 11.48.23 Ruben Verborgh wrote:
> Does that clarify the mechanism?
Not really. :-) So, there are other requirements of TPFs that aren't
expressed, like the requirement that TPFs will have metadata (i.e. the
cardinality of the pattern expressed with void:triples) and the control
information.
So, by using this interface, you don't know if you will get a TPF, or
something else. For example, you could have
<#dataset> hydra:search [
hydra:template
"http://example.org/sparql?query=CONSTRUCT%20WHERE%20%7B%20{%3Fsubject}%20{%3Fpredicate}%20{%3Fobject}%20.
%20%7D";
hydra:mapping
[ hydra:variable "subject"; hydra:property rdf:subject ],
[ hydra:variable "predicate"; hydra:property rdf:predicate ],
[ hydra:variable "object"; hydra:property rdf:object ]
].
Please excuse me if the URI pattern is invalid (I haven't gotten around to
read that spec yet), the point is to illustrate that this is encodes a
single triple pattern SPARQL query, that will return a SPARQL RDF result
according to the SPARQL Protocol, but it would probably not return
metadata and control information, that a TPF should.
Cheers,
Kjetil
Received on Tuesday, 16 June 2015 10:38:14 UTC