SPARQL paths and N3 paths: some quick thoughts.

The SPARQL WG is looking at paths...
http://www.w3.org/2009/sparql/docs/property-paths/Overview.xml

... which is quite important for querying, e.g. lists:

 select ?elt where { <alist> rdf:rest*/rdf:first ?elt }

Meanwhile, they're using / where n3 uses ., I think.

They use ^ both as N3 uses it and to do the is/of thing.

They also include regex syntax such as +,*, ? and {n,m}
and ()s (but not for match groups).

It's pretty hard to argue against this in SPARQL; people
have been asking for it from the very start of the SPARQL
design.

Perhaps N3 should adapt in this direction?

The one place I'm inclined to push on is is/of; I'd
hate to lose that from N3. Though... with the @keywords
mechanism, maybe it's not so much of a conflict.

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
gpg D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E

Received on Friday, 22 January 2010 21:10:40 UTC