I know that the SPARQL recommendation states that path elements must be URIs
(https://www.w3.org/TR/sparql11-property-paths/#id41857)
but sine the path may be expanded as noted in the recommendation so that
{noformat}
{
?x foaf:mbox <mailto:alice@example> .
?x foaf:knows/foaf:knows/foaf:name ?name .
}
{noformat}
This is the same as the strict SPARQL query:
{noformat}
{
?x foaf:mbox <mailto:alice@example> .
?x foaf:knows [ foaf:knows [ foaf:name ?name ]] .
}
{noformat}
Would it not make sense that variables could be used in the path? So that
{noformat}
{
?x foaf:mbox <mailto:alice@example> .
?x foaf:knows/?var/foaf:name ?name .
}
{noformat}
This is the same as the strict SPARQL query:
{noformat}
{
?x foaf:mbox <mailto:alice@example> .
?x foaf:knows [ ?var [ foaf:name ?name ]] .
}
{noformat}
The query builder could handle this case -- actually currently the query
builder handles this case incorrectly as it will build the path with the
var and ARQ will execute it correctly.
Is there a reason not to suggest this change to W3C? Does anyone know if
it has been discussed before?
Claude
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
