ISO 20242-4:2011

INTERNATIONAL ISO
STANDARD 20242-4
First edition
2011-12-15
Industrial automation systems and
integration — Service interface for testing
applications —
Part 4:
Device capability profile template
Systèmes d'automatisation industrielle et intégration — Interface de
service pour contrôler les applications —
Partie 4: Modèle de profil de capacité de dispositif

Reference number
©
ISO 2011
©  ISO 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2011 – All rights reserved

Contents Page
Foreword . iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Device capability profile framework . 3
5.1 General . 3
5.2 Creation procedure of DCD, CCD and PID . 4
6 Generic device capability profile template . 6
6.1 General . 6
6.2 Generic DCPT model . 6
6.3 Generic DCPT XML schema . 7
7 Common rules for DCPT . 10
7.1 General . 10
7.2 DCPT header . 11
7.3 Extension of profile template . 12
7.4 Assignment of textual information . 13
7.5 Creating PID . 14
8 Multilingual text elements. 14
Annex A (informative) ASAM GDI device capability profile template . 16
Annex B (informative) Device capability profile templates for manufacturing applications . 35
Annex C (informative) Device capability profile templates for ORiN robot applications . 55
Bibliography . 75

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 20242-4 was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 5, Interoperability, integration, and architectures for enterprise systems and automation
applications.
ISO 20242 consists of the following parts, under the general title Industrial automation systems and
integration — Service interface for testing applications:
 Part 1: Overview
 Part 2: Resource management service interface
 Part 3: Virtual device service interface
 Part 4: Device capability profile template
The following parts are under preparation:
 Part 5: Application program service interface
 Part 6: Conformance test methods, criteria and reports
iv © ISO 2011 – All rights reserved

Introduction
The motivation for ISO 20242 stems from the desire of international automotive industries and their suppliers
to facilitate the integration of automation and measurement devices, and other peripheral components for this
purpose, into computer-based applications. ISO 20242 defines rules for the construction of device drivers and
their behaviour in the context of an automation and/or measurement application.
The main goal of ISO 20242 is to provide users with:
 independence from the computer operating system;
 independence from the device connection technology (device interface/network);
 independence from device suppliers;
 the ability to ensure compatibility between device drivers and connected devices, and their behaviour in
the context of a given computer platform;
 independence from the technological device development in the future.
ISO 20242 does not necessitate the development of new device families or the use of special interface
technologies (networks). It encapsulates a device and its communication interface to make it compatible with
other devices of that kind for a given application.
INTERNATIONAL STANDARD ISO 20242-4:2011(E)

Industrial automation systems and integration — Service
interface for testing applications —
Part 4:
Device capability profile template
1 Scope
This part of ISO 20242 defines the formatting, syntax and semantic rules for describing
 device and coordinator capabilities with XML schema, and
 the configuration of devices with XML.
NOTE This part of ISO 20242 does not address the coordinator configuration, which will be addressed elsewhere in
the ISO 20242 series.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 15745-1, Industrial automation systems and integration — Open systems application integration
framework — Part 1: Generic reference description
ISO 20242-1, Industrial automation systems and integration — Service interface for testing applications —
Part 1: Overview
ISO 20242-3, Industrial automation systems and integration — Service interface for testing applications —
Part 3: Virtual device service interface
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 20242-1, ISO 20242-3 and the
following apply.
3.1
communication object
existing object which may be accessed with a communication function to read or write a value
[ISO 20242-1:2005, definition 2.3]
3.2
coordinator
program with a specified interface to handle the access of an application program to one or more device
drivers and to manage real-time application aspects, synchronization and events
[ISO 20242-1:2005, definition 2.4]
3.3
coordinator capability description
text file containing information about the capabilities of coordinators in a defined format (i.e. structure, syntax)
3.4
device capability description
text file containing information about the capabilities of virtual devices in a defined format (i.e. structure,
syntax)
[ISO 20242-1:2005, definition 2.5]
3.5
device driver
software module providing an ISO 20242-specified interface with service functions to call a platform adapter to
access physical devices
[ISO 20242-2:2010, definition 3.1]
3.6
function object
instance describing one capability of a virtual device
[ISO 20242-3:2011, definition 3.4]
3.7
operation
instance describing one complete procedure
[ISO 20242-3:2011, definition 3.5]
3.8
parameterization instance description
information about the configuration of a coordinator and of virtual devices
3.9
virtual device
representation of one or more physical devices and/or stand-alone software modules that provide an
unambiguous view of the resources of a communication interface
[ISO 20242-3:2011, definition 3.7]
4 Abbreviated terms
CCD Coordinator Capability Description
DCD Device Capability Description
DCPT Device Capability Profile Template
PID Parameterization Instance Description
2 © ISO 2011 – All rights reserved

