Hashes and Turtle

On 16 Feb 2013, at 16:27, Henry Story <henry.story@bblfish.net> wrote:

> 
> On 16 Feb 2013, at 16:04, Mo McRoberts <Mo.McRoberts@bbc.co.uk> wrote:
> 
>> As should be blindingly obvious to anybody who's worked with them, hash-based URIs are principally useful where a document describes a _single_ entity within its sphere of reference (though the nature of triples and many ontologies is that there may well be parts of descriptions of other things).
>> 
>> Ontologies/vocabs are a one solid case where it's really not a good idea to use them because it's hard to split them up into separately-served resources later.
> 
> I don' think that quite locates the problem at the right place.
> It would be completely feasible to have one #uri per vocabulary element, each at
> a different location. For example all of DBPedias resource URIs could just return
> the content inside so one could have 
> 
>   http://dbpedia.org/resource/Whiskey#x
> 
> defined by 
> 
>   http://dbpedia.org/resource/Whiskey
> 
> That would have the advantage of required half the requests on DBPedia to get 
> the information. The only problem I see with that is a syntactic one. I sent 
> this to the WebArch and RDF-Comments group as a mail and RDF group in November, 
> but got no  answer there yet
> 
> http://lists.w3.org/Archives/Public/public-rdf-comments/2012Nov/0009.html
> 
> I suppose one would need to propose a solution to the problem.
> Something allong the lines of requesting a new @prefix in Turtle 
> so that one could write:
> 
> @pre db: ("http://dbpedia.org/resource/" _ "#x")
> 
> This would allow one then to have
> 
> :j :likes db:Whiskey .
> 
> which would be equivalent to
> 
> :j :likes <http://dbpedia.org/resource/Whiskey#x> .

So the current turtle spec allows one to write 

:j :likes db:Whiskey\#x , db:Organges\#x, db:MashedPotatoes\#x .

But that is pretty awkward, clearly, especially if one
is teaching it, or writing it out by hand, as one may do 
when writing queries.

Henry

Social Web Architect
http://bblfish.net/

Received on Saturday, 16 February 2013 16:30:20 UTC