aloccid-iata
aloccid-iata
## Introduction Presently, the ONE Record standard enables third parties to suggest modifications to specific properties within logistics objects ([See Update a Logistics Object](https://iata-cargo.github.io/ONE-Record/logistics-objects/#update-a-logistics-object)). However, there's a gap in the...
**Problem Statement** Today, when a new Logistics Event has been created, a subscriber receives a notification where _hasEventType_ is equal to _LOGISTICS_EVENT_RECEIVED_ (see example below). ```http POST /notifications HTTP/1.1 Content-Type:...
### Problem statement: Currently, when retrieving all logistics events of a logistics object, we can apply a set of query parameters to filter the events. However, these query parameters are...
### Problem Statement Currently, the version of an object is provided only in the response header of a GET API call. When a user retrieves an object using the query...
### Problem Statement Currently, ONE Record defines Sensor and Measurement Logistics objects to manage data streams from IoT devices. However, sensors can generate hundreds of data points in a short...
## Problem statement Currently, we only record the creation date of a change request. However, this date does not indicate when the request is accepted or rejected. Since change requests...
## Problem Statement The ONE Record standard utilizes a publish/subscribe (PUB/SUB) model through subscriptions and notification endpoints. Currently, the recipient of a subscription determines the notification endpoint via the `hasSubscriber`...
## Problem Statement The ONE Record standard offers mechanisms to notify third parties about various actions and occurrences, such as `LOGISTICS_OBJECT_UPDATED` or `LOGISTICS_OBJECT_CREATED`. However, it currently lacks notification event types...