ISSUE-73: Should Core support the membership and subclass syntax and semantics?

Membership/subclass in Core?

Should Core support the membership and subclass syntax and semantics?

State:

CLOSED

Product:

Core

Raised by:

Dave Reynolds

Opened on:

2008-08-21

Description:

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)?

Related Actions Items:

No related actions

Related emails:

1. Re: ISSUE-73 (Membership/subclass in Core?): Should Core support the membership and subclass syntax and semantics? [Core] (from der@hplb.hpl.hp.com on 2008-08-21)
2. Re: ISSUE-73 (Membership/subclass in Core?): Should Core support the membership and subclass syntax and semantics? [Core] (from cawelty@gmail.com on 2008-08-21)
3. ISSUE-73 (Membership/subclass in Core?): Should Core support the membership and subclass syntax and semantics? [Core] (from sysbot+tracker@w3.org on 2008-08-21)

Related notes:

Display change log