VD Virtual Device
VDSI Virtual Device Service Interface
XML eXtensible Markup Language
5 Device capability profile framework
5.1 General
For the design of device capability profile templates (DCPTs), device capability descriptions (DCDs) and
coordinator capability descriptions (CCDs), a device capability profile framework as shown in Figure 1 shall be
used. The generic DCPT shall use the generic information exchange profile template of ISO 15745-1 as a
skeleton and shall be constructed in XML schema. The technology-specific DCPT describes technology-
specific capabilities and shall extend the generic DCPT in XML schema. A DCD describes capabilities of
virtual devices in a device driver and shall extend a technology-specific DCPT in XML schema. A CCD
describes capabilities of a coordinator and shall extend a technology-specific DCPT in XML schema. A CCD
imports DCDs for device drivers and describes capabilities of a system. A parameterization instance
description (PID) describes configurations of a coordinator and device drivers. A PID shall be constructed by
instantiations of one CCD and one to many DCDs. The PID is a realization of the information exchange profile
in ISO 15745-1 and can be used together with other profiles of ISO 15745.
<>
ISO15745-1::
GenericDCPT
GenericInformationExchangeProfileTemplate
<>
TechnologySpecificDCPT TechnologySpecificCapability
<>
<> <>
<>
CoordinatorCapability CCD DCD DeviceCapability
<> <>
:InformationExchangeProfile :PID
<>
(from ISO15745-1)
Figure 1 — Class diagram of device capability profile framework
Figure 2 shows the class diagram of CCD and DCD in the framework. The generic DCPT specifies the
aggregate of the generic CCD and generic DCD. The generic CCD describes generic capabilities of a
coordinator. The generic DCD describes generic capabilities of virtual devices. The technology-specific CCD
in a technology-specific DCPT shall inherit the generic CCD and describes technology-specific capabilities of
a coordinator. The technology-specific DCD shall inherit the generic DCD and describes technology-specific
capabilities of virtual devices.
GenericDCPT TechnologySpecificDCPT CCD PID
<>
GenericCCD TechnologySpecificCCD (CoordinatorSpecificCCD) (CCD instance)
0.*
DCD
1.* <>
GenericDCD TechnologySpecificDCD (DeviceSpecificCCD) (DCD instance)

Figure 2 — Class diagram of CCD and DCD
The coordinator-specific CCD shall inherit the technology-specific CCD and describes coordinator-specific
capabilities. The name of a coordinator-specific CCD can be described by the coordinator-specific name. The
device-specific DCD shall inherit the technology-specific DCD and shows device-specific capabilities. The
name of a device-specific DCD can be described by the device-driver-specific name. Between the generic
CCD and the generic DCD, there shall be an aggregation relation as shown in Figure 2. A generic CCD may
contain one to many generic DCDs. Different generic CCDs may use the same generic DCD. Generic DCDs
may exist without a generic CCD. The coordinator-specific CCD and the device-specific DCD have the
aggregation relation from inheritance. A CCD can import the DCDs of device drivers. The CCD instance in a
PID shall be an XML instance of the coordinator-specific CCD XML schema. A DCD instance in a PID shall be
an XML instance of a device-specific DCD XML schema. The XML tag name of a CCD instance shall be the
name of the coordinator-specific CCD. The XML tag name of a DCD instance shall be the name of the device-
specific DCD.
5.2 Creation procedure of DCD, CCD and PID
5.2.1 General
Figure 3 shows the creation procedure of DCD and CCD. Clause 6 defines the generic DCPT in XML schema.
The technology of each service interface defines technology-specific capabilities as a technology-specific
DCPT.
NOTE Technology-specific DCPTs for ASAM GDI, MICX and ORiN are described in Annexes A, B and C.
The vendor of a device, equipment or software module shall extend the technology-specific DCD of the
technology-specific DCPT with the capabilities of the device or equipment. The resulting DCD XML schema
shall be provided together with a device driver. The vendor of a coordinator shall extend the
technology-specific CCD of the technology-specific DCPT with the capabilities of the coordinator. The
resulting CCD XML schema shall be provided with the coordinator. A configuration tool can import the CCD
and the required DCDs to create the PID XML instance with the configuration data for the required application.
The PID shall contain all required instances with names and values. The coordinator can read the PID XML
instance and perform a coordinator setup and the configuration of devices, equipment or software modules.
The configuration shall be performed via the virtual device service interface (VDSI) of the device drivers as
defined in ISO 20242-3.
4 © ISO 2011 – All rights reserved

