Ian Hickson: > Indeed. I've already received requests from various people to make an > "HTML5" version of XBL that has its own custom format and custom parser > with defined error handling instead of using XML. The main reason for not > doing it is that a custom parser is a high implementation burden and a > high specification burden -- having written the HTML5 parsing algorithm, I > have no intention of doing it again if I can avoid it. > > However, this doesn't apply to xml:id, since the implementation burden for > supporting 'id' instead of 'xml:id' is negligible (and even possibly > lower, since you don't have to worry about what happens if someone sets > 'xml:id' on an element in SVG, HTML, or MathML and thus gives an element > _two_ IDs), and the specification burden is about one line of prose.
Note that due to DOM 3 Core’s Element.setIdAttribute, implementations need to handle multiple IDs on elements anyway. -- Cameron McCormack, http://mcc.id.au/ xmpp:[EMAIL PROTECTED] ▪ ICQ 26955922 ▪ MSN [EMAIL PROTECTED]
