W3C home > Mailing lists > Public > public-owl-wg@w3.org > October 2007

ISSUE-19 (declarations-p): REPORTED: Resolve whether to include declarations

From: OWL <sysbot+tracker@w3.org>
Date: Thu, 25 Oct 2007 04:34:28 +0000 (GMT)
To: public-owl-wg@w3.org
Message-Id: <20071025043428.909245F751@stu.w3.org>

ISSUE-19 (declarations-p): REPORTED: Resolve whether to include declarations	


Raised by: Alan Ruttenberg
On product: 

Reported by alanruttenberg, Aug 08, 2007
  Allows for detecting some kinds of errors
  Allows expression of intention in otherwise ambiguous cases
  Some duplication of information
  Uncertain impact
  Not a lot of experience with it

(there may be others)


Comment 1 by bparsia, Aug 13, 2007
It should be noted that declarations *exist*, in a sense, in OWL DL. Use typing and declarations are handled by  a mix of type triples and inference from syntactic position. Type triples are overloaded to be a kind of  declaration as well as a typing mechanism.

The second pro conflates issues concerning intention and issues concerning ambiguity. Ambiguity is generally  handled, in OWL 1.1, by manifest typing, e.g., "ObjectPropertyDomain" (vs. plain rdfs:domain in OWL). Now,  arguably, this signals your intention that the property in question is an object property (and the object of the  assertion is a class). But there are cases where nothing is ambiguous, but the author didn't intend for a  property to be punned as a class (current declarations don't enforce this bit). Thus, some form of declaration  could express this bit of authorial intent.

Comment 2 by bparsia, Aug 13, 2007
See also:


But this deals more with the syntax, afaict.
Received on Thursday, 25 October 2007 04:34:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:59 UTC