| |||
Interfaces and Methods - Schemas - FDT Specification - Quicklinks - Abbreviations | |||
| Up to FDT Specification 2.1 FDT Overview 2.2 Where FDT Fits 2.3 General FDT Architecture and Components 2.4 Overview of Objects and Interfaces 2.4.1 The Device Type Manager (DTM) 2.4.2 The Block Type Manager (BTM) 2.4.3 The FDT Frame Application 2.5 Synchronization and Serialization Issues 2.6 Parameter interchange via XML 2.6.1 Examples of usage 2.7 Persistent Storage Story 2.7.1 Persistence Overview 2.7.2 Persistence Interfaces 2.8 Basic features of a session model 2.9 Basic Operation phases 2.9.1 Roles and Access Rights 2.9.2 Operation Phases 2.10 Abstract FDT Object Model 2.11 Fieldbus independent Integration 2.12 Scanning and DTM Assignment | 2.6 Parameter interchange via XMLThe purpose of the parameter interchange via XML is to provide a way to exchange information between Frame Application and DTMs. Typically, in process control systems, multiple client applications like observing, channel assignment, or master configuration, need information about the configuration of a device. XML is not meant to replace proprietary formats; it is meant to provide access to data that is stored in a proprietary format. Data should be stored locally in the fashion that makes the most sense. XML provides an extendable standard to connect FDT components. The data exchange is done via XML documents. Within these documents XML tags are used to delimit pieces of data. XML leaves the interpretation of the data to the application that reads it. To get a common understanding of the exchanged data FDT uses XML schemas for validation. For the data access are standardized tools like the DOM (W3C's Document Object Model) available.
XML schemas are valid XML syntax themselves and are used to validate XML data. They allow the validation of the document structure and the data types of the elements W3C's Document Object Model (DOM) is a standard internal representation of the document structure. It aims to make it easy for programmers to access components and delete, add, or edit their content, attributes and style. In essence, the DOM makes it possible for programmers to write applications that work properly on all browsers and servers, and on all platforms. While programmers may need to use different programming languages, they do not need to change their programming model. An XML parser usually generates the DOM. Microsoft provides such an XML parser.. So the DOM API is free accessible in VC++, Visual Basic and VBScript. The parsing of XML documents with XML schemas guarantees a valid DOM with well-defined elements. The FDT developer should always work with the DOM because
Note: | ||
© 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. | |||