Re: [urn] CTS and CITE2 URNs (Dale R. Worley) Sun, 24 March 2019 22:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3354F12015E for <>; Sun, 24 Mar 2019 15:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Kqm014DZqcxE for <>; Sun, 24 Mar 2019 15:17:08 -0700 (PDT)
Received: from ( [IPv6:2001:558:fe16:19:96:114:154:160]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8D76812014F for <>; Sun, 24 Mar 2019 15:17:08 -0700 (PDT)
Received: from ([]) by with ESMTP id 89o1hmcDdXWoX8BQRh5Mut; Sun, 24 Mar 2019 22:17:07 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20180828_2048; t=1553465827; bh=Cw6DWry+bWFfE4CUSMT665Sq/bigucj7naKpkqOH918=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:MIME-Version:Content-Type; b=AvzrnRGQwthz+t6ndXQIHjFtfBuO19eC2q1F6KaIL1GdFTafyJr9naB0Oo5oYuSK3 pXWOW+DK9XYWopt0JOWlYvMw92NLri5JXQz1O8wv9N/c6fkupJvmAa685cVB2EcP8s UR2SzMaJq2wLr72ztu+vUuh6YXw/HhM9bt+YWdmaajKysTY3+r2eY0ggBs4IMX7Z/4 IlstFXcOE8KDP75gSN3wVXTPGhldV8YYFFVr2U1+Mpd6BBtfbf4qeo+PsLlC15v8Bh VtEQyR+KNbRBUjLGc8xMcmv9EybHt2ewuReLhwQPYEn+nDgs7yHb4EQeYVN0eb4DZY 4myIn/7i0zSyw==
Received: from ([]) by with ESMTPA id 8BQJhDg9N3i748BQNhQOlL; Sun, 24 Mar 2019 22:17:07 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedutddrjeeigdduheelucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedttdenucenucfjughrpefhvffujghsfffkgggtgfesthhqtddttddtjeenucfhrhhomhepfihorhhlvgihsegrrhhirggunhgvrdgtohhmucdlffgrlhgvucftrdcuhghorhhlvgihmdenucfkphephedtrddvgeehrdegledrudefleenucfrrghrrghmpehhvghlohephhhosghgohgslhhinhdrrghrihgrughnvgdrtghomhdpihhnvghtpeehtddrvdeghedrgeelrddufeelpdhmrghilhhfrhhomhepfihorhhlvgihsegrlhhumhdrmhhithdrvgguuhdprhgtphhtthhopehurhhnsehivghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedt
X-Xfinity-VMeta: sc=0;st=legit
Received: from ( []) by (8.14.7/8.14.7) with ESMTP id x2OMGwKs005847 for <>; Sun, 24 Mar 2019 18:16:58 -0400
Received: (from worley@localhost) by (8.14.7/8.14.7/Submit) id x2OMGwsm005844; Sun, 24 Mar 2019 18:16:58 -0400
X-Authentication-Warning: worley set sender to using -f
From: (Dale R. Worley)
In-Reply-To: <> (
Sender: (Dale R. Worley)
Date: Sun, 24 Mar 2019 18:16:58 -0400
Message-ID: <>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [urn] CTS and CITE2 URNs
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 24 Mar 2019 22:17:10 -0000

The situation we are in as one of conflicing requirements:  (1) the need
for URNs to absolutely follow the standard (RFC 8141), and (2) the need
for them to be human-convenient.

One way to square this circle would be to define two forms which are in
one-to-one correspondence:  If it starts with "urn:", it is in URN
format, and if it starts with "cts:" or "cite2:", it is in
human-friendly format.  For example, we could define these two strings
to be equivalent:



As long as this correspondence is algorithmicly defined, it shouldn't be
difficult to implement.

The latter proper URN can probably be translated into an IRI that would
show the final characers in the native Greek alphabet, but I don't know
enough about IRIs to know how that would work.