- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Sun, 29 Nov 2009 17:12:50 -0500
- To: RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>
There have been a number of Test Suite updates over the last two days that affect approved and unapproved TCs: http://github.com/msporny/rdfa-test-suite/commits/master We had not been testing for the "first" reserved word in @rel/@rev. TCs 77 and 87 have been updated to include a test for the reserved word. These tests are effectively our "reserved words" tests, so they should have included "first" and not having it in there was an oversight that has been corrected. If somebody could double-check that those tests are still valid, and that I didn't mess anything up, that would be great. http://github.com/msporny/rdfa-test-suite/commit/f6f7727bb3cf769b9c830ac88d8354e590e70f4f TC115 had two issues. The first was an issue that would occur on SAX-based processors that did not have access to the raw byte stream and thus wouldn't be able to tell if the encoded "<strong>" value should be interpreted as an XML Literal or not. The checking logs contain a bit more information about the change: http://github.com/msporny/rdfa-test-suite/commit/bfc4e3a6bc65ab67d73faa3b8d45f1f05e802293 http://github.com/msporny/rdfa-test-suite/commit/a27e4f4500a854024b0e3914af13f6227d54d805 http://github.com/msporny/rdfa-test-suite/commit/5e46f13b43a3e84e4e0ea15ebd297f9a88a4c3b8 TC 158 was merged with TC 164. TCs 147, 160, 162 and 164 were approved: http://github.com/msporny/rdfa-test-suite/commit/bda9555239ee85d9066a54f70f17b249fd6b07fa TC 142 and TC 154 have been moved to "On Hold" status. We need to discuss an implementation issue with TC 142. LibXML (which has very broad distribution - it's the Gnome projects XML library) currently has a bug where it won't pass the xmlns:xml prefix to the RDFa processor. This is an issue in Gregg Kellogg's Ruby RDFa parser and will certainly be an issue in other parsers that use LibXML... we need to have somebody contact that community and find out why they're not passing xmlns:xml, and if it is a bug, ask them to correct the issue. TC 154 contains an invalid XML character per XML 4th edition rules. We need to decide how this will affect the graph that is generated and produce some errata text to formalize the behavior. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) President/CEO - Digital Bazaar, Inc. blog: Establishing an Open Digital Media Commerce Standard http://blog.digitalbazaar.com/2009/09/28/a-digital-content-commerce-standard/
Received on Sunday, 29 November 2009 22:13:27 UTC