Commit 4da67636 authored by Peter Waher's avatar Peter Waher

Adding descriptions.

parent 0a0ea98a
This diff is collapsed.
@startuml @startuml
Node o-- Timestamp Device "1" *-- "0..*" Node
Timestamp o-- Field Node o-- "*" Timestamp
Timestamp o-- Error Device "1" o-- "*" Timestamp
Field <|-- PhysicalQuantity Timestamp "1 " o-- "*" Field
Field <|-- String Timestamp "1" o-- "*" Error
Field <|-- Boolean
Field <|-- Date Device : JID
Field <|-- DateTime
Field <|-- Duration Node : Node ID
Field <|-- Enumeration Node : Source ID
Field <|-- Int32 Node : Partition
Field <|-- Int64
Field <|-- Time Timestamp : Date & Time
@enduml
Field : Name
Field : Field Type
Field : Quality of Service
Field : Localization
Field : Custom Annotation
Error : Message
@enduml
\ No newline at end of file
This diff is collapsed.
@startuml
Field <|-- PhysicalQuantity
Field <|-- String
Field <|-- Boolean
Field <|-- Date
Field <|-- DateTime
Field <|-- Duration
Field <|-- Enumeration
Field <|-- Int32
Field <|-- Int64
Field <|-- Time
@enduml
\ No newline at end of file
Sensor Data Sensor Data
================== ==================
The XML representation of Sensor Data used by the IEEE XMPP IoT interfaces are defined as follows: This document outlines the XML representation of sensor data, as defined by the IEEE XMPP IoT Working Group. The XML representation is modelled using
an annotated XML Schema:
| Sensor Data || | Sensor Data ||
| ------------|----------------------------------| | ------------|----------------------------------|
| Namespace: | urn:ieee:iot:sensordata | | Namespace: | urn:ieee:iot:sensordata |
| Schema: | [SensorData.xsd](SensorData.xsd) | | Schema: | [SensorData.xsd](SensorData.xsd) |
Conceptual model
------------------------
The XML representation of Sensor Data used by the IEEE XMPP IoT interfaces is based on a three or four level abstraction:
![Conceptual model](Diagrams/SensorDataConceptual.svg)
Either the **device** is a simple device, with one identity, or it consists of a set of **nodes**. The later is also sometimes referred
to as a **concentrator**, as it *concentrates* several nodes, or virtual devices, into one entity. Each device then report a set of **fields**,
and each field, is stamped with a **timestamp**. In XMPP, devices are addressed using an **XMPP Address**, also referred to as a **Jabber ID** or a **JID**.
The nodes are identifid using one to three identifiers, depending on the size and needs of the concentrator. The required attribute, is the
**Node ID**. The **Source ID** allows a concentrator to divide the set of nodes into different data sources. If data sources are not used, this
attribute can be omitted. **Partitions** allow the concentrator to divide a data source into multiple pieces. This attribute can also be omitted,
if not used. It is the tripple (Node ID, Source ID, Partition) that must be unique inside the device.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment