C. Maria Keet In the annotations for the entities, besides occasional comments, there is a list of terms as it is use in the covered conceptual data modelling languages, which is in the order of and format: UML v2.4.1 EER ORM This is the OWLized version of the unifying metamodel for the static, structural components of UML class diagrams, EER, and ORM2, and their constraints. The diagrammatic representation of the static structural components only, and their rationale, are described in the following two publications: Keet, C.M., Fillottrani, P.R. Toward an ontology-driven unifying metamodel for UML Class Diagrams, EER, and ORM2. 32nd International Conference on Conceptual Modeling (ER'13). W. Ng, V.C. Storey, and J. Trujillo (Eds.). Springer LNCS 8217, 313-326. 11-13 November, 2013, Hong Kong. Keet, C.M., Fillottrani, P.R. Structural entities of an ontology-driven unifying metamodel for UML, EER, and ORM2. 3rd International Conference on Model & Data Engineering (MEDI'13). A. Cuzzocrea and S. Maabout (Eds.) September 25-27, 2013, Amantea, Calabria, Italy. Springer LNCS 8216, 188-199. A paper describing the full metamodel, including the constraints, is currently under review with an international journal version 1.2, December 2014. for value comparisons There is also a 'constrained with' in the metamodel that can be seen to be the inverse of declaredOn. We now use the inverse(declaredOn) for that to reduce a bit the number of object properties and gain some in reasoner performance. Not very imaginative name, but it is for asserting that each wak object type must be related to a normal ('strong') one Same story as with the declaredOn: also here one could choose to keep either identifies and identifiedBy. We chose the identifies, and avail of the other direciion by using inverse The object subproperties of naryProperty are only here due to reifying ternaries and quaternary. Thus, they are NOT to be used for any other axiom than for said reification. The metamodel also has participatesIn, which is replaced by inverse(participant); like with identifies and declaredOn Intrduced as artefact from formalising in OWL ('flattened' last part of values in cardinality constraints) Intrduced as artefact from formalising in OWL ('flattened' last part of values in value constraints) This class is used to group several otherwhise 'orphan' classes (subsumed only by Thing), for they have in common they deal with abstract things (numbers, values, value ranges) relic from the past, but available, so included 1 attribute attribute, but without including a data type in the diagram absent (represented differently) 1 attribute value constraint absent absent 1 Generalization of the various types of attributes Attributive property cardinality constraint in our MM, in the others: multiplicity on attribute cardinality on attribute absent (add cardinality to the fact type with a lexical object type) for attributes for both relationships and for attributes of object types For cardinality on attributes, object types, and complex ones (ORM's frequency constraints over >1 role) These are the comparison operators for the value comparison constraint 2 1 complete total total (exhaustive) covering subtypes Note: they are declared among subtypes on the subsumption relation, not between any object types 1 1 1 Same representation issues as noted for PartWhole, but then for CompositeAggregate composite aggregation absent absent 2 more general: a property can be a composite of another property (and an attribute is a property) composite attribute implicitly present by adding new roles CompoundCardinalityConstraint (involving > 1 role) in our MM, respectively: absent absent frequency constraints in one fact type over more than one role 2 Data type; LiteralSpecification absent data type for the dimensional attributes and value types, such as the kg, km, km/h etc. absent (no recording of dimension) absent absent (represented differently) 1 absent absent lexical object type / value type, with dimension 2 1 disjoint disjoint exclusive subtypes Note: they are declared among subtypes on the subsumption relation, not between any object types 2 absent absent exclusion (on fact types) 2 \{xor\} XOR exclusion (on roles) Note: here it is declared on the roles, not via the subsumption relation, as with object types To group disjoint Object types, relationships, and roles 2 implicitly present (e.g., as an \{or\}, see pp58-59 of \cite{UMLspec12}) absent disjunctive mandatory/inclusive-or on roles 1 classifier absent object type The following constraints are not represented in the OWL: 'The cardinality of Relationship and Role in ext unique is equal.' and 'The Roles on which an External uniqueness is declared on are contained in the Relationships that participate in the ext unique.' an (extended) alt key mechanism \cite{UMLODM09}; see also a refinement in \cite{Keet11keys} needed for weak entity type compound reference scheme 1 exists in part, with the qualified association exists in part, where the participants are all attributes external uniqueness constraint see annotation ExtUniqueR 1 Partial representation for the various identifiers implicitly present (e.g., as an \{and\}, see pp58-59 of \cite{UMLspec12}) AND for relationships absent alt key mechanism, for one class compound identifier, for attributes within entity type absent absent exists in part, where the participants are all attributes (see also EER's compound identifier) internal uniqueness constraint not represented: 'The cardinality of Internal uniqueness being declared on at least one Role has a maximum cardinality less than or equal the number of Roles in the Relationship that contains those Roles.' 3 4 1 4 absent absent join-exclusion among four roles in three or four relationships absent absent join-equality among four roles in three or four relationships absent absent join-subset constraint among four roles in three or four relationships 1 mandatory role mandatory mandatory Not represented, due to OWL limitations: 'If a Mandatory constraint is declared on two or more Roles, then those Roles must be contained in distinct Relationships.' 1 1 This is ORM's hidden attribute, from Value type to Data type reified and flattened out representation for cardinality. reified and flattened out representation for values. reified and flattened out representation for cardinality. reified and flattened out representation for values. absent (represented differently) multivalued attribute absent (represented differently) 1 association class associative entity objectified fact type 1 class entity type non-lexical object type / entity type for Object subtype, there is the naming, respectively: subclass subtype subtype Object type cardinality constraint in our MM, in the others, respectively: multiplicity constraint; min max cardinality constraint; min cardinality, max cardinality frequency (object cardinality) constraint; min cardinality, max cardinality for in the relationship 1 1 2 Same representation issues as noted for PartWhole, but then for CompositeAttribute and AttributiveProperty In addition, we want the AttributiveProperty and CompositeAttribute linked to part, but if we add that explicitly, then it would exclude others, and it would contradict the EntityType as domain and range for PartWhole, because AttrubutiveProeprty and EntityType are disjoint. So we put them together in PartWhole We actually want to say that for each PartWhole, there are exactly 2 EntityTypes participating in it, of which exaclty 1 is the partPlayer and exacty one is the wholePlayer, and them together consitute a subset of the participant relation. This cannot be expressed. 1 qualified association absent (limited version of) external uniqueness 2 qualified association absent absent 1 Separate, just to make clear where they come from. They all have an "R" appended in the naming scheme in this OWL file, and their own set of object properties not to be used elsewhere 2 0 2 2 1 association, can be binary according to the MOF 2.4.1, but also >2-ary according to the Superstructure Spec 2.4.1 relationship, >=2-ary atomic/compound fact type, >=1-ary For a Sub-relationship, the name is, respectively: subsetting or subtyping of association subtyping the relationship (not present in all EER variants) subset constraint on fact type 1 2 1 They're all in ORM, though the refinement on reflexivity is quite new and not all ORM tools have that 2 absent absent equality (on fact types) 2 0 2 0 1 1 1 4 association end / member end component of a relationship role 2 absent absent equality (on roles) 1 absent absent role value constraint (redundant, because one can also model it with a subtype; include it for the time being [provided it does not become too cumbersome]) 1 1 1 1 shared aggregation absent absent 1 alt key mechanism (in \cite{UMLODM09}, not in v2.4.1) made mandatory 1:1 unary identifier (mandatory 1:1) (simple) reference mode (mandatory 1:1) not represented fully: 'The Single identification has a Mandatory and a 1:1 Cardinality constraint.' not named in the MM: Role subset (inherited from the subsumption on Entity), and implcitly present: subsetting of association ends absent subset constraint on role 1 1 More precisely regarding the sub and super: 'For each sub participating in a Subsumption, there must be a matching super and its participating Entity is of the same category as the Entity participating in the sub.' `category' in the textual constraint refers to that a subsumption can be declared among any two Relationships, between any two Object types etc., but not between, say, an Object type and an Attributive property absent absent uniqueness constraint 1 1 1 2 1 absent absent value comparison constraint reified and flattened out representation for values. 1 reified and flattened out representation for values, to go with min nad max values 1 1 absent absent lexical object type / value type, without dimension 1 Value specification (see SS fig 7.5) only with optional upper and lower values, but in SS fig 7.13, there's also enumeration) absent value constraint 1 Not represented: 'A Weak identification is a combination of one or more Attributive property of the Weak object type it identifies together with the Identification constraint of its related 'strong' Object type.' absent weak identifier (limited version of) external uniqueness 1 absent weak entity type absent