IETF Logo Mail Archive

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

Larry Masinter <masinter@adobe.com> Thu, 20 October 2011 01:32 UTC

Return-Path: <masinter@adobe.com>
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 145C11F0C41 for <urn@ietfa.amsl.com>; Wed, 19 Oct 2011 18:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.292
X-Spam-Level:
X-Spam-Status: No, score=-106.292 tagged_above=-999 required=5 tests=[AWL=0.307, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 itty9gZqR5dS for <urn@ietfa.amsl.com>; Wed, 19 Oct 2011 18:32:49 -0700 (PDT)
Received: from exprod6og117.obsmtp.com (exprod6og117.obsmtp.com [64.18.1.39]) by ietfa.amsl.com (Postfix) with ESMTP id 33D1A1F0C3B for <urn@ietf.org>; Wed, 19 Oct 2011 18:32:48 -0700 (PDT)
Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob117.postini.com ([64.18.5.12]) with SMTP; Wed, 19 Oct 2011 18:32:49 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id p9K1UoYE022822; Wed, 19 Oct 2011 18:30:50 -0700 (PDT)
Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id p9K1WO5R008667; Wed, 19 Oct 2011 18:32:24 -0700 (PDT)
Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Wed, 19 Oct 2011 18:32:24 -0700
From: Larry Masinter <masinter@adobe.com>
To: "ah@TR-Sys.de" <ah@TR-Sys.de>, "sm@resistor.net" <sm@resistor.net>
Date: Wed, 19 Oct 2011 18:32:22 -0700
Thread-Topic: [urn] Comments on draft-ietf-urnbis-rfc3187bis-isbn-urn-01
Thread-Index: AcyOr1bWSPUvk+a1RY62C+C8oxJVHAAGANGQ
Message-ID: <C68CB012D9182D408CED7B884F441D4D05D4AC0EF4@nambxv01a.corp.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>
In-Reply-To: <201110192200.AAA25239@TR-Sys.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 01:32:50 -0000

>>    "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.

Larry
--
http://larry.masinter.net

v2.23.0 | Report a Bug | By Email