Re: [urn] Comments on draft-ietf-urnbis-rfc3187bis-isbn-urn-01

Juha Hakala <juha.hakala@helsinki.fi> Thu, 20 October 2011 05:16 UTC

Return-Path: <juha.hakala@helsinki.fi>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1C1B11E8085 for <urn@ietfa.amsl.com>; Wed, 19 Oct 2011 22:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.97
X-Spam-Level:
X-Spam-Status: No, score=-1.97 tagged_above=-999 required=5 tests=[AWL=4.029, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HT4kDPuuPfPs for <urn@ietfa.amsl.com>; Wed, 19 Oct 2011 22:16:33 -0700 (PDT)
Received: from smtp-rs1-vallila2.fe.helsinki.fi (smtp-rs1-vallila2.fe.helsinki.fi [128.214.173.75]) by ietfa.amsl.com (Postfix) with ESMTP id 4161811E807F for <urn@ietf.org>; Wed, 19 Oct 2011 22:16:31 -0700 (PDT)
Received: from [128.214.91.90] (kkkl25.lib.helsinki.fi [128.214.91.90]) by smtp-rs1.it.helsinki.fi (8.14.4/8.14.4) with ESMTP id p9K5Ec0T023445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 20 Oct 2011 08:14:39 +0300
Message-ID: <4E9FAE3E.3040808@helsinki.fi>
Date: Thu, 20 Oct 2011 08:14:38 +0300
From: Juha Hakala <juha.hakala@helsinki.fi>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Larry Masinter <masinter@adobe.com>
References: <6.2.5.6.2.20111019023731.0aa22fe0@elandnews.com> from SM at Oct "19, " 2011 "03:13:20" am <201110192200.AAA25239@TR-Sys.de> <C68CB012D9182D408CED7B884F441D4D05D4AC0EF4@nambxv01a.corp.adobe.com>
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D05D4AC0EF4@nambxv01a.corp.adobe.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "urn@ietf.org" <urn@ietf.org>
Subject: Re: [urn] Comments on draft-ietf-urnbis-rfc3187bis-isbn-urn-01
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions about possible revisions to the definition of Uniform Resource Names <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2011 05:16:34 -0000

Hello,

Larry Masinter wrote:
>>>    "Each product form (e.g. hardcover, paperback, PDF) MUST have its
>>>     own ISBN."
>>> Why is this a MUST?
> 
>> That's a requirement from ISO 2108.
> 
> I think this is a specification for URNs, and the conformance requirements should apply to the URNs.  What you're saying here is a statement about some OTHER standard, which I might write as:
> 
> "ISO 2108 requires that each product form (hardback, paperback, PDF) have its own ISBN."
> 
> This is just a statement of a fact about another standard, and URNs need to function even in situations that don't exactly follow that requirement, for example, as mentioned, cases where people have digitized a hardcopy book from their own collection, but not assigned a different ISBN.  
> 
> I think you should avoid using normative language for anything other than what a conforming URN and URN processing agent MUST/SHOULD/MAY do in order to reach interoperability between communication agents using URNs in their communication.

As the author of the text, it was not clear to me where to draw the 
line. The current version of RFC3187bis makes it as explicit as possible 
that in the URN:ISBN namespace, every URN must conform to the ISO 2108. 
That is, every namespace specific string must be an ISBN; nothing more, 
nothing less. In addition, I have included some ISBN rules of assignment 
into the draft as MUSTs.

But I have no problem changing the draft so that the normative language 
is only used in the way Larry suggests. Detailed guidance on how to use 
ISBNs in the URN system can be produced separately, for instance in 
co-operation with the ISBN international centre.

Similar changes should be made to 3188bis as well. But there there is no 
external standard to refer to, so IMHO RFC3188bis should provide more 
information than RFC3187bis as regards what MUST/SHOULD/MAY be done.

Best regards,

Juha
> 
> Larry
> --
> http://larry.masinter.net
> 
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn
> 

-- 

  Juha Hakala
  Senior advisor, standardisation and IT

  The National Library of Finland
  P.O.Box 15 (Unioninkatu 36, room 503), FIN-00014 Helsinki University
  Email juha.hakala@helsinki.fi, tel +358 50 382 7678