Device C
Coordinator
Capabilities
Device B
Parameters
Generic Technology- Technology-
Capabilities
Device A and
Specific
DCPT Specific
Capabilities Device
Capabilities
DCPT
(XML Schema) Configurations
(XML Schema)
DCD C
(XML Schema)
DCD B
Technology-
Generic
(XML Schema)
Specific
Extension
DCD
Extension DCD A
DCD
(XML Schema)
Import
Coordinator
Capabilities
Technology-
Generic
CCD PID
Specific
CCD
Extension (XML Schema) (XML Instance)
Extension
CCD
NOTE In this figure, a cylinder shape shows the XML file and a paper shape shows the capability or configuration
information. A solid arrow shows the extension of the XML schema file. A broken arrow shows the injection of capability or
configuration information. A small dotted arrow shows the application of the XML schema.
Figure 3 — Creation procedure of CCD and DCD
5.2.2 Device capability description (DCD)
The DCD shall be an XML schema and shall contain the following:
 identification information of the device driver;
 a description of device capabilities of virtual devices supported by the device driver.
5.2.3 Coordinator capability description (CCD)
The CCD shall be an XML schema and shall contain the following:
 identification information of the coordinator software;
 a description of coordinator capabilities;
 qualification of the supported application program service interface.
5.2.4 Parameterization instance description (PID)
The PID shall be an XML instance and shall contain the following:
 identification information of the PID as information exchange profile of ISO 15745;
 a description of parameterization instances with application-defined names;
 configuration data for the device drivers.
6 Generic device capability profile template
6.1 General
The generic DCPT defines the common structure of DCPT and is not dependent on technology of a service
interface. A technology-specific DCPT extends the generic DCPT.
6.2 Generic DCPT model
The generic DCPT extends the information of the VDSI model in ISO 20242-3. Figure 4 shows the class
structure of the generic DCPT. The information exchange profile is the root class and contains the ISO 15745
header and the ISO 15745 body. The ISO 15745 header describes the identification information of a profile.
The ISO 15745 body contains one or more generic CCDs. The information exchange profile, the ISO 15745
header and the ISO 15745 body are defined in ISO 15745-1.

InformationExchangeProfile
1.*
GenericCCD
0.*
1.*
GenericDCD
1.*
VirtualDevice
0.*
FunctionObject
0.* 0.*
CommunicationObject Operation
Figure 4 — Class diagram of generic DCPT model
The generic CCD is an abstract class that describes generic capabilities of a coordinator. The number of
generic CCDs is equal to the number of coordinators.
A generic CCD contains generic DCDs. The generic DCD is an abstract class that describes generic
capabilities of device drivers. The number of generic DCDs is equal to the number of device drivers.
6 © ISO 2011 – All rights reserved

