[RIF-test] RIF test cases

For next week's call, we have the following discussion points:

 1.  Time frame for completion of test cases & document?

 2.  Review our current approach
           We'll focus first on accumulating BLD test cases in basic form
           (similar to OWL, i.e. metadata, input, expected result) that 
directly
           captures the test case requirement,  and may be easiest for 
humans
           to read/write. This won't preclude us from later defining a 
layer on top of
           that to facilitate the implementation of test harnesses by 
specific rule
           systems. This layer would include things like Adrian's test 
query
           interfaces,  and extra metadata. 

 3.  Test metadata:
            In separate RDF manifest file, or RIF metadata embedded in one 
of 
            the test files?

           Advantages of embedded RIF metadata
                   -  we've defined a metadata format, so we should use 
that one.
                   -  one less file in the test case
                   -  can see the metadata information at the same time as 

                      looking at the content of one of the test files.
                  - ...??

            Advantages of separate RDF manifest file:
                  -  easy for human reader to get an overview of the test 
by looking
                     at just that file
                  -  manifests for individual tests can be easily merged 
into one overall
                     file for machine processing of the test suite
                  - existing tools for RDF might be useful?
                  - ...??

 4.  Submission process
          People can use the wiki  (instructions at the end of this email)
 
         We'll look at modifiying the OWL test case editor, if it would be 
helpful.
 
          If people feel inhibited by the wiki interface,  or by having to 

          put the case in completely correct PS format, they can post
          test cases by email in informal format.


 5.   Format of test cases
           proposed:  PS (presentation syntax) used for submissions and 
for 
           informative copies of test cases. XML is the normative form of 
the test
           case.

 6.   Review current test cases
           http://www.w3.org/2005/rules/wiki/Category:Test_Case


 7.   We would like to get a CVS repository set up for RIF test cases, 
like
        http://www.w3.org/2002/03owlt/


-TCG


Steps to submit test cases on the WIKI at  
http://www.w3.org/2005/rules/wiki/Category:Test_Case

1.  To create a new test case type in a new unused WIKI URL such as 
http://www.w3.org/2005/rules/wiki/Test_Case_[Name of Test Case]
and edit the page (you must be logged in).

2.  Write your test case unsing one of the existing templates for test 
cases. Currently there are two templates

- A template for positive entailment tests consisting of premises and 
conclusion(s)
http://www.w3.org/2005/rules/wiki/Template:PositiveEntailmentTest
- A template for positive syntax tests consisting of a valid RIF rule set 
example
http://www.w3.org/2005/rules/wiki/Template:PositiveSyntaxTest

To write a test case, the easiest way is to simply copy and paste the 
sources of an existing test case (edit an existing test case) to your new 
test case and change the fields. An example can be found here 
http://www.w3.org/2005/rules/wiki/Test_Case_Example

Your new test case will be automatically classified into the category of 
the template which you have used and the category of the dialect, which 
you have specified in your test case, e.g. Core, BLD, PRD.

3.  It is possible to define new templates for test cases. You might take 
a look at  the sources of the existing templates (edit the template) and 
the description of their properties at 
http://www.w3.org/2005/rules/wiki/Test_Case_Format