I see nits in this draft: Section 2 says “A newer version of the extension is expected to use an XML namespace with a higher version number than the prior versions” but I can't find anything defining what they mean by "namespace version number". Maybe I just missed it? Maybe this would be obvious to someone familiar with this RFC series? In which cases OK.
Section 6.1 says “ XML: None. Namespace URIs do not represent an XML specification." and then " XML: See the "Formal Syntax" section of this document." Hmm, a namespace URI identifies an XML markup vocabulary, so "None" is a little jarring. If there's no XML why the namespace? And it also feels inconsistent with the second statement. And, more seriously, I can't find a "Formal Syntax" section in the draft, so the 2nd statement needs a fix. On Mon, Jun 6, 2022 at 3:58 PM Michelle Thangtamsatid via RT < [email protected]> wrote: > Dear Martin and Tim (cc: regext WG), > > As the respective designated experts for the namespace (ns) and schema > registries located on the IETF XML Registry page, can you review the > proposed registration in draft-ietf-regext-epp-eai for us? Please see > > https://datatracker.ietf.org/doc/html/draft-ietf-regext-epp-eai-11 > > If this is OK, when the IESG approves the document for publication, we'll > make the registration at > > https://www.iana.org/assignments/xml-registry/ > > The IESG has asked us to set a two-week deadline for registration reviews. > The due date for this request is 2022-06-20. > > Thank You, > > Michelle Thangtamsatid > IANA Services Specialist > >
_______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
