On Jan 20, 2025 at 7:41:11 AM, "Hollenbeck, Scott" <shollenb...@verisign.com> wrote:
> > > > > *From:* Tim Bray <tb...@textuality.com> > Thank you for the review. In your note, is the concern that the namespace > prefix is being used for the element name (e.g., “addlEmail”)? I found > similar definitions in the following EPP RFCs, which are broadly > implemented: > > > > · EPP RFC 5730 with xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" > and <element name="epp" type="epp:eppType"/>. > > > > No, the element name is fine, it’s the value of the “type” attribute that > is troublesome. The namespace prefix “epp" is really only designed to > prefix element & attribute names, not to be used inside the element content > or the attribute value. There aren’t any standards (afaik) that require a > standard off-the-shelf XML processor to make those prefix/URI mappings > available. > > > > For example, would you expect this to work? > > > > <something xmlns:foo="urn:ietf:params:xml:ns:epp-1.0”><element name="epp" > type=“foo:eppType”/> > > > > I mean, it’s probably OK, enough people do this that most XML software can > handle it. It’s just that as the designated XML pedant, I feel I should > point out departures from the letter of the standard. > > > > *[SAH] Tim, do you have a suggested solution? Would ‘type="emailType"’ > work? Sorry, I don’t have a parser handy to check.* > Unfortunately I don’t understand this application well enough to know what you’re trying to accomplish. In the attribute type=“epp:eppType” what function is the “epp:” prefix serving? What meaning does it have? Would epp:Type=“emailType” work as well? Because that’s what namespace prefixes are designed for. -T
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
