Given that the test suite event did not bother to create tests for
conformance checker (CC) related assertions, I have moved all
conformance checker assertions from the P&C Test Suite edition to a
new document [1].
Rationale for the move:
Firstly, the CC assertions are poorly specified - they don't actually
say why a CC needs to do something.
Secondly, the CC assertions as they currently appear are hard to test
(far too many SHOULDs and MAYs) and some are not precise enough.
Thirdly, we don't have anyone committing to implement the assertions,
which potentially delays the progression of this specification to Rec.
Moving the CC assertions to their own spec allows them to, obviously,
be standardized independently.
The CC assertions are important and deserve their own specification -
they also need to be done properly, with collaboration of
implementers.
I again ask the working group to endorse this move as we move P&C to PR.
[1] http://dev.w3.org/2006/waf/widgets-pc-cc/Overview.src.html
--
Marcos Caceres
http://datadriven.com.au