request for assignment of informal urn

<yoshiki.sameshima.vf@hitachi-solutions.com> Mon, 09 February 2015 09:22 UTC

Return-Path: <yoshiki.sameshima.vf@hitachi-solutions.com>
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 5BA5D1A00E6 for <urn-nid@ietfa.amsl.com>; Mon, 9 Feb 2015 01:22:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.208
X-Spam-Level: ****
X-Spam-Status: No, score=4.208 tagged_above=-999 required=5 tests=[BAYES_50=0.8, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=no
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 V7AhDwWvRiTr for <urn-nid@ietfa.amsl.com>; Mon, 9 Feb 2015 01:22:13 -0800 (PST)
Received: from mail7.hitachi.co.jp (mail7.hitachi.co.jp [133.145.228.42]) by ietfa.amsl.com (Postfix) with ESMTP id 5F99F1A0016 for <urn-nid@apps.ietf.org>; Mon, 9 Feb 2015 01:22:13 -0800 (PST)
Received: from mlsv4.hitachi.co.jp (unknown [133.144.234.166]) by mail7.hitachi.co.jp (Postfix) with ESMTP id B788737AD5 for <urn-nid@apps.ietf.org>; Mon, 9 Feb 2015 18:22:12 +0900 (JST)
Received: from mfilter05.hitachi.co.jp by mlsv4.hitachi.co.jp (8.13.1/8.13.1) id t199MChP011590; Mon, 9 Feb 2015 18:22:12 +0900
Received: from vshuts04.hitachi.co.jp (vshuts04.hitachi.co.jp [10.201.6.86]) by mfilter05.hitachi.co.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id t199MBXL012289 for <urn-nid@apps.ietf.org>; Mon, 9 Feb 2015 18:22:12 +0900
Received: from gxml13a.ad.clb.hitachi.co.jp (unknown [158.213.157.129]) by vshuts04.hitachi.co.jp (Postfix) with ESMTP id 5762C14005A for <urn-nid@apps.ietf.org>; Mon, 9 Feb 2015 18:22:11 +0900 (JST)
Received: from [127.0.0.1] by gxml13a.ad.clb.hitachi.co.jp (Switch-3.1.10/Switch-3.1.9) id 71990MBUG00007210; Mon, 09 Feb 2015 18:22:11 +0900
Message-Type: Multiple Part
MIME-Version: 1.0
Message-ID: <XNM2$7$1$6$$4$8$2$A$5000104U54d87c3b@hitachi-solutions.com>
Content-Type: text/plain; charset=us-ascii
To: <urn-nid@apps.ietf.org>
From: <yoshiki.sameshima.vf@hitachi-solutions.com>
Date: Mon, 9 Feb 2015 18:22:03 +0900
Priority: normal
Importance: normal
Subject: =?ISO-2022-JP?B?cmVxdWVzdCBmb3IgYXNzaWdubWVudCBv?= =?ISO-2022-JP?B?ZiBpbmZvcm1hbCB1cm4=?=
X400-Content-Identifier: X54D87C3B00000M
X400-MTS-Identifier: [/C=JP/ADMD=GMGROUP/PRMD=GMGROUP/;mta141502091822034L7]
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/5DQ2w9HJp64kqBxjWNnTaNfymsY>
Cc: tomohiro.misawa.rf@hitachi-solutions.com, yoshiki.sameshima.vf@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: Mon, 09 Feb 2015 09:22:16 -0000

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.


9. Process for identifier resolution

The resolution of the URN is processed locally. Firstly the epub publication which
is identified by the UUID/ISBN and FILE is searched in local repository, and then
the rest EPUBCFI part is identified as specified in the EPUBCFI specification.
Future versions of this specification may specify a global resolution process.


10. Rules for Lexical Equivalence

No special considerations.


11. Conformance with URN Syntax

No special considerations.


12. Validation mechanism

None specified.


13. Scope

The scope is global.