WARNING! Gitlab maintenance operation scheduled for Monday, 20 April between 12:00 and 14:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
[n.8] W3C<sup>®</sup> Recommendation 16 July 2020: "[JSON-LD 1.1 - A JSON-based Serialization for Linked Data](http://www.w3.org/TR/json-ld/)".
[n.9] [ETSI GS CIM 019](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/019/): "cross-cutting Context Information Management (CIM); handling of provenance information in NGSI-LD".
[n.9] ETSI TS 104 179: "Data Solutions (DATA); NGSI-LD Provenance and Integrity".
[n.10] [Codes for Units of Measure used in International Trade Revision 9](http://www.unece.org/fileadmin/DAM/cefact/recommendations/rec20/rec20_Rev9e_2014.xls).
@@ -101,6 +101,8 @@ conformance to the present document.
<!-- prettier-ignore-start -->
<mark>Editor Note: Remove [i.1] (referenced it in the Introduction clause) and renumber all the remaining</mark>
::: REFS
[i.1] ETSI ISG CIM: "[NGSI-LD Status](https://docbox.etsi.org/ISG/CIM/Open/NGSI-LD%20Status.pdf)".
@@ -114,13 +116,13 @@ conformance to the present document.
[i.6] ETSI TS 104 178: "Data Solutions (DATA); NGSI-LD Information Model".
| accept | String | MIME type. It shall be one of: | 0..1 | Intended to convey the MIME type of the notification payload body (JSON, or JSON-LD, or GeoJSON). If not present, default is ["application/json"]{.HTML-Code}. |
| cooldown | Number | Greater than 0 | 0..1 | Once a failure has occurred, minimum period of time in milliseconds which shall elapse before attempting to make a subsequent notification to the same endpoint after failure. If requests are received before the cooldown period has expired, no notification is sent. |
@@ -3180,12 +3171,9 @@ Table: ExecutionResult data type definition
| problemDetails | JSON | ProblemDetails (see IETF RFC 7807 [n.6]) | 0..1 | Provides more details regarding the result status, especially when reporting an error. |
| resultStatus | String | *It shall be one of:* | 1 | Describes the status of the result. ["failure"]{.HTML-Code}, if an error is reported, ["success"]{.HTML-Code} in case of a non-empty result and ["empty"]{.HTML-Code} otherwise. |
| | | | | |
| | | ["success",]{.HTML-Code} | | |
| | | | | |
| | | ["failure"]{.HTML-Code} | | |
| | | | | |
| resultStatus | String | It shall be one of: | 1 | Describes the status of the result. ["failure"]{.HTML-Code}, if an error is reported, ["success"]{.HTML-Code} in case of a non-empty result and ["empty"]{.HTML-Code} otherwise. |
| snapshotQueriesDetails | ExecutionResultDetails[] | _List of ExecutionResultDetails_ (Clause+++root.2.6.8.3) | 0..1 | List with one result per Snapshot query execution, in the same order as Snapshot queries. |
| snapshotStatus | String | *It shall be one of:* | 1 | Indicates the status of the Snapshot, enabling the user to decide whether the snapshot is ready for querying. |
| | | | | |
| | | ["success","partial",]{.HTML-Code} | | |
| | | | | |
| snapshotStatus | String | It shall be one of: | 1 | Indicates the status of the Snapshot, enabling the user to decide whether the snapshot is ready for querying. |
| temporalSnapshotQueriesDetails | ExecutionResultDetails[] | _List of ExecutionResultDetails_ (Clause+++root.2.6.8.3) | 0..1 | List with one result per temporal Snapshot query execution, in the same order as temporal Snapshot queries. |
The present document formally describes the Context Information Management API (NGSI-LD) Specification. The Context Information Management API allows users to provide, consume and subscribe to context information in multiple scenarios and involving multiple stakeholders. Context information is modelled as attributes (properties and relationships) of context entities, also referred to as "digital twins", representing real-world assets. It enables close to real-time access to information coming from many different sources (not only IoT data sources).
The present document formally describes the NGSI-LD API Specification. The NGSI-LD API allows users to provide, consume and subscribe to context information in multiple scenarios and involving multiple stakeholders. Context information is modelled as attributes (properties and relationships) of context entities, also referred to as "digital twins", representing real-world assets. It enables close to real-time access to information coming from many different sources (not only IoT data sources).
