Commits (16)
Copyright 2019, oneM2M Partners Type 1
Copyright 2020, oneM2M Partners Type 1
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
......
......@@ -12,12 +12,12 @@ Any contributions made to the Smart Device Template format must comply with the
![](SDT/schema4.0/docs/images/SDT_simplified.png)
The Smart Device Template (SDT) is a template which is used to model the capabilities, actions and events of connected devices. The intent of the SDT is to be able to model any type of connected device using a well accepted and standardised format. The main application of SDT is to enable a uniformly structured Application Programmer's Interface (API) to applications that need to interact with connected devices. Usually, these applications would communicate to devices using an abstraction layer as an intermediary logic. The abstraction layer "hides" the technology-specific, native language format of devices of different technology type from the applications.
The Smart Device Template (SDT) is a template method which is used to model the capabilities, actions and events of connected devices. The intent of the SDT is to be able to model any type of connected device using a well accepted and standardised format. The main application of SDT is to enable a uniformly structured Application Programmer's Interface (API) for applications that need to interact with connected devices. Usually, these applications would communicate to devices using an abstraction or service layer, or cloud platform as an intermediary logic. This layer usually "hides" the technology-specific, native language format of devices of different technology type from the applications.
[Read the full Introduction.](SDT/schema4.0/docs/Introduction.md)
## Quick Links
- [UML Diagram of the SDT 4.0](SDT/schema4.0/docs/UML%20Diagram.md) ([Umlet source](SDT/schema4.0/docs/SDT_UML.uxf)) : This UML diagram describes the various components of the SDT and their relations.
- [UML Diagrams of the SDT 4.0](SDT/schema4.0/docs/UML%20Diagram.md) ([Umlet source](SDT/schema4.0/docs/SDT_UML.uxf)) : These UML diagram describes the various components of the SDT and their relations.
- ['domain.xsd' Version 4.0](SDT/schema4.0/src/domain.xsd) : This is the XSD schema file that defines the SDT XML Schema.
......
......@@ -13,6 +13,7 @@
- Added ``optional`` attribute to ``<Arg>``.
- Added ``default`` attribute to ``<Arg>``.
- Added ``default`` attribute to ``<DataPoint``.
- Added `minOccurs`` and ``maxOccurs`` to SubDevice and ModuleClass
- Unified all component identifiers, names etc to XSD type ``name``.
- Introduced JSON serialization guidelines.
- Changed case of ``<Imports>`` element.
......
......@@ -7,29 +7,30 @@
1. [ModuleClasses Definition](#echonetExampleMC)
2. [DeviceClass Definition](#echonetExampleDC)
3. [The full SDT](#echonetExampleFull)
3. [More examples](#moreExamples)
<a name="simpleExample"></a>
## A simple SDT example
The following example shows a very simple device that represents a light that can be switched on and off. It contains just a single ModuleClass "Switch", which contains a single boolean data point "status" to control the on/off status of the device.
The following example shows a very simple device that represents a light that can be switched on and off. It contains just a single [ModuleClass](SDT_Components.md#ModuleClass) "Switch", which contains a single boolean [data point](SDT_Components.md#DataPoint) "status" to control the on/off status of the device.
It is a stand-alone definition without using previously defined ModuleClasses. A more sophisticated use is presented in the next example.
It is a stand-alone definition without using previously defined [ModuleClasses](SDT_Components.md#ModuleClass). A more sophisticated use is presented in the next example.
The structure and the according SDT looks like this:
|SimpleExample.xml | |
|:--------------|-|
|Namespace information | SimpleExample |
|DeviceClasses |<ul><li>Light</li><ul><li>Switch<ul><li>status</li></ul></li></ul></ul>|
|DeviceClasses |<ul><li>Light ([DeviceClass](SDT_Components.md#DeviceClass))</li><ul><li>Switch ([ModuleClass](SDT_Components.md#ModuleClass))<ul><li>status ([DataPoint](SDT_Components.md#DataPoint)</li></ul></li></ul></ul>|
The following code section shows the fully integrated template. The source code can be found in [SimpleExample.xml](../test/SimpleExample.xml) in the "test" directory.
The following code section shows the fully integrated template. The source code can be found in [SimpleExample.xml](../test/SimpleExample.xml) in the [test](../test) directory.
```xml
<?xml version="1.0" encoding="iso-8859-1"?>
<Domain xmlns="http://www.onem2m.org/xml/sdt/4.0" id="SimpleExample" >
<DeviceClasses>
<DeviceClass id="Light">
<DeviceClass name="Light">
<Doc>This is a very simple device representing a light.</Doc>
<ModuleClasses>
<ModuleClass name="Switch">
......@@ -37,7 +38,7 @@ The following code section shows the fully integrated template. The source code
<DataPoint name="status" readable="true" writable="true">
<Doc>This property indicates the ON/OFF status.</Doc>
<DataType>
<SimpleType type="boolean" />
<Simple type="boolean" />
</DataType>
</DataPoint>
</Data>
......@@ -51,7 +52,7 @@ The following code section shows the fully integrated template. The source code
<a name="echonetExample"></a>
## A more sophisticated example
In the ideal case, a large organization or SDO would define a widely-applicable set of [ModuleClasses](SDT_Components.md#ModuleClass), each of which could be used as needed to compose the description of a complex device. In order to show the approach, this section will create a few example ModuleClasses based on - or inspired by - features in the Echonet Lite protocol. Please note that the examples shown in this document are very "cut down" and by no means represent a true representation of Echonet Lite[^echonet].
In the ideal case, a large organization or SDO would define a widely-applicable set of [ModuleClasses](SDT_Components.md#ModuleClass), each of which could be used as needed to compose the description of a complex device. In order to show the approach, this section will create a few example [ModuleClasses](SDT_Components.md#ModuleClass) based on - or inspired by - features in the Echonet Lite protocol. Please note that the examples shown in this document are very "cut down" and by no means represent a true representation of Echonet Lite[^echonet].
[^echonet]: The Echonet Consortium has standardized their specifications within IEC/ISO (IEC62394, ISO/IEC24767-1, ISO/IEC24767-2, IEC62480, ISO/IEC14543-4-1, ISO/IEC14543-4-2, IEC62457) and they provide a comprehensive collection of various types of home appliances relevant to SmartGrid applications as ECHONET Device objects (see [https://echonet.jp/spec_object_rf_en/](https://echonet.jp/spec_object_rf_en/) ).
......@@ -59,17 +60,17 @@ The source code can be found in [EchonetLiteExamples.xml](../test/EchonetLiteExa
<a name="echonetExampleMC"></a>
### ModuleClasses
For the example in this section, to show re-use of ModuleClass definitions, two complex devices are chosen which have some common features and hence could be expected to both use some of the same ModuleClasses: an air conditioner and a washing machine.
For the example in this section, to show re-use of [ModuleClass](SDT_Components.md#ModuleClass) definitions, two complex devices are chosen which have some common features and hence could be expected to both use some of the same [ModuleClasses](SDT_Components.md#ModuleClass): an air conditioner and a washing machine.
|Functionality | Air Conditioner | Washing Machine |
|:------------|:----------------|:----------------|
|operationStatus |operates on/off |operates on/off |
|measuredCumulativePowerConsumption |the cumulative power consumption |the cumulative power consumption |
|installationLocation |this sets/reads a string text describing the location (room) of the air-conditioner |this sets/reads a string text describing the location (room) of the washing machine |
|setTimer |(not applicable. there is no preset start for an air-conditioner) |This sets/reads use the on/off timer |
|setTimer |not applicable (there is no preset start for an air-conditioner) |This sets/reads use the on/off timer |
|temperatureSensorDataPoints | this reads the measured temperature | this reads the measured temperature |
Based on the simplified example above, the two appliances will need the ModuleClasses below:
Based on the simplified example above, the two appliances will need the [ModuleClasses](SDT_Components.md#ModuleClass) below:
- *air-conditioner*: operationStatus, measuredCumulativePowerConsumption, installationLocation;
- *washing-machine*: operationStatus, measuredCumulativePowerConsumption, setTimer, temperatureSensorDataPoints.
......@@ -80,7 +81,7 @@ Based on the simplified example above, the two appliances will need the ModuleCl
<DataPoint name="operationStatus" writable="true">
<Doc>This property sets/reads the ON/OFF status.</Doc>
<DataType>
<SimpleType type="boolean"/>
<Simple type="boolean"/>
</DataType>
</DataPoint>
</Data>
......@@ -96,7 +97,7 @@ Based on the simplified example above, the two appliances will need the ModuleCl
<DataPoint name="measuredCumulativePowerConsumption" writable="false">
<Doc>This indicates cumulative power consumption of the device in increments of 0.001kWh.</Doc>
<DataType>
<SimpleType type="integer"/>
<Simple type="integer"/>
</DataType>
</DataPoint>
</Data>
......@@ -107,7 +108,7 @@ Based on the simplified example above, the two appliances will need the ModuleCl
<DataPoint name="installationLocation" writable="true">
<Doc>This property indicates the installation location</Doc>
<DataType>
<SimpleType type="string"/>
<Simple type="string"/>
</DataType>
</DataPoint>
</Data>
......@@ -121,7 +122,7 @@ Based on the simplified example above, the two appliances will need the ModuleCl
<DataPoint name="measuredTemperatureValue" readable="true" writable="false">
<Doc>This property indicates the measured temperature value in units of 0.1C.</Doc>
<DataType unitOfMeasure="celsius">
<SimpleType type="integer" />
<Simple type="integer" />
</DataType>
</DataPoint>
</Data>
......@@ -131,9 +132,9 @@ Based on the simplified example above, the two appliances will need the ModuleCl
<a name="echonetExampleDC"></a>
### DeviceClass
To define a device one would now reference those ModuleClass definitions in a new DeviceClass. For the sake of simplicity only the "SimpleWashingMachine" is implemented here.
To define a device one would now reference those [ModuleClass](SDT_Components.md#ModuleClass) definitions in a new [DeviceClass](SDT_Components.md#DeviceClass). For the sake of simplicity only the "SimpleWashingMachine" is implemented here.
In addition to the previously defined ModuleClasses this "SimpleWashingMachine" DeviceClass extends the existing ModuleClass "operationStatus" with an event. It also adds a new ModuleClass "washingMachineDataPoints" with model-specific DataPoints.
In addition to the previously defined [ModuleClasses](SDT_Components.md#ModuleClass) this "SimpleWashingMachine" [DeviceClass](SDT_Components.md#DeviceClass) extends the existing [ModuleClass](SDT_Components.md#ModuleClass) "operationStatus" with an event. It also adds a new [ModuleClass](SDT_Components.md#ModuleClass) "washingMachineDataPoints" with model-specific [DataPoints](SDT_Components.md#DataPoint).
At the beginning of the definition some device Properties are defined.
......@@ -144,10 +145,10 @@ At the beginning of the definition some device Properties are defined.
<Properties>
<Property name="Name" value="washing machine">
<SimpleType type="string" />
<Simple type="string" />
</Property>
<Property name="Vendor" value="ACME">
<SimpleType type="string" />
<Simple type="string" />
</Property>
</Properties>
......@@ -190,25 +191,25 @@ At the beginning of the definition some device Properties are defined.
<DataPoint name="door_CoverOpen_CloseStatus" readable="true" writable="false">
<Doc>This property indicates whether the door/cover is open or closed.</Doc>
<DataType>
<SimpleType type="boolean" />
<Simple type="boolean" />
</DataType>
</DataPoint>
<DataPoint name="washingMachineSetting" readable="true" writable="true">
<Doc>Washing machine setting</Doc>
<DataType>
<SimpleType type="string" />
<Simple type="string" />
</DataType>
</DataPoint>
<DataPoint name="currentStageOfWashingCycle" readable="true" writable="false">
<Doc>This property indicates the current stage of the washing cycle.</Doc>
<DataType>
<SimpleType type="string" />
<Simple type="string" />
</DataType>
</DataPoint>
<DataPoint name="timeRemainingToCompleteWashingCycle" readable="true" writable="false">
<Doc>This property indicates the time remaining to complete the current washing cycle in the HH:MM:SS format.</Doc>
<DataType>
<SimpleType type="time" />
<Simple type="time" />
</DataType>
</DataPoint>
......@@ -220,19 +221,19 @@ At the beginning of the definition some device Properties are defined.
<DataPoint name="onTimerReservationSetting" readable="true" writable="true">
<Doc>Reservation ON/OFF</Doc>
<DataType>
<SimpleType type="boolean" />
<Simple type="boolean" />
</DataType>
</DataPoint>
<DataPoint name="onTimerSetting" readable="true" writable="true">
<Doc>Timer value (HH:MM)</Doc>
<DataType>
<SimpleType type="time" />
<Simple type="time" />
</DataType>
</DataPoint>
<DataPoint name="relativeTimeBasedOnTimerSetting" readable="true" writable="true">
<Doc>Timer value (HH:MM)</Doc>
<DataType>
<SimpleType type="time" />
<Simple type="time" />
</DataType>
</DataPoint>
</Data>
......@@ -249,8 +250,8 @@ The structure and the according SDT now looks like this:
|EchonetLiteExamples.xml | |
|:--------------|-|
|Namespace information | example.based.on.echonetLite |
|ModuleClasses |<ul><li>operationStatus<ul><li>operationStatus</li></ul></li><li>measuredCumulativePowerConsumption<ul><li>measuredInstantaneousPowerConsumption</li></ul></li><li>installationLocation<ul><li>installationLocation</li></ul></li><li>temperatureSensorDataPoints<ul><li>measuredTemperatureValue</li></ul></li></ul>|
|DeviceClasses |<ul><li>SimpleWaschingMachine</li><ul><li>installationLocation --> installationLocation</li><li>measuredCumulativePowerConsumption --> measuredCumulativePowerConsumption</li><li>temperatureSensorDataPoints --> temperatureSensorDataPoints</li><li>operationStatus --> washingMachineOperationStatus</li><li>washingMachineDataPoints</li><ul><li>door_CoverOpen_CloseStatus</li><li>washingMachineSetting</li><li>currentStageOfWashingCycle</li><li>timeRemainingToCompleteWashingCycle</li><li>onTimerReservationSetting</li><li>onTimerSetting</li><li>relativeTimeBasedOnTimerSetting</li></ul></ul></ul>|
|[ModuleClasses](SDT_Components.md#ModuleClass) |<ul><li>operationStatus<ul><li>operationStatus</li></ul></li><li>measuredCumulativePowerConsumption<ul><li>measuredInstantaneousPowerConsumption</li></ul></li><li>installationLocation<ul><li>installationLocation</li></ul></li><li>temperatureSensorDataPoints<ul><li>measuredTemperatureValue</li></ul></li></ul>|
|[DeviceClasses](SDT_Components.md#DeviceClass) |<ul><li>SimpleWaschingMachine</li><ul><li>installationLocation --> installationLocation</li><li>measuredCumulativePowerConsumption --> measuredCumulativePowerConsumption</li><li>temperatureSensorDataPoints --> temperatureSensorDataPoints</li><li>operationStatus --> washingMachineOperationStatus</li><li>washingMachineDataPoints</li><ul><li>door_CoverOpen_CloseStatus</li><li>washingMachineSetting</li><li>currentStageOfWashingCycle</li><li>timeRemainingToCompleteWashingCycle</li><li>onTimerReservationSetting</li><li>onTimerSetting</li><li>relativeTimeBasedOnTimerSetting</li></ul></ul></ul>|
The following code section shows the fully integrated template.
......@@ -274,7 +275,7 @@ The following code section shows the fully integrated template.
<DataPoint name="operationStatus" readable="true" writable="true">
<Doc>This property indicates the ON/OFF status.</Doc>
<DataType>
<SimpleType type="boolean" />
<Simple type="boolean" />
</DataType>
</DataPoint>
</Data>
......@@ -287,7 +288,7 @@ The following code section shows the fully integrated template.
<DataPoint name="installationLocation" readable="true" writable="true">
<Doc>This property indicates the installation location</Doc>
<DataType>
<SimpleType type="string" />
<Simple type="string" />
</DataType>
</DataPoint>
</Data>
......@@ -305,7 +306,7 @@ The following code section shows the fully integrated template.
<DataPoint name="measuredInstantaneousPowerConsumption" readable="true" writable="false">
<Doc>This property indicates the instantaneous power consumption of the device in watts.</Doc>
<DataType unitOfMeasure="watts">
<SimpleType type="integer" />
<Simple type="integer" />
</DataType>
</DataPoint>
</Data>
......@@ -316,7 +317,7 @@ The following code section shows the fully integrated template.
<DataPoint name="measuredTemperatureValue" readable="true" writable="false">
<Doc>This property indicates the measured temperature value in units of 0.1C.</Doc>
<DataType unitOfMeasure="celsius">
<SimpleType type="integer" />
<Simple type="integer" />
</DataType>
</DataPoint>
</Data>
......@@ -333,10 +334,10 @@ The following code section shows the fully integrated template.
<Properties>
<Property name="Name" value="washing machine">
<SimpleType type="string" />
<Simple type="string" />
</Property>
<Property name="Vendor" value="ACME">
<SimpleType type="string" />
<Simple type="string" />
</Property>
</Properties>
......@@ -381,25 +382,25 @@ The following code section shows the fully integrated template.
<DataPoint name="door_CoverOpen_CloseStatus" readable="true" writable="false">
<Doc>This property indicates whether the door/cover is open or closed.</Doc>
<DataType>
<SimpleType type="boolean" />
<Simple type="boolean" />
</DataType>
</DataPoint>
<DataPoint name="washingMachineSetting" readable="true" writable="true">
<Doc>Washing machine setting</Doc>
<DataType>
<SimpleType type="string" />
<Simple type="string" />
</DataType>
</DataPoint>
<DataPoint name="currentStageOfWashingCycle" readable="true" writable="false">
<Doc>This property indicates the current stage of the washing cycle.</Doc>
<DataType>
<SimpleType type="string" />
<Simple type="string" />
</DataType>
</DataPoint>
<DataPoint name="timeRemainingToCompleteWashingCycle" readable="true" writable="false">
<Doc>This property indicates the time remaining to complete the current washing cycle in the HH:MM:SS format.</Doc>
<DataType>
<SimpleType type="time" />
<Simple type="time" />
</DataType>
</DataPoint>
......@@ -411,19 +412,19 @@ The following code section shows the fully integrated template.
<DataPoint name="onTimerReservationSetting" readable="true" writable="true">
<Doc>Reservation ON/OFF</Doc>
<DataType>
<SimpleType type="boolean" />
<Simple type="boolean" />
</DataType>
</DataPoint>
<DataPoint name="onTimerSetting" readable="true" writable="true">
<Doc>Timer value (HH:MM)</Doc>
<DataType>
<SimpleType type="time" />
<Simple type="time" />
</DataType>
</DataPoint>
<DataPoint name="relativeTimeBasedOnTimerSetting" readable="true" writable="true">
<Doc>Timer value (HH:MM)</Doc>
<DataType>
<SimpleType type="time" />
<Simple type="time" />
</DataType>
</DataPoint>
</Data>
......@@ -433,6 +434,8 @@ The following code section shows the fully integrated template.
</DeviceClass>
</DeviceClasses>
</Domain>
```
<a name="moreExample"></a>
## More Examples
More examples that also show specific features of the SDT are available in the [test](../test) directory.
......@@ -47,6 +47,8 @@ Please follow the instructions for the [SDT Build System](SDT/schema4.0/docs/SDT
In short:
- Clone the SDT repository from [https://git.onem2m.org/MAS/SDT.git](https://git.onem2m.org/MAS/SDT.git)
- Install Apache ant
- In a terminal, go to the directoy *SDT/schema4.0*
- Run the command:
```sh
......
......@@ -13,12 +13,13 @@ The Smart Device Template (SDT) is an initiative from [oneM2M](http://www.onem2m
Originally initiated by the [Home Gateway Initiative (HGI)](http://www.homegatewayinitiative.org), oneM2M is now the owner and maintainer of the SDT.
At the time of writing, every software developed for Internet-of-Things gateways, for example gateways for home automation, needs to be capable of using various different protocols (ZigBee, ZWave, KNX, OPC UA, EchonetLite, DECT ULE, etc) to interact with a range of devices designed for the IoT environment. This adds extreme overheads in integrating, checking and updating code. The purpose of SDT is to describe devices and device services in a way which is independent of the LAN technology and protocols, in a format which is convenient and reliable for integration in modern code (Java, C/C++, Go, Python, ...).
At the time of writing, every software developed for Internet-of-Things gateways and applications, for example gateways for home or building automation, needs to be capable of using various different protocols (ZigBee, ZWave, KNX, OPC UA, EchonetLite, DECT ULE, etc) to interact with a range of devices designed for the IoT environment. This adds extreme overheads in integrating, testing and updating code. The purpose of the SDT is to describe devices and device services in a way which is independent of the LAN technology and protocols, in a format which is convenient and reliable for integration in modern code (C/C++, Go, Java, Javascript, Python, ...).
### Goals
The key goals of the SDT are:
1. keep it simple, especially for manufacturers to contribute device information;
2. modularity for functions and device types;
2. enable and support modularity for functions and device types;
3. make it easy for developers to create unified APIs;
4. be independent of underlying LAN technologies and protocols;
5. enable extendibility of the system in place without service interruption;
......@@ -26,28 +27,30 @@ The key goals of the SDT are:
In general a description of device (or complex appliance) behaviour can be made in many ways, with various kinds of constraints:
1. no constraints (e.g. using OWL 2.0 or even more "flexibly" RDF)
1. no constraints (e.g. using OWL 2.0 or RDF)
2. moderate constraints (e.g. using XML and a related extensible XSD template)
3. strict constraints (typical for a device certified to interoperate with a specific LAN protocol)
oneM2M chose to use the approach "moderate constraints" (XSD based) because for software development it offers ease of use and a good compromise. In particular, if there are few or no constraints on control parameters then few automatic checks can be made to detect if the software parameters are appropriate for each device integrated. XML and XSD languages were chosen because they are familiar to many developers, can be parsed and validated with common software tools, and can still be created and interpreted by humans if necessary. SDT intended use is for modeling, not as a presentation layer protocol, therefore the size of individual templates is not important.
### Guidelines for Structured Information Models
oneM2M believes that Device information models based on XML and extensible XSD need some guidelines. If every possible feature of every existing LAN technology and appliance were allowed to be described in any formally correct way, then the results would be a modern Babel, no better than today's system of widely different and wildly competing automation protocols.
Therefore oneM2M proposes to recommend a certain structure (or template) for the information model(s), but to allow extensions. Naturally, the more industry consensus is achieved for a single recommended template, the greater the utility for software developers (and in the end users and customers).
The SDT approach is to define re-usable basic functions (or services), labelled "ModuleClass" in the figure below, which can represent the typical functions found in many IoT systems, such as "on/off", "dim a lamp", "receive events from sensor", "read data from sensor", etc. Each ModuleClass is composed of a (preferable small) number of actions, datapoint read/write operations, or asynchronous events. For example, an "on/off" ModuleClass would consist perhaps of just one Action, but a "ReadKeypad" Action might have a number of possible events, each with some data value and (usually) a sequence-ID or timestamp start/stop to indicate when and how long each key was pressed.
The SDT approach is to define re-usable basic functions (or services), labelled "[ModuleClass](SDT_Components.md#ModuleClass)" in the figure below, which can represent the typical functions found in many IoT systems, such as "on/off", "dim a lamp", "receive events from sensor", "read data from sensor", etc. Each ModuleClass is composed of a (preferable small) number of actions, datapoint read/write operations, or asynchronous events. For example, an "on/off" ModuleClass would consist perhaps of just one [Action](SDT_Components.md#Action), but a "ReadKeypad" Action might have a number of possible events, each with some data value and (usually) a sequence-ID or timestamp start/stop to indicate when and how long each key was pressed.
![SmartHome Device Template for a generic device (UML, basic entities)](images/SDT_simplified.png)
**SmartHome Device Template for a generic device (UML, basic entities)**
The SDT represents the device models introduced in the above figure by using an XSD schema to allow formal checking of compliance for XML device descriptions of specific appliances. The modularity goal in the schema is achieved with re-usable XML fragments (for example the "ModuleClass" in the figure).
Complex devices or appliances can then be described by an appropriate set or collection of the agreed ModuleClasses, as indicated in the figure, which also shows an optional "Property" fragment to allow noting of static information such as device manufacturer name, device firmware version, etc.
Complex [Devices](SDT_Components.md#Devices), appliances or even [Products](SDT_Components.md#Products) can then be described by an appropriate set or collection of the agreed [ModuleClasses](SDT_Components.md#ModuleClass), as indicated in the figure, which also shows an optional "[Property](SDT_Components.md#Property)" fragment to allow noting of static information such as device manufacturer name, device firmware version, etc.
oneM2M has discussed with many SDOs to validate these concepts. SDT is designed to take into account the list of "services" compiled by the [SAREF project](https://sites.google.com/site/smartappliancesproject/home).
The SDT supports the use of a set of templates for generic devices or appliances (e.g. for a *dimmable lamp*, a basic *washing machine*, etc), which would be specific instances of the "DeviceClass", which form the basis of APIs used by application developers. These templates can also be referenced by manufacturers creating XML documents to describe their specific Products. For example, the SDT enables specification of a generic washing machine template, with *on/off*, *set-wash-temperature*, *pause* and a few other commands, which could be referenced and extended by a manufacturer as the schema for an XML description of a specific washing machine product. The SDT allows for vendor-specific additional commands (ModuleClasses) to suit specific product types.
The SDT supports the use of a set of templates for generic devices or appliances (e.g. for a *dimmable lamp*, a basic *washing machine*, etc), which would be specific instances of the "[DeviceClass](SDT_Components.md#DeviceClass)", which form the basis of APIs used by application developers. These templates can also be referenced by manufacturers creating XML documents to describe their specific Products. For example, the SDT enables specification of a generic washing machine template, with *on/off*, *set-wash-temperature*, *pause* and a few other commands, which could be referenced and extended by a manufacturer as the schema for an XML description of a specific washing machine product. The SDT allows for vendor-specific additional commands (ModuleClasses) to suit specific product types.
The interoperability benefits can potentially partially be obtained even without a fully complete interoperability of the SDT. For example, the most common functions can be modeled with SDT, and more particular functions can be modeled with technology-specific, proprietary, or seldom-used aspects.
......@@ -60,20 +63,22 @@ This section provides an overview about high-level SDT 4.0 definitions and eleme
| Term | Definition |
|------|------------|
|Domain | Unique name, or "wrapper" which acts like a namespace, set by the organization, company, or project creating the template, allowing reference to a package of definitions for the contained ModuleClasses and device definitions. Can be referenced when extending Products, ModuleClasses, and data types. It has two possible uses: to select the scope of a technology domain, or to set the scope of a use case domain (like Home, SmartGrid, etc) |
|ProductClass | A concrete device model with deterministic device Properties and ModuleClasses, without optionality. It is deemed as a specialized implementation of a DeviceClass that can be manufactured. |
|DeviceClass | A physical, addressable, identifiable appliance, sensor, or actuator. |
|Sub-Device | A device (usually one of several) which may be embedded in or attached to a (full) device. It is not designed to be operated as a standalone device. |
| ModuleClass | Specification of a single service with one or more service methods, the involved abstracted data model and related events. The expectation is that each separate service which may be used in many kinds of devices (like *PowerON/OFF*, *Open/Close*, ...) will be described by a ModuleClass which can be re-used in many *DeviceClass* or *ProductClass* definitions. |
|[Domain](SDT_Components.md#Domain) | Unique name, or "wrapper" which acts like a namespace, set by the organization, company, or project creating the template, allowing reference to a package of definitions for the contained ModuleClasses and device definitions. Can be referenced when extending Products, ModuleClasses, and data types. It has two possible uses: to select the scope of a technology domain, or to set the scope of a use case domain (like Home, SmartGrid, etc) |
|[ProductClass](SDT_Components.md#ProductClass) | A concrete device model with deterministic device Properties and ModuleClasses, without optionality. It is deemed as a specialized implementation of a DeviceClass that can be manufactured. |
|[DeviceClass](SDT_Components.md#DeviceClass) | A physical, addressable, identifiable appliance, sensor, or actuator. |
|[Sub-Device](SDT_Components.md#SubDevice) | A device (usually one of several) which may be embedded in or attached to a (full) device. It is not designed to be operated as a standalone device. |
| [ModuleClass](SDT_Components.md#ModuleClass) | Specification of a single service with one or more service methods, the involved abstracted data model and related events. The expectation is that each separate service which may be used in many kinds of devices (like *PowerON/OFF*, *Open/Close*, ...) will be described by a ModuleClass which can be re-used in many *DeviceClass* or *ProductClass* definitions. |
A major decision, facilitating validation of code and signaling, was to describe services (functionality) of devices in terms of [ModuleClasses](SDT_Components.md#ModuleClass) made up of combinations of three kinds of elements:
A major decision, facilitating validation of code and signaling, was to describe services (functionality) of devices in terms of ModuleClasses made up of combinations of three kinds of elements:
1. [DataPoints](SDT_Components.md#DataPoint) which are aspects of a functionality that can be read and/or written,
2. [Actions](SDT_Components.md#Action) which consist of more complex sequences of operations;
3. [Events](SDT_Components.md#Event) which can be signaled ("published") by devices asynchronously.
1. DataPoints which are aspects of a functionality that can be read and/or written,
2. Actions which consist of more complex sequences of operations;
3. Events which can be signaled ("published") by devices asynchronously.
Any of these elements is optional.
The ModuleClass structure is a major part of the SDT which is illustrated in detail in the following figure:
This [ModuleClass](SDT_Components.md#ModuleClass) structure is a major part of the SDT which is illustrated in detail in the following figure:
![UML description of device functionality in terms of DataPoints, Actions, and Events](images/MC.Action.DataPoint.Event.png)
**UML description of device functionality in terms of DataPoints, Actions, and Events**
......@@ -81,7 +86,7 @@ The ModuleClass structure is a major part of the SDT which is illustrated in det
<a name="Work"/></a>
## How should SDT work?
The basic concept is that a manufacturer, organisation or global SDO would define its preferred Smart Device Template, in XML, specified by and based on an XSD. Using that XSD, manufacturers or indeed hobbyists could "describe" existing or new devices by means of XML files, specifying the capabilities and the parameters needed to control the devices.
The basic concept is that a manufacturer, organisation, service provider or global SDO would define its preferred Smart Device Template, in XML, specified by and based on an XSD. Using that XSD, manufacturers or indeed hobbyists could "describe" existing or new devices by means of XML files, specifying the capabilities and the parameters needed to control the devices.
Assuming that the XML files conform to the specified XSD and to some guidelines described in this document, software developers could readily create APIs able to "parse" the XML-descriptions of devices and (assuming the underlying LAN technology of the device is supported by the software/hardware environment in the gateway) operate the equipment.
......@@ -94,7 +99,7 @@ For the convenience of users and developers, it would also be possible to collec
The SDT defines the structure of all compliant XML descriptions. Each XML description of a specific device is definable at the time of manufacture of the device and can therefore only contain "static" information: (a) manufacturer data in the form of documentation elements and properties, and (b) device capability information detailing the firmware operations and types/meanings of input/output variables.
NOT directly part of this work is a related but separate aspect of every gateway software development: a "device abstraction layer" which can translate between (a) software APIs written based on a particular SDT and (b) the "commands" expected by several different LAN protocols and their hardware controllers.
NOT directly part of this work is a related but separate aspect of every (gateway) software development: a "device abstraction layer" (or "service layer") which can translate between (a) software APIs written based on a particular SDT and (b) the "commands" expected by several different LAN protocols and their hardware controllers.
Programmers developing a "device abstraction layer" for software in a gateway need to create run-time representations of all the recognized devices, their operations and their actual states. This internal "information model" needs to be updated in real time as the devices and the users interact. Programmers may be tempted to use the SDT structure to organize their real-time information model, adding additional information elements for the current state of each device, for some kind of "history" of commands sent/acknowledged, the user etc.
......
......@@ -3,9 +3,6 @@
## Smart Device Template
- **SDT Repository** : [https://git.onem2m.org/MAS/SDT](https://git.onem2m.org/MAS/SDT)
## Further Information
- **TR-0039 Introduction to IPE and SDT** : [http://www.onem2m.org/tr-0039/ipe-and-sdt](http://www.onem2m.org/tr-0039/ipe-and-sdt)
- **The oneM2M Smart Device Template (SDT)** (BrightTALK) : [https://www.brighttalk.com/webcast/11949/340004/the-onem2m-smart-device-template-sdt](https://www.brighttalk.com/webcast/11949/340004/the-onem2m-smart-device-template-sdt)
......
# SDT Build System
This document describes the SDT build system and how to build the SDT and validate new templates and contributions.
This document describes the SDT build system and how to build the SDT schema and validate new templates and contributions.
The files referenced in this document point to version **4.0** of the SDT.
......@@ -16,7 +16,8 @@ The files referenced in this document point to version **4.0** of the SDT.
- [SDT/schema4.0/](../..) : Base directory
- [SDT/schema4.0/src/](../src/) : Source files of the SDT.
- [domain.rng](../src/domain.rng) : RELAX NG file with the SDT schema definition. This is the source file that is converted to the actual schema definition *domain.xsd* during the build. See also [http://en.wikipedia.org/wiki/RELAX_NG](http://en.wikipedia.org/wiki/RELAX_NG).
**Only edit this file when you want to make changes to the SDT!** See also [Editing the Schema](#Editing) below.
**Only edit this file when you want to make changes to the SDT! Changes to XSD file will be overwritten the next time you run the *ant* command.**
See also [Editing the Schema](#Editing) below.
- [domain.xsd](../src/domain.xsd) : The actual SDT schema definition that is generated from *domain.rng*.
- [xml.xsd](../src/xml.xsd) : General schema definitions for the SDT
- [SDT/schema4.0/test/](../test/) : This directory contains XML files with SDT definitions that should be validated whether they conform to the SDT schema.
......@@ -65,7 +66,7 @@ The output after a successful validation should look similar this:
>BUILD SUCCESSFUL
>Total time: 1 second
Otherwise you most likely receive a stack trace or some other error messages. Search the output for the line *BUILD FAILED*. Above this line you will find some helpful hints for the filename and line number on which the error occurred (here: file *mseeb.xml* on line 66) and a reason:
Otherwise you most likely receive a stack trace and some other error messages. Search the output for the line *BUILD FAILED*. Above this line you will find some helpful hints for the filename and line number on which the error occurred (here: file *mseeb.xml* on line 66) and a reason:
>[schemavalidate] /Users/someone/Sources/git/SmartDeviceTemplate/SDT/schema/test/mseeb.xml:66:18: cvc-elt.1: Cannot find the declaration of element 'Domain'.
>BUILD FAILED
......
This diff is collapsed.
......@@ -10,9 +10,9 @@
3. [Imports](#imports)
4. [Data Types](#dataTypes)
1. [SimpleType](#SimpleType)
2. [ArrayType](#ArrayType)
3. [StructType](#StructType)
4. [EnumType](#EnumType)
2. [Array](#Array)
3. [Struct](#Struct)
4. [Enum](#Enum)
5. [Extending DataTypes](#extendingDatatypes)
......@@ -20,7 +20,7 @@
<a name="introduction"/></a>
## Introduction
When SDT was introduced, XML was the favorite encoding format for schemas. Since then, JSON became more popular in the developers' communities, especially in the context of RESTful implementation.
When the Smart Device Template was introduced, XML was the favorite encoding format for schemas. Since then, JSON became more popular in developers' communities, especially in the context of RESTful implementations.
JSON is more concise and human-readable comparing to XML, but has less capability of formal schema definition and validation (such as the XML Schema as defined in [domain.xsd](../src/domain.xsd)).
......@@ -30,7 +30,7 @@ There are some open tools such as [JSON Schema](http://json-schema.org/) that mi
In this release, we chose to define the JSON serialization by the documentation below, while borrowing some valuable aspects from JSON Schema (e.g. data types and validation keywords). Full endorsement of [JSON Schema](http://json-schema.org/) may be considered in the future.
The general JSON structure follows the general SDT structure presented in [SDT_UML.md](SDT_UML.md) and described in [SDT_Components.md](SDT_Components.md).
The general JSON structure follows the general SDT structure presented in [SDT_UML.uxf](SDT_UML.uxf) and described in [SDT_Components.md](SDT_Components.md).
<a name="mappings"/></a>
## SDT mapping to JSON
......@@ -38,36 +38,38 @@ The general JSON structure follows the general SDT structure presented in [SDT_U
<a name="elements"/></a>
### Elements mapping
| SDT XML Elements | JSON Key Words | Remark |
|------------------|----------------|--------|
|Action | Action | |
|Actions | Actions | This element is an array of *Action* structures. |
|Arg | Arg | |
|Args | Args | This element is an array of *Arg* structures. |
|Constraint | Constraint | |
|Constraints | Constraints | This element is an array of *Constraint* structures. |
|Data | Data | This element is an array of *DataPoint* structures. |
|DataPoint | DataPoint | |
|DataType | DataType | |
|DataTypes | DataTypes | This element is an array of *DataType* structures. |
|DeviceClass | DeviceClass | |
|DeviceClasses | DeviceClasses | This element is an array of *DeviceClass* structures. |
|Doc |Doc | |
|Domain | Domain | |
|Event | Event | |
|Events | Events | This element is an array of *Event* structures. |
|Exclude | Exclude | |
|Extend | Extend | |
|Imports |Imports| This element is an array of *Include* structures. |
|Include | Include | |
|ModuleClass | ModuleClass | |
|ModuleClasses | ModuleClasses | This element is an array of *ModuleClass* structures. |
|ProductClass | ProductClass | |
|ProductClasses | ProductClasses | This element is an array of *ProductClasses* structures. |
|Properties | Properties | This element is an array of *Property* structures. |
|Property | Property | |
|SubDevice | SubDevice | |
|SubDevices | SubDevices | This element is an array of *SubDevice* structures. |
| SDT XML Elements | JSON Key Words | Remark |
|:-----------------------------------------------|:---------------|:----------------------------------------------------------|
| [Action](SDT_Components.md#Action) | Action | |
| Actions | Actions | This element is an array of *Action* structures. |
| [Arg](SDT_Components.md#Arg) | Arg | |
| Args | Args | This element is an array of *Arg* structures. |
| Constraint | Constraint | |
| Constraints | Constraints | This element is an array of *Constraint* structures. |
| Data | Data | This element is an array of *DataPoint* structures. |
| [DataPoint](SDT_Components.md#DataPoint) | DataPoint | |
| [DataType](SDT_Components.md#DataType) | DataType | |
| [DataTypes](SDT_Components.md#DataTypes) | DataTypes | This element is an array of *DataType* structures. |
| [DeviceClass](SDT_Components.md#DeviceClass) | DeviceClass | |
| DeviceClasses | DeviceClasses | This element is an array of *DeviceClass* structures. |
| [Doc](SDT_Components.md#Documentation) | Doc | |
| [Domain](SDT_Components.md#Domain) | Domain | |
| [Event](SDT_Components.md#Event) | Event | |
| Events | Events | This element is an array of *Event* structures. |
| Exclude | Exclude | |
| Excludes | Excludes | This element is an array of *Exclude* structures. |
| [Extend](SDT_Components.md#Extending) | Extend | |
| Imports | Imports | This is an array of URLs or file URLs to files to import. |
| Include | Include | |
| Includes | Includes | This element is an array of *Include* structures. |
| [ModuleClass](SDT_Components.md#ModuleClass) | ModuleClass | |
| ModuleClasses | ModuleClasses | This element is an array of *ModuleClass* structures. |
| [ProductClass](SDT_Components.md#ProductClass) | ProductClass | |
| ProductClasses | ProductClasses | This element is an array of *ProductClasses* structures. |
| Properties | Properties | This element is an array of *Property* structures. |
| [Property](SDT_Components.md#Property) | Property | |
| [SubDevice](SDT_Components.md#SubDevice) | SubDevice | |
| SubDevices | SubDevices | This element is an array of *SubDevice* structures. |
#### Example
......@@ -134,31 +136,34 @@ The following example defines a simple *Light* device.
<a name="attributes"/></a>
### Attributes mapping
There are common attributes (e.g. *@id, @name, @optional*) used in several SDT components (e.g. in *DeviceClass, ModuleClass*) as well as attributes used only in certain components (e.g. *@entity* in *Extend*). The mapping of those attributes to JSON follows the rules as below.
There are common attributes (e.g. *@id, @name, @optional*) used in several SDT components (e.g. in *DeviceClass, ModuleClass*) as well as attributes used only in certain components (e.g. *@entity* in *Extend*). XML attributes are represented as normal fields in JSON. The mapping of those attributes to JSON follows the rules as below.
| SDT XML Attributes | JSON Key Word |
|----------------|-------------|
|@default | default |
|@domain |domain |
|@entity |entity |
|@eventable | eventable|
|@href | href |
|@id |id |
|@name |name |
|@optional | optional|
|@parse | parse |
|@readable | readable|
|@semanticURI | semanticURI |
|@value |value |
|@writable | writable|
|@type | type |
|@unitOfMeasure | unitOfMeasure |
|:-------------------|:--------------|
| @default | default |
| @domain | domain |
| @entity | entity |
| @eventable | eventable |
| @href | href |
| @id | id |
| @maxOccurs | maxOccurs |
| @minOccurs | minOccurs |
| @name | name |
| @optional | optional |
| @parse | parse |
| @readable | readable |
| @semanticURI | semanticURI |
| @type | type |
| @unitOfMeasure | unitOfMeasure |
| @value | value |
| @writable | writable |
<a name="imports"/></a>
### Import mapping
The imports are mapped to an array of *Include* structures. Each *Include* structure contains a *href* and a *parse* element.
The imports are mapped to an array of *Include* structures. Each *Include* structure contains a *href* and a *parse* element.
A parser must make sure to import and regard the definitions in the referenced files.
#### Example
......@@ -178,19 +183,20 @@ The imports are mapped to an array of *Include* structures. Each *Include* struc
{ "Include" : { "href" : "anotherSDT.xml", "parse" : "json" } }
]
```
<a name="ExtendType"/></a>
### ExtendType mapping
In the *Include* and *Exclude* elements one may specify the type of the element to be included or excluded. The following table shows the mapping of *ExtendType*.
In the *Include* and *Exclude* elements one may specify the type of the element to be included or excluded. The following table shows the mapping of [ExtendType](SDT_Components.md#ExtendType).
| SDT ExtendType | JSON Key Word |
|----------------|---------------|
|action | action |
|datapoint | datapoint |
|event | event |
|moduleclass | moduleclass |
|property | property |
|device | device |
|subdevice |subdevice |
|:---------------|:--------------|
| action | action |
| datapoint | datapoint |
| event | event |
| moduleclass | moduleclass |
| property | property |
| device | device |
| subdevice | subdevice |
<a name="dataTypes"/></a>
......@@ -203,21 +209,21 @@ The mapping of the different kind of data types to JSON happens directly to JSON
<a name="SimpleType"/></a>
### SimpleType
Note for *SimpelType*: For simplicity, if there is no other attribute present then the type value of *SimpleType* can be directly put as the value of parent *DataType* key, e.g. ```"DataType":"string"```
| SDT Data Types | Note |
|----------------|-----------|
| boolean | boolean (JSON Schema) |
| string | string (JSON Schema) |
| byte | An integer datatype with the range of [0 - 255] |
| integer | integer (JSON Schema) |
| float | number (JSON Schema) |
| date | date (JSON Schema) |
| time | time (JSON Schema) |
| datetime | date-time (JSON Schema) |
| blob | A *base64Binary* encoded string according to [RFC 2045](https://www.w3.org/TR/xmlschema-2/#RFC2045) |
| uri | A string following the URI format (JSON Schema) |
| void | null (JSON Schema) |
Note for [SimpelType](SDT_Components.md#SimpelType): For simplicity, if there is no other attribute present then the type value of [SimpelType](SDT_Components.md#SimpelType) can be directly put as the value of parent [DataType](SDT_Components.md#DataType) key, e.g. ```"DataType":"string"```
| SDT Data Types | Note |
|:---------------|:----------------------------------------------------------------------------------------------------|
| boolean | boolean (JSON Schema) |
| string | string (JSON Schema) |
| byte | An integer datatype with the range of [0 - 255] |
| integer | integer (JSON Schema) |
| float | number (JSON Schema) |
| date | date (JSON Schema) |
| time | time (JSON Schema) |
| datetime | date-time (JSON Schema) |
| blob | A *base64Binary* encoded string according to [RFC 2045](https://www.w3.org/TR/xmlschema-2/#RFC2045) |
| uri | A string following the URI format (JSON Schema) |
| void | null (JSON Schema) |
#### Examples
......@@ -257,10 +263,10 @@ A simple data type with additional attributes:
}
```
<a name="ArrayType"/></a>
### ArrayType
<a name="Array"/></a>
### Array
An *ArrayType* definition is mapped to an *Array* JSON structure. The content of the structure is only one element that defines the type of the array. This could be any *SimpleType*, *ArrayType*, *StructType*, or *EnumType*.
An [Array](SDT_Components.md#Array) definition is mapped to an *Array* JSON structure. The content of the structure is only one element that defines the type of the array. This could be any [SimpleType](#SimpleType), [Array](#Array), [Struct](#Struct), or [Enum](#Enum).
#### Example
......@@ -286,12 +292,12 @@ A simple data type with additional attributes:
}
```
<a name="StructType"/></a>
### StructType
<a name="Struct"/></a>
### Struct
A *StructType* definition is mapped to a *Struct* JSON array. The content of the array are the individual data types for the structure. These could be any *SimpleType*, *ArrayType*, *StructType*, or *EnumType*.
A [Struct](SDT_Components.md#Struct) definition is mapped to a *Struct* JSON array. The content of the array are the individual data types for the structure. These could be any [SimpleType](#SimpleType), [Array](#Array), [Struct](#Struct), or [Enum](#Enum).
A *StructType* definition must contain a *name* attribute.
A *Struct* definition must contain a *name* attribute.
#### Example
......@@ -368,16 +374,16 @@ A more complex structured data type (a structure that contains an indentifier va
]
```
<a name="EnumType"/></a>
### EnumType
<a name="Enum"/></a>
### Enum
A *EnumType* definition is mapped to an *Enum* JSON structure. The content of the structure are the individual enum values of the enum.
A [Enum](SDT_Components.md#Enum) definition is mapped to an *Enum* JSON structure. The content of the structure are the individual enum values of the enum.
A *EnumType* definition must contain a *name* attribute.
A *Enum* definition must contain a *name* attribute.
#### Example
An *Enum* that defines three *EnumValues*. The first definition explicitly specifies the type of the *EnumValue*.
An *Enum* that defines three [EnumValues](SDT_Components.md#EnumValues). The first definition explicitly specifies the type of the [EnumValues](SDT_Components.md#EnumValues).
**XML**:
......@@ -404,12 +410,11 @@ An *Enum* that defines three *EnumValues*. The first definition explicitly speci
<a name="extendingDatatypes"/></a>
### Extending Data Types
Extending *DataTypes* are mapped the same way as extending, for example, *ModuleClasses*. However, since the *DataType* is open, the generic form *DataType* must be used for JSON serialization. It maps to a structure that contains a single *Extend* structure. This structure contains the two attributes *domain* and *entity*.
Extending [DataTypes](SDT_Components.md#DataTypes) are mapped the same way as extending, for example, [ModuleClasses](SDT_Components.md#ModuleClass). However, since the [DataType](SDT_Components.md#DataTypes) is open, the generic form [DataType](SDT_Components.md#DataTypes) must be used for JSON serialization. It maps to a structure that contains a single [Extend](SDT_Components.md#Extending) structure. This structure contains the two attributes *domain* and *entity*.
#### Example
An *Enum* that defines three *EnumValues*. The first definition explicitly specifies the type of the *EnumValue*.
An [Enum](SDT_Components.md#Enum) that defines three *EnumValues*. The first definition explicitly specifies the type of the *EnumValue*.
**XML**:
......
......@@ -5,8 +5,8 @@
<element>
<id>UMLNote</id>
<coordinates>
<x>1160</x>
<y>1424</y>
<x>1112</x>
<y>1352</y>
<w>232</w>
<h>208</h>
</coordinates>
......@@ -36,8 +36,8 @@ group=1</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>1264</x>
<y>1504</y>
<x>1216</x>
<y>1432</y>
<w>88</w>
<h>32</h>
</coordinates>
......@@ -51,8 +51,8 @@ group=1</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>1264</x>
<y>1536</y>
<x>1216</x>
<y>1464</y>
<w>88</w>
<h>24</h>
</coordinates>
......@@ -64,8 +64,8 @@ group=1</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>1272</x>
<y>1056</y>
<x>1224</x>
<y>984</y>
<w>120</w>
<h>176</h>
</coordinates>
......@@ -88,8 +88,8 @@ void</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>776</x>
<y>1120</y>
<x>728</x>
<y>1048</y>
<w>112</w>
<h>64</h>
</coordinates>
......@@ -101,8 +101,8 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>776</x>
<y>1056</y>
<x>728</x>
<y>984</y>
<w>112</w>
<h>64</h>
</coordinates>
......@@ -114,8 +114,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>392</x>
<y>1056</y>
<x>344</x>
<y>984</y>
<w>152</w>
<h>120</h>
</coordinates>
......@@ -134,8 +134,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>536</x>
<y>1016</y>
<x>488</x>
<y>944</y>
<w>544</w>
<h>96</h>
</coordinates>
......@@ -147,8 +147,8 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>536</x>
<y>1016</y>
<x>488</x>
<y>944</y>
<w>544</w>
<h>144</h>
</coordinates>
......@@ -160,12 +160,12 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>872</x>
<y>1152</y>
<x>824</x>
<y>1080</y>
<w>152</w>
<h>40</h>
</coordinates>
<panel_attributes>SimpleType
<panel_attributes>Simple
--
*@ type : BasicType*
fg=blue</panel_attributes>
......@@ -174,8 +174,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>1016</x>
<y>1176</y>
<x>968</x>
<y>1104</y>
<w>272</w>
<h>32</h>
</coordinates>
......@@ -187,8 +187,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>872</x>
<y>1248</y>
<x>824</x>
<y>1176</y>
<w>152</w>
<h>88</h>
</coordinates>
......@@ -205,8 +205,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>536</x>
<y>1136</y>
<x>488</x>
<y>1064</y>
<w>352</w>
<h>144</h>
</coordinates>
......@@ -218,8 +218,8 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>1016</x>
<y>1224</y>
<x>968</x>
<y>1152</y>
<w>336</w>
<h>112</h>
</coordinates>
......@@ -231,12 +231,12 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>872</x>
<y>1056</y>
<x>824</x>
<y>984</y>
<w>152</w>
<h>40</h>
</coordinates>
<panel_attributes>StructType
<panel_attributes>Struct
--
- DataType : DataType
fg=blue</panel_attributes>
......@@ -245,12 +245,12 @@ fg=blue</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>872</x>
<y>1104</y>
<x>824</x>
<y>1032</y>
<w>152</w>
<h>40</h>
</coordinates>
<panel_attributes>ArrayType
<panel_attributes>Array
--
- DataType : DataType
fg=blue</panel_attributes>
......@@ -259,8 +259,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>776</x>
<y>1096</y>
<x>728</x>
<y>1024</y>
<w>112</w>
<h>40</h>
</coordinates>
......@@ -273,8 +273,8 @@ fontsize=12
<element>
<id>UMLClass</id>
<coordinates>
<x>392</x>
<y>944</y>
<x>344</x>
<y>872</y>
<w>1000</w>
<h>32</h>
</coordinates>
......@@ -288,8 +288,8 @@ lw=0.1</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>104</x>
<y>72</y>
<x>56</x>
<y>0</y>
<w>1288</w>
<h>32</h>
</coordinates>
......@@ -303,15 +303,14 @@ lw=0.1</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>672</x>
<y>176</y>
<x>624</x>
<y>104</y>
<w>192</w>
<h>168</h>
<h>152</h>
</coordinates>
<panel_attributes>ModuleClass
--
*@ name : Name*
/@ optional : boolean = false/
/@ semanticURI : uri/
/@ minOccurs : text = "1"/
/@ maxOccurs : text = "1"/
......@@ -328,8 +327,8 @@ fg=blue
<element>
<id>UMLClass</id>
<coordinates>
<x>952</x>
<y>176</y>
<x>904</x>
<y>104</y>
<w>176</w>
<h>104</h>
</coordinates>
......@@ -347,8 +346,8 @@ fg=blue</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>1224</x>
<y>248</y>
<x>1176</x>
<y>176</y>
<w>168</w>
<h>104</h>
</coordinates>
......@@ -366,8 +365,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>1120</x>
<y>248</y>
<x>1072</x>
<y>176</y>
<w>120</w>
<h>32</h>
</coordinates>
......@@ -379,8 +378,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>120</x>
<y>176</y>
<x>72</x>
<y>104</y>
<w>184</w>
<h>144</h>
</coordinates>
......@@ -391,8 +390,8 @@ fontsize=12</panel_attributes>
/- Doc : Doc/
/* Imports/
/* DataTypes : DataType/
/* ModuleClasses : ModuleClass/
/* SubDevices : SubDevice/
/* ModuleClasses : ModuleClass/
/* DeviceClasses : DeviceClass/
/* ProductClasses : ProductClass/
fg=blue</panel_attributes>
......@@ -401,8 +400,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>552</x>
<y>176</y>
<x>504</x>
<y>104</y>
<w>136</w>
<h>64</h>
</coordinates>
......@@ -414,8 +413,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>384</x>
<y>424</y>
<x>336</x>
<y>352</y>
<w>176</w>
<h>128</h>
</coordinates>
......@@ -435,8 +434,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>552</x>
<y>272</y>
<x>504</x>
<y>200</y>
<w>56</w>
<h>72</h>
</coordinates>
......@@ -448,21 +447,21 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>552</x>
<y>352</y>
<x>504</x>
<y>264</y>
<w>136</w>
<h>128</h>
<h>144</h>
</coordinates>
<panel_attributes>lt=&lt;.
m1= 0..n
fontsize=12</panel_attributes>
<additional_attributes>150.0;10.0;80.0;10.0;80.0;140.0;10.0;140.0</additional_attributes>
<additional_attributes>150.0;10.0;80.0;10.0;80.0;160.0;10.0;160.0</additional_attributes>
</element>
<element>
<id>UMLClass</id>
<coordinates>
<x>1224</x>
<y>472</y>
<x>1176</x>
<y>400</y>
<w>168</w>
<h>40</h>
</coordinates>
......@@ -474,8 +473,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>856</x>
<y>176</y>
<x>808</x>
<y>104</y>
<w>112</w>
<h>56</h>
</coordinates>
......@@ -487,8 +486,8 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>1176</x>
<y>472</y>
<x>1128</x>
<y>400</y>
<w>64</w>
<h>32</h>
</coordinates>
......@@ -500,8 +499,8 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>856</x>
<y>224</y>
<x>808</x>
<y>152</y>
<w>112</w>
<h>96</h>
</coordinates>
......@@ -513,8 +512,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>952</x>
<y>288</y>
<x>904</x>
<y>216</y>
<w>176</w>
<h>144</h>
</coordinates>
......@@ -537,8 +536,8 @@ fg=blue
<element>
<id>UMLClass</id>
<coordinates>
<x>952</x>
<y>440</y>
<x>904</x>
<y>368</y>
<w>176</w>
<h>88</h>
</coordinates>
......@@ -555,8 +554,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>856</x>
<y>304</y>
<x>808</x>
<y>232</y>
<w>112</w>
<h>168</h>
</coordinates>
......@@ -568,8 +567,8 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>552</x>
<y>176</y>
<x>504</x>
<y>104</y>
<w>136</w>
<h>336</h>
</coordinates>
......@@ -581,8 +580,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>384</x>
<y>312</y>
<x>336</x>
<y>240</y>
<w>176</w>
<h>104</h>
</coordinates>
......@@ -600,8 +599,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>552</x>
<y>392</y>
<x>504</x>
<y>320</y>
<w>64</w>
<h>64</h>
</coordinates>
......@@ -613,8 +612,8 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>552</x>
<y>176</y>
<x>504</x>
<y>104</y>
<w>136</w>
<h>224</h>
</coordinates>
......@@ -625,19 +624,19 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>552</x>
<y>352</y>
<x>504</x>
<y>264</y>
<w>136</w>
<h>32</h>
<h>48</h>
</coordinates>
<panel_attributes>lt=&lt;.</panel_attributes>
<additional_attributes>150.0;10.0;80.0;10.0;80.0;20.0;10.0;20.0</additional_attributes>
<additional_attributes>150.0;10.0;80.0;10.0;80.0;40.0;10.0;40.0</additional_attributes>
</element>
<element>
<id>UMLClass</id>
<coordinates>
<x>672</x>
<y>352</y>
<x>624</x>
<y>264</y>
<w>192</w>
<h>104</h>
</coordinates>
......@@ -648,7 +647,7 @@ fontsize=12</panel_attributes>
/@ value : text/
/@ semanticURI : uri/
/- Doc : Doc/
- DataType : SimpleType
- DataType : Simple
fg=blue
transparency=80</panel_attributes>
<additional_attributes/>
......@@ -656,8 +655,8 @@ transparency=80</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>1120</x>
<y>176</y>
<x>1072</x>
<y>104</y>
<w>56</w>
<h>320</h>
</coordinates>
......@@ -669,31 +668,31 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>856</x>
<y>304</y>
<x>808</x>
<y>232</y>
<w>56</w>
<h>80</h>
<h>64</h>
</coordinates>
<panel_attributes>lt=&lt;.
m1=0..n
fontsize=12</panel_attributes>
<additional_attributes>10.0;70.0;40.0;70.0;40.0;10.0;10.0;10.0</additional_attributes>
<additional_attributes>10.0;50.0;40.0;50.0;40.0;10.0;10.0;10.0</additional_attributes>
</element>
<element>
<id>UMLClass</id>
<coordinates>
<x>632</x>
<y>1064</y>
<x>584</x>
<y>992</y>
<w>152</w>
<h>88</h>
</coordinates>
<panel_attributes>&lt;&lt;enumeration&gt;&gt;
TypeChoice
--
SimpleType : SimpleType
Struct : StructType
Array : ArrayType
Enum : EnumType
Simple : Simple
Struct : Struct
Array : Array
Enum : Enum
</panel_attributes>
<additional_attributes/>
......@@ -701,8 +700,8 @@ Enum : EnumType
<element>
<id>Relation</id>
<coordinates>
<x>536</x>
<y>1072</y>
<x>488</x>
<y>1000</y>
<w>112</w>
<h>64</h>
</coordinates>
......@@ -714,20 +713,20 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>552</x>
<y>240</y>
<x>504</x>
<y>168</y>
<w>136</w>
<h>136</h>
<h>120</h>
</coordinates>
<panel_attributes>lt=&lt;.
fontsize=12</panel_attributes>
<additional_attributes>150.0;150.0;80.0;150.0;80.0;10.0;10.0;10.0</additional_attributes>
<additional_attributes>150.0;130.0;80.0;130.0;80.0;10.0;10.0;10.0</additional_attributes>
</element>
<element>
<id>Relation</id>
<coordinates>
<x>296</x>
<y>144</y>
<x>248</x>
<y>72</y>
<w>392</w>
<h>88</h>
</coordinates>
......@@ -738,8 +737,8 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>552</x>
<y>256</y>
<x>504</x>
<y>184</y>
<w>64</w>
<h>192</h>
</coordinates>
......@@ -751,12 +750,12 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>872</x>
<y>1200</y>
<x>824</x>
<y>1128</y>
<w>152</w>
<h>40</h>
</coordinates>
<panel_attributes>EnumType
<panel_attributes>Enum
--
*- EnumValue : EnumValue*
fg=blue</panel_attributes>
......@@ -765,8 +764,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>776</x>
<y>1128</y>
<x>728</x>
<y>1056</y>
<w>112</w>
<h>104</h>
</coordinates>
......@@ -778,8 +777,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>1072</x>
<y>1216</y>
<x>1024</x>
<y>1144</y>
<w>168</w>
<h>88</h>
</coordinates>
......@@ -796,8 +795,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>1016</x>
<y>1216</y>
<x>968</x>
<y>1144</y>
<w>72</w>
<h>32</h>
</coordinates>
......@@ -809,8 +808,8 @@ fontsize=12</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>1232</x>
<y>1224</y>
<x>1184</x>
<y>1152</y>
<w>88</w>
<h>64</h>
</coordinates>
......@@ -822,8 +821,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>440</x>
<y>696</y>
<x>392</x>
<y>624</y>
<w>176</w>
<h>64</h>
</coordinates>
......@@ -839,8 +838,8 @@ fg=blue
<element>
<id>UMLClass</id>
<coordinates>
<x>936</x>
<y>696</y>
<x>888</x>
<y>624</y>
<w>192</w>
<h>56</h>
</coordinates>
......@@ -854,8 +853,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>864</x>
<y>696</y>
<x>816</x>
<y>624</y>
<w>88</w>
<h>56</h>
</coordinates>
......@@ -868,8 +867,8 @@ fontsize=12
<element>
<id>Relation</id>
<coordinates>
<x>392</x>
<y>696</y>
<x>344</x>
<y>624</y>
<w>64</w>
<h>32</h>
</coordinates>
......@@ -881,8 +880,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>1216</x>
<y>696</y>
<x>1168</x>
<y>624</y>
<w>176</w>
<h>128</h>
</coordinates>
......@@ -902,8 +901,8 @@ subdevice
<element>
<id>Relation</id>
<coordinates>
<x>1120</x>
<y>696</y>
<x>1072</x>
<y>624</y>
<w>112</w>
<h>56</h>
</coordinates>
......@@ -915,8 +914,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>
<coordinates>
<x>936</x>
<y>760</y>
<x>888</x>
<y>688</y>
<w>192</w>
<h>56</h>
</coordinates>
......@@ -930,8 +929,8 @@ fg=blue</panel_attributes>
<element>
<id>Relation</id>
<coordinates>
<x>864</x>
<y>744</y>
<x>816</x>
<y>672</y>
<w>88</w>
<h>48</h>
</coordinates>
......@@ -944,8 +943,8 @@ fontsize=12
<element>
<id>Relation</id>
<coordinates>
<x>1120</x>
<y>696</y>
<x>1072</x>
<y>624</y>
<w>112</w>
<h>120</h>
</coordinates>
......@@ -957,8 +956,8 @@ fontsize=12</panel_attributes>
<element>
<id>UMLClass</id>