Skip to content

Commit

Permalink
Preparations for FIWARE 7.8.1 release
Browse files Browse the repository at this point in the history
Merge branch 'master' into releases

- core/orion-ld 0.1.1
- iot-agents/iotagent-json 1.13.0
- iot-agents/iotagent-json 1.12.0
- processing/knowage/server 7.1.0
  • Loading branch information
jason-fox committed Jan 21, 2020
2 parents 3f0e629 + bf6f859 commit 3b371c4
Show file tree
Hide file tree
Showing 19 changed files with 806 additions and 1,102 deletions.
3 changes: 3 additions & 0 deletions .gitmodules
Original file line number Diff line number Diff line change
Expand Up @@ -184,3 +184,6 @@
[submodule "core/scorpio"]
path = core/scorpio
url = https://github.com/ScorpioBroker/ScorpioBroker
[submodule "core/orion-ld"]
path = core/orion-ld
url = https://github.com/FIWARE/context.Orion-LD.git
433 changes: 179 additions & 254 deletions README.md

Large diffs are not rendered by default.

396 changes: 185 additions & 211 deletions core/README.md

Large diffs are not rendered by default.

1 change: 1 addition & 0 deletions core/orion-ld
Submodule orion-ld added at 464374
248 changes: 98 additions & 150 deletions data-publication/README.md

Large diffs are not rendered by default.

109 changes: 44 additions & 65 deletions iot-agents/README.md
Original file line number Diff line number Diff line change
@@ -1,47 +1,38 @@
# Interface to the internet of Things

Connecting IoT devices or “things” involves the need to overcome a common set of
problems arising in the different layers of the communication model. Using
sensor data or acting upon them requires interaction with a heterogeneous
environment of devices running different protocols (due to the lack of globally
accepted standards), dispersed and accessible through multiple wireless
technologies.
Connecting IoT devices or “things” involves the need to overcome a common set of problems arising in the different
layers of the communication model. Using sensor data or acting upon them requires interaction with a heterogeneous
environment of devices running different protocols (due to the lack of globally accepted standards), dispersed and
accessible through multiple wireless technologies.

