- From: Mark Birbeck <mark.birbeck@formsPlayer.com>
- Date: Tue, 29 Jan 2008 10:52:39 +0000
- To: "Ivan Herman" <ivan@w3.org>
- Cc: "Shane McCarron" <shane@aptest.com>, "Hausenblas, Michael" <michael.hausenblas@joanneum.at>, "Michael Bolger" <michael@michaelbolger.net>, RDFa <public-rdf-in-xhtml-tf@w3.org>, peter.krantz@gmail.com
Hi Ivan, > Well... my implementation starts with an XML parser, and does everything > on the resulting DOM tree. Ie, it will not work on an HTML+RDFa version > unless it is proper XML... > > :-( Right...but that's not because an HTML DOM is different to an XHTML DOM. The methods to obtain a list of children, to get attributes, not move up and down the tree, to get the text nodes...a lot of these methods are the same. However, that's not to say that this is the only way to do it. The HTML could also be pushed through Tidy and then treated as XML. I'm just saying that the 'processing model' as defined so far, is actually agnostic as to the type of DOM being used. (Even down to the use of @xmlns, in that this is processed just like any other attribute, and so works in my parser, even when the browser is running in HTML-mode.) Regards, Mark -- Mark Birbeck, formsPlayer mark.birbeck@formsPlayer.com | +44 (0) 20 7689 9232 http://www.formsPlayer.com | http://internet-apps.blogspot.com standards. innovation.
Received on Tuesday, 29 January 2008 10:52:53 UTC