> do a second LC -- If nothing else tests for QCRs would have to be > added to the Test document. It would be a mistake to release Test as > LC now if we know it is going to change with a new feature that > requires new tests and changes old ones. My understanding is that this is likely. For instance, we may well change the status of owl:Nothing before moving test to last call. I am currently imagining a "status of this document" which explicitly links the status of the test last call working draft to the other last call working drafts and notes that post-last call decisions may impact some tests. I would be happy to list the decisions in an appendix. Test will never be ready if the WG insists on it hitting a moving target. JeremyReceived on Monday, 28 April 2003 08:59:48 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:40 GMT