W3C home > Mailing lists > Public > public-lld@w3.org > March 2011

RE: xsd or vocabulary

From: Young,Jeff (OR) <jyoung@oclc.org>
Date: Thu, 10 Mar 2011 16:59:19 -0500
Message-ID: <52E301F960B30049ADEFBCCF1CCAEF590BC4D5BD@OAEXCH4SERVER.oa.oclc.org>
To: "Adrian Pohl" <pohl@hbz-nrw.de>, <public-lld@w3.org>
Adrian,

The last time anyone dealt with OCLC Number interoperability was back
when OpenURL was being specified. They used URIs of this form:

info:oclcnum/12345

These "info" URIs are defined by this "namespace":

info:oclcnum/

I think Dublin Core has a way to wire these up, but I'm not quite sure
how.

There are a host of other legacy identifiers that have also been
upgraded to URI status using "info" URIs:

http://info-uri.info/registry/OAIHandler?verb=ListRecords&metadataPrefix
=oai_dc

This was back before httpRange-14 clarified the possibility of using
http URIs to identify things other than Web resources. We all we hope
these legacy identifiers will be upgraded to Linked Data someday. 

I'm not suggesting you worry about interoperability with OpenURL, but
these URIs are theoretically suitable for use in Linked Data. In
general, it's impossible to guess what the owner of the namespace will
decide regarding rdf:type, though. LC decided some of theirs are
owl:sameAs their skos:Concepts, which seems sensible in that case:

http://id.loc.gov/authorities/sh85148273.rdf

Jeff

> -----Original Message-----
> From: public-lld-request@w3.org [mailto:public-lld-request@w3.org] On
> Behalf Of Adrian Pohl
> Sent: Thursday, March 10, 2011 3:51 PM
> To: public-lld@w3.org
> Subject: xsd or vocabulary
> 
> Hello,
> 
> I asked the general question[1] on semanticoverflow (pasted below)
> whether to use predicates or xsd datatypes to represent in RDF
> different bibliographic identifiers a record contains. It would be
> great if you could contribute your thoughts - on semanticoverflow or
> here...
> 
> All the best,
> Adrian
> 
> [1] http://www.semanticoverflow.com/questions/3572/xsd-or-vocabulary
> 
> 
> 
> 
> 
> Deutsche Nationalbibliothek (German National Library) and hbz are
> working on a service[2] which aims to facilitate the linking of data
> from different catalogues (whether library catalogues or union
> catalogues) by providing matching information about different records.
> 
> 
> For this project we - amongst other things - need to link catalog
> entries to the bibliograhic identifiers in them. (There are a lot of
> identifiers in the realm of bibliographic data: widely known
> identifiers like ISBN, ISSN, DOI, URN, Handle, OCLC number, LCCN and
> many more local, regional and national identifiers. Some of them
> identify a bibliographic record while others identify the described
> bibliographic entity - which doesn't make it easier in a LOD context.)
> 
> 
> The question here is how to represent a link in RDF from a record or a
> bibliographic resource to the associated identifiers. We have to
decide
> between 1.) using individual predicates for each identifier or 2.)
> using the global predicate dc:identifier and characterizing the
> identifier more precisely through an xsd data type.
> 
> 
> Here is an example for each approach:
> 
> 
> 1. The "predicate approach"
> 
> 
> @prefix biro:   .
> @prefix cg:     .
> @prefix dc:     .
> 
> 
> 
>   a biro:BibliographicRecord ;
>   dc:source  ;
>   cg:bvn "BV035542944" ;
>   cg:oclcn "991052625" ;
>   ex:describes [
>   cg:isbn "3-8273-2774-1"
>   ] .
> # ex:describes is because there is no inverse property to
> wdrs:describedby.
> # Does anybody know an appropriate predicate for this?
> 
> 
> 
> 
> 2. The "datatype approach"
> 
> 
> @prefix biro:   .
> @prefix dc:    .
> 
> 
> 
>   a biro:BibliographicRecord ;
>   dc:source  ;
>   dc:identifier "BV035542944"^^xsd:BVN ;
>   dc:identifier "991052625"^^xsd:OCLCN ;
>   ex:describes [
>   dc:identifier "3-8273-2774-1"^^xsd:ISBN
>   ] .
> 
> 
> What do you think is the way to go: Creating an XSD or a vocabulary?
> 
> 
> Adrian
> 
> 
> 
> [2] http://www.hbz-nrw.de/dokumentencenter/presse/pm/culturegraph_en
> 
> 
Received on Thursday, 10 March 2011 22:00:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 10 March 2011 22:01:06 GMT