Print

Print


Karen,

Thanks for the link.

<snip>
The ISBN-A (actionable ISBN)... :

  *   By definition, an ISBN-A identifies the same referent as that ISBN. It incorporates, but does not replace, the corresponding ISBN. The referent is determined by the ISBN agency.
  *   ISBN-As do not automatically exist for every ISBN; they exist only once the agency has registered them in the DOI System.
  *

.

Examples of applications

  *   IISBN-A resolving to a managed web page service providing descriptive detail about the book e.g. publisher, title, author, subject and product description, cover image, cataloguing data. Publishers could further customize their pages with hyperlinks they control.
  *   ISBN-A associated by the publisher with an ad hoc set of relevant information and services (dynamically modifiable by the publisher at any time) to be displayed to the final user whenever a title assigned with an ISBN-A is cited and referenced over the Internet. Using DOI multiple resolution features, the ISBN may be turned into a one-click gateway to enhance the "book experience", e.g.

<snip/>

Looks to me more like an attempt to produce a PURL service to point at publisher web page URLs.  They are only created upon request, and they could point at anything.  - even less like reliable resource identifier than the ISBN!

Once you know the pattern, yes you could calculate what the ISBN-A URL would be (if there is one created for the book with that ISBN) , but that is not a translation to a linked data URI.

In the same way, knowing the oclcnum of a bib record lets you calculate what the WorldCat Linked Data URI for the resource that record describes, because of the URI pattern used in WorldCat data.  However, they are still separate and different things.

Treating it otherwise would be the equivalent of using the text string which is the title of a book to calculate what the dbpedia URI would be for the work with that title and then saying that the URI was equivalent to the title.

~Richard


From: Karen Coyle <[log in to unmask]<mailto:[log in to unmask]>>
Reply-To: Karen Coyle <[log in to unmask]<mailto:[log in to unmask]>>
Date: Friday, 2 August 2013 21:42
To: "[log in to unmask]<mailto:[log in to unmask]>" <[log in to unmask]<mailto:[log in to unmask]>>
Subject: Re: [BIBFRAME] Modeling Question

Richard, did you see my note about DOI and the ISBN? They claim to be the official ISBN as URI:

http://www.doi.org/factsheets/ISBN-A.html

I believe that there is no problem translating an ISBN string into the DOI URI.

kc

On 8/2/13 1:23 PM, Wallis,Richard wrote:

On 2 Aug 2013, at 20:18, J. McRee Elrod <[log in to unmask]<mailto:[log in to unmask]>> wrote:

Richard Wallis posted:

[In the linked data world] there is a significant difference between
the >numbers (OCLC number, LCCN, ISBN, etc.) associated with a
resource and the >URI that identifies it.

Of these numbers, only ISBN is associated with the resource.  The OCN,
LCCN, and other national bibliographic agency nubers, are associated
with the description.


That is true, the numbers have been associated with the records (descriptions). However the URI is a [linked data] identifier for the resource.

Note the '[In the linked data world]' in the text above you referenced.  Linked data uses http URIs as identifiers for resources, so that they can be linked and those links followed.  Obviously there is need to record numbers and other identifying strings (which are not http URIs) that have been used to identify the resource in other domains, as properties in the RDF description.

ISBN is a bit of a special case, it is an identifier for the resource, it is a string, it is not a http URI that can be used as a linked data identifier.  So in RDF it is captured as a string property.

~Richard.


--
Karen Coyle
[log in to unmask]<mailto:[log in to unmask]> http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet