@@ -784,13 +784,13 @@ Clause 7 studies solutions for the architectural integration of NGSI-LD and its
oneM2M resource structures already contain relevant information, however, applications often have to first discover and then individually retrieve this information to check whether it is actually relevant for them. The goal of this approach is to make the information stored in existing oneM2M resources also available to applications via the NGSI-LD API, enabling application to specify and efficiently retrieve the information they actually need.
In particular, applications can request the information by specifying the following:
- Applications can filter and scope based on the information itself (as opposed to meta information attached to resources or JSON paths) – due to the common meta information model, index structures can be used to make access efficient
- Applications can filter and scope based on the information itself (as opposed to meta information attached to resources). Specific index structures can be used to make access efficient due to the common meta information model.
- Application can project to only get the properties and relationships they are interested in (as opposed to getting the content on resource granularity)
- Applications can get back whole entity graphs by following relationships (e.g. across multiple resources)
Applications have the following interaction options using NGSI-LD:
- Retrieve specific information they can already identify, i.e. as an NGSI-LD Entity with a given identifier
- Query relevant information as described above and getting back all results, in form of NGSI-LD Entities, with a single request. There is no seperate discovery step followed by retrieval(s).
- Query relevant information as described above and getting back all results, in form of NGSI-LD Entities, with a single request. There is no separate discovery step followed by retrieval(s).
- Subscribe to be notified of relevant changes in information, or periodically.
