- From: Juan Sequeda <juanfederico@gmail.com>
- Date: Thu, 14 Jan 2010 18:51:19 -0500
- To: Michael Hausenblas <michael.hausenblas@deri.org>
- Cc: RDB2RDF WG <public-rdb2rdf-wg@w3.org>
- Message-ID: <f914914c1001141551o4712c666k323786b2102fbd2a@mail.gmail.com>
Michael and all, I have a question about reusable identifiers. If I have my movie rental company relational database and I want to expose it all as Linked Data. What should be the identifier for "Breakfast at Tiffany's?" http://dbpedia.org/resource/Breakfast_at_Tiffany%27s_%28film%29 http://data.linkedmdb.org/resource/film/71 okkam identifier for Breakfast at Tiffany's (if it exists) or should it be a http://myrentalstore.com/resource/film/123 owl:samesAs http://dbpedia.org/resource/Breakfast_at_Tiffany%27s_%28film%29 Audrey Hepburn, can be considered a well known entity with URIs in dbpedia, freebase, etc. We know that Audrey Hepburn acted in Breakfast at Tiffany's. So should I have my own URI for the movie and reuse an identifier for Audrey Hepburn? I agree that we need to offer the possibility in the language to reuse the identifiers, I'm just wondering what is the use case. Juan Sequeda, Ph.D Student Dept. of Computer Sciences The University of Texas at Austin www.juansequeda.com www.semanticwebaustin.org On Thu, Jan 14, 2010 at 5:48 AM, Michael Hausenblas < michael.hausenblas@deri.org> wrote: > > All, > > I've put my initial thoughts re the Linked Data aspects of R2RML on our > Wiki > [1]. Please read, review & comment (preferably in the Wiki; saves us all > time ;). > > Note that this will be the main discussion point for our upcoming telco on > 2010-01-19. > > Cheers, > Michael > > [1] http://www.w3.org/2001/sw/rdb2rdf/wiki/LinkedDataAspects > > -- > Dr. Michael Hausenblas > LiDRC - Linked Data Research Centre > DERI - Digital Enterprise Research Institute > NUIG - National University of Ireland, Galway > Ireland, Europe > Tel. +353 91 495730 > http://linkeddata.deri.ie/ > http://sw-app.org/about.html > > > >
Received on Thursday, 14 January 2010 23:51:54 UTC