[Image] [Image] [Image] [Image]
Next: Theory file Up: Format specifications Previous: Format specifications

Overview

  1. DATR Theory File: mytheory.dtr, the input to the tokenizer.
  2. DATR Token File: mytheory.dtr.tok, the output of the tokenizer and input to the inference engine.
  3. Query File: mytheory.qry (recommended extension), a simple list of specific queries for the inference engine.
  4. Batch query declaration File: mytheory.dec (recommended extension), containing declarations of query macros with the DATR query directives #show and #hide. These two macros are enhanced by two further directives:

    1. A convention for conditional querying, mentioned in the RFC 2.0, in order to avoid the need to keep different attribute path systems in different theories:
      #showif Node:<path> = value Node:<path> = value ... .
    2. A convention for specifying individual queries to a theory: #query Node:<path> = value ... .

    There are, however, two techniques for handling query declarations:

    1. As described above, in a separate declaration file for which the extension *.dec is recommended, e.g. for mytheory.dtr in a corresponding file mytheory.dec. This file must be specified with the command line option -D when invoking zdatr or zdatrinf for batch processing.
    2. In conventional style inside the DATR theory file, or in a file to be read as a macro with the #load directive. In this case, query declarations in a file mytheory.dtr are automatically placed in a file mytheory.dtr.dec and can be used for batch querying with the command line option -d.
  5. Log File: mytheory.dtr.log and mytheory.dtr.tok.log, documenting zdatrtok and zdatrinf status messages and performance statistics.



© Dafydd Gibbon Sun Sep 13 17:17:46 MET DST 1998