Intelligent transport systems - Public transport - Open API for distributed journey planning

This Technical Specification defines a schema for establishing an Open API for Distributed Journey Planning that can be implemented by any local, regional or national journey planning system in order to exchange journey planning information with any other participating local, regional or national journey planning system.

Intelligente Verkehrssysteme - Öffentlicher Verkehr - Offene API für verteilte Reiseplanung

Inteligentni transportni sistemi - Javni potniški promet - Odprt API za načrtovanje porazdeljenih poti

Ta tehnična specifikacija opredeljuje shemo za vzpostavljanje odprtega programskega vmesnika za distribuirano načrtovanje poti, ki ga lahko uvede katerikoli lokalni, regionalni ali nacionalni sistem za načrtovanje poti za namene izmenjave informacij o načrtovanju poti z drugimi sodelujočimi lokalnimi, regionalnimi ali nacionalnimi sistemi za načrtovanje poti.

General Information

Status
Withdrawn
Publication Date
31-Oct-2017
Withdrawal Date
10-Dec-2024
Current Stage
6060 - Definitive text made available (DAV) - Publishing
Start Date
01-Nov-2017
Due Date
27-Nov-2017
Completion Date
01-Nov-2017

Buy Standard

Technical specification
TS CEN/TS 17118:2018 - BARVE
English language
140 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-februar-2018
,QWHOLJHQWQLWUDQVSRUWQLVLVWHPL-DYQLSRWQLãNLSURPHW2GSUW$3,]DQDþUWRYDQMH
SRUD]GHOMHQLKSRWL
Intelligent transport systems - Public transport - Open API for distributed journey
planning
Intelligente Verkehrssysteme - Öffentlicher Verkehr - Offene API für verteilte
Reiseplanung
Ta slovenski standard je istoveten z: CEN/TS 17118:2017
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

CEN/TS 17118
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
November 2017
TECHNISCHE SPEZIFIKATION
ICS 35.240.60
English Version
Intelligent transport systems - Public transport - Open API
for distributed journey planning
Intelligente Verkehrssysteme - Öffentlicher Verkehr -
Offene API für verteilte Reiseplanung
This Technical Specification (CEN/TS) was approved by CEN on 28 August 2017 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2017 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 17118:2017 E
worldwide for CEN national Members.

Contents Page
European foreword . 10
0 Introduction . 11
0.1 General . 11
0.2 An Open API for distributed journey planning (OJP) . 11
0.3 The public transport information tensions . 11
0.4 Distributed journey planning architecture beyond scope . 12
0.4.1 General . 12
0.4.2 The distributed journey planning approach . 13
0.4.3 Distributed or centralised approaches . 13
0.4.4 The basis for the Open API . 14
0.4.5 Other possible uses for the Open API . 14
0.5 The European ITS Directive . 14
1 Scope . 15
2 Normative references . 15
3 Terms and definitions . 15
4 Symbols and abbreviations . 32
5 Use cases . 33
5.1 General . 33
5.2 Key tasks for Distributed Journey Planning . 34
5.2.1 Planning a component of a trip . 34
5.2.2 Discovering relevant stops . 35
5.2.3 Obtaining information about accessibility and services for those with special needs . 35
5.2.4 Seeking route information that can be displayed on maps . 35
5.3 Other possible tasks for a Distributed Journey Planning system . 35
5.3.1 Requesting a stop timetable . 35
5.3.2 Requesting times for all intermediate stops in a trip . 35
5.3.3 Requesting expected events at a particular stop . 36
5.3.4 Requesting information about the fares and ticket options for a particular trip . 36
5.3.5 Other possible questions . 36
6 System Architectures, Metadata and Data . 36
6.1 General . 36
6.2 General considerations . 36
6.3 Metadata requirements . 38
6.4 Core data requirements . 38
7 Open API for Distributed Journey Planning – OJP Services . 40
7.1 Departure Monitor . 40
7.1.1 Purpose . 40
7.1.2 Interactions . 41
7.1.3 Concerned Components . 41
7.1.4 Function 1: Departure Monitor . 41
7.2 Fare Information . 42
7.2.1 Purpose . 42
7.2.2 Interactions . 42
7.2.3 Concerned Components . 43
7.2.4 Function 1: Tariff Zones for Stop / Station . 44
7.2.5 Function 2: Static Fare Information . 44
7.2.6 Function 3: Trip-Related Fare Information . 44
7.3 Location text matching . 44
7.3.1 Purpose . 44
7.3.2 Interactions . 45
7.3.3 Concerned Components . 45
7.3.4 Function: Location text matching . 45
7.4 Object Information Service . 45
7.4.1 Purpose . 45
7.4.2 Interactions . 46
7.4.3 Concerned Components . 46
7.4.4 Function 1: Object Information . 46
7.4.5 Function 2: Finding relevant exchange points . 46
8 Open API for Distributed Journey Planning – Interface Description . 47
8.1 Notation of XML-Elements and XML-Structures . 47
8.1.1 General . 47
8.1.2 Display of XML Elements in the Text . 47
8.1.3 Display of Relationships . 47
8.1.4 Table Notation of XML Structures . 48
8.1.4.1 General . 48
8.1.4.2 Grouping . 49
8.1.4.3 Element Name . 49
8.1.4.4 Multiplicity & Choice (min:max) . 49
8.1.4.5 Data Type . 49
8.1.4.6 Explanation . 50
8.1.5 Message Exchange . 50
8.1.6 Use of SIRI Procedure . 50
8.1.7 HTTP and REST . 51
8.1.8 Roles of Server and Client . 52
8.2 Identification of Objects beyond system borders . 52
8.2.1 General . 52
8.2.2 Stops and Stopping Points . 52
8.2.3 Localities and Districts . 53
8.2.4 Addresses and POIs .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.