MUD HyprLex Testbed Interface

Minimal UNIX DATR: HyprLex Testbed Interface

Dafydd Gibbon, U Bielefeld, 31 Dec 1995


BROWSE: engcomp.dtr
fatwife6.dtr
katja2.dtr
manual.dtr
schmitt.dtr
syntax3.dtr
engcomp.dec
fatwife6.dec
fwcomp.dec
fwderi.dec
fwsimp.dec
katja2.dec
schmitt.dec
schmitt.qry
syntax.qry
SELECT FILES:
MANUAL QUERY (expandable box):
INPUT TYPE:
OUTPUT OPTIONS:
OPERATE:
These applications use HTML3 and Netscape extensions and may not be rendered satisfactorily by other browsers. DATR theories with complex inferences, or long query lists may trigger the time-out function and return an empty data file (this may have other causes, however). If a time-out occurs, check the last entry in the Result Buffer Log.

Further information on the DATR formalism and the ILEX lexicon model:
  1. The DATR ScratchPad.
  2. Various specification documents.
  3. A collection of DATR theories which have not been tested with the HyprLex interface.
  4. An authoritative definition of the DATR language see Evans & Gazdar 1995, in Computational Linguistics.
  5. Brief class notes on lexical modelling: "Lexical Syntax in ILEX/DATR".
  6. The Slides of my talk on "DATR theories or DATR models?" (original title: "DATR theories or DATR programmes?") at the DGfS Annual Conference 1995, on a related topic.
Further information on MUD-HyprLex:
  1. This is an experimental system and is subject to change without notice in respect of specifications and performance. Please do not use the Update or Upload functions or you may get lost in hyperspace.
  2. This HyprLex application presupposes a working knowledge of DATR
  3. MUD-HyprLex is a UNIX tool (approx. 1200 code lines) for interpreting standard DATR queries, query declarations (show/hide), and theories. MUD is the Minimal UNIX DATR interpreter, and HyprLex is the interactive HTML 3 based lexicon interface.
  4. Quoted atoms and enhancements such as variables are not currently supported, though atom and node declarations may be used.
  5. The tool is not optimised for performance. Consequently, long query lists take time.
  6. Currently, full syntax checking is not included.
  7. The trace function is extremely verbose, and should therefore be used with great care in order to avoid generating huge files. It should preferably only be used with manual input.
  8. Basic statistics and action information are included in DATR comment lines as a header. Comment lines also precede theorems generated by show/hide declarations and theorems generated by lists.
  9. Manual entries are treated internally like lists. The last manual query is stored in the file manual.qry and may be browsed and selected like other query lists.
  10. The call "mud notrace nocrunch theorem ..." generates a subset of the lexical closure which is also a DATR theory and can also be processed by mud. Repeated processing yields character identical files, except for comments and empty lines.

HyprLex interface generated with mud2html on text/plain Aug 24 DST
Dafydd Gibbon