SIST-TS CEN/TS 17118:2018
(Main)Intelligent transport systems - Public transport - Open API for distributed journey planning
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
Standards Content (Sample)
SLOVENSKI STANDARD
SIST-TS CEN/TS 17118:2018
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
SIST-TS CEN/TS 17118:2018 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST-TS CEN/TS 17118:2018
---------------------- Page: 2 ----------------------
SIST-TS CEN/TS 17118:2018
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.
---------------------- Page: 3 ----------------------
SIST-TS CEN/TS 17118:2018
CEN/TS 17118:2017 (E)
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
2
---------------------- Page: 4 ----------------------
SIST-TS CEN/TS 17118:2018
CEN/TS 17118:2017 (E)
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 . 53
8.2.5 Organisations: Transport Companies and Transport Authorities. 53
8.2.6 Lines and Line Directions . 54
8.2.7 Journeys . 54
8.2.8 Vehicles . 55
8.2.9 Operating Days . 55
8.2.10 Owners . 55
8.2.11 Stop- and Vehicle Equipment . 55
8.2.12 Participating Systems / IT Systems . 55
8.2.13 Incident Messages. 56
8.2.14 Fare Authority . 56
8.2.15 Tariff Zones . 56
8.2.16 Tickets and Traveller Cards . 56
8.3 Services and XML Schemas . 56
8.3.1 General . 56
8.3.2 Services Provided . 56
3
---------------------- Page: 5 ----------------------
SIST-TS CEN/TS 17118:2018
CEN/TS 17118:2017 (E)
8.3.3 XML Schemas Used Across Services . 57
8.3.4 Imported Schemas . 58
8.3.5 Error States When Operating OJP Services . 58
8.3.6 Error Codes from SIRI . 59
8.3.7 General OJP Error States . 60
8.3.8 Time Zones . 60
8.4 Common XML Structures . 60
8.4.1 General . 60
8.4.2 Root Element OJP . 60
8.4.2.1 General . 60
8.4.2.2 ServiceRequestStructure . 61
8.4.2.3 ServiceDeliveryStructure . 63
8.4.3 OJP_Utility . 64
8.4.3.1 General . 64
8.4.3.2 Simple Types . 64
8.4.3.3 InternationalTextStructure . 65
8.4.3.4 GeoPositionStructure . 65
8.4.3.5 WebLinkStructure . 65
8.4.4 OJP_ModesSupport. 65
8.4.4.1 General . 65
8.4.4.2 Simple Types . 65
8.4.4.3 The subsequent sections describe the complex structures defined in
OJP_ModesSupport. IndividualTransportOptionsStructure . 67
8.4.4.4 PtSubmodeChoiceGroup . 67
8.4.4.5 ModeStructure . 68
8.4.4.6 PtModeFilterStructure . 68
8.4.4.7 PrivateModeFilterStructure . 68
8.4.5 OJP_Common . 68
8.4.5.1 Simple Types . 68
8.4.5.2 ErrorMessageStructure . 69
8.4.5.3 PrivateCodeStructure . 69
8.4.5.4 OperatorFilterStructure . 69
8.4.5.5 LineDirectionStructure . 69
8.4.5.6 LineDirectionFilterStructure . 69
8.4.5.7 SharingServiceStructure . 70
8.4.5.8 OperatingDaysStructure . 70
8.4.5.9 WeekdayTimePeriodStructure . 70
8.4.5.10 GeneralAttributeStructure . 71
8.4.6 OJP_LocationSupport . 71
8.4.6.1 General . 71
4
---------------------- Page: 6 ----------------------
SIST-TS CEN/TS 17118:2018
CEN/TS 17118:2017 (E)
8.4.6.2 Simple Types . 71
8.4.6.3 StopPointStructure . 72
8.4.6.4 StopPlaceStructure . 72
8.4.6.5 TopographicPlaceStructure . 73
8.4.6.6 PointOfInterestStructure . 73
8.4.6.7 PointOfInterestCategoryStructure . 74
8.4.6.8 OsmTagStructure . 74
8.4.6.9 PointOfInterestFilterStructure . 74
8.4.6.10 AddressStructure . 75
8.4.6.11 PlaceStructure . 75
8.4.6.12 PlaceRefStructure . 76
8.4.6.13 ExchangePointsFilterStructure . 76
8.4.7 OJP_JourneySupport . 76
8.4.7.1 General . 76
8.4.7.2 ServiceViaPointStructure . 76
8.4.7.3 TripViaStructure . 77
8.4.7.4 DatedJourneyGroup . 77
8.4.7.5 PrivateServiceGroup . 77
8.4.7.6 DatedJourneyStructure . 78
8.4.7.7 TripLocationStructure . 78
8.4.7.8 CallAtStopStructure . 79
8.4.7.9 DatedCallAtLocationStructure . 80
8.4.7.10 ContinuousServiceStructure . 80
8.4.7.11 VehiclePositionStructure . 81
8.4.7.12 ProgressBetweenStopsStructure. 82
8.4.7.13 PlaceContextStructure . 82
8.4.7.14 AbstractResponseContextStructure . 82
8.4.7.15 LegAttributeStructure . 83
8.4.7.16 LegTrackStructure . 83
8.4.7.17 TrackSectionStructure . 83
8.4.8 OJP_FacilitySupport . 83
8.4.8.1 General . 83
8.4.8.2 siri:CommonFacilityGroup . 83
8.4.8.3 siri:StopFacilityGroup . 84
8.4.8.4 siri:ServiceFacilityGroup . 85
8.4.8.5 siri:AllFacilitiesGroup . 85
8.4.9 OJP_SituationSupport .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.