Changelog
Data Model Ontology 3.3.0¶
All changes have been tracked on GitHub via issues and have been linked to the Pull-Requests.
Detailed Changelog¶
Detailed changelog can be found in the associated GitHub commits:
Pull Request #394:¶
Additions:
- Added securityDeclarations to Shipment (#346)
- Added issuedForShipment to SecurityDeclaration (#344 & #346)
- Added totalVolume to Shipment (#347)
- Added contactDetails to Organization (#347)
- Added agentReference to Waybill (#347)
- Added otherIdentifiers to Waybill (#347 & #353)
- Added StatusUpdateEvent as subclass of LogisticsEvent (#350)
- Added recordedPieceCount to StatusUpdateEvent (#350)
- Added recordedWeight to StatusUpdateEvent (#350)
- Added recordedVolume to StatusUpdateEvent (#350)
- Added notifiedOrganization to StatusUpdateEvent (#350)
- Added transferredTo to StatusUpdateEvent (#350)
- Added transferredFrom to StatusUpdateEvent (#350)
- Added notifiedOrganization to StatusUpdateEvent (#350)
- Added restriction for eventFor to Shipment to StatusUpdateEvent (#350)
- Added restriction for eventCode to StatusCode to StatusUpdateEvent (#350)
- Added transportMovementReference to StatusUpdateEvent (#350)
- Added valuationCharge to Waybill (#350)
- Added otherIdentifiers to LogisticsActivity (#350)
- Added otherIdentifiers to PhysicalLogisticsObject (#350)
- Added regulatedEntitiesReceivedFrom to SecurityDeclaration (#350)
Removals:
Bugfixes:
- Fixed vis_element datatype from string to literal
- Fixed erratic owl:comment axioms to rdfs:comment for :AccountNumber and :handlingServiceFor
API 2.3.0¶
For this release, all changes have been tracked using GitHub project view: API Changes.
Detailed changelog¶
Below is the detailed changelog:
- Bulk endpoint for identical LogisticsEvents
- Unable to determine the acceptance date of a change request
- Only 1 Type in LO header possible, but multiple @type in LO bodies
- Expiration on AccessDelegations
- Inconsistencies in Status Query Parameters
- Allow rejection of subscription proposals
- Mechanism to communicate warnings within Verification Requests
- Access Delegation: Restrict api:isRequestedFor from n to 1
- Clarify and Define API Behavior for Revoking ActionRequests in Invalid States
- Unclear Roles in Action Requests
- Add standard errors to ONE Record specifications
More information can be found in the API Changelog page or directly on the change page.