This document describes clarifications and fixes to
The EMOF-based QVTRelation model is intended to exactly comply with the spirit of the latest QVT specification; the model therefore corrects numerous problems in the official QVT 1.0 models. The EMOF-based model should be used for modelling, where accuracy is important.
The Ecore-based QVTRelation model is intended to provide identical behaviour subject to the replacement of
The Eclipse QVTRelation Model resolves the following errors and anomalies in the OMG QVT Rose Model.
nsURI for QVTRelation is http://schema.omg.org/spec/QVT/1.0/qvtrelation.xml rather than http:///qvtrelation.ecore
nsPrefix for QVTRelation is qvtr rather than qvtrelation
name for QVTRelation is QVTRelation rather than qvtrelation
lowerBound for RelationCallExp.argument is 2 rather than 0
lowerBound for RelationCallExp.referredRelation is 1 rather than 0
lowerBound for RelationDomain.pattern is 1 rather than 0
The Eclipse QVTRelation Model resolves the following errors and anomalies in the corresponding OMG Ecore Model.
nsURI for QVTRelation is http://schema.omg.org/spec/QVT/1.0/qvtrelation.xml rather than http://www.schema.omg.org/spec/QVT/1.0/qvtrelation
nsPrefix for QVTRelation is qvtr rather than qvtrelation
name for QVTRelation is QVTRelation rather than qvtrelation
lowerBound for RelationCallExp.argument is 2 rather than 0
lowerBound for RelationCallExp.referredRelation is 1 rather than 0
lowerBound for RelationDomain.pattern is 1 rather than 0
containment for Relation.operationalImpl is true rather than false
transient for RelationImplementation.relation is true rather than false
ordered for Key.part is false rather than true
ordered for Relation.operationalImpl is false rather than true
ordered for Relation.variable is false rather than true
ordered for RelationDomain.defaultAssignment is false rather than true
ordered for RelationalTransformation.ownedKey is false rather than true
Unnavigable opposite of Relation.when is modelled
Unnavigable opposite of Relation.where is modelled
Unnavigable opposite of RelationDomain.defaultAssignment is modelled
Unnavigable opposite of RelationDomainAssignment.valueExp is modelled
Unnavigable opposite of RelationDomainAssignment.variable is modelled
The Eclipse QVTRelation Model resolves the following errors and anomalies in the corresponding OMG EMOF Model.
The model namespace is http://schema.omg.org/spec/MOF/2.0/emof.xml rather than http://www.schema.omg.org/spec/MOF/2.0/emof.xml
xmi:type of Boolean is emof:PrimitiveType rather than emof:Class
xmi:type of Integer is emof:PrimitiveType rather than emof:Class
xmi:type of String is emof:PrimitiveType rather than emof:Class
xmi:type of UnlimitedNatural is emof:PrimitiveType rather than emof:Class
package of Boolean is emof rather than primitivetypes
package of Integer is emof rather than primitivetypes
package of String is emof rather than primitivetypes
package of UnlimitedNatural is emof rather than primitivetypes
uri for QVTRelation is defined
name for QVTRelation is QVTRelation rather than qvtrelation
containment for Relation.operationalImpl is true rather than false
transient for Key.transformation is true rather than false
transient for RelationImplementation.relation is true rather than false
lowerBound for DomainPattern.templateExpression is 0 rather than 1
lowerBound for Key.transformation is 0 rather than 1
lowerBound for Relation.isTopLevel is 0 rather than 1
lowerBound for Relation.operationalImpl is 0 rather than 1
lowerBound for Relation.variable is 0 rather than 1
lowerBound for Relation.when is 0 rather than 1
lowerBound for Relation.where is 0 rather than 1
lowerBound for RelationCallExp.argument is 2 rather than 1
lowerBound for RelationDomain.defaultAssignment is 0 rather than 1
lowerBound for RelationImplementation.relation is 0 rather than 1
lowerBound for RelationalTransformation.ownedKey is 0 rather than 1
Unnavigable opposite of Relation.when is modelled
Unnavigable opposite of Relation.where is modelled
Unnavigable opposite of RelationDomain.defaultAssignment is modelled
Unnavigable opposite of RelationDomainAssignment.valueExp is modelled
Unnavigable opposite of RelationDomainAssignment.variable is modelled
The EMOF-based QVTRelation Model exhibits the following differences with respect to the Eclipse QVT Rose Model.
nsPrefix for QVTRelation is qvtr rather than qvtrelation
nsURI for QVTRelation is http://www.eclipse.org/qvt/1.0/QVTRelation rather than http://schema.omg.org/spec/QVT/1.0/qvtrelation.xml
nsPrefix for QVTRelation is eqvtr rather than qvtr
RelationalTransformation.getRelation(name) is defined
Relation.getRelationalTransformation() is defined