[urn] Re: Registration request for AR URN Namespace

Hi @Dale R. Worley<mailto:[email protected]>,

The Key Value example that I provided is a extension we intend to submit to allow for additional data to be recorded against domain names. For example a registered business number. So the values are the Key (for the attribute) and the value for, well the value supplied by the client.

We don’t have an intention in setting a key value in the URN itself.

So … it will be:

    urn:gdr:params:xml:ns:variant-1.0
    urn:gdr:params:xml:ns:kvlist-1.0

(sorry I released I may have posted an incorrect example in the past where the "ns" was missing from the full URN.).

With that clarification, is version 4 of the document acceptable in its current form?

Or should we update it to:

      extension = 1*( ALPHA / DIGIT / "-" / "." / "_" / "~")

Regards
Quoc


From: Dale R. Worley <[email protected]>
Sent: Friday, 13 February 2026 01:45
To: Quoc Pham <[email protected]>
Cc: [email protected]; [email protected]; Sharon Jonnalagadda <[email protected]>
Subject: Re: [urn] Re: Registration request for AR URN Namespace

My apologies for not dealing looking at sooner. "Quoc@ registry. godaddy" <Quoc@ registry. godaddy> writes: > Thank you both, I’ve made the updates and @Dale > R. Worley<mailto: worley@ ariadne. com> I used your suggested rephrasing
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd

My apologies for not dealing looking at sooner.



"[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> writes:

> Thank you both, I’ve made the updates and @Dale

> R. Worley<mailto:[email protected]> I used your suggested rephrasing

> (couldn’t of said it better myself).

>

> Please see the attached, hopefully this is the last revision.



> [2:text/plain Show Save:gdr_namespace_v4.txt (2kB)]



Looking at gdr_namespace_v4.txt, I think the Syntax section needs more

detail regarding the precise syntax of <extension>.  My I suggest this

version?



    Syntax:



      urn:gdr:params:xml:ns:<extension>, where <extension> is the EPP command

      extension. Some examples include but not limited to:

      * <variant>: managing variants of internationalized domain names.

      * <kvlist>: supplying a key value list to represent additional domain name

      registration details.



      All extensions extend the base EPP commands described in RFC5730,

      according to the following syntax:



      extension = segment *( ":" segment )

      segment   = 1*( ALPHA / DIGIT / "-" / "." / "_" / "~" / "=" )



The main difference is that <extension> is specified concretely as a

series of one or more "segments", which are separated by colons, and

each segment is one or more characters in the specified list.  We

haven't been talking about many examples but these have been mentioned:



    urn:gdr:params:xml:ns:rgp-1.0

    urn:gdr:params:xml:ns:variant-1.0

    urn:gdr:params:xml:variant-1.0



The first two each have one segment, "rgp-1.0" and "variant-1.0".



The last example is actually incorrect according to the syntax because

it doesn't start with "urn:gdr:params:xml:ns:".  You may want to make

the specification more general and just say "urn:gdr:<extension>", which

would allow you to make URNs that aren't XML namespace names the

third example.



The syntax I've written above allows more elaborate URNs like



    urn:gdr:params:xml:ns:variant-1.0:feature-abc



Each segment is one or more character taken from the list of characters.

It is the "unreserved" list that we've been talking about, but I've

added "=" because the discussion talks about "supplying a key value

list" so that you can have a key-value pair in a URN, perhaps like this:



    urn:gdr:params:xml:ns:variant-1.0:feature=abc



I don't know whether you intend to have URNs which prescribe values for

keys; if not, there's no need to include "=" in segment.



Dale

_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]