2 References

2.1 Normative references

References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox.

NOTE:

While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity.

The following referenced documents are necessary for the application of the present document.

[1] W3C ® Recommendation 25 February 2014: “ RDF Schema 1.1 ”.
[2] W3C ® Recommendation 16 July 2020: “ JSON-LD 1.1 - A JSON-based Serialization for Linked Data ”.
[3] IETF RFC 7231 : “Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content”.
[4] IETF RFC 7232 : “Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests”.
[5] IETF RFC 3986 : “Uniform Resource Identifier (URI): Generic Syntax”.
[6] IETF RFC 8259 : “The JavaScript Object Notation (JSON) Data Interchange Format”.
[7] IETF RFC 8288 : “Web Linking”.
[8] IETF RFC 7946 : “The GeoJSON Format”.
[9] IETF RFC 8141 : “Uniform Resource Names (URNs)”.
[10] IETF RFC 7807 : “Problem Details for HTTP APIs”.
[11] IEEE 1003.2™-1992 : “IEEE Standard for Information Technology - Portable Operating System Interfaces (POSIX™) - Part 2: Shell and Utilities”.
[12] IETF RFC 5234 : “Augmented BNF for Syntax Specifications: ABNF”.
[13] Unicode® Technical Standard #10 : “Unicode Collation Algorithm”.
[14] Open Geospatial Consortium Inc. OGC 06-103r4 : “OpenGIS ® Implementation Standard for Geographic information - Simple feature access - Part 1: Common architecture”.
[16] IETF RFC 7396 : “JSON Merge Patch”.
[17] ISO 8601: 2019 : “Date and time — Representations for information interchange”.
[18] IETF RFC 2818 : “HTTP Over TLS”.
[19] IETF RFC 5246 : “The Transport Layer Security (TLS) Protocol Version 1.2”.
[21] ECMA-262 Specification : “ECMAScript ® 2022 language specification”.
[22] The Unicode Consortium: “ Unicode® 15.0.0 ”.
[23] IETF RFC 3987 : “Internationalized Resource Identifiers (IRIs)”.
[24] OASIS Standard: “ MQTT Version 3.1.1 Plus Errata 01 ”. Edited by Andrew Banks and Rahul Gupta. 10 December 2015.
[25] OASIS Standard: “ MQTT Version 5.0 ”. Edited by Andrew Banks, Ed Briggs, Ken Borgendale and Rahul Gupta. 07 March 2019.
[26] IETF RFC 7240 : “Prefer Header for HTTP”.
[27] IETF RFC 7230 : “Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing”.
[28] IETF RFC 5646 : “Tags for Identifying Languages”.
[29] IETF RFC 3282 : “Content Language Headers”.
[30] IETF RFC 7234 : “Hypertext Transfer Protocol (HTTP/1.1): Caching”.
[31] IETF RFC 7233 : “Hypertext Transfer Protocol (HTTP/1.1): Range Requests”.
[33] IETF RFC 6906 : “The ‘profile’ Link Relation Type”.
[34] W3C ® Recommendation 25 February 2014: “ RDF 1.1 Concepts and Abstract Syntax ”.
[35] ETSI GS CIM 019 : “cross-cutting Context Information Management (CIM); handling of provenance information in NGSI-LD”.
[36] IETF RFC 6067 : “BCP 47 Extension U”.
[37] ETSI GS CIM 047 : “Context Information Management (CIM); OpenAPI Specification for NGSI-LD API”.

2.2 Informative references

References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

NOTE:

While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity.

The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader’s understanding, but are not required for conformance to the present document.

[i.1] ETSI GR CIM 002 (V1.1.1) : “Context Information Management (CIM); Use Cases (UC)”.
[i.2] ETSI GR CIM 007 : “Context Information Management (CIM); Security and Privacy”.
[i.3] OMA-TS-NGSI_Context_Management-V1_0-20120529-A : “NGSI Context Management”.
[i.4] ETSI TS 103 264 (V3.1.1): “SmartM2M; Smart Applications; Reference Ontology and oneM2M Mapping”.
[i.5] NGSI-LD Wrapper : “Experimental proxy for adaptation between FIWARE ® and NGSI-LD”.
[i.6] Graph Databases: “New Opportunities for Connected Data”. O’Reilly 2 nd Edition. Webber, Robinson, et al. ISBN:1491930896 9781491930892.
[i.7] JSON-LD Playground : “Experimentation tool for JSON-LD”.
[i.8] ETSI GS CIM 006 : “Context Information Management (CIM); Information Model (MOD0)”.
[i.10] IETF RFC 6902 : “JavaScript Object Notation (JSON) Patch”.
[i.16] ETSI GS CIM 004 (V1.1.2): “Context Information Management (CIM); Application Programming Interface (API)”.
[i.17] ETSI ISG CIM: “ NGSI-LD Status ”.
[i.18] Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation).
[i.19] MQTT URI Scheme .
[i.20] GeoJSON-LD 1.0 . Base context for processing GeoJSON according to the JSON-LD processing model.
[i.21] ETSI GR CIM 008 : “Context Information Management (CIM); NGSI-LD Primer”.