OWL Test Case Editor 
Instructions
====================

Having installed the editor, running it is as follows:

1: start tomcat
2: view the editors draft
    http://localhost:8080/wowg/jsp/main.jsp
3: start the editor
    http://localhost:8080/wowg/jsp/edit.jsp 
or
4: select specific tests to view using
    http://localhost:8080/wowg/jsp/select.html

In more detail:
1: start tomcat
Change to the directory
  $tomcat/bin
and either run
  ./startup.sh
or
  ./startup.bat

To stop tomcat you run either
  ./shutdown.sh
or
  ./shutdown.bat


2: open a browser and enter the URL
   get a cup of coffee
  (Tomcat reads nearly all the files under WWW,
   and keeps them in memory.
   It will detect some changes on the disk
   so reloading should enable you to see 
   changes you have saved.
   You may need to stop and restart tomcat
   for some changes to be detected.)
   (Note: there is still old code that
   can go look at http://www.w3.org/ for
   the files - this proved too slow.
   If you finish your cup of coffee and
   it hasn't finished, there is probably a
   configuration error).

3: Two editing tasks are
   A: creating a new test
   B: revising an old test

A:
  The editor allows you to 
  - specify which test you are creating
  - enter the test metadata
  - enter the test as RDF/XML
  - validate your RDF/XML
  - zip up the results

A.1: which test
  Tests are classifed either by langauge feature
  or if no feature by issue
  or if no feature or issue in one of the sections
    Miscellaneous
    Extra-Credit
    DL

  Using the drop down list 
  select a feature (if appropriate)
        an issue  (if appropriate)
  or check one of the three named sections
  NB: in the latter cases the feature drop down list
  MUST read "no feature"; in the last case the issue
  drop down list MUST read "no issue".

  Having checked DL say, you then need to
  subclassify the test.
  If the drop down list under the check box
  contains an appropriate subclassification then use that,
  otherwise do both:
  - enter a new subclassification name (no spaces - must be
    a valid XHTML fragment ID)
  - choose a start-test number (000 to 900)
    This start-test number must be unused by other
    subclassifications of DL.

  Having got this far, you now choose a test number, this is
  from 01 to 20 in another drop down list.

  The actual test number is either 0MM for feature or issue
  tests, or, for the Misc/DL/extra tests the first digit is
  determined by either the subclassification chosen from
  or the start-test drop-down list (for a new subsection tag).
 
  At this stage, it is best to click on the Refresh button, which
  should produce an error message indicating the test was not found.
  If it was found, then you need to use a different number.

A.2 Enter the test metadata
  Enter the author either through the list, if you have already
  contributed a test, or by typing in your name.

  Do not enter an approval URL - since this is a proposed test.

  Choose the type of test being created.
  At this stage the boiler plate button may be useful.

  During this stage or the next you must specify the level
  of any entailment, and the syntactic categorization of
  any file created.

  The editor only supports one or two file tests.
  Complex imports tests are not supported in the editor.

A.3: Enter the test data in the large text areas

A.4: Press the validate button, read any error messages,
     and fix them.

A.5: Press the zip button.
     The returned file is a zip file, whatever your browser says.
     This can be unpacked in WWW/2002/03owlt and all the files
     will be in the right place.
     If you are happy with the results either
     - commit them in CVS, and then modify the permissions
       at www.w3.org to make them world readable
     or
     - e-mail the zip to one of the editors.