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

SM <sm@resistor.net> Thu, 20 October 2011 05:53 UTC

Return-Path: <sm@resistor.net>
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 DD70621F8AEC for <urn@ietfa.amsl.com>; Wed, 19 Oct 2011 22:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.403
X-Spam-Level:
X-Spam-Status: No, score=-102.403 tagged_above=-999 required=5 tests=[AWL=0.197, BAYES_00=-2.599, 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 jXj5GhwS-RFd for <urn@ietfa.amsl.com>; Wed, 19 Oct 2011 22:53:36 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DCF6C11E807F for <urn@ietf.org>; Wed, 19 Oct 2011 22:53:36 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id p9K5pYC5006776; Wed, 19 Oct 2011 22:51:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1319089902; bh=SAN83k7H1JFHCHMTzmDb4of1ZcXSQIN2U4P6Gpw84zw=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=WTDQaLo0qm08KBA/3kifouzQLXUpDTHDxHGaa/2ayyo5poeeP+76zlq1oGcmSTiea LSu8igYK3wQZIjQtRxjFIPEa3+Z5PlbL3p376Yha7QBbk+LdGYUdOe7fRJRDxzQ6XF 43JKhZ4srgop3QrK6rj1BJ/bFAKfG9ghwjHINXwU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1319089902; bh=SAN83k7H1JFHCHMTzmDb4of1ZcXSQIN2U4P6Gpw84zw=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=wERXxxgBxsOVwpRfq4h38fFENSKn+ppvS0x99NB98y1qirU0Ab29S1MMkAu11ZiyM kT/SHb34BWSPEekMKvSH8jP4bDcId3T43Yd+YfycxEsa+mqYyxvWTU6s+Jdbko01s9 1pAUb29EnjiHBViRU/4poIiRaJLn4jYqvbNKF9AI=
Message-Id: <6.2.5.6.2.20111019221055.0c6ed8f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 19 Oct 2011 22:26:18 -0700
To: Larry Masinter <masinter@adobe.com>, ah@TR-Sys.de
From: SM <sm@resistor.net>
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D05D4AC0EF4@nambxv01a.corp. adobe.com>
References: <6.2.5.6.2.20111019023731.0aa22fe0@elandnews.com> <201110192200.AAA25239@TR-Sys.de> <C68CB012D9182D408CED7B884F441D4D05D4AC0EF4@nambxv01a.corp.adobe.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: 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:53:39 -0000

Hi Larry,
At 18:32 19-10-2011, Larry Masinter wrote:
> > 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

That is the point I was trying to make.

>  might write as:
>
>"ISO 2108 requires that each product form (hardback, paperback, PDF) 
>have its own ISBN."

Yes.  I suggest writing the specification from an IETF implementation 
perspective and not an ISO perspective.

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

Yes.

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

Yes.

Regards,
-sm