Re: [urn] Namespace application v3: reso

lars.svensson@web.de Thu, 14 January 2021 15:49 UTC

Return-Path: <lars.svensson@web.de>
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 338943A158B for <urn@ietfa.amsl.com>; Thu, 14 Jan 2021 07:49:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.017
X-Spam-Level:
X-Spam-Status: No, score=-2.017 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=web.de
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 HWTo08xCioYT for <urn@ietfa.amsl.com>; Thu, 14 Jan 2021 07:49:57 -0800 (PST)
Received: from mout.web.de (mout.web.de [217.72.192.78]) (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 BC5C23A1584 for <urn@ietf.org>; Thu, 14 Jan 2021 07:49:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1610639381; bh=/NwainIXeq7iGKdw/DbW0Ksj6nZQ5jP+D+DOim1d57o=; h=X-UI-Sender-Class:From:To:Cc:Subject:Date:In-Reply-To:References; b=J2SNUjO5isIGEGUwg75i+nTGiTfj2rz3sOvbbzILoC1nezBjClqsM+m2jALnkO05w +CrmB6tDilgagqLIibNXgNylhEuss7D5X18djcoENUoZA77gVshC6kWq0t43hwUR63 yOTsiewCd20/6ZDpsxrmHEN4a91Ty/5ghhr+NFbE=
X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9
Received: from [77.87.228.69] ([77.87.228.69]) by web-mail.web.de (3c-app-webde-bap09.server.lan [172.19.172.9]) (via HTTP); Thu, 14 Jan 2021 16:49:40 +0100
MIME-Version: 1.0
Message-ID: <trinity-edd7e603-bc36-4a95-8363-fe6881324e6e-1610639380797@3c-app-webde-bap09>
From: lars.svensson@web.de
To: Joshua Darnell <josh@reso.org>
Cc: "Dale R. Worley" <worley@ariadne.com>, Sam DeBord <sam@reso.org>, urn@ietf.org
Content-Type: text/html; charset=UTF-8
Date: Thu, 14 Jan 2021 16:49:40 +0100
Importance: normal
Sensitivity: Normal
In-Reply-To: <CAO7JUS++HvHoOut+sBW0+pOfRrqZA-rqEJPXdn__hLL0Vmw9qQ@mail.gmail.com>
References: <CAEKPRhku6Y6nBs3e_ziBzRC8qucFEzeT8k0VoV+ORgAGz6ZW2Q@mail.gmail.com> <871rgqt34r.fsf@hobgoblin.ariadne.com> <trinity-8b69b256-abae-4a94-a3e6-6672e8bba503-1608138194555@3c-app-webde-bap35> <CAO7JUSKzuSH3fwfLGXHkEDZdaHFpkpX60A3Qb8WSO05h=Gfq5w@mail.gmail.com> <CAO7JUS+u8sDCmejDO4CXaUcXbbHMGK6=q7JPMQx=69YM0u26tg@mail.gmail.com> <CAO7JUS++HvHoOut+sBW0+pOfRrqZA-rqEJPXdn__hLL0Vmw9qQ@mail.gmail.com>
X-UI-Message-Type: mail
X-Priority: 3
X-Provags-ID: V03:K1:k//a31JR6yThOpXSAaJj9ra7RZQe8Shsk3DCR5MJjLWBHXGH7gXUmUUPUOVaJ03mCZur5 SyHHCP9s7q5zs2jrH4IQiK2DqjflOfz51U27LMMF1bUJvGWJjUqJaAW75Q8dRAkgP8mSiFIDvdPh dk8t2SLL2zwEUnd7dJFnMZRvbSfMUruBthe0Xofu9xc145J5UTod0/chMHxf7IIN4BbBrBhtgdZO vxKiaYhrv40oGPuTpl1MpaXZjYsTyB/FlhnPH2p6J/QDBZrK4iVBQZfn/Hgv9QvlEQvHQgoRvT5P rU=
X-UI-Out-Filterresults: notjunk:1;V03:K0:kSTgE5G20X8=:fA2D2F0BSioq3IpLdsyAQK 64Hnk2Xm7dtPGMYT8sdD5CEAVQev1HtZDYEPKlKBqeW3IVvc6Mn9D0sI+AyJY9kY/BqQWUmDy 5SMSjWylhxEqC1N3o6MPtvRYgh2Og7hXc3gc+r1l3YTkDnAUtDSTf5l10KgdTMidBgvPJSihL TMbVpAk6pX9SBY7TYuCvg7RcMg2e6z89/zCvac/yalQcYsvyLPa5Ye1JttXnA+H7Jgs9tyUwj RIjB9ZCAoU3mERCKh3VaFJYIDgD/9KSLVedSa/tGZ3lVranICewoctpRkyomVW3zNms45Ud8h Say1/CQGyhD9bG37ZcUYziX5pPaeNFXMVrcQnJw0HV0E2pxPpKMF+WULhGpMYMjbLq/3Zqb43 Joy2X7dJizSkvHSsUrCPfP+/KMruDcCFzVh7gZgcUEUnXTqlDTc+X5JCaZVbaL4e31qq3HDUj B9ogm6Nmo5BBm8Z6DV2iPXs0y8fbWvhM3slk3YtpsCHwj4P3MmAm3bU/AyFhe3xcDTdv+StBA pr9r/CXz9WZw1HPouzfWiANbO+mPSLQX2iBJ0rJrw7qn/3F0urHb/rUvWGZy/n7Qc63OXhkyE nfHrSnPw6wh6c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/I4jd8f-cDs7P1XEyXL_W4oJ3Tow>
Subject: Re: [urn] Namespace application v3: 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: Thu, 14 Jan 2021 15:49:59 -0000

Dear Josh,
 
Thanks for your submission and for addressing my issues.
 
The application is fine with me and I have no further comments.
 
Best,
 
Lars
 
 
Gesendet: Montag, 28. Dezember 2020 um 21:20 Uhr
Von: "Joshua Darnell" <josh@reso.org>
An: lars.svensson@web.de
Cc: "Dale R. Worley" <worley@ariadne.com>om>, "Sam DeBord" <sam@reso.org>rg>, urn@ietf.org
Betreff: Re: Re: [urn] Namespace application v3: reso
Greetings,
 
There was another round of internal review after I sent the last document. I've attached the latest version of the document, which should be the final version. 
 
Let me know if you have any questions and have a happy new year.
 
-Josh
 
 
 
On Tue, Dec 22, 2020 at 10:54 PM Joshua Darnell <josh@reso.org> wrote:
Made a correction to the section numbering.
 
Apologies in advance for the additional email. This should be the last one.
 
-Josh
 
On Tue, Dec 22, 2020 at 10:49 PM Joshua Darnell <josh@reso.org> wrote:
Greetings, 
 
Thanks for your input and review, Lars and Dale.
 
I have attached a plain text version of our URN proposal which is intended to more closely match the format used by existing URN proposals. 
 
Please let us know if there are any corrections to make or if you have any further questions. 
 
Best,
Josh
 
On Wed, Dec 16, 2020 at 9:03 AM <lars.svensson@web.de> wrote:
Sam, all,

Please accept my apologies as well.

I have one observation: The I-D uses "ulid" as an example of a sub-namespace for "reso". Looking at the reso webpage about "unique licensee identifier" that page uses the abbreviation "uli" instead of "ulid" [1]. Similarily the "unique organisation identifier" page uses "uoi" while your second example uses "org" for the organisation identifier [2]. Is this something you might want to streamline before submitting the draft? I'm fine either way.

[1] https://www.reso.org/unique-licensee-identifier/" target="_blank" rel="nofollow">https://www.reso.org/unique-licensee-identifier/
[2] https://www.reso.org/unique-organization-identifier/" target="_blank" rel="nofollow">https://www.reso.org/unique-organization-identifier/

Best,

Lars

Technically the document is fine with me, so I'd be willing to accept it as-is.

> Gesendet: Donnerstag, 19. November 2020 um 04:52 Uhr
> Von: "Dale R. Worley" <worley@ariadne.com>
> An: "Sam DeBord" <sam@reso.org>
> Cc: urn@ietf.org, josh@reso.org
> Betreff: Re: [urn] Namespace application v3: reso
>
> Sam DeBord <sam@reso.org> writes:
> > Could RESO receive an update on this namespace request? Thank you.
>
> My apologies for neglecting this, especially as I've been one of the
> critics of earlier versions.
>
> Looking at the version that accompanied the message I'm responding to.
> (For clarity, I copy that part of the message below.)  The future uses
> of reso URNs are still rather unformed, but that is quite reasonable
> that this stage.  Clearly, you've put thought into how you would use
> URNs.  And I think that is sufficient to approve this proposal.
>
> I would suggest you give the text a final careful editing.  E.g., it
> contains 'This link shows the "Property" resource', but no link is
> given.
>
> Dale
>
> >>> Namespace Identifier:
> >>>
> >>>    reso
> >>>
> >>> Version:
> >>>
> >>>    0.1
> >>>
> >>> Date:
> >>>
> >>>    2020-03-08
> >>>
> >>> Registrant:
> >>>
> >>> Real Estate Standards Organization
> >>>
> >>> Sam DeBord, CEO
> >>>
> >>> sam@reso.org -- 919.504.9898
> >>>
> >>> Purpose:
> >>>
> >>> The Namespace Identifier (NID) "reso" for Uniform Resource Names
> >>> (URNs) will be used to identify resources published by Real Estate
> >>> Standards Organization: RESO <https://reso.org" target="_blank" rel="nofollow">https://reso.org>.
> >>>
> >>>
> >>> These might include published standards or protocols that RESO
> >>> defines and that make use of URNs.  These namespaces are globally
> >>> unique.  The URN namespace will be used in public networks by clients to
> >>> configure and manage resources in the network.  Servers will enforce the
> >>> uniqueness of the namespaces by using the namespace and the XPath
> >>> associated with the managed node in the network when accessing a resource.
> >>>
> >>>
> >>>
> >>> Examples of proposed uses:
> >>>
> >>>
> >>>
> >>>
> >>> Representation of Unique Licensee IDs: These will have the form of
> >>> urn:reso:ulid:x, where x is a specific licensee identifier. Licensees can
> >>> be people like Agents, photographers, appraisers, and others involved in
> >>> the transaction.
> >>>
> >>>
> >>>
> >>> Recorder IDs: These are part of an event model proposal, in which the URN
> >>> will take a form of urn:reso:recorder:org:x, where org is an organization
> >>> id well-known to RESO and x is identifier of the recording entity in that
> >>> organization.
> >>>
> >>>
> >>>
> >>> References to RESO Data Dictionary items: These are already established
> >>> in our ecosystem. This link shows the "Property" resource, which consists
> >>> of fields and enumerations. Each field has a RESO-generated RecordID
> >>> associated with it (or LookupID in the case of enumerated values). For
> >>> example, the PropertySubType field has a RecordID of 100222, and one of the
> >>> allowed values for that field is Apartment, which is part of Lookup Field
> >>> ID 302000 and has LookupID 302001. These would have URNs of the form:
> >>> urn:reso:rid:100222, urn:reso:lfid:302000, and urn:reso:lid:302001,
> >>> respectively.
> >>>
> >>> Syntax:
> >>>
> >>>    The syntax of Namespace Specific Strings for the "reso" namespace
> >>>    is <NSS> in Uniform Resource Names (URNs) [RFC8141].
> >>>
> >>> The entire URN is case-insensitive.
> >>>
> >>> Assignment:
> >>>
> >>>    RESO will maintain the list of registered resources that use the
> >>>    "reso" NID in the "RESO URN Namespace" standards at
> >>>    <https://www.reso.org/" target="_blank" rel="nofollow">https://www.reso.org/>.
> >>>
> >>>    The RESO workgroups describe the <NSS>, how namespaces will be
> >>> allocated, and how experimental namespaces can
> >>>    be used within the allocated URN.
> >>>
> >>>    RESO will manage resource classes using the "reso" NID and will be
> >>>    the authority for managing resources and associated subsequent
> >>>    strings.  RESO will guarantee the uniqueness of the strings by
> >>>    validating them against the existing content of the standards.
> >>>    RESO may also permit secondary responsibility for certain defined
> >>>    resources.  Once a subtree assignment is made, it cannot be
> >>>    deleted or reassigned.
> >>>
> >>>    RESO may allow use of experimental type values in specific
> >>>    subtrees for testing purposes only.  Note that using experimental
> >>>    types may create collision as multiple users may use the same
> >>>    values for different resources and specific strings.  All
> >>>    experimentation must follow the guidance set forth in "A Uniform
> >>>    Resource Name (URN) Namespace for Examples" [RFC6963].
> >>>
> >>> Security and Privacy:
> >>>
> >>>    There are no additional security considerations other than those
> >>>    normally associated with the use and resolution of URNs in general.
> >>>
> >>> Interoperability:
> >>>
> >>>    There are no known interoperability issues at this time.
> >>>
> >>> Resolution:
> >>>
> >>>    It is not foreseen that URNs within this namespace will undergo
> >>>    resolution.
> >>>
> >>> Documentation:
> >>>
> >>>    Documentation can be found at
> >>>    <https://www.reso.org" target="_blank" rel="nofollow">https://www.reso.org>
>
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn" target="_blank" rel="nofollow">https://www.ietf.org/mailman/listinfo/urn
>
 
 
--
Joshua Darnell
Chief Architect
Real Estate Standards Organization  
PO Box 10824 • Raleigh, NC 27605
D: 919.504.6234 • O: 919.504.9898 • C: 310-456-4640
 
https://www.reso.org/" target="_blank" rel="nofollow">https://docs.google.com/uc?export=download&id=1EzLlCgqZqplSPniGLyWKN9-UxBjGkzSC&revid=0B0gC9jFhv7PyNmtDemQrN3YweEhEbEhISS9XaVdZcm9VdE1RPQ" width="96">
 
 
--
Joshua Darnell
Chief Architect
Real Estate Standards Organization  
PO Box 10824 • Raleigh, NC 27605
D: 919.504.6234 • O: 919.504.9898 • C: 310-456-4640
 
https://www.reso.org/" target="_blank" rel="nofollow">https://docs.google.com/uc?export=download&id=1EzLlCgqZqplSPniGLyWKN9-UxBjGkzSC&revid=0B0gC9jFhv7PyNmtDemQrN3YweEhEbEhISS9XaVdZcm9VdE1RPQ" width="96">
 
 
--
Joshua Darnell
Chief Architect
Real Estate Standards Organization  
PO Box 10824 • Raleigh, NC 27605
D: 919.504.6234 • O: 919.504.9898 • C: 310-456-4640
 
https://www.reso.org/" target="_blank" rel="nofollow">https://docs.google.com/uc?export=download&id=1EzLlCgqZqplSPniGLyWKN9-UxBjGkzSC&revid=0B0gC9jFhv7PyNmtDemQrN3YweEhEbEhISS9XaVdZcm9VdE1RPQ" width="96">