Re: [urn] Namespace application v2: reso

worley@ariadne.com Fri, 24 April 2020 02:04 UTC

Return-Path: <worley@alum.mit.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 1A8E73A0D75 for <urn@ietfa.amsl.com>; Thu, 23 Apr 2020 19:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.983
X-Spam-Level:
X-Spam-Status: No, score=-0.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 04blf7RnWf06 for <urn@ietfa.amsl.com>; Thu, 23 Apr 2020 19:03:59 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78D2C3A0D77 for <urn@ietf.org>; Thu, 23 Apr 2020 19:03:59 -0700 (PDT)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id RnSbjyA1podOERnh8jdhQM; Fri, 24 Apr 2020 02:03:58 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1587693838; bh=wf3V9D0P7OaUG/iZ/gvPyiTo0Rq6GDsndxXqWWpMg8k=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=p++bCEl1kII3YTXmmMAQsIoVDFPxhR1pgHY+6ygbE2wYm9k0k7ECT9nRlrdST+dR5 Pwihh0XCxOrgihIgmTA+TQ6CZ1yz/xSrUriC+wNKlowoJXesyoq0gWuA0ca8yDEC3P 30+oG8NPT0ilkkDGpywLzpXD/up73UlMTk1mKDQG31Ft0Wz+PORmbeU5Aa/ryfhWV7 FVRyGFkmD9Zfcyg6pSouHfi6Ukjs8a2q2j1FaoYyUaez8sdrBc7vHEbCghgm2uiP9U NZ6uuGtA4rahK/Lh6JVXnA6uxI87PR65eWHwwifdRTdIuALizcFlIJLuDzRrOJiLdV i57FNQK/lJriw==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-05v.sys.comcast.net with ESMTPA id Rnh6jhdGwA3a3Rnh7jalRd; Fri, 24 Apr 2020 02:03:57 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
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 03O23umE020466; Thu, 23 Apr 2020 22:03:56 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 03O23tsp020463; Thu, 23 Apr 2020 22:03:55 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Sam DeBord <sam@reso.org>
Cc: urn@ietf.org, josh@reso.org
In-Reply-To: <CAEKPRh=EEuCGn+hLBTFWEcn5R-E=SHannVNndqPh1GH0iwbSpA@mail.gmail.com> (sam@reso.org)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 23 Apr 2020 22:03:55 -0400
Message-ID: <87r1wdtzas.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/iIuqv04g8GcJNxUbtCzKg2xQVlM>
Subject: Re: [urn] Namespace application v2: reso
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: Fri, 24 Apr 2020 02:04:01 -0000

Sorry about not responding to this sooner.

Sam DeBord <sam@reso.org> writes:
> Documentation:
>
>    Documentation can be found at
>    <https://www.reso.org>

I went to this URL, and didn't find any documentation about URNs,
although I didn't spend much time on searching.  If you intend to have a
URN system, it would help to fix a URL that goes directly to where you
record comprehensive information about the URNs.  This might be a
natural extension of your existing Data Dictionary Wiki.

I can see a way forward by taking your examples and writing them up as
specifications in the wiki:  What is the overall structure of reso URNs?
What categories do they come in?  How are licensee IDs constructed?  How
are recorder organization and entity IDs constructed?  What is the
system for constructing URNs for Data Dictionary items?

Dale