Click or drag to resize

CAEX 3.0 Changes

Differences between CAEX 2.15 and CAEX 3.0.
Edited by Prof. Dr.-Ing. Rainer Drath, Hochschule Pforzheim

This topic contains the following sections:

AmlEngine2.1 supports AutomationML documents based on CAEX 2.15 as well as documents, based on CAEX 3.0. The main differences between these versions are listed below. A document transformation service can be used, to transform CAEX 2.15 documents to CAEX 3.0 documents and back.

Mandatory Attribute RefBaseRoleClassPath

The Attribute RefBaseRoleClassPath defined for RoleRequirements is mandatory in CAEX 3.0

c 1

Back

Native Support of multiple role references

In CAEX 3.0, the CAEX Element InternalElementType can have multiple RoleRequirements assigned.

The MappingObject is moved below the RoleRequirements to define their context.

c 2

Back

AttributeLibrary and AttributeFamiliyType with reference

The AttributeTypeLib is a new library type in CAEX 3.0. It contains AttributeFamilyTypes which can be referenced in Attributes with the RefAttributeType to define the Attribute Type.

c 3
Example
c 4

Back

xs:anyType removed and replaced

The xs:anyType has been replaced with xs:string as value type.

c 5

Back

Native support of nested interfaces

The InterfaceClassType can contain child ExternalInterfaceType elements.

c 6

Back

SuperiorStandardVersion

The new attribute SuperiorStandardVersion allows defining the superior version number of the used AutomationML standard.

c 7

Back

SourceDocumentInformation

In CAEX 3.0, the SourceDocumentInformation shall be used to define information about the data source.

c 8

Back

SourceObjectInformation

The new element SourceObjectInformation can be used to store the original object-ID of the belonging document source and object source.

c 9

Back

Namespace definition

In CAEX 3.0 a namespace definition for the CAEX schema is added.

c 10

Back

Mirror objects

In CAEX 3.0 the Mirror concept is extended to attributes and interfaces but forbids that mirror objects hold individual children or attributes.

c 11

Back

InternalLink

The modeling of InternalLinks has been refined. The RefPartnerSideA and RefPartnerSideB are mandatory, open links are reflected by an empty string.

c 12

Back

Interface Mappings

The InterfaceNameMapping has been replaced by the InterfaceIdMapping. Interface mapping bases on the CAEXObject IDs instead of the CAEXObject names.

c 13

Back