Commit 39cf1dcc authored by Peter Waher's avatar Peter Waher

Fix: table headers

parent 157b12fb
......@@ -4,7 +4,7 @@ Clock Synchronization
This document outlines the XML representation of clock synchronization, as defined by the IEEE XMPP IoT Working Group. The XML representation is modelled using
an annotated XML Schema:
| Sensor Data ||
| Clock Synchronization ||
| ------------|----------------------------------------------------|
| Namespace: | urn:ieee:iot:synchronization:1.0 |
| Schema: | [Synchronization.xsd](Schemas/Synchronization.xsd) |
......
......@@ -5,7 +5,7 @@ This document outlines the XML representation of interacting with concentrators
A concentrator "concentrates" a set of underlying physical or virtual devices, called *nodes*, into one unit using one XMPP address (network identity).
The XML representation is modelled using an annotated XML Schema:
| Sensor Data ||
| Concentrator ||
| ------------|----------------------------------------------|
| Namespace: | urn:ieee:iot:concentrator:1.0 |
| Schema: | [Concentrator.xsd](Schemas/Concentrator.xsd) |
......
......@@ -4,7 +4,7 @@ Control Parameters
This document outlines the XML representation of control parameters, as defined by the IEEE XMPP IoT Working Group. The XML representation is modelled using
an annotated XML Schema:
| Sensor Data ||
| Control ||
| ------------|------------------------------------|
| Namespace: | urn:ieee:iot:ctr:1.0 |
| Schema: | [Control.xsd](Schemas/Control.xsd) |
......
......@@ -10,7 +10,7 @@ it caches the response locally, so that if the same operation occurs again, it k
cache when new rules exist for them, effectively making sure the entities adapt to the new rules by asking the relevant decision support questions again.
The XML representation is modelled using an annotated XML Schema:
| Sensor Data ||
| Decision Support ||
| ------------|----------------------------------------------------------|
| Namespace: | urn:ieee:iot:prov:d:1.0 |
| Schema: | [ProvisioningDevice.xsd](Schemas/ProvisioningDevice.xsd) |
......
......@@ -4,7 +4,7 @@ End-to-End encryption
This document outlines the XML representation of end-to-end encryption, as defined by the IEEE XMPP IoT Working Group. The XML representation is modelled
using an annotated XML Schema:
| Sensor Data ||
| End-to-End encryption ||
| ------------|----------------------------|
| Namespace: | urn:ieee:iot:e2e:1.0 |
| Schema: | [E2E.xsd](Schemas/E2E.xsd) |
......
......@@ -4,7 +4,7 @@ Peer-to-Peer communication
This document outlines the XML representation of peer-to-peer communication, as defined by the IEEE XMPP IoT Working Group. The XML representation is modelled
using an annotated XML Schema:
| Sensor Data ||
| Peer-to-Peer communication ||
| ------------|----------------------------|
| Namespace: | urn:ieee:iot:p2p:1.0 |
| Schema: | [P2P.xsd](Schemas/P2P.xsd) |
......
......@@ -7,7 +7,7 @@ future decisions made by the provisioning service. While waiting for the owner t
all requests it cannot answer by default.
The XML representation is modelled using an annotated XML Schema:
| Sensor Data ||
| Provisioning ||
| ------------|----------------------------------------------------------|
| Namespace: | urn:ieee:iot:prov:o:1.0 |
| Schema: | [ProvisioningOwner.xsd](Schemas/ProvisioningOwner.xsd) |
......
......@@ -6,7 +6,7 @@ services, users or devices can use to identify themselves. The recipient of sens
XMPP address of the immediate sender, the domain the immediate sender, and sensor, user or service tokens. The XML representation is modelled using
an annotated XML Schema:
| Sensor Data ||
| Tokens ||
| ------------|----------------------------------------------------------|
| Namespace: | urn:ieee:iot:prov:t:1.0 |
| Schema: | [ProvisioningTokens.xsd](Schemas/ProvisioningTokens.xsd) |
......
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