IETF Logo Mail Archive

[art] Re: Alternative representation of URIs in YANG

Kent Watsen <kent+ietf@watsen.net> Thu, 04 December 2025 23:44 UTC

Return-Path: <0100019aebc0b4e0-bc19abde-72ff-4758-bfbe-19a0d7ddddbd-000000@amazonses.watsen.net>
X-Original-To: art@mail2.ietf.org
Delivered-To: art@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 136B495B73A0; Thu, 4 Dec 2025 15:44:33 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=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 (1024-bit key) header.d=amazonses.com
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 Lx0AxmEg8kYW; Thu, 4 Dec 2025 15:44:32 -0800 (PST)
Received: from a48-90.smtp-out.amazonses.com (a48-90.smtp-out.amazonses.com [54.240.48.90]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 9A80095B7399; Thu, 4 Dec 2025 15:44:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1764891866; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=fp8McZRI0t3MBG/KGUQ8uhY7Prdhxxq45AMWjMOx3+o=; b=fO9Yib+6rVzgO3avarBIYMuArl8ZOx/SiKDpCiUoP7Qw7RycJUbp3EbpoGCumsao 52Ur+Q/NKzJfTJ3FFcDDOLA75DrN3CHzWx1Rj/o8eOZ5dgf+vmBEfSq21hZ45rN2R4H FbamH1yS0AsSwpOwNsIGD2mnTcntR19/gfENUUnQ=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100019aebc0b4e0-bc19abde-72ff-4758-bfbe-19a0d7ddddbd-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_96EF537B-72EF-4173-965C-8B057AE090CD"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Date: Thu, 04 Dec 2025 23:44:26 +0000
In-Reply-To: <8dd16b2f-81ca-4ce9-9e1e-fbca46f5e7e8@betaapp.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
References: <04751771-27b6-4894-81dc-82036aeea5d2@betaapp.fastmail.com> <0100019ab804a507-449eb08e-87a3-4afc-bb98-9b67827bf928-000000@email.amazonses.com> <05d03d11-f140-461e-8a68-0dd6f1bfe465@it.aoyama.ac.jp> <FRWPR07MB106228FC36F536D383AEEE6A5A2DDA@FRWPR07MB10622.eurprd07.prod.outlook.com> <331d1f14-8ae6-41b7-810d-a21c3a5a5041@it.aoyama.ac.jp> <0100019ae08ae5d4-27a4240b-c315-4363-b79c-2fb80a81eb9f-000000@email.amazonses.com> <8679986b-f7c5-4621-bd04-b970b90ce426@betaapp.fastmail.com> <0100019ae59947ac-edb18e77-10fb-4adf-8e18-da9fe0ee7a01-000000@email.amazonses.com> <fd64b5cb-a74f-4ba0-8469-7a84f127e518@betaapp.fastmail.com> <0100019ae9d410b7-65ca59e5-f278-43b4-a9d7-b269bf5dc61c-000000@email.amazonses.com> <8dd16b2f-81ca-4ce9-9e1e-fbca46f5e7e8@betaapp.fastmail.com>
X-Mailer: Apple Mail (2.3826.700.81)
Feedback-ID: ::1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2025.12.04-54.240.48.90
Message-ID-Hash: 6BCMXWOSXENAY7IEG3XNRCPV24LHBZP4
X-Message-ID-Hash: 6BCMXWOSXENAY7IEG3XNRCPV24LHBZP4
X-MailFrom: 0100019aebc0b4e0-bc19abde-72ff-4758-bfbe-19a0d7ddddbd-000000@amazonses.watsen.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-art.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>, tom petch <ietfa@btconnect.com>, "art@ietf.org" <art@ietf.org>, "uri@w3.org" <uri@w3.org>, "uri-review@ietf.org" <uri-review@ietf.org>, Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [art] Re: Alternative representation of URIs in YANG
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Ac98LKWQW1KTK8HwdD53MG6g0c8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Owner: <mailto:art-owner@ietf.org>
List-Post: <mailto:art@ietf.org>
List-Subscribe: <mailto:art-join@ietf.org>
List-Unsubscribe: <mailto:art-leave@ietf.org>

Hi Martin,

Thanks - that was helpful.  Okay, so I see now that "uri" is a bad name.  

Some options:

 decomposed-uri or uri-decomposition
suggested by Martin J. Dürst
structured-uri or uri-structured
this makes more sense to me than "decomposed", but I'm not a URI expert
url
my favorite, and I think accurate, per https://datatracker.ietf.org/doc/html/rfc3305#section-2,  anything wrong with it?

Thanks again,
Kent



> On Dec 4, 2025, at 4:16 PM, Martin Thomson <mt@lowentropy.net> wrote:
> 
> On Fri, Dec 5, 2025, at 01:46, Kent Watsen wrote:
>> But I'm still trying to square the statement "URIs are more complicated 
>> than your decomposed structure allows for".  So far, they still appear 
>> to be 1-1 to me.  Can an example where conversion doesn't hold be 
>> provided?  A pointer to some text in an RFC would also be great.
> 
> Try RFC 8141 to start.  Or sip: URIs.  Or mailto:.  Or steam:.  Or view-source:.  Or about:.  Or ipfs:.  https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml lists a lot of schemes, few of which fit your structure well, I suspect.

v2.46.0 | Report a Bug | By Email | System Status