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:
- Mandatory Attribute RefBaseRoleClassPath
- Native Support of multiple role references
- AttributeLibrary and AttributeFamiliyType with reference
- xs:anyType removed and replaced
- Native support of nested interfaces
- SuperiorStandardVersion
- SourceDocumentInformation
- SourceObjectInformation
- Namespace definition
- Mirror objects
- InternalLink
- Interface Mappings
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. An example implementation is provided here.
The Attribute RefBaseRoleClassPath defined for a RoleRequirementsType is mandatory in CAEX 3.0
Back To Top
In CAEX 3.0, the CAEX Element InternalElementType can have multiple RoleRequirements assigned.
The MappingObject is moved below the RoleRequirements to define their context.
Back To Top
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.
\
Attribute Library Example
Back To Top
The xs:anyType has been replaced with xs:string as value type.
Back To Top
The InterfaceClassType can contain child ExternalInterfaceType elements.
Back To Top
The new attribute SuperiorStandardVersion allows defining the superior version number of the used AutomationML standard.
Back To Top
In CAEX 3.0, the SourceDocumentInformation shall be used to define information about the data source.
Back To Top
The new element SourceObjectInformation can be used to store the original object-ID of the belonging document source and object source.
Back To Top
In CAEX 3.0 a namespace definition for the CAEX schema is added.
Back To Top
In CAEX 3.0 the Mirror concept is extended to attributes and external interfaces but forbids that mirror objects hold individual children or attributes.
The modeling of InternalLinks has been refined. The RefPartnerSideA and RefPartnerSideB are mandatory, open links are reflected by an empty string.
The InterfaceNameMapping has been replaced by the InterfaceIdMapping. Interface mapping bases on the CAEXObject IDs instead of the CAEXObject names.
