LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  July 2014

BIBFRAME July 2014

Subject:

Re: BibFrame and Linked Data: Identifiers

From:

LAURA DAWSON <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Fri, 18 Jul 2014 06:21:22 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (109 lines)

ISBNs have been made actionable by mEDRA (Italy) - turned into DOIs. But
the uptake for that in the US, at least in trade, has been nonexistent.

On 7/18/14, 6:16 AM, "Juha Hakala" <[log in to unmask]> wrote:

>Hello,
>
>On 17.7.2014 23:34, Stuart Yeates wrote:
>> On 07/17/2014 09:39 AM, Denenberg, Ray wrote:
>>> I think the advice is:
>>>
>>> (1) don't use a URI to identify a bf:Identifier.  Treat it as a blank
>>> node.
>>>
>>> (2) Only a non-URI identifier (e.g. isbn) should be treated a
>>> bf:Identifier.  (I.e. a URI  should not be treated as a bf:Identifer.
>>> Thus the property bf:uri should be eliminated.)
>+ 1.
>
>URLs are neither unique nor persistent and should not be treated as
>identifiers. IMO it would be better not to have them in bibliographic
>records at all. Instead they could be stored in the mapping tables of
>URN / Handle / DOI resolvers. Then we would have just one place in which
>to maintain the location information, instead doing that in hundreds of
>databases holding copies of the bibliographic record. And we could
>provide everyone the extra services URN resolution can provide, compared
>with plain vanilla HTTP GET.
>
>>>
>>> I think there is consensus on this, someone correct me if Iım wrong.
>>
>> In real systems, won't ISBNs be represented as URNs in the namespace
>> URN:ISBN:... as defined by http://www.ietf.org/rfc/rfc3187.txt ?
>
>Well, yes and no.
>
>Since a URN namespace has been registered for ISBNs, it is possible to
>expand every ISBN into a URN. Making that URN actionable is for the time
>being possible only if the address of a resolver is hard-coded into the
>URN like this:
>
>http://urn.fi/URN:ISBN:978-951-51-0007-8
>
>Global resolver discovery service should solve this problem eventually
>for all URN namespaces. Alas, ISBN namespace will be one of the tricky
>ones since many URN:ISBN resolvers are required.
>
>
>>
>> Are there really any identifiers that we care that aren't already
>> mapped to URNs? If yes, isn't the solution to map them to URNs?
>
>If only it were that easy.
>
>There are several identifier systems which do not have a URN namespace.
>Of course you can construct PIDs like urn:lccn:<lccn-number> but that is
>not "safe" since there is no quarantee that LCCN will get Namespace
>Identifier "LCCN". Moreover, there would be no resolution services
>available for your URN:LCCN:s out there. And since URNs are supposed to
>make existing identifier systems actionable, there is no real point with
>urn:xxx:yyy unless it is a hyperlink. Of course any URN may be
>searchable via Google etc., but that's not enough.
>
>Registering URN namespaces is not difficult. IETF is liberal in what it
>approves, as manifested by urn:uuid. If and when a decision is made to
>register a namespace for LCCN, writing the registration request would
>take maybe a few hours. IMO registering URN namespaces to all key
>bibliographic identifiers would do no harm, and then people could safely
>mint e.g. URN:LCCNs. The next step - how to make them actionable - could
>be more complicated.
>
>The most challenging bit in a satisfactory registration request is to
>specify how URNs in that namespace can be resolved. There are both
>technical and practical requirements which need to be taken into
>account. If the identifier is non-semantic ("dumb"), then there has to
>be a single resource out there where URNs in that namespace are
>resolved. ISSN and ISNI are examples of systems which meet both
>requirements. Then all that is needed is a political decision to
>register a namespace and creation of a URN resolver.
>
>Things get difficult when the identifier provides no hint on how to find
>the correct resolver, and there are several resolvers out there. Of all
>the existing namespaces, ISBN is one of the most complicated ones to
>manage in the Global Resolver Discovery Service, if and when it is
>established.  Of course, there are no problems to find resolvers as long
>as they are "hard-coded" into URNs, but it is to be hoped that that will
>be just an intermediate step.
>
>Best regards,
>
>Juha
>
>>
>> cheers
>> stuart
>
>
>-- 
>
>  Juha Hakala
>  Senior advisor
>
>  The National Library of Finland
>  Library Network Services
>  P.O.Box 26 (Teollisuuskatu 23)
>  FIN-00014 Helsinki University
>  Tel. +358 9 191 44293
>  Mobile +358 50 3827678

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager