- From: Sebastian Hellmann <hellmann@informatik.uni-leipzig.de>
- Date: Wed, 01 Aug 2012 08:43:26 +0200
- To: Paolo Ciccarese <paolo.ciccarese@gmail.com>
- CC: Bernhard Haslhofer <bernhard.haslhofer@cornell.edu>, public-openannotation <public-openannotation@w3.org>, Robert Sanderson <azaroth42@gmail.com>
Dear Paolo, Why wouldn't this work well? It is based on RFC5147. Offset works for any string and therefore also HTML source. Problems arise, when you interpret strings. They do not work well for DOM, of course, but this is where one would rather use xPointer (W3C) . I guess, it also wouldn't work well to use an OA text selector on an image, right? With fragments, you definitely gain: - compatibility with the web (which also means free implementations) - less triples - less generated UUID's (if any at all) What do you gain, when using selectors? I am not interested in theoretical/modelling issues. For me only things count that help you succeed in a use case. Building a parser for URIs is something very easy to implement, much easier in fact than understanding and working with selectors. Sebastian Am 31.07.2012 19:51, schrieb Paolo Ciccarese: > Is the mechanism > http://www.w3.org/DesignIssues/LinkedData.html#offset_717_729 really > working in general? > > In my experience it does not with HTML pages in general. That would mean > having lots of ways of composing the URIs that then need would need to be > parsed. That is why we designed more complex selection mechanisms ( > http://www.openannotation.org/spec/core/#Selector)... and therefore more > triples. > > Paolo -- Dipl. Inf. Sebastian Hellmann Department of Computer Science, University of Leipzig Events: * http://sabre2012.infai.org/mlode (Leipzig, Sept. 23-24-25, 2012) * http://wole2012.eurecom.fr (*Deadline: July 31st 2012*) Projects: http://nlp2rdf.org , http://dbpedia.org Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann Research Group: http://aksw.org
Received on Wednesday, 1 August 2012 06:43:58 UTC