Re: [urn] Namespace application: reso

Sam DeBord <> Tue, 10 December 2019 22:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A042A1200F1 for <>; Tue, 10 Dec 2019 14:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.877
X-Spam-Status: No, score=-1.877 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UgPFs8lHbAhL for <>; Tue, 10 Dec 2019 14:22:48 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 30B9A1200D7 for <>; Tue, 10 Dec 2019 14:22:48 -0800 (PST)
Received: by with SMTP id b8so11399626oiy.5 for <>; Tue, 10 Dec 2019 14:22:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ArlUUY2xsJD7K0cPrQ/aj7a32pP+njY4Qq6TrmoVK80=; b=JtVOnC1/KkktpTpdHx1LwMJ9eIC0RhWo1sjCuuj1jnMy2dgBDZb7TuPqst24jWB50k j+g+91hCVgbbUxjoonDhnoPvaarRK7wdtph01ilpWVDzINJHs2XLJgUsjaJxSHWUfD9p v/fnf4MPnra0knsrqTZ3ATQEtDib2p6gRA8k9rx6w/UmkLIwrf7VNSApTdDXzJdA+6N+ 8WKtjAb+KBvDTVWYclPzO7maBAILRhLX5x5sWvv5cWYIxveEhxBAs6TRPSQhNsPPjABq wugeF3iDlZlDo8WLfFLEWMOhVSBHOHsQcaWeQs4mf0LctWUWOjBPd1iZo+E4Igc4tHa8 fcWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ArlUUY2xsJD7K0cPrQ/aj7a32pP+njY4Qq6TrmoVK80=; b=mirdEGM6HQ4szkJw73fgy/oCoOqpkrMMT0smbuEDfD/dbyvEgxqqC9rU4uXDFBo2YK uGkyUuth3qS90eWbuDVTWf0xOW4kbwrSwUmqIoFMzF30OGH5S9lIt7NRqkuxA8htRyap 7eAJocB9yJQ9hjVMMJqLwqBtuSKzw7aUSned/csBReOhU5yKytyORZ2Fc9miVAvO4hUm J/KaScjwbHXh7gb4x301V6zpawSGWPHHmchkP6PUKB0c7aYexkJHZN9GvJlal8ldD0Dx ir9lvOvQ0ro4L8CXHPevV1RqaDixKfVfhuIfv4Z9/+S5znqeppmGpZkQJtmG54zAYmw/ d4Lg==
X-Gm-Message-State: APjAAAUwLExsM8T3IozWBWz7xzUT/rvd/r4psFVwZqqt/iljY9LBdiX8 sDqbpcoS+R6Okoz7tPc78ZDU1XgMZi82RiF0Q54KAQ==
X-Google-Smtp-Source: APXvYqxJcpUpk7bJ/Tz5EFJIOfDpvTBnaLeIAajCwH+JXnmMWwFxT0LmgrtLc1+L4itVT3KQ5/9Vj7dlLbkJyelBJ3E=
X-Received: by 2002:aca:df07:: with SMTP id w7mr247302oig.145.1576016567227; Tue, 10 Dec 2019 14:22:47 -0800 (PST)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: Sam DeBord <>
Date: Tue, 10 Dec 2019 14:22:34 -0800
Message-ID: <>
To: "Hakala, Juha E" <>
Cc: "Dale R. Worley" <>, "" <>
Content-Type: multipart/alternative; boundary="000000000000a66ec6059960f3ad"
Archived-At: <>
Subject: Re: [urn] Namespace application: reso
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 10 Dec 2019 22:22:51 -0000

Hello Juha,

Thanks for reviewing the RESO website. To provide some more background
about how RESO is intending to use URNs, here is a list of their proposed
uses so far:


   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.

   As a "recorder ID" in the following event model proposal
   <>, in which case
   the URN will take a form similar to the following:
   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.

   Another important use RESO has planned for URNs is for them to act as
   references to RESO Data Dictionary items 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.

Let us know if you have any further questions about the above items or
regarding our application for a URN.

*Sam DeBord*
CEO | Real Estate Standards Organization | 206.658.3225

On Mon, Nov 4, 2019 at 3:01 AM Hakala, Juha E <>

> Hello,
> I checked the RESO web site, and there is standardization (and other)
> activity which would benefit from URN assignment, such as (IMO) IDX data
> standard. However, the registration request should provide some background
> information so that it would not be necessary to retrieve it from somewhere
> else.
> Also, some examples of URNs to be assigned would give us better idea of
> the plans.
> All the best,
> Juha
> -----Alkuperäinen viesti-----
> Lähettäjä: urn <> Puolesta Dale R. Worley
> Lähetetty: sunnuntai 3. marraskuuta 2019 16.11
> Vastaanottaja: Sam DeBord <>
> Kopio:
> Aihe: Re: [urn] Namespace application: reso
> It may be that I read this document too quickly, but I got the impression
> that it is completely *valid*, but it doesn't tell me anything, as far as I
> can tell, as to what these URNs will really be used for.
> Even to the point that I've never heard of the "Real Estate Standards
> Organization" or what it does.  Does it produce a series of standards that
> are used in the real world?  Where in those standards would these URNs be
> used?
> Simimlarly, the proposed syntax is just that the URNs have to be valid
> URNs.  It doesn't hint that you've got any detailed plan in mind.
> Dale
> _______________________________________________
> urn mailing list