[urn] Re: Registration request for AR URN Namespace
[email protected] (Dale R. Worley) Wed, 21 Jan 2026 21:46:18 -0500
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
"[email protected]" <[email protected]> writes: > Yes, the URL that you are referring to will be the place. Once "gdr" > is registered, we will be making updates to all of our extensions > (which are right now using "ar") to use "gdr" and registering them > with IANA. We have one in progress which is awaiting the approval the > "gdr" registration. I just looked at https://godaddyregistry.github.io/doc/index.html again. Since it's a web page linking to a couple of dozen web pages, it's hard to get an overall sense for it. But it seems to me that it would be much better as documentation for the URNs if there was an index that was a table of URNs (or URN groups, perhaps) to the pages that defined how they are to be used. Though I don't thing that should be gating for the namespace registration. But I do think the syntax description in the registration needs to be made clearer. 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. all extensions will be in us 7bit ascii and not exceed 32 characters. The first sentence is good, but there's no syntax specification for <extension>. The following sentences suggest that "<variant>" and "<kvlist>" could be values for the nonterminal <extension>, but that makes no sense: urn:gdr:params:xml:ns:<variant> is not a URN. It would also help if the capitalization and punctuation were standardized. Dale _______________________________________________ urn mailing list -- [email protected] To unsubscribe send an email to [email protected]