Generate GML Application Schema

After you have created a GML model using the built-in MDG Technology for GML, you can generate GML Application Schema from the model Package.

Access     Extensions | GML | Generate GML Application Schema

Generate GML Application Schema

Field/Option/Button

Action

See also

Source Package

Displays the name of the selected «Application Schema» stereotyped package.

 

 

Directory

Type in or browse for the directory into which the application schema file is to be generated.

 

 

GML Version

Click on the drop-down arrow and select the version of the GML Application Schema. Currently versions 3.3 and 3.2.1 are supported.

 

 

XML Encoding

Click on the drop-down arrow and select the XML encoding scheme to be used.

 

 

Ignore Element and Property Visibility

Click on this option to include all Classes, Attributes and Association End roles in the GML Application Schema, irrespective of their visibility (or Scope). Otherwise, only those with Public visibility will be considered for generation.

(Element) Details

General Properties of Attributes

Source Role

 

Stylesheet

(Optional) Select an XSL stylesheet to post-process the Schema before saving it to file.

Import the required stylesheet into the project through the Resources window before selecting it in this field.

 

Resources

Application Schema(s)

Lists all the Application Schema packages under the selected source package.

Click on a package to display its details, as well as any of its child «Leaf» stereotyped package details, in the Package Details panel.

GML Application Schema will not be generated for any package in the list that is unchecked.

 

 

Package Details

Against each of the child «Application Schema» and (optionally) «Leaf» stereotyped packages (if any), enter a filename. To do this, double-click on the package name in the list and, on the Package Details dialog, review or complete the fields:

 

Field/Option/Button

Action

Package

The selected package name.

 

Stereotype

The stereotype of the selected package.

 

Filename

Optional for a «Leaf» stereotyped package.

Click on the [ ... ] button and type the name of the .xsd file into which the GML Application Schema is to be generated.

The filename must be in the same file path as selected in the Directory field on the Generate GML Application Schema dialog.

 

Namespace

Not required for a «Leaf» stereotyped package.

Type in the namespace for the selected package.

 

Namespace Prefix

Not required for a «Leaf» stereotyped package.

Type the abbreviated value that represents the Namespace.

 

 

The value of the Filename field will be saved as the value of the tag xsdDocument on the package
The value of the Namespace field will be saved as the value of the tag targetNamespace on the package
The value of the field Namespace Prefix will be saved as the value of the tag xmlns on the package
 

 

Generate

Generate the GML Application Schema for each of the checked packages in the Package Details panel.

 

 

View Schema

Display the generated GML Application Schema for the selected package in the Package Details panel.

 

 

Close

Close the Generate GML Application Schema dialog.

 

 

Help

Display this Help topic.

 

 

Notes

The MDG Technology for GML is available in the Professional, Corporate, Business and Software Engineering, System Engineering and Ultimate editions of Enterprise Architect
A «CodeList» stereotyped Class with the tag asDictionary set to true will be exported as a separate XML file to the directory specified in the Directory field, with the filename CodeList_<classname>.xml  (where <classname> is the name of the «CodeList» stereotyped Class)
Using the configurable file GMLStereotypes.xml in the Sparx Systems > EA > Config > GML folder, you can specify aliases for the standard GML stereotypes; the GML Application Schema Generator will also consider these aliases during Schema generation
Association Class is specific to GML 3.3; when generating GML 3.2.1 Application Schema, the Association and Class of an Association Class  are treated as separate entities

Learn more