I 4 Align trips to transmodel OJP - UnionInternationalCheminsdeFer/OSDM GitHub Wiki

I-4: Align /locations and /trips to Transmodal (OJP)

Description

Align /locations and /trips modeling with the Open Journey Protocol (OJP) of Transmodel.

Owner

  • Matthias Günter / Schlapbach Andreas (SBB)

Business Value

For customers

who request public transportation trips from A to B

the API contains Transmodel oriented types which

is a standard for journey search

that makes it easier to use Transmodel implementing systems

unlike proprietary structures or obsolete standards

our solution focus on newest European guidelines.

Business Outcomes

The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct.

  • Compliancy with this CEN standard
  • Assure compliance with other OJP implementations
  • Developers who are used to Transmodel implementations (like OJP) feel familiar with the implementation and thus can deliver results fast.

Leading Indicators

The early measures that will help predict the business outcome hypothesis.

  • Easy and fast integration with journey planning software in 2021.

Nonfunctional Requirements

Nonfunctional requirements (NFRs) associated with the epic.

  • REST best practice.

Context

The OJP initiative was born to answer the esigence to exchange accurate and timely information about public transport (PT) services and to implement systems able to provide Multi-modal information for longer-distance journeys.

Several systems have been developed to answer to this requirement, based on different architecture, but he nature of the enquiries sent between the systems, and the content of the responses sent in return, were essentially the same. This suggested that it would be possible to define a single Open Journey Planning API to support all distributed journey planning systems.

OJP allows a system to engineer just one interface that it can make available rather than having to engineer separate APIs for each bipartite exchange arrangement that may be required with other systems.

The establishment of Open APIs has been enabled by increasingly standardized in Public Transport by following the principles set out in the “Public Transport Reference Data Model” (Transmodel) EN standard, and its related implementation Standards and specifications.

(source: http://www.transmodel-cen.eu/standards/ojp/)

Specification Effort: SMALL