Copyright © 2011 Open Geospatial Consortium,
Inc. All Rights Reserved.
97
managed via web services. Improved support by OGCISO standards for models that are based on the Temporality Model would also greatly benefit its usability.
10.1.6.3 What is needed?
There are various aspects to consider. On the one hand, current model design and encoding practices need to be extended to support the Temporality Model. On the other
hand, standards for managing time varying data need to be extended to better support this type of data. Relevant aspects are described in more detail in the following subsections.
10.1.6.3.1 Model design and encoding
Currently, application schemas that deal with static information only are modeled following the General Feature meta Model see ISO 19109. The model uses
stereotyped facets – like the FeatureType, Union and CodeList stereotypes for UML classes – to indicate the specific purpose of each facet. ISO 19103,
ISO 19109 and ISO 19136 define a set of basic stereotypes that are used in Application Schema modeling and also define the theory that belongs to these stereotypes. ISO 19136
defines rules for encoding such a model in XML Schema. Each relevant stereotype has its specific encoding rules see Annex E in ISO 19136. A designer can thus capture the
intention of each model facet by choosing the appropriate stereotype for it. Encodings also called physical models of the conceptual model can then automatically be
generated
9
. The OWS-8 Domain Modeling Cookbook OGC 11-107 provides further guidelines on application schema modeling.
At the moment, AIXM designers just stereotype classes as feature or object which governs the encoding. In addition, for objects that change their value based
upon a defined schedule an explicit inheritance relationship to the abstract type PropertyWithSchedule is included in the conceptual model.
A designer of a conceptual model that involves time varying properties should be able to explicitly mark which properties are time varying and which are not
10
. This can be achieved via specific stereotypes defined for that purpose. Such stereotypes can also be
used to indicate if a type can change its values based on a defined schedule thus preventing the need to explicitly model the inheritance relationship to
PropertyWithSchedule. Encoding rules can then be defined to support these new stereotypes. The OWS-8 AIXM 5.1 Refactoring Report OGC 11-106 describes the use of
stereotypes and options to support dynamic properties in conceptual models and the encoding into a physical model in more detail.
Having explicit encoding rules would further benefit the modeling work. By stereotyping feature types and their properties, the designer can concentrate on the relevant domain
aspects – for example on which feature properties always have to be available to applications even though they may not always be encoded, for example in Tempdeltas.
9
This may require the definition of specific tagged values for the components of the conceptual model.
10
Note that this is only relevant for feature types, types and data types but not for code lists or unions.