To learn more about the Interface to the internet of Things, check out the
[documentation](https://fiwaretourguide.readthedocs.io/en/latest/iot-agents/introduction/)

### What are IoT Agents?

The IoT Agent (IDAS) component is an implementation of the Backend Device
Management GE, according to the FIWARE reference architecture. You are here
because you need to connect objects to gather data or interact with them,
typical IoT use case scenario . If so, you need to use one of the existing IoT
Agents that are part of IDAS.

You need this component if you plan to connect IoT devices/gateways to
FIWARE-based ecosystems. IoT Agents translate IoT-specific protocols into the
NGSI context information protocol, that is the FIWARE standard data exchange
model. You do not need this component if your devices or gateways natively
support the NGSI API.

FIWARE-Ready IoT devices are able demonstrate the ability of the IoT solutions
to seamless interoperate with FIWARE platforms. Any IoT device which is able to
connect to the context broker (either directly or via an IoT Agent) is able to
undergo a certification and testing process and can be added to the
The IoT Agent (IDAS) component is an implementation of the Backend Device Management GE, according to the FIWARE
reference architecture. You are here because you need to connect objects to gather data or interact with them, typical
IoT use case scenario . If so, you need to use one of the existing IoT Agents that are part of IDAS.

You need this component if you plan to connect IoT devices/gateways to FIWARE-based ecosystems. IoT Agents translate
IoT-specific protocols into the NGSI context information protocol, that is the FIWARE standard data exchange model. You
do not need this component if your devices or gateways natively support the NGSI API.

FIWARE-Ready IoT devices are able demonstrate the ability of the IoT solutions to seamless interoperate with FIWARE
platforms. Any IoT device which is able to connect to the context broker (either directly or via an IoT Agent) is able
to undergo a certification and testing process and can be added to the
[FIWARE marketplace](https://marketplace.fiware.org/) and labelled as a
[FIWARE-Ready IoT Device](http://marketplace.fiware.org/pages/how-to-devices).

### Why Use IoT Agents?

By using an IoT Agent , your devices will be represented in a FIWARE platform as
NGSI entities in a Context Broker. This means that you can query or subscribe to
changes of device parameters status by querying or subscribing to the
By using an IoT Agent , your devices will be represented in a FIWARE platform as NGSI entities in a Context Broker. This
means that you can query or subscribe to changes of device parameters status by querying or subscribing to the
corresponding NGSI entity attributes at the ContextBroker.

Additionally, you will be able trigger commands to your actuation devices by
updating specific command-related attributes in the associated NGSI entities
representation at the Context Broker. This way, all hardware interactions with
IoT devices can be handled by the Context Broker, using a homogeneous
Additionally, you will be able trigger commands to your actuation devices by updating specific command-related
attributes in the associated NGSI entities representation at the Context Broker. This way, all hardware interactions
with IoT devices can be handled by the Context Broker, using a homogeneous
[NGSI](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json)
interface.

Expand All @@ -60,9 +51,8 @@ interface.

Library for developing your own IoT Agent.

The **IoT Agent Framework Library** project is part of
[FIWARE](https://fiware.org/) and but is not rated as a standalone component. It
is used in the following IoT Agents:
The **IoT Agent Framework Library** project is part of [FIWARE](https://fiware.org/) and but is not rated as a
standalone component. It is used in the following IoT Agents:

## IoT Agent for JSON

Expand All @@ -75,19 +65,17 @@ is used in the following IoT Agents:
| ------------------------------------------------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |


IoT Agent for a JSON based protocol (with [AMQP](https://www.amqp.org/),
[HTTP](https://www.w3.org/Protocols/) and [MQTT](https://mqtt.org/) transports)
IoT Agent for a JSON based protocol (with [AMQP](https://www.amqp.org/), [HTTP](https://www.w3.org/Protocols/) and
[MQTT](https://mqtt.org/) transports)

This IoT Agent is designed to be a bridge between [JSON](https://json.org/) and
the
This IoT Agent is designed to be a bridge between [JSON](https://json.org/) and the
[NGSI](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json)
interface. It follows the standard interaction model defined in the
[IoT Agent Framework Library](https://iotagent-node-lib.rtfd.io).

### Quality Assurance

The **IoT Agent for JSON** project is part of [FIWARE](https://fiware.org/) and
has been rated as follows:
The **IoT Agent for JSON** project is part of [FIWARE](https://fiware.org/) and has been rated as follows:

- **Version Tested:**
![](https://img.shields.io/badge/dynamic/json.svg?label=Version&url=https://fiware.github.io/catalogue/json/iotagent_json.json&query=$.version&colorB=blue)
Expand All @@ -114,8 +102,8 @@ has been rated as follows:
| ----------------------------------------------------------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |


IoT Agent for the Ultralight 2.0 protocol (with [AMQP](https://www.amqp.org/),
[HTTP](https://www.w3.org/Protocols/) and [MQTT](https://mqtt.org/) transports)
IoT Agent for the Ultralight 2.0 protocol (with [AMQP](https://www.amqp.org/), [HTTP](https://www.w3.org/Protocols/) and
[MQTT](https://mqtt.org/) transports)

This IoT Agent is designed to be a bridge between Ultralight and the
[NGSI](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json)
Expand All @@ -124,8 +112,7 @@ interface. It follows the standard interaction model defined in the

### Quality Assurance

The **IoT Agent for the Ultralight** project is part of
[FIWARE](https://fiware.org/) and has been rated as follows:
The **IoT Agent for the Ultralight** project is part of [FIWARE](https://fiware.org/) and has been rated as follows:

- **Version Tested:**
![](https://img.shields.io/badge/dynamic/json.svg?label=Version&url=https://fiware.github.io/catalogue/json/iotagent_ul.json&query=$.version&colorB=blue)
Expand Down Expand Up @@ -154,16 +141,15 @@ The **IoT Agent for the Ultralight** project is part of

IoT Agent for the LoRaWAN protocol (with CayenneLpp and CBOR data models)

This IoT Agent is designed to be a bridge between the
[LoRaWAN](https://lora-alliance.org/about-lorawan) protocol and the
This IoT Agent is designed to be a bridge between the [LoRaWAN](https://lora-alliance.org/about-lorawan) protocol and
the
[NGSI](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json)
interface. It follows the standard interaction model defined in the
[IoT Agent Framework Library](https://iotagent-node-lib.rtfd.io).

### Quality Assurance

The **IoT Agent for LoRaWAN** project is part of [FIWARE](https://fiware.org/)
and has been rated as follows:
The **IoT Agent for LoRaWAN** project is part of [FIWARE](https://fiware.org/) and has been rated as follows:

- **Version Tested:**
![](https://img.shields.io/badge/dynamic/json.svg?label=Version&url=https://fiware.github.io/catalogue/json/iotagent_LoRa.json&query=$.version&colorB=blue)
Expand Down Expand Up @@ -192,18 +178,16 @@ and has been rated as follows:

IoT Agent accepting COAP requests.

This IoT Agent is designed to be a bridge between the
[OMA](https://www.omaspecworks.org/)
[Lightweight M2M](https://www.omaspecworks.org/what-is-oma-specworks/iot/lightweight-m2m-lwm2m/)
protocol and the
This IoT Agent is designed to be a bridge between the [OMA](https://www.omaspecworks.org/)
[Lightweight M2M](https://www.omaspecworks.org/what-is-oma-specworks/iot/lightweight-m2m-lwm2m/) protocol and the
[NGSI](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json)
interface. It follows the standard interaction model defined in the
[IoT Agent Framework Library](https://iotagent-node-lib.rtfd.io).

### Quality Assurance

The **IoT Agent for LightWeight Machine2Machine** project is part of
[FIWARE](https://fiware.org/) and has been rated as follows:
The **IoT Agent for LightWeight Machine2Machine** project is part of [FIWARE](https://fiware.org/) and has been rated as
follows:

- **Version Tested:**
![](https://img.shields.io/badge/dynamic/json.svg?label=Version&url=https://fiware.github.io/catalogue/json/iotagent_LWM2M.json&query=$.version&colorB=blue)
Expand Down Expand Up @@ -232,16 +216,14 @@ The **IoT Agent for LightWeight Machine2Machine** project is part of

IoT Agent accepting data from OPC UA devices.

This IoT Agent is designed to be a bridge between the
[OPC Unified Architecture](http://www.opcua.us/) protocol and the
This IoT Agent is designed to be a bridge between the [OPC Unified Architecture](http://www.opcua.us/) protocol and the
[NGSI](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json)
interface. It follows the standard interaction model defined in the
[IoT Agent Framework Library](https://iotagent-node-lib.rtfd.io).

### Quality Assurance

The **IoT Agent for OPC-UA** project is part of [FIWARE](https://fiware.org/)
and has been rated as follows:
The **IoT Agent for OPC-UA** project is part of [FIWARE](https://fiware.org/) and has been rated as follows:

- **Version Tested:**
![](https://img.shields.io/badge/dynamic/json.svg?label=Version&url=https://fiware.github.io/catalogue/json/iotagent_OPC-UA.json&query=$.version&colorB=blue)
Expand Down Expand Up @@ -270,16 +252,15 @@ and has been rated as follows:

IoT Agent for the Sigfox protocol.

This IoT Agent is designed to be a bridge between the
[Sigfox](https://www.sigfox.com/en) protocol and the
This IoT Agent is designed to be a bridge between the [Sigfox](https://www.sigfox.com/en) protocol and the
[NGSI](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json)
interface. It follows the standard interaction model defined in the
[IoT Agent Framework Library](https://iotagent-node-lib.rtfd.io).

### Quality Assurance

The **IoT Agent for Sigfox** project is a new component within
[FIWARE](https://fiware.org/) and will be rated in the current release
The **IoT Agent for Sigfox** project is a new component within [FIWARE](https://fiware.org/) and will be rated in the
current release

---

Expand All @@ -294,16 +275,14 @@ The **IoT Agent for Sigfox** project is a new component within
| -------------------------------------------------------------- | ------------------------------------------------------ | --------------------------------------------------------------- | ------------------------------------------------- | --------------------------------------------------------------------------------------------- |


A reference implementation of the [oneM2M](http://www.onem2m.org/) standard, for
conducting applied research and developing innovative M2M and IoT applications.
It offers an
A reference implementation of the [oneM2M](http://www.onem2m.org/) standard, for conducting applied research and
developing innovative M2M and IoT applications. It offers an
[NGSI](https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json)
interface for connection to the Orion Context Broker

### Quality Assurance

The **Open MTC** project is part of [FIWARE](https://fiware.org/) and has been
rated as follows:
The **Open MTC** project is part of [FIWARE](https://fiware.org/) and has been rated as follows:

- **Version Tested:**
![](https://img.shields.io/badge/dynamic/json.svg?label=Version&url=https://fiware.github.io/catalogue/json/open_mtc.json&query=$.version&colorB=blue)
Expand Down
32 changes: 17 additions & 15 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -13,30 +13,30 @@
"license": "CC-BY-4.0",
"repository": {
"type": "git",
"url": "https://github.com/Fiware/catalogue"
"url": "https://github.com/FIWARE/catalogue"
},
"devDependencies": {
"eslint": "^5.6.0",
"eslint-config-tamia": "^6.0.1",
"eslint-plugin-prettier": "^3.0.0",
"husky": "^1.1.0",
"eslint": "^5.16.0",
"eslint-config-tamia": "^6.2.1",
"eslint-plugin-prettier": "^3.1.2",
"husky": "^1.3.1",
"lint-staged": "^7.3.0",
"memfs": "2.10.1",
"prettier": "^1.14.2",
"prettier": "^1.19.1",
"remark-cli": "^6.0.1",
"remark-preset-lint-recommended": "^3.0.2",
"textlint": "^11.0.1",
"remark-preset-lint-recommended": "^3.0.3",
"textlint": "^11.6.1",
"textlint-rule-common-misspellings": "^1.0.1",
"textlint-rule-no-dead-link": "^4.4.1",
"textlint-rule-terminology": "^1.1.29",
"textlint-rule-no-dead-link": "^4.6.2",
"textlint-rule-terminology": "^1.1.30",
"textlint-rule-write-good": "^1.6.2"
},
"engines": {
"node": ">=8.6"
"node": ">=10"
},
"scripts": {
"precommit": "lint-staged",
"prettier:text": "prettier 'README.md' '*/README.md' --tab-width 4 --print-width 80 --write --prose-wrap always",
"prettier:text": "prettier 'README.md' '*/README.md' --parser markdown --tab-width 4 --print-width 120 --write --prose-wrap always",
"lint:md": "remark -f 'README.md' '*/README.md'",
"lint:text": "textlint 'README.md' '*/README.md'",
"test": "textlint 'README.md' '*/README.md'"
Expand All @@ -48,15 +48,17 @@
},
"lint-staged": {
"*.md": [
"prettier --tab-width 4 --print-width 80 --write --prose-wrap always",
"prettier --parser markdown --tab-width 4 --print-width 120 --write --prose-wrap always",
"git add"
]
},
"remarkConfig": {
"settings" : {
"settings": {
"bullet": "-",
"paddedTable": true
},
"plugins": ["remark-preset-lint-recommended"]
"plugins": [
"remark-preset-lint-recommended"
]
}
}
Loading

0 comments on commit 3b371c4

Please sign in to comment.