- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 18 Feb 2009 15:16:38 +0100
- To: Henri Sivonen <hsivonen@iki.fi>
- CC: Mark Birbeck <mark.birbeck@webbackplane.com>, Ben Adida <ben@adida.net>, Karl Dubost <karl@la-grange.net>, Sam Ruby <rubys@intertwingly.net>, Kingsley Idehen <kidehen@openlinksw.com>, Dan Brickley <danbri@danbri.org>, Michael Bolger <michael@michaelbolger.net>, public-rdfa@w3.org, RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>, Tim Berners-Lee <timbl@w3.org>, Dan Connolly <connolly@w3.org>, Ian Hickson <ian@hixie.ch>
Henri Sivonen wrote: > On Feb 18, 2009, at 15:21, Julian Reschke wrote: > >> I still do not understand the nature of the problem. >> >> If you are in a namespace-aware environment (such as XOM, or something >> using the XPath data model, such as XSLT), then use the supplied XML >> namespace information. > > > While HTML5 parsing as defined today supplies namespace information for > each element and attribute name, it doesn't supply xmlns:foo-based > namespace mapping context for resolving prefixes in attribute content on > the application layer. > > Changing HTML5 parsing to supply this context would mean a parsing-level > change for the benefit of RDFa. None of the features drafted HTML 5 so > far need this. I was trying to understand your comments with respect to parsing RDFa in a XOM instance. As far as I can tell, what you're saying is: if I plug my HTML5 SAX parser into XOM, and feed it with HTML5 text/html containing xmlns:* attributes, it's not going to work. This seems to be caused by the fact that XOM expects namespace mapping events, and the parser is not supplying them. So this is either a bug in the parser, or a bug in the way it is integrated into XOM. If your point was: there are cases where *today* existing components plugged together cause RDFa not to work, then yes, that's probably true. I'm pretty sure this is also true for many many other things in the specs we're working on. BR, Julian
Received on Wednesday, 18 February 2009 14:17:27 UTC