Technical Documentation
The Technical Documentation describes the architecture, security model and technical specifications that enable interoperability within the BoB ecosystem.
The BoB standard allows independent ticketing systems operated by different participants to issue, exchange and validate tickets across organisational boundaries. To support this, the standard defines a set of common concepts, technical specifications and system interfaces.
This section provides the detailed technical documentation required to implement BoB-compatible systems.
Structure of the Technical Documentation
The technical documentation is organised into four main areas.
Area | Description |
|---|---|
Ticketing Concepts | Describes the ticket models used in BoB, including electronic tickets and ID-based travelling. |
Security & Trust | Defines how participants authenticate, exchange keys and establish trust between systems. |
MTS Documentation | Provides the technical specifications that define ticket structure, signatures and validation rules. |
BoB API Documentation | Describes the APIs used by systems to issue tickets, validate travel rights and exchange operational data. |
Together these components define how ticketing systems can interoperate while allowing participants to maintain their own internal systems and implementations.
Who should read this section?
The Technical Documentation is intended for:
system architects designing BoB-compatible solutions
developers implementing ticketing systems
vendors building validation and inspection equipment
integrators connecting multiple ticketing systems
Related Documentation
Additional guidance for implementing BoB can be found in:
Introduction to the BoB Standard
Getting Started with BoB
Testing and Validation in BoB
Change Management for the BoB Standard