Re: URN UUID question

worley@ariadne.com (Dale R. Worley) Wed, 19 March 2014 21:39 UTC

Return-Path: <worley@ariadne.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 00B711A07E2 for <urn-nid@ietfa.amsl.com>; Wed, 19 Mar 2014 14:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 5QTBkFjNeRNM for <urn-nid@ietfa.amsl.com>; Wed, 19 Mar 2014 14:39:53 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:17]) by ietfa.amsl.com (Postfix) with ESMTP id AD05F1A07F2 for <urn-nid@ietf.org>; Wed, 19 Mar 2014 14:39:48 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta10.westchester.pa.mail.comcast.net with comcast id fVMR1n0020bG4ec5AZffTk; Wed, 19 Mar 2014 21:39:39 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta03.westchester.pa.mail.comcast.net with comcast id fZff1n00F1KKtkw3PZffsC; Wed, 19 Mar 2014 21:39:39 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s2JLddUU012676; Wed, 19 Mar 2014 17:39:39 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s2JLdchi012675; Wed, 19 Mar 2014 17:39:38 -0400
Date: Wed, 19 Mar 2014 17:39:38 -0400
Message-Id: <201403192139.s2JLdchi012675@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Joel Kalvesmaki <kalvesmaki@gmail.com>
In-reply-to: <CALPpAZ_fLwK80dcM5ty5pp2pLiafpW36uvK2WoJdKpuaWX6PQw@mail.gmail.com> (kalvesmaki@gmail.com)
Subject: Re: URN UUID question
References: <CALPpAZ_fLwK80dcM5ty5pp2pLiafpW36uvK2WoJdKpuaWX6PQw@mail.gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395265179; bh=5Hq1uT/6rboXqNwgZZf4uTK/k3VxRNhfHaV8YjPhvM4=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=vOymfe7w3FlIc7TDhGrPhREkX8OwEcNhoRn93qQZXscs9b8IPYvkuY7A522FrSnCg vUlmgbmi/O+JNa2D8l6REt1Muz5i832C9fiHvoKsrO4kHHoFhKnIIU5sioTiHMbr9G 8DjbW2lJKpCP0U1/cgHF0F0huk8w7OeSiN3GUrR7s6vIywr6/ON4OEYM3MCYhKX/bR jZyYiccxii/w4pyTMWWg7vFw/4Ge9rpfct5AaxEtUQIeQPOIyoLijTeewGQzfiTOoS zGb59Ywp7S6NIPZPCj3rXT6H/frf4qwrbkgfV8tbchWGigk/1AowkZOpKljv8UAIE2 XLCubdEMqQNfg==
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/ItYds1ifQqpgsxMvZHofTiGJyTE
Cc: urn-nid@ietf.org
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: Wed, 19 Mar 2014 21:39:57 -0000

> From: Joel Kalvesmaki <kalvesmaki@gmail.com>

> Are there any other issues I should consider before adopting a naming
> scheme like this?

There are many issues to be considered.  As you state it, the problem
is very unconstrained.  At the very least, why you want it to be a URN
is not explained.

> [1:text/plain Hide]
> 
> I am developing an XML data model that requires users to name versions of a
> document. Each version's name should be unique, but patterned to allow
> anyone (human or computer) to associate it with the names of other versions
> of that document and to place it in chronological sequence. The name of
> each version must be a single string, specifically a IRI/URI (to
> facilitate, among other things, straightforward declarations in RDF). It
> should not be split into two elements. Naming must be as decentralized as
> possible.
> 
> My favored scheme for naming these entities would concatenate a UUID (any
> style), a middle delimiter, and an ISO date/dateTime, e.g.,
> 
> urn:uuid:f60330fd-1900-44ac-a825-de70074e142e::2014-02-07Z
> urn:uuid:f60330fd-1900-44ac-a825-de70074e142e::2014-02-28T00:20:58.3Z
> 
> Would it be misleading to begin such a string with "urn:uuid:" and if so,
> what are the alternative best practices?

Given that the resulting string would not be a legitimate URN, the
format is somewhat deceiving.  I suggest that the delimiter between
the parts be a character that is not valid in URIs, thus clearly
separating the URN from the version.

Another alternative is to assign documents object IDs, and using the
last number in the object ID to indicate the sequence.  Thus,

urn:oid:1.3.6.1.4.1.14490.4.23178

designates a document (through its history), wile the various versions
of it are:

urn:oid:1.3.6.1.4.1.14490.4.23178.1
urn:oid:1.3.6.1.4.1.14490.4.23178.2
urn:oid:1.3.6.1.4.1.14490.4.23178.3
urn:oid:1.3.6.1.4.1.14490.4.23178.4
urn:oid:1.3.6.1.4.1.14490.4.23178.5

Dale