- From: Gregg Kellogg <gregg@kellogg-assoc.com>
- Date: Fri, 9 Mar 2012 10:21:13 -0500
- To: Ivan Herman <ivan@w3.org>
- CC: Manu Sporny <msporny@digitalbazaar.com>, W3C RDFWA WG <public-rdfa-wg@w3.org>
On Mar 9, 2012, at 8:09 AM, "Ivan Herman" <ivan@w3.org> wrote: > Guys, > > having successfully passed the tests with XHTML1+RDFa, I am now HTML5+RDFa. > > One issue there is test 236: > > <!DOCTYPE html> > <html > > <head> > <title>Test 0236</title> > </head> > <body which is not closed should generate a processor error > </html> > > The problem, in HTML5, that the HTML5 parser (at least the one I use) does not generate any errors, just closes the body element in the DOM tree and returns an, essentially, empty DOM. Ie, no error is generated. > > I think we run into the issue of when would an HTML5 go through the lax process of HTML5, which we should, for the purpose of HTML5, keep away from in my view. I would propose NOT to include this test for HTML5 (ie, modify the manifest). The XHTML1 is clear in this respect, and tests the RDFa processor which is the goal after all. The purpose of this test is to show that a processor generates an rdfa:Error when it detects a malformed document. If a processor can do this with XHTML I think that's sufficient. As fas as I'm concerned, we can remove it for HTML4 & HTML5. Gregg > Ivan > > ---- > Ivan Herman, W3C Semantic Web Activity Lead > Home: http://www.w3.org/People/Ivan/ > mobile: +31-641044153 > FOAF: http://www.ivan-herman.net/foaf.rdf > > > > >
Received on Friday, 9 March 2012 15:22:22 UTC