W3C home > Mailing lists > Public > public-rif-wg@w3.org > August 2008

ISSUE-73 (Membership/subclass in Core?): Should Core support the membership and subclass syntax and semantics? [Core]

From: Rule Interchange Format Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 21 Aug 2008 12:35:05 +0000 (GMT)
To: public-rif-wg@w3.org
Message-Id: <20080821123505.CA2996B63D@kent.w3.org>


ISSUE-73 (Membership/subclass in Core?): Should Core support the membership and subclass syntax and semantics? [Core]

http://www.w3.org/2005/rules/wg/track/issues/73

Raised by: Dave Reynolds
On product: Core

We've previously suggested membership and subclass be omitted form CORE on the grounds that CORE is minimal and those can regarded as largely syntactic sugar.

Many PR systems have a notion of object with a type and class hierarchy and so there is some support for member and subclass in PRD which suggests they should be in Core. However, since such systems often can't support assertion of membership or subclass relations, only query of it, then PRD currently doesn't permits rules to conclude (assert) a member or subclass relation.  

So the maximal intersection of BLD and PRD would only permit query not derivation of these properties. Such a limitation complicates the presentation of Core and restricts implementations of Core from using them to export type relations which don't meet those constraints. 

Should we err on the side of simplicity (just leave them out) or maximal intersection (include them along with constraints on usage)?
Received on Thursday, 21 August 2008 12:35:42 GMT

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