Draft on IDN Tables in XML
kim.davies at icann.org
Thu Mar 1 23:12:10 CET 2012
On Mar 1, 2012, at 12:21 PM, Thomas Roessler wrote:
A few quick comments on the XML format level upon skimming this (mostly nit-picking):
- you don't seem to identify the namespace URI in the normative text, it's hidden in the RNG schema
- you don't use the namespace in your examples.
- the example in 3.4 doesn't follow the specification for the description element: You either need a CDATA construct, or you need to entity-escape the pointy brackets.
- in the specification for the description element, don't talk of "CDATA" as an element. It isn't, but rather a particular way to mark up textual data:
So: The content model for <description> is text; if content includes markup, then CDATA is a convenient method to write that out.
- MIME-type -> media type
All great fixes I'll work into the next revision.
- To the unique identifier point in your issues list -- agree that it might be useful to give the table a unique identifier. I probably wouldn't choose an ID attribute, but would include a "this version" and "latest version" URI in the <meta> section.
Sounds good to me.
- I may be missing something, but what's the extension model for the @when attribute on <var>? Are certain names there reserved for IANA, and others up for grabs? Want to use URIs for these names, so everybody can coin their own without stepping on others' toes? Something else?
Good points, the mechanism for specifying "when" attributes is undefined right now. Right now I know to implement some tables we need to support context in Arabic script strings. I don't know if it is knowable in advance all the types of contextual modes that will need to be supported. If we assume they can not be, then I agree there needs to be a mechanism to keep track of them so the format doesn't extend in competing directions and lose its utility.
Hope these are useful,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Idna-update