Issue 16034: OWLClass::isClassKind:OCLClassKind breaks convention that ‘is’ at the start of properties is used to indicate Booleans (odm-rtf)
Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com)
Nature: Uncategorized Issue
Severity: 
Summary: The property OWLClass::isClassKind:OCLClassKind (introduced in Annex F) breaks the convention that ‘is’ at the start of properties is used to indicate Booleans. The name ‘classKind’ or ‘hasClassKind’ (for consistency with ‘hasRestrictionKind’ would be more appropriate
Resolution: 
Revised Text: 
Actions taken:
February 16, 2011: received issue
Discussion: 

End of Annotations:=====
ubject: Issues on ODM metamodel
Date: Wed, 16 Feb 2011 11:07:01 -0800
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issues on ODM metamodel
Thread-Index: AcvODJGE0bKWyV4TTVamVfqNduRiaQ==
From: "Pete Rivett" <pete.rivett@adaptive.com>
To: <issues@omg.org>
Cc: <ekendall@sandsoft.com>, <evan.wallace@nist.gov>,
        <nicolas.f.rouquette@jpl.nasa.gov>


I.d appreciate early feedback on these, especially the following where I.m less sure of my ground: 6, 9.

This is issue # 16034

OWLClass::isClassKind:OCLClassKind breaks convention that .is. at the start of properties is used to indicate Booleans

The property OWLClass::isClassKind:OCLClassKind (introduced in Annex F) breaks the convention that .is. at the start of properties is used to indicate Booleans. The name .classKind. or .hasClassKind. (for consistency with .hasRestrictionKind. would be more appropriate