Maciej Katafiasz <[email protected]> writes: > but then the problem is that Stephen's work is based on CXML, and not > closure-html. Stephen, why exactly is that? The problem is that > weblocks does not output XHTML[*] but HTML, and browsers see it as > such. Thus it should be parsed by a HTML parser.
Yes, Weblocks sends HTML instead of XHTML, and browsers will parse the output with an HTML parser rather than an XML parser. But as far as I'm concerned, if it looks like XML, walks like XML, and quacks like XML, it's XML. The reason for my choice is that unifying XML is more generally useful than unifying HTML. In particular, it can be used as a replacement for accessing the DOM API directly in XML-using applications, which can be quite tedious when you're trying to extract information from a complex document, or build a document. Scraping and constructing HTML is certainly useful, but it is only one use, and the transform between general HTML to XHTML is well-understood, whereas transforming general non-XHTML XML to HTML is not. What remains of cxml unification is to write LIFT unit tests, and the WHO-compatible input syntax, without which constructing template DOM trees is quite tedious. -- Sorry but you say Nibiru is a Hoax? Doesnt Exist? So maybe The Sumerian people doesnt exist also! --Anonymous by way of SkI --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
