Asset Oriented Modeling (AOM)

- Constraints -

Constraints can be used to define additional restrictions for properties. Constraints can be defined


Constraints can be specified with a context expression. For example, a constraint between sub-properties of a single property could specify the path of that property as context, and specify the sub-properties relative to that path:

name::(not(first) or (first and last))

Constraint languages:

Constraint prefixes:

A model may specify a default constraint language, or several constraint language prefixes. This allows the use of different constraint languages within the same model. Constraints that are formulated in a constraint language other than the default constraint language must be specified with a constraint language prefix which is separated from the rest of the constraint by a colon:

name::xpath:(not(first) or (first and last))

Constraint label:

Optionally it is possible to decorate a constraint with a label. A constraint label does not have any specific purpose within AOM but helps to identify constraints. The label is separated from the rest of the constraint expression with a left curly bracket. Note, that there is no closing bracket.

c1{name::xpath:(not(first) or (first and last))

Abstract constraints:

Abstract constraints are simply specified by an (optional) context, an (optional) label, and a constraint name. The concrete constraint depends on the implementation. In particular, abstract constraints allow to implement soft constraints (soft coded business rules). The names of abstract constraints constitute one or several vocabularies. The vocabulary used is specified with the constraint language prefix or by the default constraint language.



Home Definition Step-by-Step Examples Downloads

Contact: support 'at'