A generic DCD contains virtual devices. The virtual device is an abstract class that describes generic
capabilities of virtual devices.
A virtual device contains function objects. The function object is an abstract class that describes generic
capabilities of functions of virtual devices.
A function object contains communication objects and operations.
The communication object is an abstract class that describes generic capabilities of communication objects
defined in ISO 20242-3.
The operation is an abstract class that describes generic capabilities of operations defined in ISO 20242-3.
6.3 Generic DCPT XML schema
The generic DCPT XML schema in Figure 5 describes the information exchange profile template. The generic
DCPT XML schema includes the generic CCD XML schema and refers to the generic CCD element. The
DCPT header used in the annotation part of Figure 5 is defined in 7.2.

xmlns="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
targetNamespace="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
elementFormDefault="qualified">




GenericDCPT
1.0
Generic DCPT
GenericDCPT.xsd
2011-07-01























fixed="InformationExchange"/>
minOccurs="0"/>
minOccurs="0"/>

fixed="CSI"
minOccurs="0"        maxOccurs="unbounded"/>





fixed="1"/>
fixed="1"/>
fixed="None"/>















































Figure 5 — Generic DCPT XML schema
8 © ISO 2011 – All rights reserved

The generic CCD XML schema in Figure 6 describes the generic CCD template. The generic CCD XML
schema includes the generic DCD XML schema and refers to the generic DCD element. The DCPT header
used in the annotation part of Figure 5 is defined in 7.2.

xmlns="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
targetNamespace="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
elementFormDefault="qualified">




GenericCCD
1.0
Generic CCD
GenericCCD.xsd
2011-07-01














use="required"  fixed="CCD"/>


Figure 6 — Generic CCD XML schema
The generic DCD XML schema in Figure 7 describes the generic DCD template. It includes templates of the
virtual device, the function object, the communication object and the operation. The DCPT header used in the
annotation part of Figure 5 is defined in 7.2.

xmlns="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
targetNamespace="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
elementFormDefault="qualified">




GenericDCD
1.0
Generic DCD
GenericDCD.xsd
2009-03-16




type="GenericDCDType" abstract="true"/>






use="required"   fixed="DCD"/>

type="VirtualDeviceType" abstract="true"/>






use="required"   fixed="MODULE"/>

type="FunctionObjectType" abstract="true"/>







use="required"   fixed="INTERFACE"/>

type="CommunicationObjectType" abstract="true"/>




type="OperationType" abstract="true"/>



use="required"   fixed="OPERATION"/>


Figure 7 — Generic DCD XML schema
7 Common rules for DCPT
7.1 General
The common rules shall be used for the extension of DCPT. Names of XML elements (tags) may be defined
corresponding to a coordinator and to devices. Any attributes and elements may be added for a special
purpose that is not addressed by this part of ISO 20242.
10 © ISO 2011 – All rights reserved

7.2 DCPT header
The identification information of a DCD and CCD is described with xsd:appinfo element of xsd:annotation in
XML Schema. The DCPT header contains the attributes specified in Table 1. The XML data types used in
[9]
Table 1 are defined in REC-xmlschema-2-20041028 .
Table 1 — DCPT header elements
Element Description
DCPTIdentification DCPT identification.
XML data type : string
EXAMPLE ABC-123-XX
DCPTRevision Revision of the DCPT.
XML data type : string
EXAMPLE 2.34
DCPTName Descriptive name of the DCPT.
XML data type : string
EXAMPLE DCD Thermometer
DCPTSource Identification of the DCPT developer.
XML data type : string
EXAMPLE ASAM
DCPTClassID Identification of the profile class.
XML data type : string
Valid profile classes are:
GenericDCPT
TechnlogySpecificDCPT
CCD
DCD
EXAMPLE DCD
DCPTDate The release date of this revision of the profile in CCYY-MM-DD format.
XML data type : date
EXAMPLE 2011-09-21
AdditionalInformation Location of diagrams/additional information for the profile.
This field is optional.
XML data type : anyURI
EXAMPLE http://www.asam.net
ISO20242Reference Identifies the part of ISO 20242 (see ISO20242Part), together with its edition (see
ISO20242Edition) and the technology (see Technology).
Multiple references are allowed, e.g. for a device with more than one communication interface.
ISO20242Edition Edition of the referenced part of ISO 20242.
XML data type : positiveInteger
EXAMPLE 1
Technology Name of the referenced technology.
XML data type : string
If no ISO 20242 technology is applicable, then the value “None” shall be used.
EXAMPLE None
The XML Schema is described in Figure 8.

































