Our mission
Your needs
Standards
Developers
Newsroom
Get involved
About us
Our mission
Your needs
Standards
Developers
Newsroom
Get involved
About us
Developer Portal
Search
Search input bar
All 219
website 203
developer portal 16
1. Introduction - Bill of Lading 3.0
The objective of the DCSA Interface Standard for the Bill of Lading is to simplify the exchange of information between shipper, carrier and consignee, as related to Transport Documents.
Website
Standards
Standard Documentation Overview | Bill of Lading 3.0 Beta 2
In collaboration with its member carriers, DCSA has developed OpenAPI specifications supporting the use cases and user stories defined in the DCSA Interface Standards.
Website
Standards
Interoperability is key to unlocking digital's potential in the shipping industry | DCSA
DCSA's Niels Nuyen sat down with Parsan Chand of Lenzing AG to discuss the importance of common standards in advancing digital transformation.
Website
Newsroom article
5. Technical appendix - Booking 2.0
This technical appendix provides technical information required for understanding how to implement the DCSA standard API specifications for Booking 2.0.0 and Bill of Lading 3.0.0. It serves as a critical resource for technical teams responsible for implementing the DCSA standard APIs, providing the necessary information to ensure a successful deployment and operation.
Website
Standards
4. State Transition Diagrams - Booking 2.0
A state transition diagram is a graphical representation used in system modeling to depict the various states an object or system can exist in and the transitions between those states. It consists of nodes representing different states and arrows representing transitions between states. Events (defined by use cases) or conditions trigger these transitions.
Website
Standards
3. Use cases - Booking 2.0
In line with the techniques used in software development, DCSA has incorporated user stories and use cases into the standards development process to support the digitalization efforts of the shipping industry. Both user stories and use cases serve the purpose of capturing and documenting requirements, but they differ in granularity, level of detail, and the stages of the development process in which they are most prominently used. They are complementary (a user story may be supported by one or more use cases and vice versa) and can be used together to provide a comprehensive understanding of software requirements. In this section we will focus on use cases.
Website
Standards
33
34
35
36
37