Re: [urn] CTS and CITE2 URNs

"Smith, Neel" <nsmith@holycross.edu> Tue, 05 March 2019 13:40 UTC

Return-Path: <nsmith@holycross.edu>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4D7131161 for <urn@ietfa.amsl.com>; Tue, 5 Mar 2019 05:40:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 E5qlJ8A7KfI8 for <urn@ietfa.amsl.com>; Tue, 5 Mar 2019 05:40:40 -0800 (PST)
Received: from us-smtp-delivery-160.mimecast.com (us-smtp-delivery-160.mimecast.com [63.128.21.160]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6E161310E7 for <urn@ietf.org>; Tue, 5 Mar 2019 05:40:38 -0800 (PST)
Received: from mail-lf1-f70.google.com (mail-lf1-f70.google.com [209.85.167.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-276-jar8UeQCON-s-uk1ASNfKQ-1; Tue, 05 Mar 2019 08:40:34 -0500
Received: by mail-lf1-f70.google.com with SMTP id f69so1206850lfg.10 for <urn@ietf.org>; Tue, 05 Mar 2019 05:40:34 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=flWrFkMj01xz7oXITFBl4wwg6IdzI9TBySSV7lFA1zk=; b=Ssd9ygjtITQOair2mYVapY4OTMP6Z2SrtuU3+4DjJVrQPmI+bk1CmrsdGi6nYXhuPK l81MboQqIMXGxDj/rXYRnc0Vg/zyxOPeF8GvF2lQf+Ku9iBoXhsCUV64jJNU2cWb8zwv MMraRi4MDve6KzjJrsbh2JGmQia1uyXBlrNsE2T75I2u/B5cm9iOxyvu97iP7vbGZIZ+ OndGVoWPSBcS9D6u0HERXUti4r87zaBzxxYcR27Ro2QasmFRDAisZNY02OLsDlvN4o5V 3DHTqmZRxSIbGwAojYRv70L0qZ15E2ebHospf2bQfmWpIghpDWijaMNn5utjhvBmSOQN K0bA==
X-Gm-Message-State: APjAAAXNAhjgm9BIZHiLZq2pq+9tzuWEi9jN9USjSFuLQVSB7SMyraCM R13PNVihoMAusgGJuLfnN4i6FRABM52yI73bCMagtFjghWvlqdkSNh9XttzNobGfr9cQhy4e18W qHLXWZtV6k88SOU+YKr/ySrKx9l1OhErgC9MuBuZk9voHxw==
X-Received: by 2002:a2e:3009:: with SMTP id w9mr529427ljw.144.1551793232721; Tue, 05 Mar 2019 05:40:32 -0800 (PST)
X-Google-Smtp-Source: APXvYqzTAthJLBV/xLY+nHXy0HW55l0aA+DZbHV7qKgyH632Jnon/QBP6VUvKDvn0Jf/eUSpNRHx0IF30dQP/NqwIv0=
X-Received: by 2002:a2e:3009:: with SMTP id w9mr529409ljw.144.1551793232365; Tue, 05 Mar 2019 05:40:32 -0800 (PST)
MIME-Version: 1.0
References: <f6f76959-e746-1a21-0d15-21fd88cb5c17@stpeter.im> <HE1PR07MB30973B4C5F2D5B5899D76A75FA720@HE1PR07MB3097.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB30973B4C5F2D5B5899D76A75FA720@HE1PR07MB3097.eurprd07.prod.outlook.com>
From: "Smith, Neel" <nsmith@holycross.edu>
Date: Tue, 5 Mar 2019 14:40:21 +0100
Message-ID: <CAJh0TCBcyNFKkfkPC2vMJsnMz9ByzgZ7V3z+cngJkFtMkJfYnw@mail.gmail.com>
To: "Hakala, Juha E" <juha.hakala@helsinki.fi>
Cc: Peter Saint-Andre <stpeter@stpeter.im>, "urn@ietf.org" <urn@ietf.org>
X-MC-Unique: jar8UeQCON-s-uk1ASNfKQ-1
X-Mimecast-Spam-Score: 0
Content-Type: multipart/alternative; boundary="00000000000061680d05835904e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/moKTGCOEJZfOtsP5UcSW8JsSo1k>
Subject: Re: [urn] CTS and CITE2 URNs
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2019 13:40:44 -0000

I believe the original rationale was that in the literary texts the Cts URN
was primarily imagined for, "#" might appear far more frequently "@", and
thus would more frequently require either escaping or eye-straining runs of
"##" (the first syntactic, the second interpreted as content).

Thanks for pointing out the outdated RFC reference!

Neel

On Tue, Mar 5, 2019 at 7:59 AM Hakala, Juha E <juha.hakala@helsinki.fi>
wrote:

> Hello,
>
> from my point of view these namespace registrations are interesting, not
> least because I am currently involved revision of ISO 690, the ISO standard
> for bibliographic referencing. URNs for citing resources is something that
> needs to be considered in the revision process.
>
> I am in favour of registering these namespaces. The only reservation I
> have is the usage of "@" to separate subreferences. Would it be possible to
> use hash character for this purpose?
>
> At https://cite-architecture.github.io/ohco2/quick/
>
> the researchers themselves give the following example:
>
> urn:cts:greekLit:tlg5026.msA.hmt:1.2.lemma#μῆνις
>
> which would be better aligned with RFCs 3986 and 8141. According to the
> request, there are no plans to make these URNs actionable, so in the short
> term it does not really matter which character is used, but if in the long
> term actionability becomes an issue, it is better not to divert from RFC
> 3986 unless there is a good reason to do so.
>
> The project refers to RFC 2141 at http://cite-architecture.org/ctsurn/
> and elsewhere; they should use RFC 8141 instead.
>
> In theory, the project should use ISTC (International Standard Text Code)
> to identify textual works, but since ISTC has kicked the bucket, I would
> not insist on using it.
>
> Best,
>
> Juha
>
>
> -----Original Message-----
> From: urn <urn-bounces@ietf.org> On Behalf Of Peter Saint-Andre
> Sent: tiistai 5. maaliskuuta 2019 3.52
> To: urn@ietf.org
> Subject: [urn] CTS and CITE2 URNs
>
> A few months ago while doing research for a side project, I came across
> two URN namespaces (used in humanistic scholarship) that had not yet been
> registered: CTS and CITE2. Since then I've worked with the scholars who
> designed these URN namespaces regarding the registration process. As a
> result, they have prepared the following two registrations:
>
> http://cite-architecture.org/ctsurn/rfc.txt
>
> http://cite-architecture.org/cite2urn/rfc.txt
>
> Review by the other members of the expert review team would be appreciated.
>
> Thanks!
>
> Peter
>
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn
>