dear all,<br>
<br>
in a former life, we had a BSCW workspace for PET, where emily<br>
once posted a very relevant message. i am about to shut down<br>
the PET workspace, hence forward emily's message below (and<br>
will do the same for a few more messages).<br>
<br>
all best, oe<br>
<br>
======= 17-aug-04 posting by emily =======<br>
<br>
Hello,<br>
<br>
The past few months have seen a two minor extensions<br>
to tdl as accepted by the LKB:<br>
<br>
-- Documentation strings, enclosed in " ", in<br>
the first line after the parents. (Types only)<br>
<br>
-- Type addenda statements, signalled by :+ (instead<br>
of :=) which allow users to (monotonically) add<br>
information to previously defined types: additional<br>
parents, additional constraints, and/or additional<br>
documentation strings.<br>
<br>
In BNF, the revisions look like this:<br>
<br>
Avm-def -> := Conjunction | Comment Conjunction<br>
Comment -> " string "<br>
<br>
Type-addendum -> Type Avm-addendum .<br>
Avm-addendum -> :+ Parents Conjunction | Parents Comment
<pre> Conjunction | Parents | Parents Comment |<br> Comment Conjunction | Comment |<br> Conjunction</pre>
The motivation for the type addendum is from<br>
the Grammar Matrix. I hope to soon define modules<br>
for, say, basic word order, in which I'll be defining<br>
types that I expect grammar writers to want to add<br>
to. Defining a subtype to bear the additional<br>
constraints is not always an option, and overwriting<br>
the existing Matrix type with a new type containing<br>
the original info plus the new constraints is<br>
a) hacky and b) bad news for distributing Matrix<br>
updates.<br>
<br>
The documentation strings should eventually be<br>
browseable within the LKB, and we intend (someday :-)<br>
to document the Matrix in this way.<br>
<br>
The purpose of this note is to request that these<br>
extensions be considered for inclusion in PET (flop)<br>
as well.<br>
<br>
Thanks,
<br>
Emily