The IATA ONE Record vocabulary, described using W3C RDF Schema and the Web Ontology Language.
IATA ONE Record API vocabulary
Initial content of the Logistics Object at the creation moment, represented via a Memento
List of change requests that were sent as PATCH on for a Logistics Object
Non mandatory error details
PATCH body of a change request sent for a specific Logistics Object
The party that has requested the change request
Company details
Error details
List of mementos of a Logistics Object
PATCH object to modify
List of operations to apply as PATCH on a Logistics Object
Logistics Object Reference for which the audit trail applies
Latest revision of the Logistics Object
Operation objects must have exactly one op (operation) member; this value indicates which operation is to be performed. The value must be one of add or del; all other values result in an error
Operations objects must have exactly one p, predicate, member. The value of this member must be an IRI
Timestamp of the change request
Company which sent the change request
ACCEPTED or REJECTED
Supported logistics object types on the server
Supported content types of the server
Endpoint of the company in the Internet of Logistics
Company Id, for example airline code.
Identifiers of the logistics objects to which the access is requested
Parties that receive the delegated rights
REVOKE or DELEGATE
GET or PATCH
Error code
Field of the object for which the error applies
Object for which the error applies
Message of the error
Brief description of the error
Id of the reference Logistics Object
Type of the reference Logistics Object
First version of the Logistics Object
Label of the memento
Date and time of the memento creation
Name of the memento creator
The actual data
First memento of the Logistics Object
Last memento of the Logistics Object
Link to the memento
Non mandatory label of the memento
Creation date of the memento
OBJECT_CREATED or OBJECT_UPDATED
Type of Logistics Object
Logistics Object for which the notification is sent
Value to update
Data type of the field to update
Revision number of the Logistics Object
Reference of the Logistics Object to which the change request is applied to
The company identifier of the entity that is requesting the change request
Reason for the change (optional)
Company Identifier of the company the subscriber wants to subscribe to (delegation scenario).
The Logistics Object type to which the subscriber wants subscribe to
Callback URL of the Client Subscription API where the subscriber receives Logistics Objects
The company identifier from the Internet of Logistics of my company.
Content types that the subscriber wants to receive in the notifications
Either a secret or API Key that ensures that only companies with this subscription information can POST to the subscriber callback endpoint
Flag specifying if the subscriber wants to receive updates for a Logistics Object
Flag specifying if the publisher should send the whole logistics object or not in the notification object
Duration of the period to cache the subscription information in seconds
Link to the initial version of the Logistics Object
Link to the time gate of the Logistics Object, if applicable
Audit trail of a Logistics Object
AuditTrail
Company information in the Internet of Logistics
CompanyInformation
Change Request for the audit trail
ChangeRequest
Operation Request contained in the PATCH body
Operation
Delegation Request to 3rd parties
DelegationRequest
Details
Error model
Error
Reference to a Logistics Object
LogisticsObjectRef
Version of a Logistics Object
Memento
Memento list model
Mementos
MementoList
Memento entry from the time map
MementoEntry
Notification sent by the publisher to the subscriber
Notification
Object to modify in the PATCH request
OperationObject
PATCH Request body containing updates on a Logistics Object
PatchRequest
Subscription information sent to the publisher
Subscription
Timemap of a Logistics Object containing mementos and timegate URI
Timemap