Figure 8 — DCPT header XML schema
7.3 Extension of profile template
7.3.1 Creating DCD
A DCD contains device type specific elements which are derived from technology-specific elements and
substitute the abstract elements of the generic DCPT.
NOTE This part of ISO 20242 does not require the import of the generic or technology-specific XML schemas into
device-specific DCDs. However, independently created DCDs will need to contain the same information as DCDs with
imported XML schemas of this part of ISO 20242.
The element names (tags) for the DCD may be specific to device types. The elements shall be supplemented
by an attribute named "category" containing a keyword for the type of this element as defined in Table 2. The
content of this attribute is a reference to the corresponding element of generic DCPT.
12 © ISO 2011 – All rights reserved

Table 2 — Keywords for type of element
Element of generic DCPT Contents of XML attribute "category"
GenericCCD CCD
GenericDCD DCD
VirtualDevice MODULE
FunctionObject INTERFACE
Operation OPERATION
Additional elements may get specific contents for attribute "category" in technology-specific annexes.
7.3.2 Assignment of device-specific elements
A device-specific DCD element contains one or more device-specific virtual device elements which shall not
belong to any other device-specific DCD element.
A device-specific VD element is the substitute for the generic VD element and contains zero or more
device-specific function object elements which shall not belong to any other device-specific VD element.
A device-specific function object element is the substitute for the generic function object element and contains
zero or more device-specific communication object elements which shall not belong to any other
device-specific function object element. Also, the device-specific function object element contains zero or
more device-specific operation elements which shall not belong to any other device-specific function object
element.
7.3.3 Instantiation order for VDSI
For the creation of virtual devices, function objects and communication objects via services VDSI_Initiate,
VDSI_CreateFuncObject and VDSI_CreateCommObject of ISO 20242-3, an extra XML attribute, named
"initOrder", shall supplement virtual device elements, function object elements and communication object
elements. This XML attribute is of type unsignedInt as defined in XML schema and contains the order for
creating the instance of the element via VDSI.
7.3.4 Parameterization of communication objects
If a value is assigned to a communication object, this value shall be written by the coordinator with the
VDSI_Write service of VDSI. It is possible to define an extra order for writing values to communication objects.
This is done using the XML attribute named "initOrder".
NOTE Annex A provides an example that shows how a communication object can be written multiple times.
7.4 Assignment of textual information
Any element of DCPT may have two kinds of textual information attached. A short message and a long
message. These messages shall be defined in an extra XML instance and numbered as described in Clause 8.
Message numbering is hierarchically organized in numbered text areas with numbered text entries. The text
numbers are assigned to DCPT elements by optional XML attributes of type xsd:unsignedInt described in
Table 3.
Table 3 — XML attributes for text assignment
XML attribute name Description of content
areaMsg number of area of short message
infMsg number of short message
areaText number of area of long message
infText number of long message
7.5 Creating PID
7.5.1 XML instances of CCD classes
An XML instance of a coordinator-specific CCD class describes features of a coordinator. The CCD instance
contains one or more XML instances of DCD classes.
7.5.2 XML instances of DCD classes
An XML instance of a device-specific DCD class describes a device driver that is an entity of a VDSI of
ISO 20242-3. The DCD instance contains one or more XML instances of device-specific VD classes.
7.5.3 XML instances of VD classes
An XML instance of a device-specific VD class describes an instance of a VD created by service VDSI_Initiate
of VDSI. There may be multiple instances of one device-specific VD class. The instance of a VD contains zero
or more instances of device-specific function object classes.
7.5.4 XML instances of function object classes
An XML instance of a device-specific function object class describes an instance of a function object created
by service VDSI_CreateFuncObject of VDSI. There may be multiple instances of one device-specific function
object class. The instance of a function object contains zero or more instances of device-specific
communication object classes and/or zero or more instances of device-specific operation classes.
7.5.5 XML instances of communication object classes
An XML instance of a device-specific communication object class describes an instance of a communication
object created by service VDSI_CreateCommObject of VDSI. There shall be only one instance of one
concrete communication object class.
7.5.6 XML instances of operation classes
An XML instance of a device-specific operation class describes an instance of an operation created implicitly
with the instantiation of the associated function object class via VDSI. There shall be only one instance of one
device-specific operation class.
8 Multilingual text elements
For textual information, this part of ISO 20242 defines three kinds of messages:
 short information messages;
 long information messages;
 error messages.
