[e2e testing] NGSI-LD #849
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -83,6 +83,50 @@ e.g.: | |
| } | ||
| ``` | ||
|
|
||
| #### NGSI-LD data and metadata considerations | ||
|
|
||
| When provisioning devices for an NGSI-LD Context Broker, `type` values should typically correspond to one of the | ||
| following: | ||
|
|
||
| - `Property`, `Relationship`, `Geoproperty` | ||
| - Native JSON types (e.g. `String`, `Boolean`, `Float` , `Integer` `Number`) | ||
| - Temporal Properties (e.g. `Datetime`, `Date` , `Time`) | ||
| - GeoJSON types (e.g `Point`, `LineString`, `Polygon`, `MultiPoint`, `MultiLineString`, `MultiPolygon`) | ||
|
|
||
| Most NGSI-LD attributes are sent to the Context Broker as _properties_. If a GeoJSON type or native JSON type is | ||
| defined, the data will be converted to the appropriate type. Temporal properties should always be expressed in UTC, | ||
| using ISO 8601. This ISO 8601 conversion is applied automatically for the `observedAt` _property-of-a-property_ metadata | ||
| where present. | ||
|
|
||
| Data for any attribute defined as a _relationship_ must be a valid URN. | ||
|
|
||
| Note that when the `unitCode` metadata attribute is supplied in the provisioning data under NGSI-LD, the standard | ||
| `unitCode` _property-of-a-property_ `String` attribute is created. | ||
|
|
||
| Other unrecognised `type` attributes will be passed as NGSI-LD data using the following JSON-LD format: | ||
|
|
||
| ```json | ||
| "<property_name>": { | ||
| "type" : "Property", | ||
| "value": { | ||
| "@type": "<property_type>", | ||
| "@value": { string or object} | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| `null` values will be passed in the following format: | ||
|
There was a problem hiding this comment. Why did you choose to pass null values in the following format, is it a requirement ? I cannot find this mentionned in the ngsi-ld specification. There was a problem hiding this comment. This is a restriction based on the definitions of the ESTI NGSI-LD specification
and ...
so basically, you cannot store The attribute type is based on There was a problem hiding this comment. (late reply) It's not clear to me, you say you cannot store There was a problem hiding this comment. What do you think about passing a default value? as you use that only for numbers, 0 seems to be a correct choice. There was a problem hiding this comment.
No that is precisely what I am attempting to do. Directly sending
But |
||
|
|
||
| ```json | ||
| "<property_name>": { | ||
| "type" : "Property", | ||
| "value": { | ||
| "@type": "Intangible", | ||
| "@value": null | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ### Data mapping plugins | ||
|
|
||
| The IoT Agent Library provides a plugin mechanism in order to facilitate reusing code that makes small transformations | ||
|
|
@@ -166,8 +210,9 @@ events in the IoT Agent with the configured type name will be marked as events. | |
|
|
||
| ##### Timestamp Processing Plugin (timestampProcess) | ||
|
|
||
| This plugin processes the entity attributes looking for a `TimeInstant` attribute. If one is found, for NGSI-v1/NGSIv2, | ||
| the plugin adds a `TimeInstant` attribute as metadata for every other attribute in the same request. With NGSI-LD, the | ||
| Standard `observedAt` property-of-a-property is used instead. | ||
|
|
||
| ##### Expression Translation plugin (expressionTransformation) | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have done a little refactor to the NGIS-LD entries in the CNR file.
The line "Lazy attributes" is mine but I guess is correct, as in #842 (comment) see Lazy Attribute checked.
@jason-fox is my understanding correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes - Lazy Attributes are mapped to the forwarded GET
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thus, NTC (I guess)