ISSUE-43: Subclass relationship ## in RIF-BLD [CP]

Subclass relationship ## in RIF-BLD [CP]

State:
CLOSED
Product:
Technical Design (multiple dialects/documents)
Raised by:
Michael Kifer
Opened on:
2007-10-16
Description:
Objections have been raised to the inclusion of the subclass relationship,
a##b, in RIF-BLD on the grounds that it duplicates rdfs:subclassOf.

Defenders of this relationship state that:

1. Subclass relationship is a common and very basic concept of any
object-oriented/frame representation, and frame representation requirement
is in the Charter.

2. The rdfs:subclassOf relationship is not a standard subclassOf relationship.
Using it instead of ## introduces additional axioms into the semantics,
which are not supported by standard object-oriented languages.

3. Not including ## in the language means that systems like FLORA-2,
Ontobroker, FLORID, etc. must invent a new dialect to exchange their
Horn subsets just because ## is not included.

4. Excluding this construct precludes us from stating simple things like
bar##foo (i.e., bar is a subclass of foo) without carrying the baggage
of the additional axioms of rdfs:subclassOf.

5. ## does not preclude the use of rdfs:subclassOf for languages that want
to use RDFS\' notion of subclass.
Related Actions Items:
No related actions
Related emails:
  1. Re: ACTION-420 Review of SW-compatibility (from debruijn@inf.unibz.it on 2008-03-10)
  2. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from csma@ilog.fr on 2008-01-11)
  3. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from der@hplb.hpl.hp.com on 2008-01-11)
  4. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from debruijn@inf.unibz.it on 2008-01-11)
  5. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from csma@ilog.fr on 2008-01-10)
  6. [Admin] draft of RIF telecon minutes for 8 January 2008 (from cleo@us.ibm.com on 2008-01-08)
  7. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from csma@ilog.fr on 2008-01-08)
  8. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from csma@ilog.fr on 2008-01-08)
  9. [Admin] Agenda for RIF telecon January 8 (from csma@ilog.fr on 2008-01-07)
  10. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from der@hplb.hpl.hp.com on 2008-01-07)
  11. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from cawelty@gmail.com on 2008-01-06)
  12. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from kifer@cs.sunysb.edu (Michael Kifer) on 2008-01-05)
  13. Re: ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from debruijn@inf.unibz.it on 2008-01-05)
  14. ISSUE-43 ISSUE 41 - Proposed resolution for membership and classification (from cawelty@gmail.com on 2008-01-05)
  15. ISSUE-43: Subclass relationship ## in RIF-BLD (from dean+cgi@w3.org on 2007-10-16)
  16. RE: ISSUE-43: Subclass relationship ## in RIF-BLD (from pvincent@tibco.com on 2007-10-16)
  17. Re: ISSUE-43: Subclass relationship ## in RIF-BLD (from kifer@cs.sunysb.edu (Michael Kifer) on 2007-10-16)

Related notes:

Closed by WG consensus on 1/8/2008 telecon:

RESOLVED: Close Issue-43 by including in BLD subclass formulae of the form a ## b. In the RDF compatibility document, ## and rdfs:subClassOf will be connected appropriately, i.e. whenever a ## b holds, a rdfs:subClassOf b is required to hold.

Christopher Welty, 9 Jan 2008, 13:27:29

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 43.html,v 1.1 2013-02-08 09:09:35 vivien Exp $