Here are answer to some of your questions:
> There are a couple of places in the presentation model MRL which depend
> upon expressions. But we haven't come to terms on what those are yet
> syntactically. Do you want the modified presentation model less these?
>
Let's for now declare an object type called Expression, with no attributes,
and use it everywhere where expressions are explicitly mentioned in the MRL.
> Also, the presentation model MRL uses a Type_Bool. There is no Type_Bool
> in the Type_Code in my version of the API. I'm assuming that's an oversight
> in the API manual and am adding a Bool to the MRL syntax. Let me know if
> this is incorrect.
>
Yes, we need a Bool. I think this was an oversight, but I'll let Ewald
comment on this one.
> Also also :-) the Object Parameter now stores value as a Float with a comment
> that it should be an Any. Now that we have Any in the syntax, should I
> make that the type of Parameter.value?
>
Yes, use Any.
Pedro Szekely
USC/ISI, 4676 Admiralty Way, Marina del Rey, CA 90292
Phone: 310/822-1511, Fax: 310/823-6714
URL: http://www.isi.edu/isd/szekely.html