14 © ISO 2011 – All rights reserved

These messages shall be contained in an XML instance with a structure defined in Figure 9.

elementFormDefault="qualified">




















minOccurs="0" maxOccurs="unbounded"/>




minOccurs="0" maxOccurs="unbounded"/>











Figure 9 — Device information text XML schema
Long information messages are placed in XML element , short information messages are
placed in element and error messages are placed in element .
Language-specific messages are placed in XML elements with the XML attribute "lang" for identifying
the language.
Annex A
(informative)
ASAM GDI device capability profile template
A.1 General
The ASAM GDI (Generic Device Interface) specifies a general device interface for testing applications. This
[3]
annex defines the GDI-specific device capability profile template of ASAM GDI Version 4.4 , and provides
examples of DCD, CCD and PID.
A.2 GDI-specific profile model
A.2.1 General
The GDI-specific profile model contains all information that is necessary for the device capability description
and all information that is necessary for parameterization. Figure A.1 shows the class diagram of GDI-specific
device capability profile template.

Generic DCPT
GenericCCD GDI_CCD
1.*
0,1
GDI_DCD GDI_Header
GenericCCD
1.*
VirtualDevice GDI_Module
CreateParameter
0.*
FunctionObject GDI_Interface
0,1
OperationInParameter
0.* 0.*
CommunicationObject Operation GDI_Operation
OperationOutParameter
0,1
AttributeReadWrite AttributeReadOnly Parameter

Figure A.1 — Class diagram of GDI-specific DCPT model
16 © ISO 2011 – All rights reserved

A.2.2 GDI_CCD
The GDI_CCD class shows the capabilities of the GDI-specific coordinator. It inherits the GenericCCD class
and is an abstract class. A coordinator-specific CCD class inherits it and defines capabilities of the specific
coordinator.
A.2.3 GDI_DCD
The GDI_DCD class shows the capabilities of the GDI-specific device driver. It inherits the GenericDCD class
and is an abstract class. A device-specific GDI_DCD class inherits it and defines capabilities of the specific
device driver.
A.2.4 GDI_Header
The GDI_Header class contains additional information, which is used for the instantiation of the device driver.
The elements of GDI_Header are described in Table A.1. A definition of GDI_Header is also given in
GDIcommon.xsd in A.6.2.
Table A.1 — Elements of GDI_Header
Element of GDI_Header Element type Description
DCD_Version xsd:unsignedInt A number for the DCD version
DeviceVersion xsd:unsignedInt A number for the device version
DriverName xsd:string The name of the driver
DriverVersion xsd:unsignedInt A number for the driver version
Factory xsd:string The name of the manufacturer
DIT xsd:string The name of the XML text file
GDI_Version Major xsd:unsignedByte Major version number
Minor xsd:unsignedByte Minor version number
Revision xsd:unsignedByte Revision number

A.2.5 GDI_Module
The GDI_Module class shows capabilities of the GDI-specific virtual device. It inherits the VirtualDevice class
and is an abstract class. A device-specific GDI_Module class inherits it and defines the capabilities of the
specific virtual device. A GDI_Module class may have a CreateParameter and is identified by a number
contained in an additional XML attribute named "moduleId" of type "xsd:unsignedShort".
A.2.6 GDI_Interface
The GDI_Interface class shows capabilities of function objects of the GDI-specific virtual device. It inherits the
FunctionObject class and is an abstract class. A device-specific GDI_Interface class inherits it and defines the
capabilities of the device-specific function object. A GDI_Interface class may have a CreateParameter and is
identified by a number contained in an additional XML
...