Re: URN UUID question

Peter Saint-Andre <stpeter@stpeter.im> Tue, 11 March 2014 17:24 UTC

Return-Path: <stpeter@stpeter.im>
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 D6D9F1A0778 for <urn-nid@ietfa.amsl.com>; Tue, 11 Mar 2014 10:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, 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 KUJsTvCwVbwz for <urn-nid@ietfa.amsl.com>; Tue, 11 Mar 2014 10:24:08 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7A91A0779 for <urn-nid@ietf.org>; Tue, 11 Mar 2014 10:24:08 -0700 (PDT)
Received: from aither.local (unknown [24.8.184.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 6167140464; Tue, 11 Mar 2014 11:24:02 -0600 (MDT)
Message-ID: <531F46B1.1030301@stpeter.im>
Date: Tue, 11 Mar 2014 11:24:01 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Joel Kalvesmaki <kalvesmaki@gmail.com>, urn-nid@ietf.org
Subject: Re: URN UUID question
References: <CALPpAZ_fLwK80dcM5ty5pp2pLiafpW36uvK2WoJdKpuaWX6PQw@mail.gmail.com>
In-Reply-To: <CALPpAZ_fLwK80dcM5ty5pp2pLiafpW36uvK2WoJdKpuaWX6PQw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/3Qtn_YcvdBN7FIxf1al4LAsieKM
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, 11 Mar 2014 17:24:10 -0000

On 3/4/14, 8:32 AM, Joel Kalvesmaki wrote:
> 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?
>
> Perhaps there already exists a urn scheme that does what I intend?
>
> Are there any other issues I should consider before adopting a naming
> scheme like this?

As far as I can see, you don't really need or necessarily want the 
"urn:uuid:" string at the front. Why not things like this?

f60330fd-1900-44ac-a825-de70074e142e::2014-02-07Z
f60330fd-1900-44ac-a825-de70074e142e::2014-02-28T00:20:58.3Z

Peter