[urn] Re: Submission URN:SDMX
worley@ariadne.com Fri, 21 August 2026 02:19 UTC
Return-Path: <dale.worley@comcast.net>
X-Original-To: urn@mail2.ietf.org
Delivered-To: urn@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5A2F012D253C0 for <urn@mail2.ietf.org>; Thu, 20 Aug 2026 19:19:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787278769; bh=apcb7EzZ0/fdktaD3lHGMtZpbCpbf/O+u5setONI1YE=; h=From:To:Cc:Subject:In-Reply-To:Date; b=qBQ/GotaOlK/qXfx20SKN/UYNudO1w6RdRT2aTUgN1c7zzVGK+8jBudEq/u6y9pbM z6fhR8Oegvmx5gW9M3b2Z8t1y0cNTashDCtnN1CQw7PL5Bc46KQIIpE8d6iiinHqI7 tE/4cbIm3UagbEaZoggO6xj7+bWTNNOJNtmqX3ms=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NGfxh5TrsWwt for <urn@mail2.ietf.org>; Thu, 20 Aug 2026 19:19:25 -0700 (PDT)
Received: from resqmta-c2p-570641.sys.comcast.net (resqmta-c2p-570641.sys.comcast.net [IPv6:2001:558:fd00:56::9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id EFCF212D2529E for <urn@ietf.org>; Thu, 20 Aug 2026 19:19:24 -0700 (PDT)
Received: from resomta-c2p-555662.sys.comcast.net ([96.102.18.235]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resqmta-c2p-570641.sys.comcast.net with ESMTPS id xDDjwT5aCEnvoxEqkwhV2S; Fri, 21 Aug 2026 02:19:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1787278758; bh=Uh4oC+sEWYvv2DEegwQbJaNv5aOFC+UkVCx0E02O/0c=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=X+cp2GBwNawI9GU4iVLixD7oZvM4kkbtEyWT354QO2FBcYN+OpY5p8JHMYwguz3pC /StOfp35f+KUunI9u9E1DQwWp4abX+TQngh8cNEhRAt6eDjQgiLroCb+vEtz2Iir6N YWVX5AZp4NDtEZQGz/Yr/54peF3p9by5hLQjFRY2JaW7nW9Vd3mZqrWwLgukf+AIqs Tz16a9aYKbbPeMKInoeJhve5S4YD+rVcDI84NC+WNoTe45iWwSrJBz+F5CgEP0M1i1 8qPVpwKr/AJX+zgZ7JxdzhoP8z7yXRdCQNJQmkC6VZuT3cor+GMBAJqsVY3AARazu1 6hhc8UJpfcU9w==
Received: from hobgoblin.ariadne.com ([76.118.106.138]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resomta-c2p-555662.sys.comcast.net with ESMTPSA id xEqjwiMcgoS8dxEqjw1cJn; Fri, 21 Aug 2026 02:19:18 +0000
Xfinity-QID: xEqjwiMcgoS8dxEqjw1cJn
Xfinity-Graffiti: 66402250898
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 67L2JG2h2069943 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 20 Aug 2026 22:19:16 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 67L2JGjq2069940; Thu, 20 Aug 2026 22:19:16 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to Dale.Worley@comcast.net using -f
From: worley@ariadne.com
To: Tom Roberts <dataguy@smartxdata.com>
In-Reply-To: <CACszovQz9+L4iMkwWNFD_d_hP79au9n=VLRLpfYf+HFYRfpDyg@mail.gmail.com> (dataguy@smartxdata.com)
Sender: worley@ariadne.com
Date: Thu, 20 Aug 2026 22:19:16 -0400
Message-ID: <87qzjs2p23.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4xfCd1m1ecT24W4cy2Eo8GjAMipSjvZuoMhw9DmyadFGr4fHEUafwoCV69qL9xLLzXXRj+/0QLEIrS3C8p8F1x1PDr79T+gSuGNmDibTl5K9+YLIa5Vxfe 1M5k1Z/mwhTtjIw1jMRejoRCAJubuKJaLXVdfk00s+fjtvIyKAkddv2u84FS/qspf6ZaltoFv0QUV0V0h7XOlWmMzJJuqg2EerVga5emrjBiusg9GoXWx22k
Message-ID-Hash: 3BBF4UOPYI3DMY6FXQ2WCHOKRZWGBX7W
X-Message-ID-Hash: 3BBF4UOPYI3DMY6FXQ2WCHOKRZWGBX7W
X-MailFrom: dale.worley@comcast.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-urn.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: urn@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [urn] Re: Submission URN:SDMX
List-Id: "Discussion about Uniform Resource Names (URNs)." <urn.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/GcJym1UJ83sw6Bmzh1agRLep6Dk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Owner: <mailto:urn-owner@ietf.org>
List-Post: <mailto:urn@ietf.org>
List-Subscribe: <mailto:urn-join@ietf.org>
List-Unsubscribe: <mailto:urn-leave@ietf.org>
Reading the registration, one thing that strikes me is that the syntax
is unusually complicated. I assume that the SMDx Sponsors have good
reason for that complexity and I see no reason to object to it.
Process of identifier assignment:
Names are granted via SDMx registration procedures, including the
SDMx Global Registry and designated national or international
organizations.
The registration procedures are probably explained somewhere ISO 17369
or on https://sdmx.org/, but it seems to me that it would be good for
the community if the registration outlined the registration procedures
and provided links to the details, particularly if there are specified
interactions between organizations. E.g., is there some sort of
delegation from the SDMx umbrella organization to the sponsors? What
sort of relationships must an organization enter into in order to cause
needed SDMX URNs to be created? It would be helpful if the registration
contained a quick reference.
Process of identifier resolution:
The official resolver is:
https://urn.sdmx.io/resolve/[urn]
where [urn] is the percent-encoded form of the URN. Alternative
resolvers may exist, but only the official resolver is authoritative.
The instruction "where [urn] is the percent-encoded form of the URN" is
surprising because all of the characters allowed in an SDMX URN are in
"pchar" (RFC 3986) and may be used in HTTP URL "path" parts without
percent-encoding. It seems to me that you should write what everybody
will be doing (is required to do!):
Process of identifier resolution:
The official resolver is:
https://urn.sdmx.io/resolve/[urn]
where [urn] is the URN. Alternative resolvers may exist, but only
the official resolver is authoritative.
Dale
- [urn] Submission URN:SDMX Tom Roberts
- [urn] Re: Submission URN:SDMX Lars G. Svensson
- [urn] Re: Submission URN:SDMX worley