Mark Birbeck wrote:
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.


Ah, o.k. Great.

I must publicly admit that I have never ever worked with the HTML DOM (as opposed to the XHTML DOM; I try to keep away from javascript whenever I can:-), so...

Ivan

(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


--

Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to