[developers] variable type mapping as part of VPM

Stephan Oepen oe at ifi.uio.no
Thu Aug 7 16:44:05 CEST 2008


hi zhang yi,

i am about to check in changes to the (Lisp) VPM code, to finally have
the mappings from grammar-internal to MRS variables be part of the VPM
too (such that, among other things, the mapping can be bidirectional).
adding these to the ERG `semi.vpm' (see attachment), cheap complains:

  Invalid line while reading vpm.

the intention is that variable type mappings take the same form as the
variable property mappings, but they occur outside a block of property
name correspondencnes, i.e. before any X : Y statements.

conceptually, this extension of the VPM makes the following obsolete, i
believe:

  mrs-event-type := event.
  mrs-event-or-index-type := individual.
  mrs-deg-ind-type := deg-ind.
  mrs-non-expl-ind-type := non_expl-ind.
  mrs-handle-type := handle.
  mrs-ref-ind-type := ref-ind.
  mrs-non-event-type := non_event.

in the LKB, the old way of mapping variable types will remain available
(for backwards compatibility, at least for some time), but for PET i am
tempted to suggest we build the new MRS code without such legacy (other
than the ERG, no grammars support native MRS mode in PET yet, i think)?

either way, would you have time to extend the PET VPM implementation?

                                                   best wishes  -  oe

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++ Universitetet i Oslo (IFI); Boks 1080 Blindern; 0316 Oslo; (+47) 2284 0125
+++     CSLI Stanford; Ventura Hall; Stanford, CA 94305; (+1 650) 723 0515
+++       --- oe at ifi.uio.no; oe at csli.stanford.edu; stephan at oepen.net ---
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

-------------- next part --------------
A non-text attachment was scrubbed...
Name: semi.vpm
Type: application/octet-stream
Size: 3144 bytes
Desc: not available
URL: <http://lists.delph-in.net/archives/developers/attachments/20080807/98b50374/attachment.obj>


More information about the developers mailing list