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  May 2013

BIBFRAME May 2013

Subject:

Re: Instance of ISBNs in MARC records

From:

Juha Hakala <[log in to unmask]>

Reply-To:

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

Date:

Tue, 21 May 2013 13:38:15 +0300

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (78 lines)

Hello,

IETF URNbis working group

http://datatracker.ietf.org/wg/urnbis/charter/

has produced an updated version of RFC3187 which does accommodate both 
ISBN-10 and ISBN-13. The ISBN International Agency is well aware of this 
work.

See http://tools.ietf.org/id/draft-ietf-urnbis-rfc3187bis-isbn-urn-03.txt

This Internet Draft is currently out of date, and it is not likely that 
the URNBis working group will approve of it.

The reason for this is that there is no agreement on how to treat URI 
query and fragment properties. As specified here:

http://tools.ietf.org/html/draft-ietf-urnbis-rfc2141bis-urn-03

the initial approach was that the query and fragment are not part of the 
identifier. The idea was that the identifier as a rule identifies the 
entire document, and the fragment just takes the user to a specified 
position within the document. This is in some respect aligned with how 
the HTTP protocol works; the entire file is retrieved, and the browser 
uses fragment to take the user into the wanted position within the 
file.  Fragment must then be understood in the HTTP sense of the word; 
it is also possible to identify logical parts / fragments, but how to do 
this must be specified separately in each URN namespace.

Likewise, the query could be used to retrieve the document, descriptive 
metadata about the document, technical metadata about the document, and 
so forth, but the identified resource would remain the same.

Alas, the working group could not reach an agreement about how to use 
fragment and query, and the latest version of the URN syntax

http://tools.ietf.org/html/draft-ietf-urnbis-rfc2141bis-urn-04

omits them, which I think is a problem since query and fragment have 
been part of the URI syntax since 2005, but still no persistent 
identifier system uses them. This may be an indication that mixing 
identification and location information is not a great idea.

The authors of rfc3187bis are unwilling to produce a dumb down version 
of the draft, so it does not look likely that the URNbis WG will be able 
to complete its charter unless a workable compromise is found. IMHO it 
would be a bad idea to say that e.g. a fragment is part of the 
identifier string, since then it would not be possible to use fragments 
in e.g. the ISBN namespace.

All the best,

Juha

On 21.5.2013 8:42, Stuart Yeates wrote:
>>> It's trivial for a computer to calculate that a 13-digit and 10-digit
>>> ISBN are the same.
>> Assuming Kevin et al. know of the situation, and program for it.
> There's actually a case for prodding the International ISBN Agency to update RFC 3187 so that that information is embedded in the URN representation. RFC 3187 predates 13 digit ISBNs. Some of the links and other information appear to be outdated too.
>
> http://tools.ietf.org/html/rfc3187
>
> cheers
> stuart


-- 

  Juha Hakala
  Senior advisor

  The National Library of Finland
  P.O.Box 15 (Unioninkatu 36, room 503)
  FIN-00014 Helsinki University
  tel +358 9 191 44293
  

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

March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
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