- From: Ivan Herman <ivan@w3.org>
- Date: Thu, 19 Jan 2012 06:18:00 +0100
- To: RDF Web Applications Working Group WG <public-rdfa-wg@w3.org>
- Cc: "public-rdfa-wg@w3.org" <public-rdfa-wg@w3.org>
As far as I know (and this is also Mike's argument), HTML5 explicitly disallows xmlns: and RDFa+HTML5 is an extension of the core HTML5. This means that the usage of xmlns: in there is an error. Ie, my answer to the question is: yes. Ivan ---- Ivan Herman Tel:+31 641044153 http://www.ivan-herman.net On 19 Jan 2012, at 06:12, RDF Web Applications Working Group Issue Tracker <sysbot+tracker@w3.org> wrote: > > ISSUE-126 (HTML5+RDFa conformance): Can use of xmlns: be reported as an error for HTML5+RDFa 1.1? [RDFa 1.1 in HTML5] > > http://www.w3.org/2010/02/rdfa/track/issues/126 > > Raised by: Manu Sporny > On product: RDFa 1.1 in HTML5 > > This issue was raised by Michael(tm) Smith: > > He was working on the new validator code for W3C and said that getting xmlns: support into the HTML5 validator was going to be a fairly large undertaking. Additionally, we're the only ones that override the HTML5 spec to add xmlns: support, even though we have deprecated it's usage. Mike would like to see the following text: > > "Conformance checkers must accept attribute names that have a case insensitive prefix matching "xmlns:" as conforming. Conformance checkers should generate warnings noting that the use of xmlns: is deprecated." > > to this (for HTML5+RDFa): > > "Conformance checkers may report the use of xmlns: as an error." > > >
Received on Thursday, 19 January 2012 05:16:45 UTC