refersTo
type: ObjectProperty
comment: The refersTo relation is an inverse of hasContextRelation.

Attribute
type: Class
subclass of: Restriction
  on property: hasType
  all values from: Type
subclass of: Restriction
  on property: hasValue
  all values from: Value
subclass of: Restriction
  on property: hasType
  qualified cardinality: 1
  on class: Type
subclass of: Restriction
  on property: hasValue
  qualified cardinality: 1
  on class: Value
subclass of: Restriction
  on property:
    inverse of: hasAttribute
  qualified cardinality: 1
  on class: SpatialInformationObject
comment: Types and Values are needed for the semantics for the same types of spatial objects are labeled differently schema to schema. Attribute must have exactly one Value and exactly one Type. It must be attached to exactly one SpatialInformationObject. Note that it is possible for two different SpatialInformationObjects to have attributes of the same Type and Value.

ContextualizedRelation
type: Class
subclass of: Restriction
  on property: refersTo
  some values from: SpatialInformationObject
subclass of: Restriction
  on property: hasType
  all values from: Type
subclass of: Restriction
  on property: hasValue
  all values from: Value
subclass of: Restriction
  on property: hasType
  qualified cardinality: 1
  on class: Type
subclass of: Restriction
  on property: hasValue
  qualified cardinality: 1
  on class: Value
comment: Types and Values are needed for the semantics for the same types of spatial objects are labeled differently schema to schema. Attribute must have exactly one Value and exactly one Type. It must be attached to exactly one SpatialInformationObject. Note that it is possible for two different SpatialInformationObjects to have attributes of the same Type and Value. ContextualizedRelation must have exactly one Value and exactly one Type. ContextualizedRelation refers to at least one SpatialInformationObject.

SpatialInformationObject
type: Class
subclass of: Restriction
  on property: hasAttribute
  all values from: Attribute
subclass of: Restriction
  on property: hasContextRelation
  all values from: ContextualizedRelation
subclass of: Restriction
  on property: represents
  all values from: SpatialObject
subclass of: Restriction
  on property: represents
  qualified cardinality: 1
  on class: SpatialObject
comment: A SpatialInformationObject may have Attribute and may have ContextualizedRelation. Since Attributes and ContextualizedRelations have different descriptions in different data schema, these model classes were also chosen to work for any of the schemas used by our domain tools.

SpatialObject
type: Class
comment: An InformationObject represents exactly one SpatialObject.

Type
type: Class
comment: Our use of hasType makes the model more amenable to resolving the large variation of schema differences that exist; instead of subclassing we consider types to be instances of individuals so that we are not burdened by the decision to say that something is a subtype or not. Doing so would cause more hierarchical confusion instead of help in terms of its application. Nevertheless, having typing through properties does not preclude us from adding in the function of such a hierarchy later on.