Re: [urn] Namespace application v3: reso

lars.svensson@web.de Wed, 16 December 2020 17:03 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 363A13A111E for <urn@ietfa.amsl.com>; Wed, 16 Dec 2020 09:03:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 qekEPLLjuiBk for <urn@ietfa.amsl.com>; Wed, 16 Dec 2020 09:03:30 -0800 (PST)
Received: from mout.web.de (mout.web.de [212.227.17.12]) (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 3B9723A1124 for <urn@ietf.org>; Wed, 16 Dec 2020 09:03:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1608138194; bh=jD2Ah67NNA9zGZxyp8k+OkEIq9DlY+TCqM0reeE7FvU=; h=X-UI-Sender-Class:From:To:Cc:Subject:Date:In-Reply-To:References; b=oa50HKLueIdoLMMuPAFexsbxj8VnDLT8w48WvLUepLOf6otKXgzX+/wRPaetciwQS YKzU9O8FVXg/GoSgf5Gaa2IvUNEC8Nsmaw2KxGTGFCp3tfq4LctyMY970R/MC7dmy6 gBx6XKUmramFxP4cp9pad4x2eDHPVMyaJmzjwwT4=
X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9
Received: from [77.87.224.102] ([77.87.224.102]) by web-mail.web.de (3c-app-webde-bap35.server.lan [172.19.172.35]) (via HTTP); Wed, 16 Dec 2020 18:03:14 +0100
MIME-Version: 1.0
Message-ID: <trinity-8b69b256-abae-4a94-a3e6-6672e8bba503-1608138194555@3c-app-webde-bap35>
From: lars.svensson@web.de
To: "Dale R. Worley" <worley@ariadne.com>
Cc: Sam DeBord <sam@reso.org>, urn@ietf.org, josh@reso.org
Content-Type: text/plain; charset=UTF-8
Date: Wed, 16 Dec 2020 18:03:14 +0100
Importance: normal
Sensitivity: Normal
In-Reply-To: <871rgqt34r.fsf@hobgoblin.ariadne.com>
References: <CAEKPRhku6Y6nBs3e_ziBzRC8qucFEzeT8k0VoV+ORgAGz6ZW2Q@mail.gmail.com> <871rgqt34r.fsf@hobgoblin.ariadne.com>
X-UI-Message-Type: mail
X-Priority: 3
X-Provags-ID: V03:K1:gysjLHg/B/QeROxMtGnv250ldvYb7JzvBDWwdDIcWlqlBhHAkt55R5oby8AGNYu2wpO5b YpOFD8PMeh6A2oBx4YXxJvJ6h6FT+BYPhhNkcGDfZeAhASIDLC/j5BBj5gMQVsS1REe1Z47TElkz LRcDcQPJg3yHC1EM1YF9ch3bE/Uv/ngeYN3YRI5L3irJgbgzqexpAB3R6/1lkQQMAOLFdWtX/9C8 QVx0Zz5UlZqkYfDfHE699a5K5KGia+2C7yxasAjiJNDOJD6PnbnkB0D1QR92Y3i+KK85VSFZB2bx 6I=
X-UI-Out-Filterresults: notjunk:1;V03:K0:SUzrIt8zSdY=:yS95/OZ1i4cckhRpWRpTa7 M5J/Vl+qoKYn2elLFpBGMGcojq/C1XVG34mI2P+iRP2TK3x4LRX8WrTCSCi1ptYs/2QrjQm6s CKSoGNaoayjiDGBRI+tKTn/pHTi62HJRnWIrWLc7Df58F0DgeEQ7z9jE3iPsmOeYPxnaFyoqd WH+NnGbGV3VA6/8D9BDxQuwwpfQvenrsKdLZOSjl4kXYXsC+p5bxqcDDWFJFdz14icEsVQPr+ CCiity3II0spNd6Cu5ufaTuI/y3hBZoOE2RrjFHD5KTnrASjWl34IxE+zVSFHxdq5c5FrT1er 0Ez1BpmSfMvth2wV5O3SXd1c+EXGf772xjWMSGR7CwJDhCrcm3mxCDVnv7L+cE3AGapq2afJo yl4UQB37OHWmXz5GbWgg5tiXCAi67jTLbeu4HsbmV9743hq6wsnY6yRMatBCsG3f9s2pqjNY8 ysBzgn8zE+GwI7rmIqhuE+lMwy0ISMMMgw4lPSvIaPkkUmUqBKqc7OThJi6DQDYUpITRQkZf6 n6ULUxSndNEoyGEtgF1hPbRfa9XoS3jdtIeESMkUwH4Hs6pu87Kxvw/fLhelwYp7p7uVQmyBZ RGifQlg+Qy02E=
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/Z7sUWWp2wES7MEJWPFFZWVgFO6Q>
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: Wed, 16 Dec 2020 17:03:35 -0000

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/
[2] 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>.
> >>>
> >>>
> >>> 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/>.
> >>>
> >>>    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>
>
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn
>