Revision as of 13:53, 14 June 2007

This article focuses on authoring and using XML Schemas for the purpose of generating an EMF model.

Introduction

An EMF Model (files of type *.genmodel) is your hub for importing/exporting other metamodel formats, linking to other EMF models, and generating implementation code. Out-of-the-box, EMF can import XML Schema Definitions (XSDs) into Ecore Models (files of type *.ecore). Similarly, EMF can export Ecore Models to XSDs. But without some additional information, EMF uses a default set of transformations that rarely yields the desired results.

Luckily, both Ecore models and XML Schemas have support for annotations. Annotations can be almost anything, but for this discussion, annotations will serve two main purposes:

• Provide additional information when transforming one metamodel to another
• Provide additional information on how to serialize/deserialize your model objects

EMF supports transformations in both directions (to and from XSDs). Currently, if you start with an Ecore model, round-tripping to XSD and back to Ecore should be lossless. However, Ecore supports some structures that have no XSD equivalent, such as multiple inheritance. Information will be lost in such cases. Also, if you start with an XSD, not all of the information will be captured in the Ecore model. Therefore, XSD->Ecore->XSD is not a recommended practice as of the Europa release.

This article will focus only on authoring and annotating XSDs, and importing them into Ecore models. However, it is often a useful learning tool to model certain structures first in Ecore, and then export to see the XSD equivalent, including the ecore annotations.

Reasons to use XSDs with EMF

Important Differences between XSDs and Ecore Models

Multiple Inheritance

Global Elements and Attributes

The Transformation Process

1. An EMF Model is created and associated with one or more XSDs
2. When the Wizard finishes, the conversion process creates *.ecore files
3. At this point, EMF will not read your XSDs again. All information needed by EMF has been tucked away somewhere else.
4. If you modify your schemas, the transformation can be performed again from the .genmodel Editor. Affected Ecore models are completely replaced.

Which Parts of an XML Schema are Processed?

Without being told otherwise, EMF will process your Schema, all of its globally declared Elements, and all Types contained therein. Other content (e.g. globally-declared Attributes, AttributeGroups, and Groups) is ignored by EMF. These entries are just macros that Elements and Types can reference, effectively in-lining a copy. If two Types reference the same global Attribute, AttributeGroup, or Element, EMF sees them as two distinct features which happen to have identical information.

What is the Output of the Process

The Process generates, updates, or replaces the following:

1. Ecore Models

   Schemas become Packages; Simple/Complex Types become EClasses, EDataTypes, and EEnums; Elements and Attributes become EStructuralFeatures

   Annotations in your Ecore Models

   Ecore annotations are added in several places to capture the way your model should be serialized/deserialized. These annotations are what enable EMF to read and write XML documents that don't conform to EMF's default serialization format.

   A Helper EClass named "DocumentRoot"

   In certain cases, EMF must create a DocumentRoot class to store additional information.

   Helper EStructuralFeatures, such as feature maps with the suffix "group"

   To handle XSD features like substitution groups, the substitution rule to be used when writing must be known. To handle these cases, your Class' EReferences don't hold onto the actual content, but are instead derived from these "group" references which contains keys in addition to the actual referenced object.

   Your EMF Model

   References to the schemas you imported are kept so that you can invoke a reload later. Generations options are configured the first time with different defaults, under the assumption that you'll be reading and writing to XML files.

Reference Section

Customizing Package Creation

The first thing any ECore model needs is an EPackage. Each XSD imported contains a <schema> element that is mapped to an EPackage. Since the schema element is often the first element, it also defines the namespace prefixes for the entire document.

Here is an example schema declaration, showing both required and optional attributes:

xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" 

Defining the namespace prefix for ecore is necessary when using any ecore markup.

ecore:nsPrefix="cc" 

Setting the nsPrefix determines the prefix used when saving documents.

ecore:package="org.example.core.model.countryclub" 

The package statement determines both the name of the EPackage, and the full name for the java package of the generated implementation.

Customizing Global Elements or Document Content

Schemas contain globally declared elements for the following purposes:

1. To define root elements which can appear in a document
2. To declare a replaceable element, which can be substituted by other global elements
3. For convenience, to define an Element once, and reference it multiple times from other elements

If the element exists for one of the first two reasons, EMF needs to map the element, which results in a reference on the magical DocumentRoot class in the same Package. Otherwise, you can instruct EMF to ignore the element.

ecore:ignore="true" 

Indicates that the element and any anonymous types in it should be ignored.

ecore:name="overrideName" 

Overrides the name assigned to the feature that is created on the DocumentRoot class. The default is to use the element's name.

Customizing Type Creation

DataTypes

<xs:simpleType name="RGB">
	<xs:restriction base="xs:string"/>
</xs:simpleType>

Enums

<xs:simpleType name="Align">
	<xs:restriction base="xs:string">
		<xs:enumeration value="Left"/>
		<xs:enumeration value="Center"/>
		<xs:enumeration value="Right"/>
	</xs:restriction>
</xs:simpleType>

Customizing the creation of Structural Features

Using Substitution Groups

--Hudsonr.us.ibm.com 14:26, 12 June 2007 (EDT)