- From: Michael Kifer <kifer@cs.sunysb.edu>
- Date: Mon, 17 Nov 2008 16:46:40 -0500
- To: "Adrian Paschke" <adrian.paschke@gmx.de>
- Cc: <cleo@us.ibm.com>, <gary.hallmark@oracle.com>, <Harold.Boley@nrc-cnrc.gc.ca>, <kifer@cs.stonybrook.edu>, <public-rif-wg@w3.org>
On Mon, 17 Nov 2008 22:18:45 +0100 "Adrian Paschke" <adrian.paschke@gmx.de> wrote: > >What is ?Date = ex:Date[...] and so on? Did you mean # instead of =? > >Unfortunately even ?Date#ex:Date[...] is not allowed and must be written > >as And(?Date#ex:Date ?Date[...]). > > > It means, that the frame object is bound to a variable which is then used in > the value position of a frame slot. It was intended to be a work-around > solution to allow complex frames as values of frame slots. Adrian, ?Date = ex:Date[...] is still nesting, and isn't allowed. But why would you do something like this in the first place? Why don't you use function terms with named arguments? This is all you need. michael > Do you see another solution to allow slot values which are complex?
Received on Monday, 17 November 2008 21:47:23 UTC