W3C home > Mailing lists > Public > public-xg-lld@w3.org > August 2010

Possible use case

From: Karen Coyle <kcoyle@kcoyle.net>
Date: Thu, 12 Aug 2010 12:45:51 -0700
Message-ID: <20100812124551.19t3torh8g04s0gg@kcoyle.net>
To: public-xg-lld@w3.org
I have a possible use case but it may be too specific. I was thinking  
of writing up the actual effort being made to export Open Library  
entities in RDF. There are three entities: Work, Author, and Edition.  
They do not strictly follow library practice, which is what makes them  
interesting as cases, IMO.

Here are some examples. Assume that the RDF in each case is only one  
possible solution:

Author in UI: http://openlibrary.org/authors/OL22022A/Barbara_Cartland
Author RDF: http://openlibrary.org/authors/OL22022A.rdf

Work in UI: http://openlibrary.org/works/OL6037025W/Code
Work in RDF: http://openlibrary.org/works/OL6037025W.rdf

Edition (Manifestation + Expression, more or less) in UI:
    http://openlibrary.org/books/OL6807502M/Code
Edition in RDF: http://openlibrary.org/books/OL6807502M.rdf

Some of the issues that the case would raise are:
   There are many versions of FRBR - does it matter which one you use?
   We have frbr:Person, RDA:Person, foaf:Person, FRAD:Person....  
again, how to decide?
   There are many elements in library data that do not yet have an  
identifier; how does one approach that?

Or is this too specific for a use case?

-- 
Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet
Received on Thursday, 12 August 2010 19:46:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 12 August 2010 19:46:24 GMT