{"id":231876,"date":"2024-10-19T15:06:24","date_gmt":"2024-10-19T15:06:24","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-15531-22015-tc\/"},"modified":"2024-10-25T09:28:17","modified_gmt":"2024-10-25T09:28:17","slug":"bs-en-15531-22015-tc","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-15531-22015-tc\/","title":{"rendered":"BS EN 15531-2:2015 – TC"},"content":{"rendered":"

SIRI uses a consistent set of general communication protocols to exchange information between client and server. The same pattern of message exchange may be used to implement different specific functional interfaces as sets of concrete message content types. Two well-known specific patterns of client server interaction are used for data exchange in SIRI: Request\/Response and Publish\/Subscribe. \u2014 Request\/Response allows for the ad hoc exchange of data on demand from the client. \u2014 Publish\/Subscribe allows for the repeated asynchronous push of notifications and data to distribute events and Situations detected by a Real-time Service. The use of the Publish\/Subscribe pattern of interaction follows that described in the Publish-Subscribe Notification for Web Services (WS-PubSub) specification, and as far as possible, SIRI uses the same separation of concerns and common terminology for publish\/subscribe concepts and interfaces as used in WS-PubSub. WS-PubSub breaks down the server part of the Publish\/Subscribe pattern into a number of separate named roles and interfaces (for example, Subscriber, Publisher, Notification Producer, and Notification Consumer): in an actual SIRI implementation, certain of these distinct interfaces may be combined and provided by a single entity. Although SIRI is not currently implemented as a full WS-PubSub web service, the use of a WS-PubSub architecture makes this straightforward to do in future. Publish\/Subscribe will not normally be used to support large numbers of end user devices. For the delivery of data in responses (to both requests and subscriptions), SIRI supports two common patterns of message exchange, as realised in existent national systems: \u2014 A one step \u2018 Direct Delivery\u2019, as per the classic client-server paradigm, and normal WS-PubSub publish subscribe usage; and; \u2014 A two-step \u2018 Fetched Delivery\u2019 which elaborates the delivery of messages into a sequence of successive messages pairs to first notify the client, and then to send the data when the client is ready. Fetched Delivery is a stateful pattern in its own right. Each delivery pattern allows different trade-offs for implementation efficiency to be made as appropriate for different target environments. A SIRI implementation may support either or both delivery methods; in order to make the most efficient use of the available computational and communication resources. The delivery method may either be preconfigured and static for a given implementation, or each request or subscription may indicate the delivery method required by the client dynamically as part of the request policy, and the server may refuse a request if it does not support that method, giving an appropriate error code. The Interaction patterns and the Delivery patterns are independent aspects of the SIRI protocol and may be used in any combination in different implementations. For a given SIRI Functional Service type (Connection Monitoring, Stop Monitoring etc.), the message payload content is the same regardless of whether information is exchanged with a Request\/Response or Publish\/Subscribe pattern, or whether it is returned by Direct or Fetched Delivery. The SIRI Publish\/Subscribe Protocol prescribes particular mediation behaviour for reducing the number of notifications and the amount of network traffic arising from subscriptions. The mediation groups the various subscriptions from a subscriber into one or more Subscriber Channels, and is able to manage notifications and updates for the aggregate. Only partial updates to the data set since the last delivery for the subscription need to be sent. The SIRI Communication protocols are designed to fail gracefully. Considerations for resilience and recovery are covered below.<\/p>\n

PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
1<\/td>\ncompares BS EN 15531-2:2015 <\/td>\n<\/tr>\n
2<\/td>\nTRACKED CHANGES
Text example 1 \u2014 indicates added text (in green) <\/td>\n<\/tr>\n
150<\/td>\nContents Page <\/td>\n<\/tr>\n
152<\/td>\nEuropean foreword <\/td>\n<\/tr>\n
153<\/td>\nIntroduction <\/td>\n<\/tr>\n
154<\/td>\n1 Scope <\/td>\n<\/tr>\n
155<\/td>\n2 Normative references
3 Terms and definitions
4 Symbols and abbreviations
5 Common communication aspects
5.1 Data Exchange Patterns of Interaction
5.1.1 Introduction
5.1.2 Request\/Response Pattern <\/td>\n<\/tr>\n
156<\/td>\nFigure 1 \u2014 Request \/ Response Interaction
5.1.3 Publish\/Subscribe Pattern <\/td>\n<\/tr>\n
157<\/td>\nFigure 2 \u2014 Simple Publish\/Subscribe Interaction
5.1.4 Publish\/Subscribe with Broker Pattern <\/td>\n<\/tr>\n
158<\/td>\nFigure 3 \u2014 Brokered Publish\/Subscribe Interaction
5.1.5 Request\/Response \u2013 Compound Requests
Figure 4 \u2014 Request\/Response: Compound Requests <\/td>\n<\/tr>\n
159<\/td>\n5.1.6 Publish\/Subscribe \u2013 Compound Subscriptions
Figure 5 \u2014 Publish\/Subscribe: Compound Subscriptions
5.2 Delivery Patterns
5.2.1 Introduction
5.2.2 Direct Delivery
Figure 6 \u2014 One Step Direct Delivery <\/td>\n<\/tr>\n
160<\/td>\n5.2.3 Fetched Delivery
Figure 7 \u2014 Fetched Delivery <\/td>\n<\/tr>\n
161<\/td>\nFigure 8 \u2014 Fetched Delivery for Publish\/Subscribe
5.2.4 Data Horizon for Fetched Delivery <\/td>\n<\/tr>\n
162<\/td>\nFigure 9 \u2014 Fetched Delivery for Request\/Response
5.2.5 Get Current Message
5.2.6 Multipart Despatch of a Delivery <\/td>\n<\/tr>\n
163<\/td>\nFigure 10 \u2014 Multipart Delivery
5.2.7 Multipart Despatch of a Fetched Delivery \u2013 MoreData
Figure 11 \u2014 Fetched Multipart Delivery <\/td>\n<\/tr>\n
164<\/td>\n5.3 Mediation Behaviour
5.3.1 Introduction
5.3.2 Mediation Behaviour \u2013 Maintaining Subscription Last Updated State <\/td>\n<\/tr>\n
165<\/td>\nFigure 12 \u2014 Mediation: Update Tracking and sensitivity threshold for Direct Delivery <\/td>\n<\/tr>\n
166<\/td>\nFigure 13 \u2014 Mediation: Handling Fetched Delivery Latencies
5.3.3 Mediation Behaviour \u2013 Subscription Filters <\/td>\n<\/tr>\n
168<\/td>\nFigure 14 \u2014 Mediation: Subscription Filter
5.4 Recovery Considerations for Publish Subscribe
5.4.1 Introduction <\/td>\n<\/tr>\n
169<\/td>\n5.4.2 Check Status \u2013 Polling
Figure 15 \u2014 Check Status \u2014 UML Sequence
5.4.3 Heartbeat \u2013 Pinging
Figure 16 \u2014 Heartbeat Message \u2014 UML Sequence
5.4.4 Degrees of Failure <\/td>\n<\/tr>\n
170<\/td>\n5.4.5 Detecting a Failure of the Producer
5.4.5.1 Detecting a Failure Using Check Status
Figure 17 \u2014 Check Status with Recovery & Re-subscribe \u2014 UML Sequence
5.4.5.2 Detecting a Failure Using Heartbeat <\/td>\n<\/tr>\n
171<\/td>\nFigure 18 \u2014 Heartbeat Monitoring \u2013 Loss of Service \u2014 UML Sequence
Figure 19 \u2014 Heartbeat Monitoring \u2013 Interruption of Service \u2014 UML Sequence
5.4.6 Detecting a Failure of the Consumer <\/td>\n<\/tr>\n
172<\/td>\n5.5 Recovery Considerations for Direct Delivery
Figure 20 \u2014 Robust Direct Delivery \u2014 UML Sequence
5.6 Request Parameters and Interactions <\/td>\n<\/tr>\n
173<\/td>\nTable 1 \u2014 SIRI Request and Subscription Parameters <\/td>\n<\/tr>\n
174<\/td>\nTable 2 \u2014 Topics and Policies for SIRI Functional Service Types <\/td>\n<\/tr>\n
175<\/td>\n5.7 Error Conditions for Requests
Table 3 \u2014 System and Application Error Conditions <\/td>\n<\/tr>\n
176<\/td>\nTable 4 \u2014 Application Error Conditions Related to Request Parameters <\/td>\n<\/tr>\n
177<\/td>\n5.8 Versioning
5.8.1 Introduction
5.8.2 The Overall SIRI Framework Version Level
5.8.3 The SIRI Functional Service Type Version Level
5.9 Access Controls: Security and Authentication
5.9.1 Introduction
5.9.2 System Mechanisms External to SIRI Messages
5.9.2.1 General <\/td>\n<\/tr>\n
178<\/td>\n5.9.2.2 Authentication Key (+SIRI v2.0)
5.9.2.3 Application Level Authentication
5.9.2.4 The Access Permission Matrix
5.9.2.5 Request Authentication
5.10 Service Discovery
5.10.1 Introduction
5.10.2 Discovery of Servers that Support SIRI Services <\/td>\n<\/tr>\n
179<\/td>\n5.10.3 Discovery of the Capabilities of a SIRI Server
5.10.4 Discovery of the Coverage of a Given SIRI Functional Service
Table 5 \u2014 SIRI Discovery Service Matrix <\/td>\n<\/tr>\n
180<\/td>\n5.11 Capability Matrix
5.11.1 Introduction
5.11.2 SIRI General Capabilities
Table 6 \u2014 SIRI General Capabilities <\/td>\n<\/tr>\n
181<\/td>\n6 Request\/Response
6.1 Making a Direct Request
6.1.1 Introduction
Table 7 \u2014 SIRI Request Delivery Types <\/td>\n<\/tr>\n
182<\/td>\n6.1.2 ServiceRequest Message \u2014 Element
Table 8 \u2014 ServiceRequest \u2014 Attributes <\/td>\n<\/tr>\n
183<\/td>\n6.1.3 The ServiceRequestContext \u2014 Element
6.1.3.1 General <\/td>\n<\/tr>\n
184<\/td>\nTable 9 \u2014 ServiceRequestContext Parameters <\/td>\n<\/tr>\n
185<\/td>\n6.1.3.2 DeliveryMethod \u2014 Allowed values
Table 10 \u2014 DeliveryMethod \u2014Allowed Values (SIRI 2.0)
6.1.3.3 AllowedPredictors \u2014 Allowed values
Table 11 \u2014 AllowedPredictors \u2014Allowed Values (SIRI 2.0)
6.1.4 Common Properties of ServiceRequest Messages \u2014 Element <\/td>\n<\/tr>\n
186<\/td>\nTable 12 \u2014 SIRI Functional Service Common Request \u2014 Attributes
6.1.5 ServiceRequest \u2014 Example
6.1.6 Access Controls on a Request <\/td>\n<\/tr>\n
187<\/td>\n6.2 Receiving a Data Delivery
6.2.1 Introduction <\/td>\n<\/tr>\n
188<\/td>\nTable 13 \u2014 Delivery Content Elements
6.2.2 ServiceDelivery
6.2.2.1 ServiceDelivery\u2014 Element <\/td>\n<\/tr>\n
189<\/td>\nTable 14 \u2014 ServiceDelivery\u2014 Attributes <\/td>\n<\/tr>\n
190<\/td>\n6.2.2.2 Common Properties of SIRI Functional Service Delivery Messages
Table 15 \u2014 SIRI Function Service xxxDelivery\u2014 Attributes <\/td>\n<\/tr>\n
191<\/td>\n6.2.2.3 ServiceDelivery \u2014 Example <\/td>\n<\/tr>\n
192<\/td>\n7 Subscriptions
7.1 Setting up Subscriptions
7.1.1 Introduction <\/td>\n<\/tr>\n
193<\/td>\nTable 16 \u2014 SIRI Request and Delivery Types <\/td>\n<\/tr>\n
194<\/td>\n7.1.2 SubscriptionRequest
7.1.2.1 SubscriptionRequest \u2014 Element
Table 17 \u2014 SubscriptionRequest \u2014 Attributes <\/td>\n<\/tr>\n
195<\/td>\n7.1.2.2 SubscriptionRequestContext \u2014 Element
Table 18 \u2014 SubscriptionContext \u2014 Attributes <\/td>\n<\/tr>\n
196<\/td>\n7.1.2.3 The Common Properties of SIRI Functional Service Subscription Requests
Table 19 \u2014 SIRI Functional Service Common Subscription \u2014 Attributes
7.1.2.4 SubscriptionRequest \u2014 Example
7.1.3 SubscriptionResponse
7.1.3.1 SubscriptionResponse \u2014 Element <\/td>\n<\/tr>\n
197<\/td>\nTable 20 \u2014 SubscriptionResponse \u2014 Attributes <\/td>\n<\/tr>\n
198<\/td>\nTable 21 \u2014 ResponseStatus \u2014 Attributes
7.1.3.2 SubscriptionResponse \u2014 Example <\/td>\n<\/tr>\n
199<\/td>\n7.2 Subscription Validity
7.3 Terminating Subscriptions
7.3.1 Introduction
7.3.2 The TerminateSubscriptionRequest
7.3.2.1 TerminateSubscriptionRequest \u2014 Element <\/td>\n<\/tr>\n
200<\/td>\nTable 22 \u2014 TerminateSubscriptionRequest \u2014 Attributes
7.3.2.2 TerminateSubscriptionRequest \u2014 Example
7.3.3 The TerminateSubscriptionResponse
7.3.3.1 TerminateSubscriptionResponse \u2014 Element <\/td>\n<\/tr>\n
201<\/td>\nTable 23 \u2014 TerminateSubscriptionResponse \u2014 Attributes
7.3.3.2 TerminateSubscriptionResponse \u2014 Example <\/td>\n<\/tr>\n
202<\/td>\n7.3.4 The SubscriptionTerminatedNotification (SIRI 2.0)
7.3.4.1 SubscriptionTerminatedNotification \u2014 Element
Table 24 \u2014 SubscriptionTerminatedNotification \u2014 Attributes <\/td>\n<\/tr>\n
203<\/td>\n7.3.4.2 SubscriptionTerminatedNotification \u2014 Example
8 Delivering data
8.1 Direct Delivery
8.1.1 Introduction <\/td>\n<\/tr>\n
204<\/td>\n8.1.2 Acknowledging Receipt of Data (DataReceivedAcknowledgement)
8.1.2.1 DataReceivedAcknowledgement \u2014 Element
Table 25 \u2014 DataReceivedAcknowledgement \u2014 Attributes
8.1.2.2 DataReceivedAcknowledgement \u2014 Example
8.2 Fetched Delivery
8.2.1 Introduction <\/td>\n<\/tr>\n
205<\/td>\n8.2.2 Signalling Data Availability (DataReadyNotification \/ DataReadyResponse)
8.2.2.1 Procedure
8.2.2.2 DataReadyNotification\u2014 Element
Table 26 \u2014 DataReadyNotification \u2014 Attributes
8.2.2.3 DataReadyNotification \u2014 Example <\/td>\n<\/tr>\n
206<\/td>\n8.2.2.4 DataReadyAcknowledgement\u2014 Element
Table 27 \u2014 DataReadyAcknowledgement \u2014 Attributes
8.2.2.5 DataReadyAcknowledgement \u2014 Example <\/td>\n<\/tr>\n
207<\/td>\n8.2.3 Polling Data (DataSupplyRequest\/ServiceDelivery)
8.2.3.1 Procedure
8.2.3.2 DataSupplyRequest Message \u2014 Element
Table 28 \u2014 DataSupplyRequest \u2014 Attributes <\/td>\n<\/tr>\n
208<\/td>\n8.2.3.3 DataSupplyRequest \u2014 Example
8.2.3.4 ServiceDelivery Message
8.3 Delegated Delivery +SIRI 2.0
9 Recovery from system failure
9.1 Introduction
9.2 Recovery after Client Failure <\/td>\n<\/tr>\n
209<\/td>\n9.3 Recovery after Server Failure
9.4 Reset after Interruption of Communication
Table 29 \u2014 Error Statuses and Actions in Communication Failure Conditions <\/td>\n<\/tr>\n
210<\/td>\n9.5 Alive Handling
9.5.1 Introduction
9.5.2 CheckStatusRequest
9.5.2.1 CheckStatusRequest Message \u2014 Element
Table 30 \u2014 CheckStatusRequest \u2014 Attributes <\/td>\n<\/tr>\n
211<\/td>\n9.5.2.2 CheckStatusRequest \u2014 Example
9.5.3 CheckStatusResponse
9.5.3.1 CheckStatusResponse Message \u2014 Element
Table 31 \u2014 CheckStatusResponse \u2014 Attributes <\/td>\n<\/tr>\n
212<\/td>\n9.5.3.2 CheckStatusResponse \u2014 Example <\/td>\n<\/tr>\n
213<\/td>\n9.5.4 HeartbeatNotification
9.5.4.1 Heartbeat Message \u2014 Element
Table 32 \u2014 HeartbeatNotification \u2014 Attributes
9.5.4.2 HeartbeatNotification \u2014 Example <\/td>\n<\/tr>\n
214<\/td>\n9.6 Additional Failure modes for delegated delivery (+SIRI v2.0)
10 Transport of SIRI messages
10.1 Separation of Addressing from Transport Protocol
10.2 Logical Endpoint Addresses
10.2.1 Endpoint Addresses <\/td>\n<\/tr>\n
215<\/td>\nTable 33 \u2014 Server Logical Endpoints
Table 34 \u2014 Client Logical Endpoints
10.2.2 Endpoint Address \u2014 Examples <\/td>\n<\/tr>\n
216<\/td>\nTable 35 \u2014 Client Logical Endpoints
10.3 Parallelism and Endpoint Addresses <\/td>\n<\/tr>\n
217<\/td>\n10.4 Encoding of XML messages
10.4.1 Principles
10.4.2 Encoding of Errors in XML
10.4.3 Character Set
10.4.4 Schema Packages <\/td>\n<\/tr>\n
218<\/td>\nFigure 21 \u2014 SIRI Schema Packages
10.4.5 Siri.XSD \u2013 Use of XML Choice <\/td>\n<\/tr>\n
219<\/td>\nFigure 22 \u2014 Example for XML choice <\/td>\n<\/tr>\n
220<\/td>\n10.4.6 SiriSG.XSD \u2013 Use of XML Substitution groups
Figure 23 \u2014 Example: XML Substitution groups <\/td>\n<\/tr>\n
221<\/td>\n10.5 Use of SIRI with SOAP \/ WSDL
10.5.1 Introduction
10.5.2 Web Services
10.5.2.1 General
10.5.2.2 SOAP (Simple Object Access Protocol) <\/td>\n<\/tr>\n
222<\/td>\n10.5.2.3 WSDL (Web Services Definition Language) <\/td>\n<\/tr>\n
223<\/td>\nFigure 24 \u2014 WSDL 1.1 and 2.0 main concepts (source http:\/\/en.wikipedia.org\/wiki\/File:WSDL_11vs20.png)
10.5.3 Use of SOAP
10.5.4 SIRI WSDL
10.5.4.1 SIRI WSDL Definition
10.5.4.2 WSDL 1.1 encoding styles <\/td>\n<\/tr>\n
224<\/td>\n10.5.5 SIRI WSDL structure
Table 36 \u2014 SIRI Producer functional services <\/td>\n<\/tr>\n
225<\/td>\nTable 37 \u2014 SIRI Producer communication management and utility services
Table 38 \u2014 SIRI Consumer notification <\/td>\n<\/tr>\n
226<\/td>\nFigure 25 \u2014 SIRI SOAP Producer Document\/Literal WSDL
Figure 26 \u2014 SIRI SOAP Consumer RPC\/Literal WSDL
10.5.6 SIRI RPC WSDL
10.5.6.1 General <\/td>\n<\/tr>\n
227<\/td>\n10.5.6.2 WSDL RPC Example: StopTimetable Service
Figure 27 \u2014 SIRI SOAP WSDL GetStopTimetable detail
10.5.6.3 SOAP Example: Monitoring Service
Table 39 \u2014 SOAP Example: GetStopMonitoring request <\/td>\n<\/tr>\n
228<\/td>\nTable 40 \u2014 SOAP Example Message: GetStopMonitoring Answer <\/td>\n<\/tr>\n
231<\/td>\n10.5.7 SIRI Document WSDL (+SIRI v2.0)
Table 41 \u2014 SOAP Message Structures; XSD files
10.5.8 SIRI WSDL 2.0 (+SIRI v2.0)
10.5.9 SIRI WSDL Status
11 Capability Discovery Requests
11.1 General
11.2 Capability Request <\/td>\n<\/tr>\n
232<\/td>\nTable 42 \u2014 CapabilityDiscoveryRequest <\/td>\n<\/tr>\n
233<\/td>\n11.3 Service Capability Discovery
11.3.1 Service Capability Discovery Request \u2014 Element
Table 43 \u2014 SIRI Service CapabilityDiscoveryRequest \u2014 Attributes
11.3.2 Service Capability Discovery Response \u2014 Element <\/td>\n<\/tr>\n
234<\/td>\nTable 44 \u2014 CapabilityDiscoveryResponse \u2014 Attributes
11.3.3 Functional Service Capability Discovery Response \u2014 Element
11.3.3.1 General <\/td>\n<\/tr>\n
235<\/td>\nTable 45 \u2014 SIRI Common Capability Responses
11.3.3.2 CommunicationsTransportMethod \u2014 Allowed values <\/td>\n<\/tr>\n
236<\/td>\nTable 46 \u2014 CommunicationsTransportMethod \u2014 Allowed Values (SIRI 2.0)
11.3.3.3 CompressionMethod \u2014 Allowed values
Table 47 \u2014 CompressionMethod \u2014 Allowed Values (SIRI 2.0) <\/td>\n<\/tr>\n
237<\/td>\n11.3.4 Service Capability Response \u2014 Example <\/td>\n<\/tr>\n
238<\/td>\n11.4 Functional Service Capability Permission Matrix
11.4.1 Introduction <\/td>\n<\/tr>\n
239<\/td>\nTable 48 \u2014 SIRI Functional Service Common Permission \u2014 Attributes
11.4.2 OperatorPermissions \u2014 Element
Table 49 \u2014 OperatorPermissions \u2014 Attributes <\/td>\n<\/tr>\n
240<\/td>\n11.4.3 LinePermissions \u2014 Element
Table 50 \u2014 LinePermissions \u2014 Attributes
11.4.4 ConnectionLinkPermissions \u2014 Element
Table 51 \u2014 ConnectionLinkPermissions \u2014 Attributes
11.4.5 StopMonitorPermissions \u2014 Element <\/td>\n<\/tr>\n
241<\/td>\nTable 52 \u2014 StopMonitorPermissions \u2014 Attributes
11.4.6 VehicleMonitorPermissions \u2014 Element
Table 53 \u2014 VehicleMonitorPermissions \u2014 Attributes
11.4.7 InfoChannelPermissions \u2014 Element
Table 54 \u2014 InfoChannelPermissions \u2014 Attributes <\/td>\n<\/tr>\n
242<\/td>\n12 SIRI for Simple Web Services \u2013 SIRI Lite (+SIRI v2.0)
12.1 Introduction
12.1.1 General <\/td>\n<\/tr>\n
243<\/td>\n12.1.2 Existing Implementations
12.1.3 Using SIRI-LITE services in combination
12.1.3.1 General
12.1.3.2 Providing real-time Stop Arrivals & Departures \u2013 Use Case for SIRI LITE
12.1.3.3 Vehicle positions \u2013 Use Case for SIRI LITE <\/td>\n<\/tr>\n
244<\/td>\n12.1.4 Alternative Response Encoding
Table 55 \u2013 Alternative Response Encodings for SIRI Simple Web Services
12.1.5 Lossless transforms
12.1.6 Simple transforms
12.2 Encoding of URL Requests
12.2.1 Complete Request Encoding in HTTP URL\u2019s <\/td>\n<\/tr>\n
245<\/td>\n12.2.2 General format of SIRI Lite request URL
12.2.3 Endpoints and Service Identification
12.2.4 Encoding of Service Parameters on http request <\/td>\n<\/tr>\n
246<\/td>\n12.2.5 Naming of Request Parameters with Hierarchy
12.2.6 Naming of Parameters with Plural Cardinality
12.2.7 Handling of invalid request combinations
12.2.8 Specifying the encoding of the Response
12.3 Examples
12.3.1 General <\/td>\n<\/tr>\n
247<\/td>\n12.3.2 SIRI-SM Simple Stop Monitoring request to fetch stop departures \u2013 SIRI LITE Examples
12.3.2.1 General
12.3.2.2 Simple Stop Monitoring request to fetch stop departures \u2013 XML Example
12.3.2.3 Simple Stop Monitoring request to return stop departures \u2013 JSON Example
12.3.2.4 Simple Stop Monitoring response to return stop departures \u2013 XML Example <\/td>\n<\/tr>\n
248<\/td>\n12.3.2.5 Simple Stop Monitoring response to return stop departures \u2013 JSON Example <\/td>\n<\/tr>\n
250<\/td>\n12.3.3 SIRI-VM Simple Vehicle Monitoring request to fetch vehicle positions \u2013 SIRI Lite Examples
12.3.3.1 General
12.3.3.2 Simple Vehicle Monitoring request to fetch vehicle positions \u2013 XML Example <\/td>\n<\/tr>\n
251<\/td>\n12.3.3.3 Simple Vehicle Monitoring request to fetch vehicle positions \u2013 JSON Example
12.3.3.4 Simple Vehicle Monitoring response to return vehicle positions \u2013 XML Example <\/td>\n<\/tr>\n
252<\/td>\n12.3.3.5 Simple Vehicle Monitoring response to return vehicle positions \u2013 JSON Example <\/td>\n<\/tr>\n
253<\/td>\n12.3.4 SIRI-VM Complex Vehicle Monitoring to obtain journeys \u2013 SIRI Lite Examples
12.3.4.1 General
12.3.4.2 Complex Vehicle Monitoring request to fetch monitored journeys \u2013 XML Example
12.3.4.3 Complex Vehicle Monitoring request to fetch monitored journeys \u2013 RESTful Example
12.3.4.4 Complex Vehicle Monitoring response to return monitored journeys \u2013 XML Example <\/td>\n<\/tr>\n
256<\/td>\n12.3.4.5 Complex Vehicle Monitoring response to return monitored journeys \u2013 JSON Example <\/td>\n<\/tr>\n
259<\/td>\n12.3.5 SIRI-SM Stop Monitoring failed request with Exception \u2013 SIRI LITE Examples
12.3.5.1 General
12.3.5.2 Simple Stop Monitoring response to return exceptions \u2013 XML Example <\/td>\n<\/tr>\n
260<\/td>\n12.3.5.3 Simple Stop Monitoring response to return exceptions \u2013 JSON Example
12.4 Mapping of SIRI XML to Alternative encodings
12.4.1 Use of syntactic features of alternative rendering formats
12.4.2 Mapping of SIRI data types to alternative encodings <\/td>\n<\/tr>\n
261<\/td>\n12.5 Recommendations for the use of SIRI Simple Web Services
12.5.1 General
12.5.2 Services useful for device Passenger Information Services
12.5.3 Response filtering
12.5.4 Incorporation of reference data in responses
12.5.5 Multiple functional service deliveries in the same response <\/td>\n<\/tr>\n
262<\/td>\n12.5.6 Support a choice of response encodings
12.5.7 Provide reporting identifiers
13 Common SIRI elements & Data Types
13.1 General
Table 56 SIRI \u2013 NETEX equivalents <\/td>\n<\/tr>\n
263<\/td>\n13.2 Introduction
13.3 Base Data Types
13.3.1 W3C Simple Types
Table 57 \u2014 W3C XML simple data types used in SIR <\/td>\n<\/tr>\n
264<\/td>\n13.3.2 SIRI Simple Types
Table 58 \u2014 SIRI simple data types used in SIRI
13.3.3 NationalLanguageStringStructure \u2014 Element
13.4 Shared Elements & Structures
13.4.1 FramedVehicleJourneyRef \u2014 Element <\/td>\n<\/tr>\n
265<\/td>\nTable 59 \u2014 FramedVehicleJourneyRef
13.4.2 Location \u2014 Element
Table 60 \u2014 Location
13.4.3 Error \u2014 Element
13.4.3.1 General
Table 61 \u2014 Error Code <\/td>\n<\/tr>\n
266<\/td>\n13.4.3.2 Error Conditions \u2014 Elements
Table 62 \u2014 Error Conditions
13.5 Shared groups of elements
13.5.1 ServiceInfoGroup \u2014 Group <\/td>\n<\/tr>\n
267<\/td>\nTable 63 \u2014 ServiceInfoGroup \u2014 Elements
13.5.2 JourneyInfoGroup \u2014 Group
Table 64 \u2014 JourneyInfoGroup \u2014 Elements
13.5.3 VehicleJourneyInfoGroup \u2014 Group
13.5.3.1 General <\/td>\n<\/tr>\n
268<\/td>\nTable 65 \u2014 VehicleJourneyInfoGroup \u2014 Elements <\/td>\n<\/tr>\n
269<\/td>\n13.5.3.2 FirstOrLastJourney \u2014 Allowed values
Table 66 \u2014 FirstOrLastJourney \u2014Allowed Values (SIRI 2.0)
13.5.4 JourneyPatternInfoGroup \u2014 Group
13.5.4.1 General
Table 67 \u2014 JourneyPatternInfoGroup \u2014 Elements <\/td>\n<\/tr>\n
270<\/td>\n13.5.4.2 VehicleMode \u2014 Allowed values
Table 68 \u2014 VehicleMode \u2014 Allowed Values (SIRI 2.0)
13.5.5 DisruptionGroup \u2014 Group
13.5.5.1 General
Table 69 \u2014 DisruptionGroup \u2014 Elements
13.5.5.2 FacilityChangeElement \u2014 Element <\/td>\n<\/tr>\n
271<\/td>\nTable 70 \u2014 FacilityChangeElement \u2014 Elements <\/td>\n<\/tr>\n
272<\/td>\n13.5.5.3 EquipmentStatus \u2014 Allowed values
Table 71 \u2014 EquipmentStatus \u2014Allowed Values
13.5.5.4 MobilityFacility \u2014 Allowed values
Table 72 \u2014 MobilityFacility \u2014Allowed Values
13.5.6 JourneyProgressGroup \u2014 Group
13.5.6.1 General <\/td>\n<\/tr>\n
273<\/td>\nTable 73 \u2014 JourneyProgressGroup \u2014 Elements
13.5.6.2 MonitoringError \u2014 Allowed values
Table 74 \u2014 MonitoringError \u2014Allowed Values <\/td>\n<\/tr>\n
274<\/td>\n13.5.6.3 ConfidenceLevel \u2014 Allowed values
Table 75 \u2014 ConfidenceLevel \u2014Allowed Values
13.5.6.4 ProgressRate \u2014 Allowed values
Table 76 \u2014 ProgressRate \u2014Allowed Values
13.5.6.5 Occupancy \u2014 Allowed values
Table 77 \u2014 Occupancy \u2014Allowed Values <\/td>\n<\/tr>\n
275<\/td>\n13.5.6.6 CallStatus \u2014 Allowed values
Table 78 \u2014 CallStatus \u2014Allowed Values
13.5.6.7 VehicleStatus \u2014 Allowed values
Table 79 \u2014 VehicleStatus \u2014Allowed Values <\/td>\n<\/tr>\n
276<\/td>\n13.6 OperationalBlockGroup \u2014 Group
Table 80 \u2014 OperationalBlockGroup \u2014 Elements
13.7 OperationalInfoGroup \u2014 Group
Table 81 \u2014 OperationalInfoGroup \u2014 Elements <\/td>\n<\/tr>\n
277<\/td>\nBibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Tracked Changes. Public transport. Service interface for real-time information relating to public transport operations – Communications<\/b><\/p>\n\n\n\n\n
Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
BSI<\/b><\/a><\/td>\n2020<\/td>\n280<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":231878,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[698,2641],"product_tag":[],"class_list":{"0":"post-231876","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-35-240-60","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/231876","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/231878"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=231876"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=231876"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=231876"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}