archive/org.eclipse.qvt.declarative.ecore.qvtbase/QVTBaseCompliance.html - mmt/org.eclipse.qvtd - Git at Google

 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
 <!-- This file was autogenerated on Wed Jan 14 19:03:04 GMT 2009 by the org.eclipse.qvt.declarative.test.emof.qvtbase.QVTBaseConsistencyTest.testQVTBaseConsistency() JUnit test -->
 <html>
 <head>
 <title>QVTBase Model Compliance</title>
 <meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
 </head>
 <body lang="EN-US">
 <h1>QVTBase Model Compliance</h1>
 <p>
 This document describes clarifications and fixes to
 <ul>
 	<li><a href="http://www.omg.org/docs/formal/06-01-01.pdf">OMG MOF 2.0 specification (06-01-01)</a></li>
 	<li><a href="http://www.omg.org/docs/formal/06-05-01.pdf">OMG OCL 2.0 specification (06-05-01)</a></li>
 	<li><a href="http://www.omg.org/docs/formal/08-04-03.pdf">OMG QVT 1.0 specification (08-04-03)</a></li>
 </ul>
 realised by the Ecore-based and EMOF-based QVTBase models.
 <p>
 The EMOF-based <tt>QVTBase</tt> 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.
 <p>
 The Ecore-based <tt>QVTBase</tt> model is intended to provide identical behaviour subject to the replacement of
 <ul>
 	<li>the <tt>EMOF</tt> package by Ecore (from Eclipse EMF)</li>
 	<li>the <tt>EssentialOCL</tt> package by the Ecore OCL package (from  Eclipse MDT).</li>
 </ul>
 The Ecore-based model should be used within tools, where the power of Ecore and its associated tooling is important.
 <h2>EMOF-based Model Compliance with respect to the OMG QVT Rose Model</h2>
 The OMG QVT Rose Model is the source of all diagrams in the QVT specification
 and the notional source of all other generated models.
 <p>
 The Eclipse <tt>QVTBase</tt> Model resolves the following errors
 and anomalies in the OMG QVT Rose Model.
 <p>
 <br><tt>nsPrefix</tt> for <tt>QVTBase</tt> is <tt>qvtb</tt> rather than <tt>qvtbase</tt>
 <br><tt>nsURI</tt> for <tt>QVTBase</tt> is <tt>http://schema.omg.org/spec/QVT/1.0/qvtbase.xml</tt> rather than <tt>http:///qvtbase.ecore</tt>
 <br><tt>name</tt> for <tt>QVTBase</tt> is <tt>QVTBase</tt> rather than <tt>qvtbase</tt>
 <br><tt>lowerBound</tt> for <tt>Rule.transformation</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>ordered</tt> for <tt>Rule.domain</tt> is <tt>true</tt> rather than <tt>false</tt>
 <h2>EMOF-based Model Compliance with respect to the OMG Ecore Model</h2>
 The OMG Ecore Models are notionally generated from the OMG QVT Rose Model.
 <p>
 The Eclipse <tt>QVTBase</tt> Model resolves the following errors and anomalies in the corresponding OMG Ecore Model.
 <p>
 <br><tt>nsPrefix</tt> for <tt>QVTBase</tt> is <tt>qvtb</tt> rather than <tt>qvtbase</tt>
 <br><tt>nsURI</tt> for <tt>QVTBase</tt> is <tt>http://schema.omg.org/spec/QVT/1.0/qvtbase.xml</tt> rather than <tt>http://www.schema.omg.org/spec/QVT/1.0/qvtbase</tt>
 <br><tt>name</tt> for <tt>QVTBase</tt> is <tt>QVTBase</tt> rather than <tt>qvtbase</tt>
 <br><tt>abstract</tt> for <tt>Domain</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>abstract</tt> for <tt>Rule</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>lowerBound</tt> for <tt>Rule.transformation</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>ordered</tt> for <tt>Pattern.bindsTo</tt> is <tt>false</tt> rather than <tt>true</tt>
 <br><tt>ordered</tt> for <tt>Pattern.predicate</tt> is <tt>false</tt> rather than <tt>true</tt>
 <br><tt>ordered</tt> for <tt>Transformation.ownedTag</tt> is <tt>false</tt> rather than <tt>true</tt>
 <br><tt>ordered</tt> for <tt>Transformation.rule</tt> is <tt>false</tt> rather than <tt>true</tt>
 <br><tt>ordered</tt> for <tt>TypedModel.dependsOn</tt> is <tt>false</tt> rather than <tt>true</tt>
 <br><tt>ordered</tt> for <tt>TypedModel.usedPackage</tt> is <tt>false</tt> rather than <tt>true</tt>
 <br>Unnavigable <tt>opposite</tt> of <tt>Rule.overrides</tt> is modelled
 <br>Unnavigable <tt>opposite</tt> of <tt>Transformation.extends</tt> is modelled
 <br>Unnavigable <tt>opposite</tt> of <tt>TypedModel.dependsOn</tt> is modelled
 <h2>EMOF-based Model Compliance with respect to the OMG EMOF Model</h2>
 The OMG EMOF Model is notionally generated from the OMG QVT Rose Model.
 <p>
 The Eclipse <tt>QVTBase</tt> Model resolves the following errors and anomalies in the corresponding OMG EMOF Model.
 <p>
 <br>The model namespace is <tt>http://schema.omg.org/spec/MOF/2.0/emof.xml</tt> rather than <tt>http://www.schema.omg.org/spec/MOF/2.0/emof.xml</tt>
 <br><tt>xmi:type</tt> of <tt>Boolean</tt> is <tt>emof:PrimitiveType</tt> rather than <tt>emof:Class</tt>
 <br><tt>xmi:type</tt> of <tt>Integer</tt> is <tt>emof:PrimitiveType</tt> rather than <tt>emof:Class</tt>
 <br><tt>xmi:type</tt> of <tt>String</tt> is <tt>emof:PrimitiveType</tt> rather than <tt>emof:Class</tt>
 <br><tt>xmi:type</tt> of <tt>UnlimitedNatural</tt> is <tt>emof:PrimitiveType</tt> rather than <tt>emof:Class</tt>
 <br><tt>package</tt> of <tt>Boolean</tt> is <tt>emof</tt> rather than <tt>primitivetypes</tt>
 <br><tt>package</tt> of <tt>Integer</tt> is <tt>emof</tt> rather than <tt>primitivetypes</tt>
 <br><tt>package</tt> of <tt>String</tt> is <tt>emof</tt> rather than <tt>primitivetypes</tt>
 <br><tt>package</tt> of <tt>UnlimitedNatural</tt> is <tt>emof</tt> rather than <tt>primitivetypes</tt>
 <p>
 <br><tt>uri</tt> for <tt>QVTBase</tt> is defined
 <br><tt>name</tt> for <tt>QVTBase</tt> is <tt>QVTBase</tt> rather than <tt>qvtbase</tt>
 <br><tt>abstract</tt> for <tt>Domain</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>abstract</tt> for <tt>Rule</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>transient</tt> for <tt>Domain.rule</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>transient</tt> for <tt>Predicate.pattern</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>transient</tt> for <tt>Rule.transformation</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>transient</tt> for <tt>TypedModel.transformation</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>lowerBound</tt> for <tt>Domain.isCheckable</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Domain.isEnforceable</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Domain.typedModel</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Function.queryExpression</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Pattern.bindsTo</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Pattern.predicate</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Rule.domain</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Rule.overrides</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Rule.transformation</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Transformation.extends</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Transformation.modelParameter</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Transformation.ownedTag</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>Transformation.rule</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br><tt>lowerBound</tt> for <tt>TypedModel.dependsOn</tt> is <tt>0</tt> rather than <tt>1</tt>
 <br>Unnavigable <tt>opposite</tt> of <tt>Rule.overrides</tt> is modelled
 <br>Unnavigable <tt>opposite</tt> of <tt>Transformation.extends</tt> is modelled
 <br>Unnavigable <tt>opposite</tt> of <tt>TypedModel.dependsOn</tt> is modelled
 <h2>EMOF-based Model Compliance with respect to the Eclipse QVT Rose Model</h2>
 The Eclipse QVT Rose Model provides the definition for all models; it resolves numerous errors in the OMG QVT Rose Model.
 <p>
 The EMOF-based <tt>QVTBase</tt> Model exhibits the following differences with respect to the Eclipse QVT Rose Model.
 <p>
 <br><tt>nsPrefix</tt> for <tt>QVTBase</tt> is <tt>qvtb</tt> rather than <tt>qvtbase</tt>
 <h2>Ecore-based Model Compliance with respect to the EMOF-based Model</h2>
 The Ecore-based <tt>QVTBase</tt> model exhibits the following differences with respect to its EMOF-based counterpart.
 <p>
 <br><tt>nsPrefix</tt> for <tt>QVTBase</tt> is <tt>eqvtb</tt> rather than <tt>qvtb</tt>
 <br><tt>nsURI</tt> for <tt>QVTBase</tt> is <tt>http://www.eclipse.org/qvt/1.0/QVTBase</tt> rather than <tt>http://schema.omg.org/spec/QVT/1.0/qvtbase.xml</tt>
 <br><tt>eType</tt> for <tt>Transformation.ownedTag</tt> is <tt>EAnnotation</tt> rather than <tt>Tag</tt>
 <br><tt>unsettable</tt> for <tt>Domain.isCheckable</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>unsettable</tt> for <tt>Domain.isEnforceable</tt> is <tt>true</tt> rather than <tt>false</tt>
 <br><tt>Transformation.getFunction(name)</tt> is defined
 <br><tt>Transformation.getModelParameter(name)</tt> is defined
 </body>
 </html>
	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
	<!-- This file was autogenerated on Wed Jan 14 19:03:04 GMT 2009 by the org.eclipse.qvt.declarative.test.emof.qvtbase.QVTBaseConsistencyTest.testQVTBaseConsistency() JUnit test -->
	<html>
	<head>
	<title>QVTBase Model Compliance</title>
	<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
	</head>
	<body lang="EN-US">
	<h1>QVTBase Model Compliance</h1>
	<p>
	This document describes clarifications and fixes to
	<ul>
	<li><a href="http://www.omg.org/docs/formal/06-01-01.pdf">OMG MOF 2.0 specification (06-01-01)</a></li>
	<li><a href="http://www.omg.org/docs/formal/06-05-01.pdf">OMG OCL 2.0 specification (06-05-01)</a></li>
	<li><a href="http://www.omg.org/docs/formal/08-04-03.pdf">OMG QVT 1.0 specification (08-04-03)</a></li>
	</ul>
	realised by the Ecore-based and EMOF-based QVTBase models.
	<p>
	The EMOF-based <tt>QVTBase</tt> 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.
	<p>
	The Ecore-based <tt>QVTBase</tt> model is intended to provide identical behaviour subject to the replacement of
	<ul>
	<li>the <tt>EMOF</tt> package by Ecore (from Eclipse EMF)</li>
	<li>the <tt>EssentialOCL</tt> package by the Ecore OCL package (from Eclipse MDT).</li>
	</ul>
	The Ecore-based model should be used within tools, where the power of Ecore and its associated tooling is important.
	<h2>EMOF-based Model Compliance with respect to the OMG QVT Rose Model</h2>
	The OMG QVT Rose Model is the source of all diagrams in the QVT specification
	and the notional source of all other generated models.
	<p>
	The Eclipse <tt>QVTBase</tt> Model resolves the following errors
	and anomalies in the OMG QVT Rose Model.
	<p>
	<br><tt>nsPrefix</tt> for <tt>QVTBase</tt> is <tt>qvtb</tt> rather than <tt>qvtbase</tt>
	<br><tt>nsURI</tt> for <tt>QVTBase</tt> is <tt>http://schema.omg.org/spec/QVT/1.0/qvtbase.xml</tt> rather than <tt>http:///qvtbase.ecore</tt>
	<br><tt>name</tt> for <tt>QVTBase</tt> is <tt>QVTBase</tt> rather than <tt>qvtbase</tt>
	<br><tt>lowerBound</tt> for <tt>Rule.transformation</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>ordered</tt> for <tt>Rule.domain</tt> is <tt>true</tt> rather than <tt>false</tt>
	<h2>EMOF-based Model Compliance with respect to the OMG Ecore Model</h2>
	The OMG Ecore Models are notionally generated from the OMG QVT Rose Model.
	<p>
	The Eclipse <tt>QVTBase</tt> Model resolves the following errors and anomalies in the corresponding OMG Ecore Model.
	<p>
	<br><tt>nsPrefix</tt> for <tt>QVTBase</tt> is <tt>qvtb</tt> rather than <tt>qvtbase</tt>
	<br><tt>nsURI</tt> for <tt>QVTBase</tt> is <tt>http://schema.omg.org/spec/QVT/1.0/qvtbase.xml</tt> rather than <tt>http://www.schema.omg.org/spec/QVT/1.0/qvtbase</tt>
	<br><tt>name</tt> for <tt>QVTBase</tt> is <tt>QVTBase</tt> rather than <tt>qvtbase</tt>
	<br><tt>abstract</tt> for <tt>Domain</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>abstract</tt> for <tt>Rule</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>lowerBound</tt> for <tt>Rule.transformation</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>ordered</tt> for <tt>Pattern.bindsTo</tt> is <tt>false</tt> rather than <tt>true</tt>
	<br><tt>ordered</tt> for <tt>Pattern.predicate</tt> is <tt>false</tt> rather than <tt>true</tt>
	<br><tt>ordered</tt> for <tt>Transformation.ownedTag</tt> is <tt>false</tt> rather than <tt>true</tt>
	<br><tt>ordered</tt> for <tt>Transformation.rule</tt> is <tt>false</tt> rather than <tt>true</tt>
	<br><tt>ordered</tt> for <tt>TypedModel.dependsOn</tt> is <tt>false</tt> rather than <tt>true</tt>
	<br><tt>ordered</tt> for <tt>TypedModel.usedPackage</tt> is <tt>false</tt> rather than <tt>true</tt>
	<br>Unnavigable <tt>opposite</tt> of <tt>Rule.overrides</tt> is modelled
	<br>Unnavigable <tt>opposite</tt> of <tt>Transformation.extends</tt> is modelled
	<br>Unnavigable <tt>opposite</tt> of <tt>TypedModel.dependsOn</tt> is modelled
	<h2>EMOF-based Model Compliance with respect to the OMG EMOF Model</h2>
	The OMG EMOF Model is notionally generated from the OMG QVT Rose Model.
	<p>
	The Eclipse <tt>QVTBase</tt> Model resolves the following errors and anomalies in the corresponding OMG EMOF Model.
	<p>
	<br>The model namespace is <tt>http://schema.omg.org/spec/MOF/2.0/emof.xml</tt> rather than <tt>http://www.schema.omg.org/spec/MOF/2.0/emof.xml</tt>
	<br><tt>xmi:type</tt> of <tt>Boolean</tt> is <tt>emof:PrimitiveType</tt> rather than <tt>emof:Class</tt>
	<br><tt>xmi:type</tt> of <tt>Integer</tt> is <tt>emof:PrimitiveType</tt> rather than <tt>emof:Class</tt>
	<br><tt>xmi:type</tt> of <tt>String</tt> is <tt>emof:PrimitiveType</tt> rather than <tt>emof:Class</tt>
	<br><tt>xmi:type</tt> of <tt>UnlimitedNatural</tt> is <tt>emof:PrimitiveType</tt> rather than <tt>emof:Class</tt>
	<br><tt>package</tt> of <tt>Boolean</tt> is <tt>emof</tt> rather than <tt>primitivetypes</tt>
	<br><tt>package</tt> of <tt>Integer</tt> is <tt>emof</tt> rather than <tt>primitivetypes</tt>
	<br><tt>package</tt> of <tt>String</tt> is <tt>emof</tt> rather than <tt>primitivetypes</tt>
	<br><tt>package</tt> of <tt>UnlimitedNatural</tt> is <tt>emof</tt> rather than <tt>primitivetypes</tt>
	<p>
	<br><tt>uri</tt> for <tt>QVTBase</tt> is defined
	<br><tt>name</tt> for <tt>QVTBase</tt> is <tt>QVTBase</tt> rather than <tt>qvtbase</tt>
	<br><tt>abstract</tt> for <tt>Domain</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>abstract</tt> for <tt>Rule</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>transient</tt> for <tt>Domain.rule</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>transient</tt> for <tt>Predicate.pattern</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>transient</tt> for <tt>Rule.transformation</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>transient</tt> for <tt>TypedModel.transformation</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>lowerBound</tt> for <tt>Domain.isCheckable</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Domain.isEnforceable</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Domain.typedModel</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Function.queryExpression</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Pattern.bindsTo</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Pattern.predicate</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Rule.domain</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Rule.overrides</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Rule.transformation</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Transformation.extends</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Transformation.modelParameter</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Transformation.ownedTag</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>Transformation.rule</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br><tt>lowerBound</tt> for <tt>TypedModel.dependsOn</tt> is <tt>0</tt> rather than <tt>1</tt>
	<br>Unnavigable <tt>opposite</tt> of <tt>Rule.overrides</tt> is modelled
	<br>Unnavigable <tt>opposite</tt> of <tt>Transformation.extends</tt> is modelled
	<br>Unnavigable <tt>opposite</tt> of <tt>TypedModel.dependsOn</tt> is modelled
	<h2>EMOF-based Model Compliance with respect to the Eclipse QVT Rose Model</h2>
	The Eclipse QVT Rose Model provides the definition for all models; it resolves numerous errors in the OMG QVT Rose Model.
	<p>
	The EMOF-based <tt>QVTBase</tt> Model exhibits the following differences with respect to the Eclipse QVT Rose Model.
	<p>
	<br><tt>nsPrefix</tt> for <tt>QVTBase</tt> is <tt>qvtb</tt> rather than <tt>qvtbase</tt>
	<h2>Ecore-based Model Compliance with respect to the EMOF-based Model</h2>
	The Ecore-based <tt>QVTBase</tt> model exhibits the following differences with respect to its EMOF-based counterpart.
	<p>
	<br><tt>nsPrefix</tt> for <tt>QVTBase</tt> is <tt>eqvtb</tt> rather than <tt>qvtb</tt>
	<br><tt>nsURI</tt> for <tt>QVTBase</tt> is <tt>http://www.eclipse.org/qvt/1.0/QVTBase</tt> rather than <tt>http://schema.omg.org/spec/QVT/1.0/qvtbase.xml</tt>
	<br><tt>eType</tt> for <tt>Transformation.ownedTag</tt> is <tt>EAnnotation</tt> rather than <tt>Tag</tt>
	<br><tt>unsettable</tt> for <tt>Domain.isCheckable</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>unsettable</tt> for <tt>Domain.isEnforceable</tt> is <tt>true</tt> rather than <tt>false</tt>
	<br><tt>Transformation.getFunction(name)</tt> is defined
	<br><tt>Transformation.getModelParameter(name)</tt> is defined
	</body>
	</html>