Characterisation Ontology

Development

I am using Protege 3.2-beta to develop an OWL-DL ontology of the characterisation 1.0 schema. This ontology imports STC1.3.owl discussed in StcOntology.

The latest attached version of the ontology is characterisation1.11.owl, updated in January 2008.

Links

• http://alinda.u-strasbg.fr/Model/Characterisation/schema/characterisation.0.95.xsd - Characterisation 0.95 schema

Questions and Issues: 0.95

1. Note: The first draft of the characterisation ontology includes a hierarchy of classes and properties only. No inferences have been added yet.
2. Several class names are duplicated between the characterisation ontology and the STC ontology it imports. After initial experimentation, the duplicates have been kept in the characterisation ontology since some (but not all) duplicates have different parent or children classes or different properties. Examples include CError3, Resolution, and anyType.
3. Classes in the characterisation ontology have only been assigned to parent classes from STC where the STC type is explicitly stated in the characterisation schema.
4. Some datatype properties have type "URI" in the characterisation schema's corresponding attributes. However, Protege 3.2-beta no longer includes "URI" has an option for datatype property ranges. These properties have been left as type "any", but they could be converted to "string" instead.
5. The domain of properties imported from the STC ontology cannot be extended to include characterisation ontology classes. Therefore, there are some duplicate property names kept in the characterisation ontology that are also present in the imported STC ontology.
6. The characterisation schema includes the element limits that is given different types in different parts of the schema: CharCoordArea as part of BoundsType, and type stc:coordScalarIntervalType as part of ResolutionSupportType. In the current characterisation ontology, limits has been assigned type stc:coordScalarIntervalType.
7. Classes that are assigned type anyType from the xsd namespace - should these actually be datatype properties with range "Any"?
8. The CharCoordArea class does not seem to have a parent class. Can its function be taken over by stc:coordScalarIntervalType instead? CharCoordArea is only used in the context of a second parent class for limits, which is already assigned to type stc:coordScalarIntervalType.

Note: ontology of Characterisation 1.0 schema now attached. - 26 Feb 2007

Questions and Issues: 1.0

1. Restrictions of AxisFrameType^?: SpatialAxisFrameType^?, SpectralAxisFrameType^?, TimeAxisFrameType^?. Are these genuine subsumptions, and is the restriction formally made through enumeration of axisFrame values?
2. Restrictions of CharacterisationAxisType^?: SpatialAxisType^?, SpectralAxisType^?, TimeAxisType^?. Are these genuine subsumptions, and is the restriction formally made through enumeration of axisFrame values?
3. Look at "has" relationships between numBins, numBins1, numBins2, and numBins3
4. Should ErrorRefValue^? be child of ErrorRefValueType^? instead of child of anyType?
5. The coordsystem element is used with attributes id, idref, and coord_system_id. Can a rule be established to make these equivalent?

-- ElizabethAuden - 23 Sep 2006