URN UUID question

Joel Kalvesmaki <kalvesmaki@gmail.com> Tue, 04 March 2014 15:32 UTC

Return-Path: <kalvesmaki@gmail.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id C17891A0117 for <urn-nid@ietfa.amsl.com>; Tue, 4 Mar 2014 07:32:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id LOW52afWJprd for <urn-nid@ietfa.amsl.com>; Tue, 4 Mar 2014 07:32:08 -0800 (PST)
Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id DD9BE1A0085 for <urn-nid@ietf.org>; Tue, 4 Mar 2014 07:32:07 -0800 (PST)
Received: by mail-vc0-f180.google.com with SMTP id ks9so4517908vcb.11 for <urn-nid@ietf.org>; Tue, 04 Mar 2014 07:32:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=83JFCFSJ42SzQG6wlY9lFhV2htl/TUA89RN0ZpKWMBQ=; b=piw8Mdzs3L0/nuSlSRFG1MAPX9MGuoA8yez+UH4xwAd9sarlLQ8km3K5oIgRbIB6fg SAtwPZSaYanCaOEwBs6BB2NRqiFJx34wMCdiHvl7JKWw2q9/z3Qs9FUz1cqOtscVHSmj wDYndPGH1v1eUjq78eCGtENxxORkeBF7I6foJVSa/g1yq1TWZBR2pnuE6JN7LKx/5LeG mntKM/iCamgMheEQ9kNC+3j73ER8ARnz6tn5xj3KCCrArLa9Mn13bdmoRRDYz46HNy7U Zw/szbjdv0z0po2n6ozgDpvXSXunWXDLKMl4ZzGJU+pke1MSy5UKW5syYQUTr1FGp6Sw 7v/A==
MIME-Version: 1.0
X-Received: by with SMTP id fy14mr38373vec.23.1393947124020; Tue, 04 Mar 2014 07:32:04 -0800 (PST)
Received: by with HTTP; Tue, 4 Mar 2014 07:32:03 -0800 (PST)
Date: Tue, 4 Mar 2014 10:32:03 -0500
Message-ID: <CALPpAZ_fLwK80dcM5ty5pp2pLiafpW36uvK2WoJdKpuaWX6PQw@mail.gmail.com>
Subject: URN UUID question
From: Joel Kalvesmaki <kalvesmaki@gmail.com>
To: urn-nid@ietf.org
Content-Type: multipart/alternative; boundary=089e013a12f029ea7004f3c99b2a
Archived-At: http://mailarchive.ietf.org/arch/msg/urn-nid/_xZPjITDwgDzSNAGZRi4m7tTo4A
X-Mailman-Approved-At: Tue, 11 Mar 2014 10:20:16 -0700
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, 04 Mar 2014 15:41:57 -0000

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

My favored scheme for naming these entities would concatenate a UUID (any
style), a middle delimiter, and an ISO date/dateTime, e.g.,


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?

Best wishes,

Joel Kalvesmaki