- From: Herbert van de Sompel <hvdsomp@gmail.com>
- Date: Fri, 14 Jan 2011 07:50:49 -0700
- To: Christopher Gutteridge <cjg@ecs.soton.ac.uk>
- Cc: "<public-lod@w3.org>" <public-lod@w3.org>
- Message-ID: <AANLkTi=JotLyWs1cV6rvc5B4r3j+VvuotKTP4yJTAmRN@mail.gmail.com>
Chris, I can't answer this question in a general sense, but what you suggest is explicitly covered in OAI-ORE [1], where there is an equivalence between the HTTP 303 redirect from an ORE Aggregation to a describing ORE ResourceMap [2] and the ore:isDescribedBy relationship between these two resources in the Data Model. This approach, however, does not seem to be generally accepted/promoted in the Linked Data world. For, example, the Linked Data tutorial [4] does not promote such a relationship. Cheers Herbert [1] http://www.openarchives.org/ore/1.0/toc [2] http://www.openarchives.org/ore/1.0/http [3] http://www.openarchives.org/ore/1.0/datamodel [4] http://www4.wiwiss.fu-berlin.de/bizer/pub/LinkedDataTutorial/ On Fri, Jan 14, 2011 at 12:50 AM, Christopher Gutteridge < cjg@ecs.soton.ac.uk> wrote: > (related to seeAlso discussion) If I resolve a URI /foo and it gives a 301 > seeOther to /bar then I should be able to infer a triple from that, I think? > At the very least, /foo rdfs:seeAlso /bar . > > Resolvable URIs are a cool hack, but I think the system would make more > sense if they were an alternate way of writing something you could express > directly as triples. It feels like that's missing from the stack. > > -- > Christopher Gutteridge -- http://id.ecs.soton.ac.uk/person/1248 > > You should read the ECS Web Team blog: > http://blogs.ecs.soton.ac.uk/webteam/ > > > -- Herbert Van de Sompel Digital Library Research & Prototyping Los Alamos National Laboratory, Research Library http://public.lanl.gov/herbertv/ ==
Received on Friday, 14 January 2011 14:51:23 UTC