|
Hi XML Geeks, The rise of HTML5 is raising practical problems for XML developers that want to embrace it, mainly by the need of delivering “nice” user interfaces and take advantage of convenient features, like Web Components, but in
the other hand, handle HTML5 as trees, to do things like storing it on XML Databases. This is not a proposal, is just a re-post of a
dichotomy aroused in the eXist-db mailing list: how to parse non well-formed HTML5 created by no-xml aware developers (like third party libraries), with the aim of hearing your opinions about a possible solution (could
it be <?xml version=”1.2”?>). The main issues of contention are these three: 1.
Empty attributes (widely used in HTML5 like disabled become disabled="disabled" in XML) 2.
Script friendly handling of ampersand and angle brackets (Programmers don’t like to escape them when writing code). 3.
Empty elements no closed (like <link > instead of <link />) I want to hear your solutions, but I’ll also suggest these in my ignorance: 1.
Allow empty attributes in well-formed XML 2.
Allow non-escaped ampersands and angle brackets when enclosed in a parenthesis expression. 3.
Propose
a gentlemen's agreement to xml-haters
and convince them of the desirability of
a single / before closing an
empty element. As usual, we will be
happy to read
the enlighten opinions shared here, William David Velásquez Director de Investigación y Desarrollo Visión Tecnológica S.A.S. Tel (57 4) 444 7292 Movil (57) 311 709 8421 Follow me @williamda |