ISSUE-18
property typing
WITHDRAWN/REJECTED: Fine-grained property typing
- State:
- CLOSED
- Product:
- Raised by:
- Jeremy Carroll
- Opened on:
- 2007-10-24
- Description:
Reported by jlc415, Jun 11, 2007 In OWL-DL whether a role name represented an object or a datatype property was inferred globally on the basis of the entire ontology. (If it was not possible to infer which type a property was, then the difference did not make any difference to interpretation of the ontology.) It was possible to use a property in (for example) cardinality restrictions without making it explicit which type of property was used. The current syntax specification requires that every use of a property explicitly encode whether the property should be treated as a datatype or as an object property. The extra verbosity required might not be considered an issue for the (already cumbersome) abstract syntax, but it prevents any terse alternate syntax from being converted to a valid OWL 1.1 fragment. Manchester OWL Syntax, for example, lets one to write expressions along the lines of hasAddress atleast 1 but there are two possible translations of this expression to OWL 1.1: ObjectMinCardinality(1 hasAddress) and DataMinCardinality(1 hasAddress) This is a significant problem for interfaces which allow users to write OWL fragments in isolation. This issue is related to that of object/datatype property punning. If such punning were disallowed then there would be no need for such explicit typing.
- Related Actions Items:
- No related actions
- Related emails:
- ISSUE-18 (property typing): REPORTED: Fine-grained property typing (from sysbot+tracker@w3.org on 2007-10-24)
Related notes:
2007-11-20 09:37:21: See also ISSUE 17 (http://www.w3.org/2007/OWL/tracker/issues/17) [Ian Horrocks]
2008-04-04 13:53:34:
I withdraw this issue, since it appears to be resolved with the resolution of issue 17; and if it isn't it may be incoherent. [Jeremy Carroll]
Changelog:
2007-10-24 21:16:42: Created issue 'REPORTED: Fine-grained property typing' nickname property typing owned by Peter Patel-Schneider on product , description 'Reported by jlc415, Jun 11, 2007 In OWL-DL whether a role name represented an object or a datatype property was inferred globally on the basis of the entire ontology. (If it was not possible to infer which type a property was, then the difference did not make any difference to interpretation of the ontology.) It was possible to use a property in (for example) cardinality restrictions without making it explicit which type of property was used. The current syntax specification requires that every use of a property explicitly encode whether the property should be treated as a datatype or as an object property. The extra verbosity required might not be considered an issue for the (already cumbersome) abstract syntax, but it prevents any terse alternate syntax from being converted to a valid OWL 1.1 fragment. Manchester OWL Syntax, for example, lets one to write expressions along the lines of hasAddress atleast 1 but there are two possible translations of this expression to OWL 1.1: ObjectMinCardinality(1 hasAddress) and DataMinCardinality(1 hasAddress) This is a significant problem for interfaces which allow users to write OWL fragments in isolation. This issue is related to that of object/datatype property punning. If such punning were disallowed then there would be no need for such explicit typing. ' non-public [Peter Patel-Schneider]
2007-11-20 09:36:03: title changed to 'ACCEPTED: Fine-grained property typing' [Ian Horrocks]
2007-11-20 09:36:03: Issue dissociated from any product [Ian Horrocks]
2007-11-20 09:37:21: Issue dissociated from any product [Ian Horrocks]
2007-12-20 08:45:55: Owner changed to 'Jeremy Carroll' [Peter Patel-Schneider]
2007-12-20 08:45:55: Issue dissociated from any product [Peter Patel-Schneider]
2008-04-04 13:53:34: title changed to 'WITHDRAWN/REJECTED: Fine-grained property typing'
2008-04-04 13:53:34: Issue dissociated from any product
2008-04-04 13:53:34: Status changed to 'closed'