Review policy and practice ideas

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

The following ideas were captured regarding review policy and practice:

  1 - judge the eligibility of a test by:
      - accuracy of test
      - scope of test
      - clarity of test
      - clarity of aspect of recommendation being tested
      - should/shall use in the recommendation
        - is the test testing a discretionary item?
      - atomic/molecular nature of the test

  2 - judge each eligible test through a process
      - run thorugh multiple processors
        - any differences imply examination by committee
        - consensus opinion to accept the test, reject the test, or defer 
deciding on the test while the issue is forwarded to the W3C for clarification
        - possible actions:
          - reject test and update errata and errata exclusion
          - reject comment with advice to go to W3C if the submitter is not 
convinced
          - forward to W3C for clarification
      - accommodate external comment from the community at large
        - committee publishes consensus opinion of response to comment with 
justification from Recommendation (not just precedence of how a processor 
has acted)

  3 - game plan for tests
      - a member will report to the list the hierarchy of tests undertaken 
for comparison with multiple processors
      - tally of tests will tracked on a visible web page for the committee
      - members report that all tests in a given hierarchy have been 
examined, incl. a summary of findings of tests not to be included in the 
resulting suite
      - a given hierarchy is not considered complete until reports from at 
least two members have been submitted

  4 - public review
      - initial suite of a very small set of files will be used to test 
procedures and scripts and stylesheets
      - committee will publish draft work periodically, starting with very 
small set
      - committee will solicit comments on usability of the product
      - committee will publish a disposition of comments
      - committee progresses on the testing of files until all hierarchies 
covered


.................... Ken

--
G. Ken Holman                      mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.               http://www.CraneSoftwrights.com/m/
Box 266, Kars, Ontario CANADA K0A-2E0     +1(613)489-0999   (Fax:-0995)
Web site:     XSL/XML/DSSSL/SGML/OmniMark services, training, products.
Book:  Practical Transformation Using XSLT and XPath ISBN 1-894049-06-3
Article: What is XSLT? http://www.xml.com/pub/2000/08/holman/index.html
Next public instructor-led training:  2001-03-04,2001-03-05,2001-03-06,
-    2001-03-07,2001-03-21,2001-04-06,2001-05-01,2001-05-14,2001-05-15,
-     2001-05-16,2001-05-17,2001-05-21,2001-05-22,2001-07-20,2001-09-19