Re: [art] [Uri-review] Re: Alternative representation of URIs in YANG

Sorry for dropping the ball on this...

"Martin Thomson" <mt@lowentropy.net> writes:
> I know that you are trying to make the case for decomposition Dale,
> but I don't think it has been made.  RFC 6991 made the right call
> (mostly; see below) in avoiding the need for a URL parser.
>
> steam://run/<digits> doesn't follow the authority form, but will be
> parsed successfully as such.  Is that a good outcome?

I don't see precisely what the problem is here.  Syntactically, it has a
<authority> of "run", which is syntactically a <host>, and an
<path-abempty> of "/<digits>".  Of course *semantically* "run" is almost
certainly not a valid host name.  (Then again, maybe not.  I remember
hearing the story of a fellow whose e-mail address was <something@se>
because the country root domain "se" had an MX record.)  But it's not
clear to me that the "validity" of a URI depends on the <host> being the
name of an existing host.

As for parsing URI's, I've not written a parser personally but I did
work with someone who wrote a "Perl-compatible regular expression" that
was exeuted by a "PCRE" C package and it worked straightforwardly.

Though I don't really have a strong opinion about which way the Yang
module does it.

Dale

Received on Thursday, 22 January 2026 02:09:44 UTC