Re: Re: request for assignment of informal urn

worley@ariadne.com (Dale R. Worley) Thu, 26 February 2015 03:37 UTC

Return-Path: <worley@alum.mit.edu>
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 1CBAC1A1AB5 for <urn-nid@ietfa.amsl.com>; Wed, 25 Feb 2015 19:37:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.465
X-Spam-Level: *
X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=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 1vFThSa8O3fS for <urn-nid@ietfa.amsl.com>; Wed, 25 Feb 2015 19:37:24 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21D111A1AA1 for <urn-nid@apps.ietf.org>; Wed, 25 Feb 2015 19:37:24 -0800 (PST)
Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-06v.sys.comcast.net with comcast id wrdP1p0012N9P4d01rdP2o; Thu, 26 Feb 2015 03:37:23 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-ch2-13v.sys.comcast.net with comcast id wrdN1p0031KKtkw01rdNE2; Thu, 26 Feb 2015 03:37:23 +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 t1Q3bLcZ023142; Wed, 25 Feb 2015 22:37:21 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id t1Q3bKQx023139; Wed, 25 Feb 2015 22:37:20 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: <yoshiki.sameshima.vf@hitachi-solutions.com>
Subject: Re: Re: request for assignment of informal urn
In-Reply-To: <XNM2$7$1$6$$4$8$2$A$5000151U54ed864b@hitachi-solutions.com> (yoshiki.sameshima.vf@hitachi-solutions.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Wed, 25 Feb 2015 22:37:20 -0500
Message-ID: <87a9019wcv.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1424921843; bh=RFMQf/sfVCvWbpxLM3rxmVGnkgI3AD9UXVwOsVvQcGA=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=WgnFTeNBVLs96oV2pI6+tJOL8vIU60S2N+Fe11quUB9KfyvyuYYHWa3FDn5qlT5gh qzZtS2evDBApAdWLUrhgFbTQeqzucpdS1tMtnCwwFyRPQTdKWuNL0kYg4XbaCtsUwm Qy+Q9UBC4/f+clNT2OzTKMLS0lwgDdXdVb7jFsDZ4azkNy1zwBpfq/BzeA6Wz4GjU1 01BY9K3tlqEKlGEVY37H4QxiSDrEa7IDHnsefWFoj0v7Y+9RKjBSyV1+U4LHJkA3G5 LGJnLsn35Ps1Lm7dnsjvrFhZL72g4/ncAe7NlUwGF5dcmjceM4Suqg2naqUQByqk/d TLhq7JmCPNuMw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/PXYyFUniB3bkTQMNf4dYeGPMfrE>
Cc: tomohiro.misawa.rf@hitachi-solutions.com, urn-nid@apps.ietf.org, yoshiki.sameshima.vf@hitachi-solutions.com, takanobu.hosoe.ju@hitachi-solutions.com
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: Thu, 26 Feb 2015 03:37:25 -0000

<yoshiki.sameshima.vf@hitachi-solutions.com> writes:
> As a result, our urn is a form of UUID/ISBN + FILENAME + EPUBCFI.

For some reason, I overlooked the FILENAME component.  That's a mistake
on my part.

But it means that we can't look at these as simply "UUID/ISBN plus
fragment identifier (EPUBCFI)".

An alternative syntax would be if the FILENAME information could be
included in the EPUBCFI.  But I expect that you've verfied that there is
no good way to do that.

I can see why you'd need a new namespace, because you need the
additional FILENAME information in the URN proper.

Dale