...terms,
We describe the Prolog representations only. There exists others, e.g. in LISP.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...t104ageb7002e7199r1jpytransfer.
See [Alexandersson et al. (1997a),Auerswald (1997)] for more information on segment identifiers used in Verbmobil and the value ranges of their fields. Note that channels s and t are reserved for string and treebank input, repectively.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...specific.
See [Kasper et al. (2000),] for the concrete semantic representation classes used in Verbmobil. For information on the language specific semantic databases, see [Flickinger (2000),Kasper (2000),Shimada (2000)].
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...h[a-z][0-9]*
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...
The letter after the i encodes the producer of the instance symbol (c: chunk parser; d: dialogue summary; h: HPSG parser; k: context evaluation; r: robust semantics; s: statistical parser; t: transfer). For offline processing this information is optional. All this holds for label and hole symbols, too.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...table:
For the sort and dialogue act values and their relations, i.e. the semi-lattices, see Section gif and [Alexandersson et al. (1998)], respectively.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...properties:
Of course, all partners are free to use any other representations, e.g. lexicon extensions (see Appendix gif), within their components.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...VIT.
The original version of this checker was developed by Michael Schiehlen.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...information.
For hackers: all Prolog predicates used in Code are defined in either vitBasicTypes.pl or vitValues.pl and can be seen in the on-line lexicon vitSemLex.pl (see Appendix gif).
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...groupings.
The original version of this pretty-printer was developed by Michael Schiehlen.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...hierarchy.
Note that anything is not a valid sort value within a VIT, i.e. the checker will raise an error if the value of a sort is equivalent to anything. The same holds for the most general dialogue act value, called dialog_act. Hence, in both cases, this information should be left out if no more specific values can be inferred locally.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...too.
See vitHierarchy.pl for the code.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...databases.
The +-signs marking separable prefixes/particles in ths original databases are removed in the on-line version.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Michael Dorna , VM Report 238, 5/18/2000