Abstract Model

S3Model is by name as well as by definition and design a constraint based multi-level modeling approach. This means that there are multiple models with increasing specificity to get to the instance data point. S3Model is constraint based which provides a complete syntactic validation path back to the reference model for the instance data. The semantic model is designed around the concepts of this multi-level model approach. Extensions to the reference model concepts are not allowed.

When answering the high-level question: How do we elaborate the components required for a generic, implementation independent interoperability platform? These few components were the answer.


Shareable, Structured, Semantic Model (S3Model)

The root concept. The abstract idea of S3Model. All of the S3Model classes are subclasses of this class.


Reference Model

A set of components called Core Model Components (CMCs) that provide structural integrity for a domain concept. Some CMCs are mandatory in DMs and some are optional. Optionality is defined in each RM implementation.


Core Model Component

A composable model contained in a reference model. A CMC represents a specific core type of component that further contains elements with base datatypes and/or other CMCs to define its structure.


Core Model Symbol

A CMS represents a CMC in instance data. In practice, it is usually substituted for by a Reusable Model Symbol (RMS). This substitution is due to the fact that constraints are expressed in a Reusable Model Component (RMC) which is then represented by a RMS.


Data Model

A set of selected RMCs that are constraints on the RM components (CMCs) in order to represent a domain concept. In the implementation language there may be additional syntactic conventions required. Caution: Not to be confused with Data Instance.


Reusable Model Component

The name given to a CMC that has been constrained for use in a DM. Through the constraints, a RMC defines a single concept based on syntactic data constraints as well as specified semantics. It is reusable because it can be reused in multiple DMs.


Reusable Model Symbol Represents a RMC in instance data. Can be considered as a data container for the components of a RMC.


A set of data items that reports via isInstanceOf property that it conforms to a DM. In this state it has not been tested for validation.


Subclass of DataInstance. A set of data items that conforms to a DM to represent an instance of that concept AND the all of the data values are valid according to the DM constraints.


Subclass of DataInstance. A set of data items that conforms to a DM to represent an instance of that concept AND at least some of the data values are NOT valid according to the DM constraints. An Invalid Data Instance must contain one or more children of an Exception.


Subclass of DataInstance. A set of data items that DOES NOT conform to the DM it represents OR it contains invalid data and does not contain one or more children of an Exception. If there are no noted Exceptions in the Data Instance then it should be considered suspect and discarded.


Indicates that some data is outside of the parameters defined by the DM and provides some context as to the cause of the anomaly through defined subclasses.

These components are realized in an OWL ontology named s3model.owl and are documented here