W3C home > Mailing lists > Public > public-rif-wg@w3.org > May 2009

Re: Two issues with RIF-Core

From: Dave Reynolds <der@hplb.hpl.hp.com>
Date: Wed, 13 May 2009 09:14:37 +0100
Message-ID: <4A0A816D.8040302@hplb.hpl.hp.com>
To: Christian De Sainte Marie <csma@fr.ibm.com>
CC: Gary Hallmark <gary.hallmark@gmail.com>, RIF WG <public-rif-wg@w3.org>, Sandro Hawke <sandro@w3.org>
Christian De Sainte Marie wrote:
> 
> ********* NOTICE **********
> My new email address at IBM is: csma@fr.ibm.com
> My ILOG email address will not be forwarded after June 8
> *****************************
> 
> Dave,
> 
> Dave Reynolds wrote on 10/05/2009 11:02:34:
>  >
>  > Gary Hallmark wrote:
>  > > ok, I can implement quantification over property names using Java
>  > > reflection, so how about
>  > >
>  > > Frame ::= TERM '[' ((Const|Var) '->'  TERM)* ']'
>  >
>  > That doesn't help you because you can still do things like:
>  >
>  > [...]
>  >
>  > To restrict the types of things that can be slot names that would have
>  > to go in the semantics rather than the syntax (that was my error in my
>  > too-quick-reply). E.g. restrict the domain of Iframe to be
>  > SetOfFiniteBags((Dind - Dlist) x Dind)
> 
> Wouldn't an additional condition in the definition of the context of a 
> symbol do what Gary wants?

No that's still a syntactic notion. We need to continue allow variables 
in the slot positions and we have no syntactic means to restrict the 
types of variables.

Dave
-- 
Hewlett-Packard Limited
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England
Received on Wednesday, 13 May 2009 08:15:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:34:08 GMT