Re: request for assignment of informal urn

Peter Saint-Andre - &yet <peter@andyet.net> Tue, 17 February 2015 16:06 UTC

Return-Path: <peter@andyet.net>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B06301A8A7D for <urn-nid@ietfa.amsl.com>; Tue, 17 Feb 2015 08:06:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.201
X-Spam-Level:
X-Spam-Status: No, score=-1.201 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A0v8-QW6av3q for <urn-nid@ietfa.amsl.com>; Tue, 17 Feb 2015 08:06:10 -0800 (PST)
Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A77971A8A90 for <urn-nid@apps.ietf.org>; Tue, 17 Feb 2015 08:03:22 -0800 (PST)
Received: by pabrd3 with SMTP id rd3so7253313pab.1 for <urn-nid@apps.ietf.org>; Tue, 17 Feb 2015 08:03:22 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=g0eHCIZ1Sj8Wzh/aZyuTn0I23joKacamJxtPllKQQ9o=; b=Lr+yvugp3l1sBMZb+WwgPSy2O8hlJGGEJlHIPAEVzCPe94iFlI5FjOwHEaCX+RplZy wWbJGur8amfcm2h6wzC3Y5FuNSx0VV3PKjqosMV4MJlfjCVrhhEY3Nh9lzXkr/NGHs+H gZ79bGE0msN73v9okwg7Ansj83aX90mSlpM5FxwS77X0tRxBZkcQorvz96rk7G4fc49m d2+86bpskbwR5NQ57Yc5UYkI5+E7QTRf5an2sZVrb5h9r4p1IYoaPtCdLm9vyJZ6LfMj NB1xISP5SW9JtRdyKl+BxgOJeKbGsZgRAEjUG73fy/jn57hFIrYmZdoOX73KtAPU9Qkn BxwA==
X-Gm-Message-State: ALoCoQkZ9xlC/fuMt2dtc8vD/9m8eF9Kvf45UUL8EH6gdD87TNcrUd3NL/XghFcCudVIwkt76nKJ
X-Received: by 10.70.134.97 with SMTP id pj1mr50312380pdb.125.1424189002215; Tue, 17 Feb 2015 08:03:22 -0800 (PST)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id a10sm18050532pdl.61.2015.02.17.08.03.20 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Feb 2015 08:03:21 -0800 (PST)
Message-ID: <54E36647.4060506@andyet.net>
Date: Tue, 17 Feb 2015 09:03:19 -0700
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: yoshiki.sameshima.vf@hitachi-solutions.com, urn-nid@apps.ietf.org
Subject: Re: request for assignment of informal urn
References: <XNM2$7$1$6$$4$8$2$A$5000104U54d87c3b@hitachi-solutions.com>
In-Reply-To: <XNM2$7$1$6$$4$8$2$A$5000104U54d87c3b@hitachi-solutions.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/y4YMeJqM2HruwTclQLYbZ6WMaAE>
X-Mailman-Approved-At: Tue, 17 Feb 2015 08:09:39 -0800
Cc: tomohiro.misawa.rf@hitachi-solutions.com, takanobu.hosoe.ju@hitachi-solutions.com
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2015 16:06:12 -0000

On 2/9/15 2:22 AM, yoshiki.sameshima.vf@hitachi-solutions.com wrote:
> Dear URN NID members,
>
> This is a request for assignment of informal urn.
>
> The following is a URN Namespace Definition according to the template
> described in RFC 3406.
>
> Please send comments to addresses in the cc field.
>
> Best regards,
>
> Yoshiki Sameshima, Hitachi Solutions
>
>
> ---------------- URN Namespace Definition ----------------
>
> I. Namespace ID
>
> To be assigned.
>
>
> 2. Registration Information
>
> Version 1
> Date: 2015-02-09
>
>
> 3. Declared registrant of the namespace
>
> Name:		Yoshiki SAMESHIMA
> 		Takanobu HOSOE
> 		Tomohiro MISAWA
> Affiliation:	Hitachi Solutions, Ltd.
> Address:	4-12-7 Higashi-Shinagawa Shinagawa-ku, Tokyo 140-0002 Japan
> Contact:	Yoshiki Sameshima
> 		yoshiki (dot) sameshima (dot) vf (at) hitachi-solutions (dot) com
>
>
> 4. Declaration of structure
>
> The identifier structure is as follows:
>
> NEW-URN	= "urn:" ASSIGNED-SCHEME ":" ( CoNETS-EPUB-UUID / CoNETS-EPUB-ISBN )
>
> ; There are two types of the new scheme.
>
>
> ;;;
> ;;; First type: CoNETS EPUB UUID
> ;;;
>
> CoNETS-EPUB-UUID = "conets-epub-uuid:" UUID *( "/" FILE ) [ "#" EPUBCFI ]
> UUID = 1*(HEXDIGIT) 0*( "-" 1*(HEXDIGIT))
> FILE = PCHAR *PCHAR
>
> ; The first type is a combination of UUID, optionally file name and EPUBCFI.
> ; A bulky book or a series of books may have a single UUID, but it may consist
> ; of multiple epub publication files. In this case the epub file name is
> ; included in the URN.
> ; A piece of content or any location in an epub publication file is identified
> ; with EPUBCFI, which is a fragment identifier for epub publication, such as
> ; chapter, image, page, etc. EPUBCFI is specified in EPUB Canonical Fragment
> ; Identifier Specification. See Sec. 5.
> ; PCHAR is the same as RFC 3986 or its successors.
>
>
> ;;;
> ;;; Second type: CoNETS EPUB ISBN
> ;;;
>
> CoNETS-EPUB-ISBN = "conets-epub-isbn:" ISBN *( "/" FILE ) [ "#" EPUBCFI ]
> ISBN = 1*(DIGIT / ALPHA) 0*("-" 1*(DIGIT / ALPHA))
>
> ; The second type is as the same as CoNETS-EPUB-UUID except that ISBN is used
> ; instead of UUID. ISBN in URN can be found in RFC 3187
> ; 'Using International Standard Book Numbers as Uniform Resource Names.'
>
>
> 5. Relevant ancillary documentation
>
> Definition of EPUBCFI can be found in:
>      International Digital Publishing Forum,
>      EPUB Canonical Fragment Identifier (epubcfi) Specification
>      http://www.idpf.org/epub/linking/cfi/epub-cfi.html
>
>
> 6. Identifier uniqueness considerations
>
> The URN consists of epub publication identifier (UUID or ISBN), optionally an epub
> publication file and a fragment that identifies content or location in the epub
> file. That is, the URN points some part in the epub publication, and reassignment
> of the URN cannot happen.
>
>
> 7. Identifier persistence considerations
>
> Each time the publication is revised, the UUID/ISBN is changed, and a URN will
> persist in identifying a particular publication even after its lifetime.
>
> As for usability of the identifier, identifier resolution is processed locally
> in this version as described in Section 9, and the usability is assured as long as
> the publication is stored locally. Future versions of this specification may
> specify global repository and persistence of usability of the URN identifier.
>
>
> 8. Process of identifier assignment
>
> UUID is 128 bits long, and requires no central registration process. The generation
> process described in RFC 4122 will give a unique identifier from all other UUIDs
> that have been or will be assigned. ISBN is assigned from the International ISBN
> Agency. As for the other part of the identifier, FILE and EPUBCFI, the assignment
> is open.

I'm confused. Why do we need a new URN namespace, given that we already 
have a URN namespace for UUIDs and a URN namespace for ISBNs?

Peter

-- 
Peter Saint-Andre
https://andyet.com/