I have assembled a very preliminary Editor's Draft for MicroXML. It is about 20 pages long, and covers for MicroXML what is covered by XML 1.0 (Fifth Edition), Namespaces in XML 1.0 (Third Edition), XML Infoset (Second Edition), Namespaces in XML 1.0 (Third Edition), xml:id 1.0, and XML Base (Second Edition), which total about 82 pages.
It still needs formal normative references, and there are a few open issues listed in section 10. Comments and corrections are earnestly solicited either in comments here or in email.
4 comments:
2.7 Names:
Note that COLON, ... are explicitly permitted.
That appears to be both strange and false.
1 Introduction
This argument applied to SGML would imply...
Which argument? It's implicit in the previous paragraphs but referring to it so directly without actually stating it looks very odd.
2.2 Elements
For compatibility, an empty element whose name is br SHOULD be expressed
with an empty-tag.
Even if it's a short for "branch" in my language describing a version control repository?
If you do want it to be compatible with an HTML br element aren't you supposed to leave a space between the "r" and the "/"?
Ed Davies:
COLON removed, SGML remark reworded, and thanks.
Unless you use namespaces, MicroXML doesn't know if something is HTML5 or not. In any case, it's a SHOULD, which means that you can override it if you have a reason to, specifically if you don't care about compatibility.
Please keep the comments coming!
Post a Comment