14.1 Identification Transformation

In order to transform protocol specific XML documents to protocol independent XML documents, protocol specific XSL Transformations are to be used. Syntax in this document: FDTxxxIdentTransformation.xsl where xxx is the protocol identification.

Examples:

FDTHARTIdentTransformation.xsl
FDTProfibusIdentTransformation.xsl

Frame Application has to copy this xsl file provided by Communication-DTMs into the protocol specific schema path and perform it to get protocol independent formatted identification documents, which can be validated using DTM[Scan|DeviceType]Schema.xml. Hint:
It is strongly recommended for Communication-DTMs to use the official transformation style sheets from FDT-JIG. Refer to best practice document for more information about tasks and rules.

The left picture describes the role of the XSLT for HART for the scan workflow. The XSLT is processed by a Frame Application. See XSLT implementations in protocol specific chapter. The right picture describes the role of the XSLT for HART for the DTM device identification workflow.

Such a protocol specific transformation style sheet processes protocol specific XML documents returned by OnScanResponse() as well as GetDeviceIdentificationInformation() and creates protocol independent XML-documents.

All protocol specific data formats are converted to strings.
All defined attributes with semantic meaning are transformed to defined protocol independent semantic tags.
The semantic tag mapping rules are defined for each protocol in the corresponding protocol specific appendix.

© by M&M Software GmbH, parts of this website taken from FDT Interface Specification Version 1.2.1, © by FDT Group, AISBL.
This website is published for support of M&M products as granted in license conditions, chapter 2.1.
Last updated 2015-02-05 15:17
Email: FDT Technical Support Line.