1. SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services
1.1. The toplevel element siri:CapabilitiesRequest
|
|
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||||
1.2. The toplevel element siri:CapabilitiesResponse
|
|
Responses with the capabilities of an implementation. |
||||
1.3. The toplevel element siri:ServiceDelivery
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delvery message with more current updates that follows this one. Default is 'false'. |
||
|
1:* |
Subsititutable type for a SIRI Functional Service request. |
||||
1.4. The toplevel element siri:ServiceRequest
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General request properties - typically configured rather than repeated on request. |
|||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
1.5. The toplevel element siri:Siri
|
|
- |
||||
|
|
1:1 |
||||
|
The element contains one of the following elements (a-c) |
|||||
|
The element contains one of the following elements (a-d) |
|||||
|
The element contains one of the following elements (a-c) |
|||||
| siri:ServiceRequestGroup |
aaa |
-1:1 |
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) |
||
|
aab |
-1:1 |
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. |
|||
|
aac |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
The element contains one of the following elements (a-b) |
|||||
| siri:DeliveryRequestGroup |
aba |
-1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
||
|
abb |
-1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
|||
|
The element contains one of the following elements (a-b) |
|||||
| siri:StatusRequestGroup |
aca |
-1:1 |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
||
|
acb |
-1:1 |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
|
The element contains one of the following elements (a-b) |
|||||
| siri:DiscoveryRequestGroup |
ada |
-1:1 |
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||
|
adb |
-1:1 |
Abstract Discovery request. |
|||
|
The element contains one of the following elements (a-d) |
|||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:ServiceResponseGroup |
baa |
-1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
||
|
bab |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
The element contains one of the following elements (a-c) |
|||||
| siri:DeliveryResponseGroup |
bba |
-1:1 |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
||
|
bbb |
-1:1 |
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. |
|||
|
bbc |
-1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
|
The element contains one of the following elements (a) |
|||||
| siri:StatusResponseGroup |
bca |
-1:1 |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
||
|
The element contains one of the following elements (a-b) |
|||||
| siri:DiscoveryResponseGroup |
bda |
-1:1 |
Responses with the capabilities of an implementation. |
||
|
bdb |
-1:1 |
Abstract type for a discovery delivery. |
|||
|
c |
-0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
|||
1.6. The toplevel element siri:SubscriptionRequest
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
|
1:* |
Subsititutable type for a SIRI Functional Service subscription request. |
||||
1.7. The group siri:DeliveryResponseGroup
|
|
Responses that deliver payload content. |
||||
|
The element contains one of the following elements (a-c) |
|||||
| siri:DeliveryResponseGroup |
a |
-1:1 |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
||
|
b |
-1:1 |
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. |
|||
|
c |
-1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
1.8. The group siri:RequestGroup
|
|
SIRI All Requests. |
||||
|
The element contains one of the following elements (a-d) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ac) |
|||||
| siri:ServiceRequestGroup |
aa |
-1:1 |
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) |
||
|
ab |
-1:1 |
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. |
|||
|
ac |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'b', the element contains one of the following elements (ba-bb) |
|||||
| siri:DeliveryRequestGroup |
ba |
-1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
||
|
bb |
-1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
|||
|
In case of choice 'c', the element contains one of the following elements (ca-cb) |
|||||
| siri:StatusRequestGroup |
ca |
-1:1 |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
||
|
cb |
-1:1 |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
|
In case of choice 'd', the element contains one of the following elements (da-db) |
|||||
| siri:SiriDiscoveryRequestGroup |
da |
-1:1 |
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||
|
In case of choice 'db', the element contains one of the following elements (dba-dbh) |
|||||
| siri:SiriReferenceDiscoveryRequestGroup |
dba |
-1:1 |
Requests a list of the STOP POINTs and places covered by a Producer. |
||
|
dbb |
-1:1 |
Requests a list of the LINEs covered by a Producer. |
|||
|
dbc |
-1:1 |
Requests a list of the Service Features covered by a Producer. |
|||
|
dbd |
-1:1 |
Requests a list of the Product Categories covered by a Producer. |
|||
|
dbe |
-1:1 |
Requests a list of the Vehicle Features covered by a Producer. |
|||
|
dbf |
-1:1 |
Requests a list of the Info Channels covered by a Producer. |
|||
|
dbg |
-1:1 |
Requests a list of the Facilities covered by a Producer. |
|||
|
dbh |
-1:1 |
Requests a list of the CONNECTION LINKs covered by a Producer. (since SIRI 2.0) |
|||
1.9. The group siri:ResponseGroup
|
|
SIRI Service Responses. |
||||
|
The element contains one of the following elements (a-d) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ab) |
|||||
| siri:ServiceResponseGroup |
aa |
-1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
||
|
ab |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'b', the element contains one of the following elements (ba-bc) |
|||||
| siri:DeliveryResponseGroup |
ba |
-1:1 |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
||
|
bb |
-1:1 |
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. |
|||
|
bc |
-1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
|
In case of choice 'c', the element contains one of the following elements (ca) |
|||||
| siri:StatusResponseGroup |
ca |
-1:1 |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
||
|
In case of choice 'd', the element contains one of the following elements (da-db) |
|||||
| siri:SiriDiscoveryResponseGroup |
da |
-1:1 |
Responses with the capabilities of an implementation. |
||
|
In case of choice 'db', the element contains one of the following elements (dba-dbh) |
|||||
| siri:SiriDiscoveryReferenceDeliveryGroup |
dba |
-1:1 |
Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest. |
||
|
dbb |
-1:1 |
Returns the LINEs covered by a web service. Answers a LINEsRequest. |
|||
|
dbc |
-1:1 |
Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. |
|||
|
dbd |
-1:1 |
Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest. |
|||
|
dbe |
-1:1 |
Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. |
|||
|
dbf |
-1:1 |
Returns the Info Channels covered by a service. Answers a InfoChannelRequest. |
|||
|
dbg |
-1:1 |
Returns the Facilities covered by a service. Answers a StopPointsRequest. |
|||
|
dbh |
-1:1 |
Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. (since SIRI 2.0) |
|||
1.10. The group siri:ServiceDeliveryBodyGroup
|
|
Elements for SIRI Service Delivery. |
||||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. |
||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
| siri:SiriServiceDeliveryGroup |
a |
-0:* |
Delivery of Situation Exchange Service included as supplement to main functional service delivery. |
||
|
In case of choice 'a', the element contains one of the following elements (aa-aj) |
|||||
|
aa |
-1:* |
Delivery for Production Timetable Service. |
|||
|
ab |
-1:* |
Delivery for Estimated Timetable Service. |
|||
|
ac |
-1:* |
Delivery for Stop Timetable Service. |
|||
|
ad |
-1:* |
Delivery for Stop Monitoring Service. |
|||
|
ae |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
af |
-1:* |
Delivery for Connection Timetable Service. |
|||
|
ag |
-1:* |
Feeder Delivery for Connection Monitoring Service. |
|||
|
ah |
-1:* |
Distributor Delivery for Connection Monitoring Service. |
|||
|
ai |
-1:* |
Delivery for General Message Service. |
|||
|
aj |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
b |
-1:* |
Delivery for Situation Exchange Service. |
|||
1.11. The group siri:ServiceRequestGroup
|
|
Requests for service provision. |
||||
|
The element contains one of the following elements (a-c) |
|||||
| siri:ServiceRequestGroup |
a |
-1:1 |
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) |
||
|
b |
-1:1 |
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. |
|||
|
c |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
1.12. The group siri:ServiceResponseGroup
|
|
Responses to requests other than deliveries and status information. |
||||
|
The element contains one of the following elements (a-c) |
|||||
| siri:ServiceResponseGroup |
a |
-1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
||
|
b |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
c |
-1:1 |
Notification from Subscriber to Subscription Manager to terminate a subscription. |
|||
1.13. The group siri:SiriDiscoveryRequestGroup
|
|
Requests for reference data for use in SIRI Functional Service requests. |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:SiriDiscoveryRequestGroup |
a |
-1:1 |
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||
|
In case of choice 'b', the element contains one of the following elements (ba-bh) |
|||||
| siri:SiriReferenceDiscoveryRequestGroup |
ba |
-1:1 |
Requests a list of the STOP POINTs and places covered by a Producer. |
||
|
bb |
-1:1 |
Requests a list of the LINEs covered by a Producer. |
|||
|
bc |
-1:1 |
Requests a list of the Service Features covered by a Producer. |
|||
|
bd |
-1:1 |
Requests a list of the Product Categories covered by a Producer. |
|||
|
be |
-1:1 |
Requests a list of the Vehicle Features covered by a Producer. |
|||
|
bf |
-1:1 |
Requests a list of the Info Channels covered by a Producer. |
|||
|
bg |
-1:1 |
Requests a list of the Facilities covered by a Producer. |
|||
|
bh |
-1:1 |
Requests a list of the CONNECTION LINKs covered by a Producer. (since SIRI 2.0) |
|||
1.14. The group siri:SiriDiscoveryResponseGroup
|
|
Responses with reference data for use in SIRI Functional Service requests. |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:SiriDiscoveryResponseGroup |
a |
-1:1 |
Responses with the capabilities of an implementation. |
||
|
In case of choice 'b', the element contains one of the following elements (ba-bh) |
|||||
| siri:SiriDiscoveryReferenceDeliveryGroup |
ba |
-1:1 |
Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest. |
||
|
bb |
-1:1 |
Returns the LINEs covered by a web service. Answers a LINEsRequest. |
|||
|
bc |
-1:1 |
Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. |
|||
|
bd |
-1:1 |
Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest. |
|||
|
be |
-1:1 |
Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. |
|||
|
bf |
-1:1 |
Returns the Info Channels covered by a service. Answers a InfoChannelRequest. |
|||
|
bg |
-1:1 |
Returns the Facilities covered by a service. Answers a StopPointsRequest. |
|||
|
bh |
-1:1 |
Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. (since SIRI 2.0) |
|||
1.15. The group siri:SiriServiceCapabilitiesRequestGroup
|
|
Defines the capabilities of an individual SIRI service request functions. |
||||
| siri:SiriServiceCapabilitiesRequestGroup |
0:1 |
Request for information about ProductionTimetable Service Capabilities. Answered with a ProductionTimetableCapabilitiesResponse. |
|||
|
0:1 |
Request for information about Estimated Timetable Service Capabilities. Answered with a EstimatedTimetableCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Stop Monitoring Service Capabilities. Answered with StopMonitoringCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Connection Timetable Service Capabilities. Answered with a ConnectionTimetableCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Connection Monitoring Service Capabilities. Answered with a ConnectionMontoringCapabilitiesResponse. |
||||
|
0:1 |
Request for information about General Message Service Capabilities. Answered with a GeneralMessageCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Situation Exchange Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
||||
1.16. The group siri:SiriServiceCapabilitiesResponseGroup
|
|
Defines the capabilities of an individual SIRI service response functions. |
||||
| siri:SiriServiceCapabilitiesResponseGroup |
0:1 |
Capabilities for ProductionTimetable Service. Answers a Answered with a ProductionTimetableCapabilitiesRequest. |
|||
|
0:1 |
Capabilities for Estimated Timetable Service. Answers a EstimatedTimetableCapabilitiesRequest. |
||||
|
0:1 |
Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Stop Monitoring Service. Answers a StopMonitoringCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Connection Timetable Service. Answers a ConnectionTimetableCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Connection Monitoring Service. Answers a ConnectionMontoringCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for General Message Service. Answers a GeneralMessageCapabilitiesResponse. |
||||
|
0:1 |
Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Situation Exchange Service. Answers a VehicleMontoringCapabilitiesRequest. |
||||
1.17. The group siri:SiriServiceDeliveryGroup
|
|
SIRI Functional Service Delivery types. |
||||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
| siri:SiriServiceDeliveryGroup |
a |
-0:* |
Delivery of Situation Exchange Service included as supplement to main functional service delivery. |
||
|
In case of choice 'a', the element contains one of the following elements (aa-aj) |
|||||
|
aa |
-1:* |
Delivery for Production Timetable Service. |
|||
|
ab |
-1:* |
Delivery for Estimated Timetable Service. |
|||
|
ac |
-1:* |
Delivery for Stop Timetable Service. |
|||
|
ad |
-1:* |
Delivery for Stop Monitoring Service. |
|||
|
ae |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
af |
-1:* |
Delivery for Connection Timetable Service. |
|||
|
ag |
-1:* |
Feeder Delivery for Connection Monitoring Service. |
|||
|
ah |
-1:* |
Distributor Delivery for Connection Monitoring Service. |
|||
|
ai |
-1:* |
Delivery for General Message Service. |
|||
|
aj |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
b |
-1:* |
Delivery for Situation Exchange Service. |
|||
1.18. The group siri:SiriServiceRequestGroup
|
|
SIRI Functional Service Concrete Requests. |
||||
|
The element contains one of the following elements (a-k) |
|||||
| siri:SiriServiceRequestGroup |
a |
-1:* |
Request for daily production timetables. |
||
|
b |
-1:* |
Request for information about the estimated timetable. |
|||
|
c |
-1:* |
Request for information about Stop Visits, i.e. arrival and departure at a stop. |
|||
|
d |
-1:* |
Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop. SIRI 1.3 |
|||
|
e |
-1:* |
Request for information about Stop Visits, i.e. arrivals and departures at a stop. |
|||
|
f |
-1:* |
Request for information about Vehicle Movements. |
|||
|
g |
-1:* |
Request for information about timetabled connections at a stop. |
|||
|
h |
-1:* |
Request for information about changes to connections at a stop for Connection Monitoring service. |
|||
|
i |
-1:* |
Request for information about general information messages affecting stops, vehicles or services. |
|||
|
j |
-1:* |
Request for information about Facilities status. |
|||
|
k |
-1:* |
Request for information about Facilities status. |
|||
1.19. The group siri:SiriSubscriptionRequestGroup
|
|
SIRI Functional Service Subscription types. For a given SubscriptionRequest, must all be of the same service type. |
||||
|
The element contains one of the following elements (a-j) |
|||||
| siri:SiriSubscriptionRequestGroup |
a |
-1:* |
Request for a subscription to the Production Timetable Service. |
||
|
b |
-1:* |
Request for a subscription to the Estimated Timetable Service. |
|||
|
c |
-1:* |
Request for a subscription to Stop TimetablesService. |
|||
|
d |
-1:* |
Request for a subscription to Stop Monitoring Service. |
|||
|
e |
-1:* |
Request for a subscription to the Vehicle Monitoring Service. |
|||
|
f |
-1:* |
Subscription Request for information about Timetabled connections at a stop. |
|||
|
g |
-1:* |
Request for a subscription to Connection Monitoring Service. |
|||
|
h |
-1:* |
Request for a subscription to General Message Service. |
|||
|
i |
-1:* |
Request for a subscription to the Vehicle Monitoring Service. |
|||
|
j |
-1:* |
Request for a subscription to the Situation Exchange Service. |
|||
1.20. The complex type siri:CapabilitiesRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
||||
|
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
|||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SiriServiceCapabilitiesRequestGroup |
0:1 |
Request for information about ProductionTimetable Service Capabilities. Answered with a ProductionTimetableCapabilitiesResponse. |
|||
|
0:1 |
Request for information about Estimated Timetable Service Capabilities. Answered with a EstimatedTimetableCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Stop Monitoring Service Capabilities. Answered with StopMonitoringCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Connection Timetable Service Capabilities. Answered with a ConnectionTimetableCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Connection Monitoring Service Capabilities. Answered with a ConnectionMontoringCapabilitiesResponse. |
||||
|
0:1 |
Request for information about General Message Service Capabilities. Answered with a GeneralMessageCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
||||
|
0:1 |
Request for information about Situation Exchange Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
||||
1.21. The complex type siri:CapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
||||
| siri:SiriServiceCapabilitiesResponseGroup |
0:1 |
Capabilities for ProductionTimetable Service. Answers a Answered with a ProductionTimetableCapabilitiesRequest. |
|||
|
0:1 |
Capabilities for Estimated Timetable Service. Answers a EstimatedTimetableCapabilitiesRequest. |
||||
|
0:1 |
Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Stop Monitoring Service. Answers a StopMonitoringCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Connection Timetable Service. Answers a ConnectionTimetableCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Connection Monitoring Service. Answers a ConnectionMontoringCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for General Message Service. Answers a GeneralMessageCapabilitiesResponse. |
||||
|
0:1 |
Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. |
||||
|
0:1 |
Capabilities for Situation Exchange Service. Answers a VehicleMontoringCapabilitiesRequest. |
||||
1.22. The complex type siri:ServiceDeliveryBodyStructure
|
|
Type for SIRI Service Delivery Body.. |
||||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. |
||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
| siri:SiriServiceDeliveryGroup |
a |
-0:* |
Delivery of Situation Exchange Service included as supplement to main functional service delivery. |
||
|
In case of choice 'a', the element contains one of the following elements (aa-aj) |
|||||
|
aa |
-1:* |
Delivery for Production Timetable Service. |
|||
|
ab |
-1:* |
Delivery for Estimated Timetable Service. |
|||
|
ac |
-1:* |
Delivery for Stop Timetable Service. |
|||
|
ad |
-1:* |
Delivery for Stop Monitoring Service. |
|||
|
ae |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
af |
-1:* |
Delivery for Connection Timetable Service. |
|||
|
ag |
-1:* |
Feeder Delivery for Connection Monitoring Service. |
|||
|
ah |
-1:* |
Distributor Delivery for Connection Monitoring Service. |
|||
|
ai |
-1:* |
Delivery for General Message Service. |
|||
|
aj |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
b |
-1:* |
Delivery for Situation Exchange Service. |
|||
1.23. The complex type siri:ServiceDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. |
||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
| siri:SiriServiceDeliveryGroup |
a |
-0:* |
Delivery of Situation Exchange Service included as supplement to main functional service delivery. |
||
|
In case of choice 'a', the element contains one of the following elements (aa-aj) |
|||||
|
aa |
-1:* |
Delivery for Production Timetable Service. |
|||
|
ab |
-1:* |
Delivery for Estimated Timetable Service. |
|||
|
ac |
-1:* |
Delivery for Stop Timetable Service. |
|||
|
ad |
-1:* |
Delivery for Stop Monitoring Service. |
|||
|
ae |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
af |
-1:* |
Delivery for Connection Timetable Service. |
|||
|
ag |
-1:* |
Feeder Delivery for Connection Monitoring Service. |
|||
|
ah |
-1:* |
Distributor Delivery for Connection Monitoring Service. |
|||
|
ai |
-1:* |
Delivery for General Message Service. |
|||
|
aj |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
b |
-1:* |
Delivery for Situation Exchange Service. |
|||
1.24. The complex type siri:ServiceRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General request properties - typically configured rather than repeated on request. |
|||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
The element contains one of the following elements (a-k) |
|||||
| siri:SiriServiceRequestGroup |
a |
-1:* |
Request for daily production timetables. |
||
|
b |
-1:* |
Request for information about the estimated timetable. |
|||
|
c |
-1:* |
Request for information about Stop Visits, i.e. arrival and departure at a stop. |
|||
|
d |
-1:* |
Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop. SIRI 1.3 |
|||
|
e |
-1:* |
Request for information about Stop Visits, i.e. arrivals and departures at a stop. |
|||
|
f |
-1:* |
Request for information about Vehicle Movements. |
|||
|
g |
-1:* |
Request for information about timetabled connections at a stop. |
|||
|
h |
-1:* |
Request for information about changes to connections at a stop for Connection Monitoring service. |
|||
|
i |
-1:* |
Request for information about general information messages affecting stops, vehicles or services. |
|||
|
j |
-1:* |
Request for information about Facilities status. |
|||
|
k |
-1:* |
Request for information about Facilities status. |
|||
1.25. The complex type siri:SiriServiceDeliveryStructure
|
|
Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL. |
||||
|
The element contains one of the following element sequences (a) |
|||||
|
In case of choice 'a', the element contains one of the following elements (ab) or element sequences (aa) |
|||||
| siri:SiriServiceDeliveryGroup |
aa |
-0:* |
Delivery of Situation Exchange Service included as supplement to main functional service delivery. |
||
|
In case of choice 'aa', the element contains one of the following elements (aaa-aaj) |
|||||
|
aaa |
-1:* |
Delivery for Production Timetable Service. |
|||
|
aab |
-1:* |
Delivery for Estimated Timetable Service. |
|||
|
aac |
-1:* |
Delivery for Stop Timetable Service. |
|||
|
aad |
-1:* |
Delivery for Stop Monitoring Service. |
|||
|
aae |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
aaf |
-1:* |
Delivery for Connection Timetable Service. |
|||
|
aag |
-1:* |
Feeder Delivery for Connection Monitoring Service. |
|||
|
aah |
-1:* |
Distributor Delivery for Connection Monitoring Service. |
|||
|
aai |
-1:* |
Delivery for General Message Service. |
|||
|
aaj |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
ab |
-1:* |
Delivery for Situation Exchange Service. |
|||
1.26. The complex type siri:SiriSubscriptionRequestStructure
|
|
Type for SIRI Functional Service Subscription types. Used for WSDL exchanges. |
||||
|
The element contains one of the following elements (a-j) |
|||||
| siri:SiriSubscriptionRequestGroup |
a |
-1:* |
Request for a subscription to the Production Timetable Service. |
||
|
b |
-1:* |
Request for a subscription to the Estimated Timetable Service. |
|||
|
c |
-1:* |
Request for a subscription to Stop TimetablesService. |
|||
|
d |
-1:* |
Request for a subscription to Stop Monitoring Service. |
|||
|
e |
-1:* |
Request for a subscription to the Vehicle Monitoring Service. |
|||
|
f |
-1:* |
Subscription Request for information about Timetabled connections at a stop. |
|||
|
g |
-1:* |
Request for a subscription to Connection Monitoring Service. |
|||
|
h |
-1:* |
Request for a subscription to General Message Service. |
|||
|
i |
-1:* |
Request for a subscription to the Vehicle Monitoring Service. |
|||
|
j |
-1:* |
Request for a subscription to the Situation Exchange Service. |
|||
1.27. The complex type siri:SubscriptionRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
|
Inherited content is followed by own content: |
|||||
|
The element contains one of the following elements (a-j) |
|||||
| siri:SiriSubscriptionRequestGroup |
a |
-1:* |
Request for a subscription to the Production Timetable Service. |
||
|
b |
-1:* |
Request for a subscription to the Estimated Timetable Service. |
|||
|
c |
-1:* |
Request for a subscription to Stop TimetablesService. |
|||
|
d |
-1:* |
Request for a subscription to Stop Monitoring Service. |
|||
|
e |
-1:* |
Request for a subscription to the Vehicle Monitoring Service. |
|||
|
f |
-1:* |
Subscription Request for information about Timetabled connections at a stop. |
|||
|
g |
-1:* |
Request for a subscription to Connection Monitoring Service. |
|||
|
h |
-1:* |
Request for a subscription to General Message Service. |
|||
|
i |
-1:* |
Request for a subscription to the Vehicle Monitoring Service. |
|||
|
j |
-1:* |
Request for a subscription to the Situation Exchange Service. |
|||
1.28. The complex type group[siri:ServiceDeliveryRequestStatusGroup]/ErrorCondition#complexType (typedef-50.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
b |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
1.29. The complex type element[siri:SubscriptionRequest]#complexType (typedef-53.2)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
|
1:* |
Subsititutable type for a SIRI Functional Service subscription request. |
||||
1.30. The complex type element[siri:StopPointsRequest]#complexType (typedef-73.1)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
|
1:1 |
Version number of request. Fixed |
|||
|
The element contains one of the following elements (a-c) |
|||||
| siri:StopPointsDiscoveryRequestTopicGroup |
a |
|
-0:1 |
Rectangle containing stops be returned. ((since SIRI 2.0)) |
|
|
b |
|
-0:1 |
Circle containing stops be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) |
||
|
c |
|
-0:1 |
Filter the results to include only stops associated with the PLACE . ((since SIRI 2.0)) |
||
|
|
0:1 |
Filter the results to include only stops run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Filter the results to include only stops for the given LINE. ((since SIRI 2.0)) |
|||
| siri:StopPointsDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
1.31. The complex type element[siri:ServiceFeaturesRequest]#complexType (typedef-73.2)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
|
1:1 |
Version number of request. Fixed |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
1.32. The complex type element[siri:ProductionTimetableSubscriptionRequest]#complexType (typedef-74.2)
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
1:1 |
Request for daily production timetables. |
||||
| siri:ProductionTimetableSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
1.33. The complex type element[siri:ProductionTimetableCapabilitiesRequest]#complexType (typedef-74.3)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
|
1:1 |
Version number of request. Fixed. |
|||
|
|
0:1 |
Whether to include the requestors permissions in the response. Only applies if Access control capability supported. Default is 'false'. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
1.34. The complex type element[siri:Siri]#complexType (typedef-77.1)
|
|
- |
||||
|
|
1:1 |
||||
|
The element contains one of the following elements (a-c) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ad) |
|||||
|
In case of choice 'aa', the element contains one of the following elements (aaa-aac) |
|||||
| siri:ServiceRequestGroup |
aaa |
-1:1 |
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) |
||
|
aab |
-1:1 |
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. |
|||
|
aac |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'ab', the element contains one of the following elements (aba-abb) |
|||||
| siri:DeliveryRequestGroup |
aba |
-1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
||
|
abb |
-1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
|||
|
In case of choice 'ac', the element contains one of the following elements (aca-acb) |
|||||
| siri:StatusRequestGroup |
aca |
-1:1 |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
||
|
acb |
-1:1 |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
|
In case of choice 'ad', the element contains one of the following elements (ada-adb) |
|||||
| siri:DiscoveryRequestGroup |
ada |
-1:1 |
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||
|
adb |
-1:1 |
Abstract Discovery request. |
|||
|
In case of choice 'b', the element contains one of the following elements (ba-bd) |
|||||
|
In case of choice 'ba', the element contains one of the following elements (baa-bab) |
|||||
| siri:ServiceResponseGroup |
baa |
-1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
||
|
bab |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'bb', the element contains one of the following elements (bba-bbc) |
|||||
| siri:DeliveryResponseGroup |
bba |
-1:1 |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
||
|
bbb |
-1:1 |
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. |
|||
|
bbc |
-1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
|
In case of choice 'bc', the element contains one of the following elements (bca) |
|||||
| siri:StatusResponseGroup |
bca |
-1:1 |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
||
|
In case of choice 'bd', the element contains one of the following elements (bda-bdb) |
|||||
| siri:DiscoveryResponseGroup |
bda |
-1:1 |
Responses with the capabilities of an implementation. |
||
|
bdb |
-1:1 |
Abstract type for a discovery delivery. |
|||
|
c |
-0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
|||
1.35. The complex type element[siri:ServiceRequest]#complexType (typedef-77.2)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General request properties - typically configured rather than repeated on request. |
|||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
1.36. The complex type element[siri:SubscriptionRequest]#complexType (typedef-77.3)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
|
1:* |
Subsititutable type for a SIRI Functional Service subscription request. |
||||
1.37. The complex type element[siri:ServiceDelivery]#complexType (typedef-77.4)
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delvery message with more current updates that follows this one. Default is 'false'. |
||
|
1:* |
Subsititutable type for a SIRI Functional Service request. |
||||
2. SIRI Common Request Fra,mework
2.1. The toplevel element siri:CapabilitiesRequest
|
|
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||||
2.2. The toplevel element siri:CapabilitiesResponse
|
|
Responses with the capabilities of an implementation. |
||||
2.3. The toplevel element siri:ServiceDelivery
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delvery message with more current updates that follows this one. Default is 'false'. |
||
|
1:* |
Subsititutable type for a SIRI Functional Service request. |
||||
2.4. The toplevel element siri:ServiceRequest
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General request properties - typically configured rather than repeated on request. |
|||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:* |
Subsititutable type for a SIRI Functional Service request. |
||||
2.5. The toplevel element siri:SubscriptionRequest
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
|
1:* |
Subsititutable type for a SIRI Functional Service subscription request. |
||||
2.6. The group siri:DeliveryResponseGroup
|
|
Responses that deliver payload content. |
||||
|
The element contains one of the following elements (a-c) |
|||||
| siri:DeliveryResponseGroup |
a |
-1:1 |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
||
|
b |
-1:1 |
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. |
|||
|
c |
-1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
2.7. The group siri:DiscoveryRequestGroup
|
|
Requests for reference data for use in service requests. |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:DiscoveryRequestGroup |
a |
-1:1 |
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||
|
b |
-1:1 |
Abstract Discovery request. |
|||
2.8. The group siri:DiscoveryResponseGroup
|
|
Responses with reference data for use in service requests. |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:DiscoveryResponseGroup |
a |
-1:1 |
Responses with the capabilities of an implementation. |
||
|
b |
-1:1 |
Abstract type for a discovery delivery. |
|||
2.9. The group siri:RequestGroup
|
|
SIRI Requests. |
||||
|
The element contains one of the following elements (a-d) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ac) |
|||||
| siri:ServiceRequestGroup |
aa |
-1:1 |
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) |
||
|
ab |
-1:1 |
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. |
|||
|
ac |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'b', the element contains one of the following elements (ba-bb) |
|||||
| siri:DeliveryRequestGroup |
ba |
-1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
||
|
bb |
-1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
|||
|
In case of choice 'c', the element contains one of the following elements (ca-cb) |
|||||
| siri:StatusRequestGroup |
ca |
-1:1 |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
||
|
cb |
-1:1 |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
|
In case of choice 'd', the element contains one of the following elements (da-db) |
|||||
| siri:DiscoveryRequestGroup |
da |
-1:1 |
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||
|
db |
-1:1 |
Abstract Discovery request. |
|||
2.10. The group siri:ResponseGroup
|
|
SIRI Service Responses. |
||||
|
The element contains one of the following elements (a-d) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ab) |
|||||
| siri:ServiceResponseGroup |
aa |
-1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
||
|
ab |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'b', the element contains one of the following elements (ba-bc) |
|||||
| siri:DeliveryResponseGroup |
ba |
-1:1 |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
||
|
bb |
-1:1 |
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. |
|||
|
bc |
-1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
|
In case of choice 'c', the element contains one of the following elements (ca) |
|||||
| siri:StatusResponseGroup |
ca |
-1:1 |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
||
|
In case of choice 'd', the element contains one of the following elements (da-db) |
|||||
| siri:DiscoveryResponseGroup |
da |
-1:1 |
Responses with the capabilities of an implementation. |
||
|
db |
-1:1 |
Abstract type for a discovery delivery. |
|||
2.11. The group siri:ServiceDeliveryBodyGroup
|
|
Elements for SIRI Service Delivery type. |
||||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delvery message with more current updates that follows this one. Default is 'false'. |
||
|
1:* |
Subsititutable type for a SIRI Functional Service request. |
||||
2.12. The group siri:ServiceRequestGroup
|
|
Requests for service provision. |
||||
|
The element contains one of the following elements (a-c) |
|||||
| siri:ServiceRequestGroup |
a |
-1:1 |
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) |
||
|
b |
-1:1 |
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. |
|||
|
c |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
2.13. The group siri:ServiceResponseGroup
|
|
Responses to requests other than deliveries and status information. |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:ServiceResponseGroup |
a |
-1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
||
|
b |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
2.14. The complex type siri:CapabilitiesRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
||||
|
1:1 |
Subsititutable type for a SIRI Functional Service Capabiloitiesequest. |
||||
2.15. The complex type siri:CapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Subsititutable type for a SIRI Functional Service Capabiloitiesequest. |
||||
2.16. The complex type siri:ServiceDeliveryBodyStructure
|
|
Type for SIRI Service Delivery type. |
||||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. |
||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
| siri:SiriServiceDeliveryGroup |
a |
-0:* |
Delivery of Situation Exchange Service included as supplement to main functional service delivery. |
||
|
In case of choice 'a', the element contains one of the following elements (aa-aj) |
|||||
|
aa |
-1:* |
Delivery for Production Timetable Service. |
|||
|
ab |
-1:* |
Delivery for Estimated Timetable Service. |
|||
|
ac |
-1:* |
Delivery for Stop Timetable Service. |
|||
|
ad |
-1:* |
Delivery for Stop Monitoring Service. |
|||
|
ae |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
af |
-1:* |
Delivery for Connection Timetable Service. |
|||
|
ag |
-1:* |
Feeder Delivery for Connection Monitoring Service. |
|||
|
ah |
-1:* |
Distributor Delivery for Connection Monitoring Service. |
|||
|
ai |
-1:* |
Delivery for General Message Service. |
|||
|
aj |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
b |
-1:* |
Delivery for Situation Exchange Service. |
|||
2.17. The complex type siri:ServiceDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. |
||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
| siri:SiriServiceDeliveryGroup |
a |
-0:* |
Delivery of Situation Exchange Service included as supplement to main functional service delivery. |
||
|
In case of choice 'a', the element contains one of the following elements (aa-aj) |
|||||
|
aa |
-1:* |
Delivery for Production Timetable Service. |
|||
|
ab |
-1:* |
Delivery for Estimated Timetable Service. |
|||
|
ac |
-1:* |
Delivery for Stop Timetable Service. |
|||
|
ad |
-1:* |
Delivery for Stop Monitoring Service. |
|||
|
ae |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
af |
-1:* |
Delivery for Connection Timetable Service. |
|||
|
ag |
-1:* |
Feeder Delivery for Connection Monitoring Service. |
|||
|
ah |
-1:* |
Distributor Delivery for Connection Monitoring Service. |
|||
|
ai |
-1:* |
Delivery for General Message Service. |
|||
|
aj |
-1:* |
Delivery for Vehicle Monitoring Service. |
|||
|
b |
-1:* |
Delivery for Situation Exchange Service. |
|||
2.18. The complex type siri:ServiceRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General request properties - typically configured rather than repeated on request. |
|||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
2.19. The complex type siri:SiriSchema
|
|
- |
||||
|
|
1:1 |
||||
|
The element contains one of the following elements (a-c) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ad) |
|||||
|
In case of choice 'aa', the element contains one of the following elements (aaa-aac) |
|||||
| siri:ServiceRequestGroup |
aaa |
-1:1 |
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) |
||
|
aab |
-1:1 |
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. |
|||
|
aac |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'ab', the element contains one of the following elements (aba-abb) |
|||||
| siri:DeliveryRequestGroup |
aba |
-1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
||
|
abb |
-1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
|||
|
In case of choice 'ac', the element contains one of the following elements (aca-acb) |
|||||
| siri:StatusRequestGroup |
aca |
-1:1 |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
||
|
acb |
-1:1 |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
|
In case of choice 'ad', the element contains one of the following elements (ada-adb) |
|||||
| siri:SiriDiscoveryRequestGroup |
ada |
-1:1 |
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||
|
In case of choice 'adb', the element contains one of the following elements (adba-adbh) |
|||||
| siri:SiriReferenceDiscoveryRequestGroup |
adba |
-1:1 |
Requests a list of the STOP POINTs and places covered by a Producer. |
||
|
adbb |
-1:1 |
Requests a list of the LINEs covered by a Producer. |
|||
|
adbc |
-1:1 |
Requests a list of the Service Features covered by a Producer. |
|||
|
adbd |
-1:1 |
Requests a list of the Product Categories covered by a Producer. |
|||
|
adbe |
-1:1 |
Requests a list of the Vehicle Features covered by a Producer. |
|||
|
adbf |
-1:1 |
Requests a list of the Info Channels covered by a Producer. |
|||
|
adbg |
-1:1 |
Requests a list of the Facilities covered by a Producer. |
|||
|
adbh |
-1:1 |
Requests a list of the CONNECTION LINKs covered by a Producer. (since SIRI 2.0) |
|||
|
In case of choice 'b', the element contains one of the following elements (ba-bd) |
|||||
|
In case of choice 'ba', the element contains one of the following elements (baa-bab) |
|||||
| siri:ServiceResponseGroup |
baa |
-1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
||
|
bab |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'bb', the element contains one of the following elements (bba-bbc) |
|||||
| siri:DeliveryResponseGroup |
bba |
-1:1 |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
||
|
bbb |
-1:1 |
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. |
|||
|
bbc |
-1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
|
In case of choice 'bc', the element contains one of the following elements (bca) |
|||||
| siri:StatusResponseGroup |
bca |
-1:1 |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
||
|
In case of choice 'bd', the element contains one of the following elements (bda-bdb) |
|||||
| siri:SiriDiscoveryResponseGroup |
bda |
-1:1 |
Responses with the capabilities of an implementation. |
||
|
In case of choice 'bdb', the element contains one of the following elements (bdba-bdbh) |
|||||
| siri:SiriDiscoveryReferenceDeliveryGroup |
bdba |
-1:1 |
Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest. |
||
|
bdbb |
-1:1 |
Returns the LINEs covered by a web service. Answers a LINEsRequest. |
|||
|
bdbc |
-1:1 |
Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. |
|||
|
bdbd |
-1:1 |
Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest. |
|||
|
bdbe |
-1:1 |
Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. |
|||
|
bdbf |
-1:1 |
Returns the Info Channels covered by a service. Answers a InfoChannelRequest. |
|||
|
bdbg |
-1:1 |
Returns the Facilities covered by a service. Answers a StopPointsRequest. |
|||
|
bdbh |
-1:1 |
Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. (since SIRI 2.0) |
|||
|
c |
-0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
|||
2.20. The complex type siri:SubscriptionRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
|
Inherited content is followed by own content: |
|||||
|
1:* |
Subsititutable type for a SIRI Functional Service subscription request. |
||||
2.21. The complex type group[siri:ServiceDeliveryRequestStatusGroup]/ErrorCondition#complexType (typedef-50.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
b |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
2.22. The complex type element[siri:ServiceRequest]#complexType (typedef-53.1)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General request properties - typically configured rather than repeated on request. |
|||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:* |
Subsititutable type for a SIRI Functional Service request. |
||||
2.23. The complex type element[siri:SubscriptionRequest]#complexType (typedef-53.2)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
|
1:* |
Subsititutable type for a SIRI Functional Service subscription request. |
||||
2.24. The complex type element[siri:ServiceDelivery]#complexType (typedef-53.3)
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delvery message with more current updates that follows this one. Default is 'false'. |
||
|
1:* |
Subsititutable type for a SIRI Functional Service request. |
||||
2.25. The complex type element[siri:StopPointsRequest]#complexType (typedef-73.1)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
|
1:1 |
Version number of request. Fixed |
|||
|
The element contains one of the following elements (a-c) |
|||||
| siri:StopPointsDiscoveryRequestTopicGroup |
a |
|
-0:1 |
Rectangle containing stops be returned. ((since SIRI 2.0)) |
|
|
b |
|
-0:1 |
Circle containing stops be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) |
||
|
c |
|
-0:1 |
Filter the results to include only stops associated with the PLACE . ((since SIRI 2.0)) |
||
|
|
0:1 |
Filter the results to include only stops run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Filter the results to include only stops for the given LINE. ((since SIRI 2.0)) |
|||
| siri:StopPointsDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
2.26. The complex type element[siri:ServiceFeaturesRequest]#complexType (typedef-73.2)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
|
1:1 |
Version number of request. Fixed |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
2.27. The complex type element[siri:ServiceRequest]#complexType (typedef-77.2)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General request properties - typically configured rather than repeated on request. |
|||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
2.28. The complex type element[siri:SubscriptionRequest]#complexType (typedef-77.3)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
|
1:* |
Subsititutable type for a SIRI Functional Service subscription request. |
||||
2.29. The complex type element[siri:ServiceDelivery]#complexType (typedef-77.4)
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delvery message with more current updates that follows this one. Default is 'false'. |
||
|
1:* |
Subsititutable type for a SIRI Functional Service request. |
||||
3. SIRI Framework - Common Requests.
3.1. Simple type definitions
|
|
Delivery Method: Fetched or Direct Delivery. |
||||
|
|||||
|
|
Allowed values for predictors. |
||||
|
|||||
3.2. The toplevel element siri:CheckStatusRequest
|
|
+siri:CheckStatusRequestStructure (↔ siri:AbstractTrackedRequest) |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
|||
3.3. The toplevel element siri:CheckStatusResponse
|
|
+siri:CheckStatusResponseStructure (↔ siri:AbstractResponse) |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
|||
3.4. The toplevel element siri:DataReadyAcknowledgement
|
|
+siri:DataReadyResponseStructure (↔ siri:AbstractResponse) |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
|||
3.5. The toplevel element siri:DataReadyNotification
|
|
+siri:DataReadyRequestStructure (↔ siri:ProducerRequest) |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
|||
3.6. The toplevel element siri:DataReceivedAcknowledgement
|
|
+siri:DataReceivedResponseStructure (↔ siri:AbstractResponse) |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
3.7. The toplevel element siri:DataSupplyRequest
|
|
+siri:DataSupplyRequestStructure (↔ siri:AbstractRequest) |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
|||
3.8. The toplevel element siri:HeartbeatNotification
|
|
+siri:HeartbeatNotificationStructure (↔ siri:ProducerRequest) |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
3.9. The toplevel element siri:ResponseStatus
|
|
Contains infromation about the processing of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). |
||||
3.10. The toplevel element siri:SubscriptionResponse
|
|
+siri:SubscriptionResponseStructure (↔ siri:AbstractResponse) |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
|||
3.11. The toplevel element siri:SubscriptionTerminatedNotification
|
|
+siri:SubscriptionTerminatedNotificationStructure (↔ siri:AbstractResponse) |
Notification from Subscriber to Subscription Manager to terminate a subscription. |
|||
3.12. The toplevel element siri:TerminateSubscriptionRequest
|
|
+siri:TerminateSubscriptionRequestStructure (↔ siri:AuthenticatedRequest) |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
3.13. The toplevel element siri:TerminateSubscriptionResponse
|
|
+siri:TerminateSubscriptionResponseStructure (↔ siri:AbstractResponse) |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
3.14. The group siri:CheckStatusPayloadGroup
|
|
Data received AcknowledgementService Status Check Request content. |
||||
| siri:CheckStatusPayloadGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Whether data delivery is ready to be fetched SIRI v 2.0 |
|||
|
|
0:1 |
Description of any error or warning condition that applies to the status check. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:CheckStatusPayloadGroup |
|
0:1 |
Time at which current instantiation of service started. |
||
3.15. The group siri:ClientEndpointAddressGroup
|
|
Address elements for SIRI messages to the Subscriber/Consumer client. |
||||
| siri:ClientEndpointAddressGroup |
|
0:1 |
Address to which CheckStatus responses and heartbeats are to be sent. If absent, same as SubscriberAddress. |
||
|
|
0:1 |
Address to which subscription responses are to be sent. |
|||
|
|
0:1 |
Address to which notifcations requests are to be sent. If absent, same as SubscriberAddress. |
|||
|
|
0:1 |
Address to which data is to be sent. If absent, same as NotifyAddress. |
|||
3.16. The group siri:DataReceivedPayloadGroup
|
|
Data received Acknowledgement content. |
||||
| siri:DataReceivedPayloadGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
3.17. The group siri:DataSupplyGroup
|
|
Groups the data supply messages. |
||||
| siri:DataSupplyGroup |
1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
|||
|
1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
||||
|
1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
||||
3.18. The group siri:DataSupplyTopicGroup
|
|
Specifies content to be included in data supply. |
||||
| siri:DataSupplyTopicGroup |
|
0:1 |
Reference to a specific notification message for which data is to be fetched. Can be used to distinguish between notfcatiosn for the same service and subscriber but for different filters.If none specified, |
||
|
|
0:1 |
Whether to return all data, or just new updates since the last delivery. Default false, i.e. just updates. |
|||
3.19. The group siri:DeliveryContextGroup
|
|
Delivery options. |
||||
| siri:DeliveryContextGroup |
|
0:1 |
Whether Delivery is fetched or retrieved. |
||
|
|
0:1 |
Whether multi-part delivery is allowed, i.e. the breaking up of updates into more than one delivery messages with a MoreData flag, |
|||
|
|
0:1 |
Whether Consumers should issue an acknowledgement on successful receipt of a delivery. Default is ' false'. |
|||
3.20. The group siri:DeliveryEndpointGroup
|
|
Elements identifying data Consumer, i.e. requestor, if synchronous delivery or subscriber if asynchronous. |
||||
| siri:DeliveryEndpointGroup |
0:1 |
Reference to a requestor - Participant Code. |
|||
|
|
0:1 |
Reference to an arbitrary unique reference associated with the request which gave rise to this response. |
|||
3.21. The group siri:DeliveryRequestGroup
|
|
General requests for fetched data delivery. |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:DeliveryRequestGroup |
a |
-1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
||
|
b |
-1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
|||
3.22. The group siri:PredictionMethodGroup
|
|
Prediction options. |
||||
| siri:PredictionMethodGroup |
|
0:1 |
Who may make a prediction. |
||
|
|
0:1 |
Name of prediction method used. |
|||
3.23. The group siri:ReferenceContextGroup
|
|
Namespace related elements in Request Context. |
||||
| siri:ReferenceContextGroup |
|
0:1 |
Default names pace used to scope data identifiers. |
||
|
|
0:* |
Preferred languages in which to return text values. |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
b |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
|
0:1 |
Units for Distance Type. Default is metres. (since SIRI 2.0) |
|||
|
|
0:1 |
Units for Distance Type. Default is metres per second. (since SIRI 2.0) |
|||
3.24. The group siri:ResourceContextGroup
|
|
Resources related elements in Request Context. |
||||
| siri:ResourceContextGroup |
|
0:1 |
Maximum Number of subscriptions that can be sustained by the subscriber. If absent no limit. |
||
3.25. The group siri:ServiceEndpointAddressGroup
|
|
Address elements for SIRI messages to the Producer server. |
||||
| siri:ServiceEndpointAddressGroup |
|
0:1 |
Address to which CheckStatus requests are to be sent. |
||
|
|
0:1 |
Address to which subscription requests are to be sent. |
|||
|
|
0:1 |
Address to which subscription requests are to be sent. If absent, same as SubscribeAddress. |
|||
|
|
0:1 |
Address to which requests are to return data. |
|||
3.26. The group siri:SiriCommonIndexGroup
|
|
Convenience artefact to pick out main elements of the common requests. |
||||
| siri:SubscriptionManagementGroup |
1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
|||
|
1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
||||
|
1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
||||
| siri:DataSupplyGroup |
1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
|||
|
1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
||||
|
1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:StatusRequestGroup |
a |
-1:1 |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
||
|
b |
-1:1 |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
|
The element contains one of the following elements (a) |
|||||
| siri:StatusResponseGroup |
a |
-1:1 |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
||
3.27. The group siri:StatusRequestGroup
|
|
Requests about system status. |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:StatusRequestGroup |
a |
-1:1 |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
||
|
b |
-1:1 |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
3.28. The group siri:StatusResponseGroup
|
|
Responses that infrom about the service status. |
||||
|
The element contains one of the following elements (a) |
|||||
| siri:StatusResponseGroup |
a |
-1:1 |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
||
3.29. The group siri:SubscriptionManagementGroup
|
|
groups the subscription request. |
||||
| siri:SubscriptionManagementGroup |
1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
|||
|
1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
||||
|
1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
||||
3.30. The group siri:SubscriptionResponsePayloadGroup
|
|
Subscription Response content. |
||||
| siri:SubscriptionResponsePayloadGroup |
1:* |
Contains infromation about the processing of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). |
|||
|
|
0:1 |
Endpoint address of subscription manager if different from that of the Producer or known default. |
|||
|
|
0:1 |
Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
3.31. The group siri:TemporalContextGroup
|
|
Timing related elements in Request Context: |
||||
| siri:TemporalContextGroup |
|
0:1 |
Maximum data horizon for requests. |
||
|
|
0:1 |
Timeout for requests. [Should this be separate for each type?] |
|||
3.32. The group siri:TerminateSubscriptionTopicGroup
|
|
Parameters that specify the content to be processed. |
||||
| siri:TerminateSubscriptionTopicGroup |
|
0:1 |
Participant identifier of Subscriber. Subscription ref will be unique within this. |
||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Terminate all subscriptions for the requestor. |
||
|
b |
|
-1:* |
Terminate the subscription identfiied by the reference. |
||
3.33. The group siri:TerminationStatusGroup
|
|
Status Info. |
||||
| siri:TerminationStatusGroup |
|
0:* |
Status of each subscription termnination response. |
||
3.34. The complex type siri:CheckStatusRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
3.35. The complex type siri:CheckStatusResponseBodyStructure
|
|
Type for Body of Service Status Check Response. Used in WSDL. Same as CheckStatusResponseStructure, but without extension to be consistent with the other operation definition. |
||||
| siri:CheckStatusPayloadGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Whether data delivery is ready to be fetched SIRI v 2.0 |
|||
|
|
0:1 |
Description of any error or warning condition that applies to the status check. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:CheckStatusPayloadGroup |
|
0:1 |
Time at which current instantiation of service started. |
||
3.36. The complex type siri:CheckStatusResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CheckStatusPayloadGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Whether data delivery is ready to be fetched SIRI v 2.0 |
|||
|
|
0:1 |
Description of any error or warning condition that applies to the status check. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:CheckStatusPayloadGroup |
|
0:1 |
Time at which current instantiation of service started. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
3.37. The complex type siri:ContextualisedRequestStructure
|
|
Type for General SIRI Request. |
||||
|
|
0:1 |
General request properties - typically configured rather than repeated on request. |
|||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
3.38. The complex type siri:DataNameSpacesStructure
|
|
Name spaces. |
||||
|
|
0:1 |
Name space for STOP POINTs. |
|||
|
|
0:1 |
Name space for LINE names and DIRECTIONss. |
|||
|
|
0:1 |
Name space for Product Categories. |
|||
|
|
0:1 |
Name space for service features. |
|||
|
|
0:1 |
Name space for VEHICLE features. |
|||
3.39. The complex type siri:DataReadyRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:ProducerRequestEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from ProducerRef and preconfigured data. |
||
|
|
0:1 |
Unique identifier of Producer - Participant reference. |
|||
|
|
0:1 |
Arbitrary unique reference to this message. Some systems may use just timestamp for this. Where there are multiple SubscriptionFilters, this can be used to distinguish between different notifications for different filters. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
3.40. The complex type siri:DataReadyResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ConsumerResponseEndpointGroup |
|
0:1 |
Unique identifier of Consumer - a Participant reference. |
||
|
|
0:1 |
Reference to an arbitrary unique idenitifer associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
||||
|
|
0:1 |
Description of any error or warning condition as to why Consumer cannot fetch data. |
|||
3.41. The complex type siri:DataReceivedResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ConsumerResponseEndpointGroup |
|
0:1 |
Unique identifier of Consumer - a Participant reference. |
||
|
|
0:1 |
Reference to an arbitrary unique idenitifer associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:DataReceivedPayloadGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
3.42. The complex type siri:DataSupplyRequestBodyStructure
|
|
Type for Body of Data Supply Request. Used in WSDL. |
||||
| siri:DataSupplyTopicGroup |
|
0:1 |
Reference to a specific notification message for which data is to be fetched. Can be used to distinguish between notfcatiosn for the same service and subscriber but for different filters.If none specified, |
||
|
|
0:1 |
Whether to return all data, or just new updates since the last delivery. Default false, i.e. just updates. |
|||
3.43. The complex type siri:DataSupplyRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:ConsumerRequestEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Unique identifier of Consumer - a Participant reference. |
|||
|
|
0:1 |
Arbitrary unique reference to this message. Some systems may use just timestamp for this. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:DataSupplyTopicGroup |
|
0:1 |
Reference to a specific notification message for which data is to be fetched. Can be used to distinguish between notfcatiosn for the same service and subscriber but for different filters.If none specified, |
||
|
|
0:1 |
Whether to return all data, or just new updates since the last delivery. Default false, i.e. just updates. |
|||
3.44. The complex type siri:HeartbeatNotificationStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:ProducerRequestEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from ProducerRef and preconfigured data. |
||
|
|
0:1 |
Unique identifier of Producer - Participant reference. |
|||
|
|
0:1 |
Arbitrary unique reference to this message. Some systems may use just timestamp for this. Where there are multiple SubscriptionFilters, this can be used to distinguish between different notifications for different filters. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:CheckStatusPayloadGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Whether data delivery is ready to be fetched SIRI v 2.0 |
|||
|
|
0:1 |
Description of any error or warning condition that applies to the status check. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:CheckStatusPayloadGroup |
|
0:1 |
Time at which current instantiation of service started. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
3.45. The complex type siri:ServiceRequestContextStructure
|
|
Configurable context for requests. Intended Primarily as a documentation mechanism. |
||||
| siri:ServiceEndpointAddressGroup |
|
0:1 |
Address to which CheckStatus requests are to be sent. |
||
|
|
0:1 |
Address to which subscription requests are to be sent. |
|||
|
|
0:1 |
Address to which subscription requests are to be sent. If absent, same as SubscribeAddress. |
|||
|
|
0:1 |
Address to which requests are to return data. |
|||
| siri:ClientEndpointAddressGroup |
|
0:1 |
Address to which CheckStatus responses and heartbeats are to be sent. If absent, same as SubscriberAddress. |
||
|
|
0:1 |
Address to which subscription responses are to be sent. |
|||
|
|
0:1 |
Address to which notifcations requests are to be sent. If absent, same as SubscriberAddress. |
|||
|
|
0:1 |
Address to which data is to be sent. If absent, same as NotifyAddress. |
|||
| siri:ReferenceContextGroup |
|
0:1 |
Default names pace used to scope data identifiers. |
||
|
|
0:* |
Preferred languages in which to return text values. |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
b |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
|
0:1 |
Units for Distance Type. Default is metres. (since SIRI 2.0) |
|||
|
|
0:1 |
Units for Distance Type. Default is metres per second. (since SIRI 2.0) |
|||
| siri:TemporalContextGroup |
|
0:1 |
Maximum data horizon for requests. |
||
|
|
0:1 |
Timeout for requests. [Should this be separate for each type?] |
|||
| siri:DeliveryContextGroup |
|
0:1 |
Whether Delivery is fetched or retrieved. |
||
|
|
0:1 |
Whether multi-part delivery is allowed, i.e. the breaking up of updates into more than one delivery messages with a MoreData flag, |
|||
|
|
0:1 |
Whether Consumers should issue an acknowledgement on successful receipt of a delivery. Default is ' false'. |
|||
| siri:ResourceContextGroup |
|
0:1 |
Maximum Number of subscriptions that can be sustained by the subscriber. If absent no limit. |
||
| siri:PredictionMethodGroup |
|
0:1 |
Who may make a prediction. |
||
|
|
0:1 |
Name of prediction method used. |
|||
3.46. The complex type siri:StatusResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:SubscriptionIdentifierResourcePropertyGroup |
|
0:1 |
Unique identifier of Subscriber - reference to a Participant. |
||
|
|
0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
|||
|
|
1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
|||
|
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
||||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
3.47. The complex type siri:SubscriptionResponseBodyStructure
|
|
Type for Body of Subscription Response. Used in WSDL. |
||||
|
1:* |
Contains infromation about the processing of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). |
||||
|
|
0:1 |
Endpoint address of subscription manager if different from that of the Producer or known default. |
|||
|
|
0:1 |
Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. |
|||
3.48. The complex type siri:SubscriptionResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ResponseEndpointGroup |
|
0:1 |
Address for further interaction. |
||
|
|
0:1 |
Participant reference that identifies responder. |
|||
|
|
0:1 |
Reference to an arbitrary unique reference associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:SubscriptionResponsePayloadGroup |
1:* |
Contains infromation about the processing of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). |
|||
|
|
0:1 |
Endpoint address of subscription manager if different from that of the Producer or known default. |
|||
|
|
0:1 |
Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
3.49. The complex type siri:SubscriptionTerminatedNotificationStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:SubscriptionIdentifierResourcePropertyGroup |
|
0:1 |
Unique identifier of Subscriber - reference to a Participant. |
||
|
|
0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
|||
|
|
1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
|||
|
|
0:1 |
Text description providing additional information about the reason for the subscription termination. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
3.50. The complex type siri:TerminateSubscriptionRequestBodyStructure
|
|
Type for Body of Terminate Subscription Request content. Used in WSDL. |
||||
| siri:TerminateSubscriptionTopicGroup |
|
0:1 |
Participant identifier of Subscriber. Subscription ref will be unique within this. |
||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Terminate all subscriptions for the requestor. |
||
|
b |
|
-1:* |
Terminate the subscription identfiied by the reference. |
||
3.51. The complex type siri:TerminateSubscriptionRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:TerminateSubscriptionTopicGroup |
|
0:1 |
Participant identifier of Subscriber. Subscription ref will be unique within this. |
||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Terminate all subscriptions for the requestor. |
||
|
b |
|
-1:* |
Terminate the subscription identfiied by the reference. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
3.52. The complex type siri:TerminateSubscriptionResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ResponseEndpointGroup |
|
0:1 |
Address for further interaction. |
||
|
|
0:1 |
Participant reference that identifies responder. |
|||
|
|
0:1 |
Reference to an arbitrary unique reference associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:TerminationStatusGroup |
|
0:* |
Status of each subscription termnination response. |
||
3.53. The complex type siri:TerminationResponseStatusStructure
|
|
Type for Status of termination response. |
||||
|
0:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:SubscriptionIdentifierResourcePropertyGroup |
|
0:1 |
Unique identifier of Subscriber - reference to a Participant. |
||
|
|
0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
|||
|
|
1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
|||
|
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
||||
|
|
0:1 |
Description of any error or warning condition. |
|||
3.54. The complex type complexType[siri:TerminationResponseStatusStructure]/ErrorCondition#complexType (typedef-51.1)
|
|
- |
||||
|
The element contains one of the following elements (a-d) |
|||||
|
a |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
b |
-1:1 |
Error: Subscriber not found. |
|||
|
c |
-1:1 |
Error: Subscription not found. |
|||
|
d |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
3.55. The complex type complexType[siri:DataReadyResponseStructure]/ErrorCondition#complexType (typedef-51.2)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Error: Subscription not found. |
|||
|
b |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
3.56. The complex type group[siri:DataReceivedPayloadGroup]/ErrorCondition#complexType (typedef-51.3)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Error: Subscription not found. |
|||
|
b |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
3.57. The complex type group[siri:CheckStatusPayloadGroup]/ErrorCondition#complexType (typedef-51.4)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Error: Functional service is not available to use (but it is still capable of giving this response). |
|||
|
b |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
4. SIRI Framework Error COnditions.
4.1. The toplevel element siri:AccessNotAllowedError
|
|
+siri:AccessNotAllowedErrorStructure (↔ siri:ErrorCode) |
Error: Requestor is not authorised to the service or data requested. |
|||
4.2. The toplevel element siri:AllowedResourceUsageExceededError
|
|
+siri:AllowedResourceUsageExceededErrorStructure (↔ siri:ErrorCode) |
Error: Valid request was made but request would exceed the permitted resource usage of the client. |
|||
4.3. The toplevel element siri:BeyondDataHorizon
|
|
+siri:BeyondDataHorizonErrorStructure (↔ siri:ErrorCode) |
Error: Data period or subscription period is outside of period covered by service. |
|||
4.4. The toplevel element siri:CapabilityNotSupportedError
|
|
+siri:CapabilityNotSupportedErrorStructure (↔ siri:ErrorCode) |
Error: Service does not support the requested capability. |
|||
4.5. The toplevel element siri:EndpointDeniedAccessError
|
|
+siri:EndpointDeniedAccessStructure (↔ siri:ErrorCode) |
Error:Endpoint to which a message is to be distributed did not allow access by the cloient. (since SIRI 2.0) |
|||
4.6. The toplevel element siri:EndpointNotAvailableAccessError
|
|
+siri:EndpointNotAvailableAccessStructure (↔ siri:ErrorCode) |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
|||
4.7. The toplevel element siri:ErrorCode
|
|
Subsititutable type for a SIRI Error code. |
||||
4.8. The toplevel element siri:ErrorCondition
|
|
Description of error or warning condition associated with response. |
||||
4.9. The toplevel element siri:ErrorConditionElement
|
|
Element fror an erroc condition (for use in WSDL.) |
||||
4.10. The toplevel element siri:InvalidDataReferencesError
|
|
+siri:InvalidDataReferencesErrorStructure (↔ siri:ErrorCode) |
Error: Request contains references to identifiers that are not known. (since SIRI 2.0). |
|||
4.11. The toplevel element siri:NoInfoForTopicError
|
|
+siri:NoInfoForTopicErrorStructure (↔ siri:ErrorCode) |
Error: Valid request was made but service does not hold any data for the requested topic. expression. |
|||
4.12. The toplevel element siri:OtherError
|
|
+siri:OtherErrorStructure (↔ siri:ErrorCode) |
Error: Error type other than the well defined codes. |
|||
4.13. The toplevel element siri:ParametersIgnoredError
|
|
+siri:ParametersIgnoredErrorStructure (↔ siri:ErrorCode) |
Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. (since SIRI 2.0). |
|||
4.14. The toplevel element siri:ServiceDeliveryErrorConditionElement
|
|
Element fror an erroc condition for use in WSDL. |
||||
4.15. The toplevel element siri:ServiceNotAvailableError
|
|
+siri:ServiceNotAvailableErrorStructure (↔ siri:ErrorCode) |
Error: Functional service is not available to use (but it is still capable of giving this response). |
|||
4.16. The toplevel element siri:UnapprovedKeyAccessError
|
|
+siri:UnapprovedKeyAccessStructure (↔ siri:ErrorCode) |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
|||
4.17. The toplevel element siri:UnknownEndpointError
|
|
+siri:UnknownEndpointErrorStructure (↔ siri:ErrorCode) |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
4.18. The toplevel element siri:UnknownExtensionsError
|
|
+siri:UnknownExtensionsErrorStructure (↔ siri:ErrorCode) |
Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0). |
|||
4.19. The toplevel element siri:UnknownParticipantError
|
|
+siri:UnknownParticipantErrorStructure (↔ siri:ErrorCode) |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
4.20. The toplevel element siri:UnknownSubscriberError
|
|
+siri:UnknownSubscriberErrorStructure (↔ siri:ErrorCode) |
Error: Subscriber not found. |
|||
4.21. The toplevel element siri:UnknownSubscriptionError
|
|
+siri:UnknownSubscriptionErrorStructure (↔ siri:ErrorCode) |
Error: Subscription not found. |
|||
4.22. The group siri:ApplicationErrorGroup
|
|
Errors that may arise in the execution of a request. |
||||
|
The element contains one of the following elements (a-j) |
|||||
| siri:ApplicationErrorGroup |
a |
-1:1 |
Error: Functional service is not available to use (but it is still capable of giving this response). |
||
|
b |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
c |
-1:1 |
Error: Requestor is not authorised to the service or data requested. |
|||
|
d |
-1:1 |
Error: Request contains references to identifiers that are not known. (since SIRI 2.0). |
|||
|
e |
-1:1 |
Error: Data period or subscription period is outside of period covered by service. |
|||
|
f |
-1:1 |
Error: Valid request was made but service does not hold any data for the requested topic. expression. |
|||
|
g |
-1:1 |
Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. (since SIRI 2.0). |
|||
|
h |
-1:1 |
Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0). |
|||
|
i |
-1:1 |
Error: Valid request was made but request would exceed the permitted resource usage of the client. |
|||
|
j |
-1:1 |
Error: Error type other than the well defined codes. |
|||
4.23. The group siri:DistributionErrorGroup
|
|
Errors that may arise in the execution of a delegated distribution request. (since SIRI 2.0) |
||||
|
The element contains one of the following elements (a-e) |
|||||
| siri:DistributionErrorGroup |
a |
-1:1 |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
||
|
b |
-1:1 |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
|
c |
-1:1 |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
|
d |
-1:1 |
Error:Endpoint to which a message is to be distributed did not allow access by the cloient. (since SIRI 2.0) |
|||
|
e |
-1:1 |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
|||
4.24. The group siri:ServiceRequestErrorGroup
|
|
Errors that may arise in the execution of a request. |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ae) |
|||||
| siri:DistributionErrorGroup |
aa |
-1:1 |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
||
|
ab |
-1:1 |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
|
ac |
-1:1 |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
|
ad |
-1:1 |
Error:Endpoint to which a message is to be distributed did not allow access by the cloient. (since SIRI 2.0) |
|||
|
ae |
-1:1 |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
|||
|
In case of choice 'b', the element contains one of the following elements (ba-bj) |
|||||
| siri:ApplicationErrorGroup |
ba |
-1:1 |
Error: Functional service is not available to use (but it is still capable of giving this response). |
||
|
bb |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
bc |
-1:1 |
Error: Requestor is not authorised to the service or data requested. |
|||
|
bd |
-1:1 |
Error: Request contains references to identifiers that are not known. (since SIRI 2.0). |
|||
|
be |
-1:1 |
Error: Data period or subscription period is outside of period covered by service. |
|||
|
bf |
-1:1 |
Error: Valid request was made but service does not hold any data for the requested topic. expression. |
|||
|
bg |
-1:1 |
Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. (since SIRI 2.0). |
|||
|
bh |
-1:1 |
Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0). |
|||
|
bi |
-1:1 |
Error: Valid request was made but request would exceed the permitted resource usage of the client. |
|||
|
bj |
-1:1 |
Error: Error type other than the well defined codes. |
|||
4.25. The group siri:SuccessInfoGroup
|
|
Additional information provided if request is successful. |
||||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
4.26. The complex type siri:AccessNotAllowedErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
4.27. The complex type siri:AllowedResourceUsageExceededErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
4.28. The complex type siri:BeyondDataHorizonErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
4.29. The complex type siri:CapabilityNotSupportedErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Id of capabiliuty that is noit supported. |
|||
4.30. The complex type siri:EndpointDeniedAccessStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Endpoint that was denied access + SIRI v2.0 |
|||
4.31. The complex type siri:EndpointNotAvailableAccessStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Endpoint that is noit available. + SIRI v2.0 |
|||
4.32. The complex type siri:ErrorCodeStructure
|
|
Type for Error Code. |
||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
4.33. The complex type siri:ErrorConditionElementStructure
|
|
Type for Standard ErrorConditions for Service request. |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ab) |
|||||
|
In case of choice 'aa', the element contains one of the following elements (aaa-aae) |
|||||
| siri:DistributionErrorGroup |
aaa |
-1:1 |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
||
|
aab |
-1:1 |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
|
aac |
-1:1 |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
|
aad |
-1:1 |
Error:Endpoint to which a message is to be distributed did not allow access by the cloient. (since SIRI 2.0) |
|||
|
aae |
-1:1 |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
|||
|
In case of choice 'ab', the element contains one of the following elements (aba-abj) |
|||||
| siri:ApplicationErrorGroup |
aba |
-1:1 |
Error: Functional service is not available to use (but it is still capable of giving this response). |
||
|
abb |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
abc |
-1:1 |
Error: Requestor is not authorised to the service or data requested. |
|||
|
abd |
-1:1 |
Error: Request contains references to identifiers that are not known. (since SIRI 2.0). |
|||
|
abe |
-1:1 |
Error: Data period or subscription period is outside of period covered by service. |
|||
|
abf |
-1:1 |
Error: Valid request was made but service does not hold any data for the requested topic. expression. |
|||
|
abg |
-1:1 |
Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. (since SIRI 2.0). |
|||
|
abh |
-1:1 |
Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0). |
|||
|
abi |
-1:1 |
Error: Valid request was made but request would exceed the permitted resource usage of the client. |
|||
|
abj |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
b |
-1:1 |
Error: Subscription not found. |
|||
|
|
0:1 |
Text description of error. |
|||
4.34. The complex type siri:ErrorConditionStructure
|
|
Type for RequestErrorCondition. |
||||
|
The element contains one of the following elements (a) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-aj) |
|||||
| siri:ApplicationErrorGroup |
aa |
-1:1 |
Error: Functional service is not available to use (but it is still capable of giving this response). |
||
|
ab |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
ac |
-1:1 |
Error: Requestor is not authorised to the service or data requested. |
|||
|
ad |
-1:1 |
Error: Request contains references to identifiers that are not known. (since SIRI 2.0). |
|||
|
ae |
-1:1 |
Error: Data period or subscription period is outside of period covered by service. |
|||
|
af |
-1:1 |
Error: Valid request was made but service does not hold any data for the requested topic. expression. |
|||
|
ag |
-1:1 |
Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. (since SIRI 2.0). |
|||
|
ah |
-1:1 |
Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0). |
|||
|
ai |
-1:1 |
Error: Valid request was made but request would exceed the permitted resource usage of the client. |
|||
|
aj |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
4.35. The complex type siri:ErrorDescriptionStructure
|
|
|
- |
|||
4.36. The complex type siri:InvalidDataReferencesErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Invalid reference values encoountered. |
|||
4.37. The complex type siri:NoInfoForTopicErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
4.38. The complex type siri:OtherErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
4.39. The complex type siri:ParametersIgnoredErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Name of the unsupported parameter. |
|||
4.40. The complex type siri:ServiceDeliveryErrorConditionStructure
|
|
Type for Standard ErrorConditiosn for Service request. |
||||
|
The element contains one of the following elements (a) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ab) |
|||||
|
In case of choice 'aa', the element contains one of the following elements (aaa-aae) |
|||||
| siri:DistributionErrorGroup |
aaa |
-1:1 |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
||
|
aab |
-1:1 |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
|
aac |
-1:1 |
Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) |
|||
|
aad |
-1:1 |
Error:Endpoint to which a message is to be distributed did not allow access by the cloient. (since SIRI 2.0) |
|||
|
aae |
-1:1 |
Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) |
|||
|
In case of choice 'ab', the element contains one of the following elements (aba-abj) |
|||||
| siri:ApplicationErrorGroup |
aba |
-1:1 |
Error: Functional service is not available to use (but it is still capable of giving this response). |
||
|
abb |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
abc |
-1:1 |
Error: Requestor is not authorised to the service or data requested. |
|||
|
abd |
-1:1 |
Error: Request contains references to identifiers that are not known. (since SIRI 2.0). |
|||
|
abe |
-1:1 |
Error: Data period or subscription period is outside of period covered by service. |
|||
|
abf |
-1:1 |
Error: Valid request was made but service does not hold any data for the requested topic. expression. |
|||
|
abg |
-1:1 |
Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. (since SIRI 2.0). |
|||
|
abh |
-1:1 |
Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0). |
|||
|
abi |
-1:1 |
Error: Valid request was made but request would exceed the permitted resource usage of the client. |
|||
|
abj |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
4.41. The complex type siri:ServiceNotAvailableErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Expected time fro reavailability of servcie. (since SIRI 2.0) |
|||
4.42. The complex type siri:UnapprovedKeyAccessStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
User key. |
|||
4.43. The complex type siri:UnknownEndpointErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Endpoint that is noit known. + SIRI v2.0 |
|||
4.44. The complex type siri:UnknownExtensionsErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Name of the unknown encountered extensions. |
|||
4.45. The complex type siri:UnknownParticipantErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Reference to Participant who is unknown. + SIRI v2.0 |
|||
4.46. The complex type siri:UnknownSubscriberErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Id of capabiliuty that is noit supported. + SIRI v2.0 |
|||
4.47. The complex type siri:UnknownSubscriptionErrorStructure
|
|
Type for Error Code. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Error code number associated with error. |
|||
|
|
0:1 |
Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Ubscription code that could not be found. + SIRI v2.0 |
|||
5. SIRI Common Framework basic identifier types.
5.1. Simple type definitions
|
|
xs:NMTOKEN: (empty restriction) |
Type for capability code. |
|||||||||||
|
|
Enumeration of communications transport method usage. |
||||||||||||
|
|||||||||||||
|
|
Enumeration of compression usage. |
||||||||||||
|
|||||||||||||
|
|
xs:anyURI: (empty restriction) |
Type for a endpoint. |
|||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an Item. A transient reference for efficient handling of events. |
|||||||||||
5.2. The toplevel element siri:IncludeInterchanges
|
|
|
Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
|||
5.3. The toplevel element siri:IncludeJourneyRelations
|
|
|
Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
|||
5.4. The toplevel element siri:IncludeTrainFormations
|
|
|
Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
|||
5.5. The toplevel element siri:IncludeTranslations
|
|
|
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
|||
5.6. The toplevel element siri:RequestorRef
|
|
Reference to a requestor - Participant Code. |
||||
5.7. The toplevel element siri:RequestTimestamp
|
|
|
Timestamp on request. |
|||
5.8. The toplevel element siri:ResponseTimestamp
|
|
|
Time individual response element was created. |
|||
5.9. The complex type siri:CapabilityRefStructure
|
|
Type for capability code. |
||||
5.10. The complex type siri:ItemRefStructure
|
|
Type for identifier of an Item. A transient reference for efficient handling of events. |
||||
5.11. The complex type siri:MessageQualifierStructure
|
|
|
- |
|||
5.12. The complex type siri:MessageRefStructure
|
|
- |
||||
5.13. The complex type siri:SubscriptionFilterRefStructure
|
|
|
- |
|||
5.14. The complex type siri:SubscriptionFilterStructure
|
|
|
- |
|||
5.15. The complex type siri:SubscriptionQualifierStructure
|
|
|
- |
|||
5.16. The complex type siri:SubscriptionRefStructure
|
|
- |
||||
6. SIRI Common Request Framework.
6.1. The toplevel element siri:AbstractDiscoveryDelivery
|
|
+siri:AbstractDiscoveryDeliveryStructure (↔ siri:AbstractResponse) |
Abstract type for a discovery delivery. |
|||
6.2. The toplevel element siri:AbstractDiscoveryRequest
|
|
+siri:AbstractDiscoveryRequestStructure (↔ siri:AuthenticatedRequest) |
Abstract Discovery request. |
|||
6.3. The toplevel element siri:AbstractFunctionalServiceCapabilitiesRequest
|
|
+siri:AbstractServiceRequestStructure (↔ siri:AbstractServiceRequest) |
Subsititutable type for a SIRI Functional Service Capabiloitiesequest. |
|||
6.4. The toplevel element siri:AbstractFunctionalServiceCapabilitiesResponse
|
|
+siri:AbstractServiceCapabilitiesResponseStructure (↔ siri:AbstractResponse) |
Subsititutable type for a SIRI Functional Service Capabiloitiesequest. |
|||
6.5. The toplevel element siri:AbstractFunctionalServiceDelivery
|
|
+siri:AbstractServiceDeliveryStructure (↔ siri:AbstractResponse) |
Subsititutable type for a SIRI Functional Service request. |
|||
6.6. The toplevel element siri:AbstractFunctionalServiceRequest
|
|
+siri:AbstractFunctionalServiceRequestStructure (↔ siri:AbstractServiceRequest) |
Subsititutable type for a SIRI Functional Service request. |
|||
6.7. The toplevel element siri:AbstractFunctionalServiceSubscriptionRequest
|
|
Subsititutable type for a SIRI Functional Service subscription request. |
||||
6.8. The toplevel element siri:AbstractRequest
|
|
Subsititutable type for a timestamped SIRI request. |
||||
6.9. The toplevel element siri:AbstractResponse
|
|
Subsititutable type for a SIRI response. |
||||
6.10. The toplevel element siri:AbstractServiceRequest
|
|
+siri:AbstractServiceRequestStructure (↔ siri:AbstractRequest) |
Substitutable type for a SIRI Functional Service request. |
|||
6.11. The toplevel element siri:AbstractTrackedRequest
|
|
Subsititutable type for a SIRI request with requestor dteials tracked. |
||||
6.12. The toplevel element siri:AuthenticatedRequest
|
|
Subsititutable type for an authenticated request Authenticated. |
||||
6.13. The toplevel element siri:ProducerRequest
|
|
+siri:ProducerRequestEndpointStructure (↔ siri:AuthenticatedRequest) |
||||
6.14. The toplevel element siri:Status
|
|
|
Whether the request was processed successfully or not. Default is 'true'. |
|||
6.15. The group siri:AuthenticatedRequestGroup
|
|
Elemenst for authecticiation. (since SIRI 2.0) |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
6.16. The group siri:CapabilityStatusGroup
|
|
Status Information for individual request. |
||||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
6.17. The group siri:ConsumerRequestEndpointGroup
|
|
Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. |
||||
| siri:ConsumerRequestEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Unique identifier of Consumer - a Participant reference. |
|||
|
|
0:1 |
Arbitrary unique reference to this message. Some systems may use just timestamp for this. |
|||
6.18. The group siri:ConsumerResponseEndpointGroup
|
|
Unique reference to this response message from Consumer. May be used to reference the response in subsequent interactions. |
||||
| siri:ConsumerResponseEndpointGroup |
|
0:1 |
Unique identifier of Consumer - a Participant reference. |
||
|
|
0:1 |
Reference to an arbitrary unique idenitifer associated with the request which gave rise to this response. |
|||
6.19. The group siri:ContextualisedRequestEndpointGroup
|
|
Unique reference to request: participant and SIRI service type are given by context. Used on requests that are embedded in the context of another request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
6.20. The group siri:ContextualisedResponseEndpointGroup
|
|
Endpoint reference proprerties for response message: participant and SIRI service type are given by context. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
6.21. The group siri:DelegatorEndpointGroup
|
|
If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. |
||||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
6.22. The group siri:DeliveryDefaultGroup
|
|
Common defaults. |
||||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
6.23. The group siri:DeliveryStatusGroup
|
|
Status Information for individual request. |
||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
6.24. The group siri:OptionalSubscriberEndpointGroup
|
|
Unique reference to subscription May be used to reference subscription in subsequent interactions. |
||||
| siri:OptionalSubscriberEndpointGroup |
|
0:1 |
If Delivery is for a Subscription, Participant reference of Subscriber. |
||
|
|
0:1 |
If Delivery is for a Subscription, unique identifier of service subscription request within Service and subscriber - a Timestamp. |
|||
6.25. The group siri:ProducerRequestEndpointGroup
|
|
Unique reference to request from producer. May be used to reference request in subsequent interactions. |
||||
| siri:ProducerRequestEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from ProducerRef and preconfigured data. |
||
|
|
0:1 |
Unique identifier of Producer - Participant reference. |
|||
|
|
0:1 |
Arbitrary unique reference to this message. Some systems may use just timestamp for this. Where there are multiple SubscriptionFilters, this can be used to distinguish between different notifications for different filters. |
|||
6.26. The group siri:ProducerResponseEndpointGroup
|
|
Unique reference to reponse from producer. May be used to reference request in subsequent interactions. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
6.27. The group siri:RequestorEndpointGroup
|
|
Elements relating to system that sent request. |
||||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
6.28. The group siri:ResponseEndpointGroup
|
|
Unique reference to response May be used to reference response in subsequent interactions. |
||||
| siri:ResponseEndpointGroup |
|
0:1 |
Address for further interaction. |
||
|
|
0:1 |
Participant reference that identifies responder. |
|||
|
|
0:1 |
Reference to an arbitrary unique reference associated with the request which gave rise to this response. |
|||
6.29. The group siri:ServiceDeliveryRequestStatusGroup
|
|
Status Information for overall request. Specific error conditions will be given on each individual request. |
||||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
6.30. The group siri:SubscriberEndpointGroup
|
|
Unique reference to request. May be used to reference request in subsequent interactions. |
||||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
6.31. The group siri:SubscriptionIdentifierResourcePropertyGroup
|
|
Unique reference to subscription May be used to reference subscription in subsequent interactions. |
||||
| siri:SubscriptionIdentifierResourcePropertyGroup |
|
0:1 |
Unique identifier of Subscriber - reference to a Participant. |
||
|
|
0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
|||
|
|
1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
|||
6.32. The group siri:SubscriptionIdentityGroup
|
|
Type for unique identifier of a subscription. |
||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
6.33. The complex type siri:AbstractCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
6.34. The complex type siri:AbstractDiscoveryDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
6.35. The complex type siri:AbstractDiscoveryRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
6.36. The complex type siri:AbstractFunctionalServiceRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
6.37. The complex type siri:AbstractIdentifiedItemStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Identifier of item. |
|||
6.38. The complex type siri:AbstractItemStructure
|
|
Type for an Activity. |
||||
|
|
1:1 |
Time at which data was recorded. |
|||
6.39. The complex type siri:AbstractNotificationStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:ProducerRequestEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from ProducerRef and preconfigured data. |
||
|
|
0:1 |
Unique identifier of Producer - Participant reference. |
|||
|
|
0:1 |
Arbitrary unique reference to this message. Some systems may use just timestamp for this. Where there are multiple SubscriptionFilters, this can be used to distinguish between different notifications for different filters. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
6.40. The complex type siri:AbstractReferencingItemStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Reference to an Activity Element of a delivery. |
|||
6.41. The complex type siri:AbstractRequestStructure
|
|
Type for General SIRI Request. |
||||
|
1:1 |
Timestamp on request. |
||||
6.42. The complex type siri:AbstractRequiredIdentifiedItemStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Identifier of item. |
|||
6.43. The complex type siri:AbstractRequiredReferencingItemStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to an Activity Element of a delivery. |
|||
6.44. The complex type siri:AbstractServiceCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
6.45. The complex type siri:AbstractServiceDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
Inherited content is followed by own content: |
|||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
6.46. The complex type siri:AbstractServiceRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
6.47. The complex type siri:AbstractSubscriptionRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
6.48. The complex type siri:AbstractSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
6.49. The complex type siri:AuthenticatedRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
6.50. The complex type siri:CapabilityGeneralInteractionStructure
|
|
Type for Common Request Policy capabilities. |
||||
|
|
1:1 |
Interaction capabilities. |
|||
|
|
1:1 |
Delivery capabilities. |
|||
|
|
1:1 |
Whether the service supports multiple part despatch with MoreData flag. Default is 'true'. |
|||
|
|
1:1 |
Whether the service supports multiple Subscriber Filters. Default is ' false'. |
|||
|
|
1:1 |
Whether the service supports Delivery confirm. |
|||
|
|
1:1 |
Whether the service has a heartbeat message. Default is 'false'. |
|||
|
|
0:1 |
Whether VisitNumber can be used as a strict order number within JOURNEY PATTERN. Default is 'false'. |
|||
6.51. The complex type siri:CapabilityRequestPolicyStructure
|
|
Type for Common Request Policy capabilities. |
||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
6.52. The complex type siri:CapabilitySubscriptionPolicyStructure
|
|
Type for Common Subscription capabilities. |
||||
|
|
0:1 |
Whether incremental updates can be specified for updates Default is ' true'. |
|||
|
|
0:1 |
Whether change threshold can be specified for updates. Default is 'true'. |
|||
6.53. The complex type siri:ConsumerRequestEndpointStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:ConsumerRequestEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Unique identifier of Consumer - a Participant reference. |
|||
|
|
0:1 |
Arbitrary unique reference to this message. Some systems may use just timestamp for this. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
6.54. The complex type siri:ConsumerResponseEndpointStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:ConsumerResponseEndpointGroup |
|
0:1 |
Unique identifier of Consumer - a Participant reference. |
||
|
|
0:1 |
Reference to an arbitrary unique idenitifer associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
6.55. The complex type siri:ProducerRequestEndpointStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:ProducerRequestEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from ProducerRef and preconfigured data. |
||
|
|
0:1 |
Unique identifier of Producer - Participant reference. |
|||
|
|
0:1 |
Arbitrary unique reference to this message. Some systems may use just timestamp for this. Where there are multiple SubscriptionFilters, this can be used to distinguish between different notifications for different filters. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
6.56. The complex type siri:ProducerResponseEndpointStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
6.57. The complex type siri:ProducerResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
6.58. The complex type siri:RequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
6.59. The complex type siri:ResponseEndpointStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:ResponseEndpointGroup |
|
0:1 |
Address for further interaction. |
||
|
|
0:1 |
Participant reference that identifies responder. |
|||
|
|
0:1 |
Reference to an arbitrary unique reference associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
6.60. The complex type siri:ResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
1:1 |
Time individual response element was created. |
||||
6.61. The complex type siri:ServiceCapabilitiesRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed. |
|||
|
|
0:1 |
Whether to include the requestors permissions in the response. Only applies if Access control capability supported. Default is 'false'. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
6.62. The complex type siri:SubscriptionContextStructure
|
|
Type for Subscription context - Configuration parameters which may be evrriden. |
||||
|
|
0:1 |
Interval for heartbeat. |
|||
6.63. The complex type siri:TransportDescriptionStructure
|
|
Type for implementation structure. |
||||
|
|
1:1 |
Communications Transport method used to exchange messages. Default is 'httpPost'. |
|||
|
|
1:1 |
Compression method used to compress messages for transmission. Default is 'none'. |
|||
6.64. The complex type group[siri:ServiceDeliveryRequestStatusGroup]/ErrorCondition#complexType (typedef-50.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
b |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
6.65. The complex type complexType[siri:CapabilityGeneralInteractionStructure]/Interaction#complexType (typedef-50.2)
|
|
- |
||||
|
|
1:1 |
Whether the service supports Request Response Interaction. Default is 'true'. |
|||
|
|
1:1 |
Whether the service supports Publish Subscribe Interaction. Default is 'true'. |
|||
6.66. The complex type complexType[siri:CapabilityGeneralInteractionStructure]/Delivery#complexType (typedef-50.3)
|
|
- |
||||
|
|
1:1 |
Whether the service supports Direct delivery. |
|||
|
|
1:1 |
Whether the service supports Fetched delivery (VDV Style) |
|||
7. SIRI-CM Connection Monitoring Service.
7.1. Simple type definitions
|
|
Detail Levels for Connection Monitoring Request. |
||||||||
|
|||||||||
7.2. The toplevel element siri:ConnectionMonitoringCapabilitiesRequest
|
|
+siri:ServiceCapabilitiesRequestStructure (↔ siri:AbstractFunctionalServiceCapabilitiesRequest) |
Request for information about Connection Monitoring Service Capabilities. Answered with a ConnectionMontoringCapabilitiesResponse. |
|||
7.3. The toplevel element siri:ConnectionMonitoringCapabilitiesResponse
|
|
+siri:ConnectionMonitoringCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Capabilities for Connection Monitoring Service. Answers a ConnectionMontoringCapabilitiesRequest. |
|||
7.4. The toplevel element siri:ConnectionMonitoringDistributorDelivery
|
|
+siri:ConnectionMonitoringDistributorDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Distributor Delivery for Connection Monitoring Service. |
|||
7.5. The toplevel element siri:ConnectionMonitoringFeederDelivery
|
|
+siri:ConnectionMonitoringFeederDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Feeder Delivery for Connection Monitoring Service. |
|||
7.6. The toplevel element siri:ConnectionMonitoringPermissions
|
|
- |
||||
|
|
0:* |
||||
7.7. The toplevel element siri:ConnectionMonitoringRequest
|
|
+siri:ConnectionMonitoringRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about changes to connections at a stop for Connection Monitoring service. |
|||
7.8. The toplevel element siri:ConnectionMonitoringServiceCapabilities
|
|
Capabilities of Connection Monitoring Service. |
||||
7.9. The toplevel element siri:ConnectionMonitoringSubscriptionRequest
|
|
+siri:ConnectionMonitoringSubscriptionRequestStructure (↔ siri:AbstractFunctionalServiceSubscriptionRequest) |
Request for a subscription to Connection Monitoring Service. |
|||
7.10. The toplevel element siri:MonitoredFeederArrival
|
|
+siri:MonitoredFeederArrivalStructure (↔ siri:FeederItem) |
A feeder arrival at the connection point. |
|||
7.11. The toplevel element siri:MonitoredFeederArrivalCancellation
|
|
+siri:MonitoredFeederArrivalCancellationStructure (↔ siri:FeederItem) |
Cancellation of a feeder arrival at a connection point. |
|||
7.12. The group siri:ConnectionMonitoringDistributorPayloadGroup
|
|
Distributor (fetcher) payload content. |
||||
| siri:ConnectionMonitoringDistributorPayloadGroup |
|
0:* |
An action to delay the Distributor (fetcher) until a specified time. |
||
|
|
0:* |
A Change to a stop position. |
|||
|
|
0:* |
Deletion of previous connection. |
|||
7.13. The group siri:ConnectionMonitoringFeederPayloadGroup
|
|
Feeder delivery payload content. |
||||
| siri:ConnectionMonitoringFeederPayloadGroup |
0:* |
A feeder arrival at the connection point. |
|||
|
0:* |
Cancellation of a feeder arrival at a connection point. |
||||
7.14. The group siri:ConnectionMonitoringRequestPolicyGroup
|
|
Parameters that affect the request processing. |
||||
| siri:ConnectionMonitoringRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. |
|||
7.15. The group siri:ConnectionMonitoringSubscriptionPolicyGroup
|
|
Parameters that affect the subscription processing. |
||||
| siri:ConnectionMonitoringSubscriptionPolicyGroup |
|
0:1 |
The amount of change to the arrival time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. |
||
7.16. The group siri:ConnectionMonitoringTopicGroup
|
|
Parameters that specify the content to be returned. |
||||
| siri:ConnectionMonitoringTopicGroup |
|
0:1 |
Forward duration for which events should be included, that is, interval before predicted arrival at the stop for which to include events: only journeys which will arrive or depart within this time span will be returned. |
||
|
|
1:1 |
CONNECTION LINK for which data is to be supplied. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Return only journeys for the specified time. |
||
|
b |
|
-1:* |
Return only the specified journeys. |
||
7.17. The group siri:InterchangeDistributorIdentityGroup
|
|
Identifiers of Interchange Distributor Stop. |
||||
| siri:InterchangeDistributorIdentityGroup |
|
0:1 |
Reference to the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned and at which SERVICE JOURNEY INTERCHANGE takes place. A reference associated with known feeder arrival and distributor departure STOP POINTs. |
|||
|
|
0:1 |
Reference to a STOP POINT within CONNECTION link from which distributor leaves. Reference to a STOP POINT. |
|||
|
|
0:1 |
Order of visit to a stop within JOURNEY PATTERN of distributor VEHICLE JOURNEY. |
|||
|
|
0:1 |
For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation. |
|||
7.18. The group siri:SiriConnectionMonitoringIndexGroup
|
|
Convenience artifact to pick out main elements of the Connection Monitoring Service. |
||||
| siri:SiriConnectionMonitoringIndexGroup |
1:1 |
Request for information about changes to connections at a stop for Connection Monitoring service. |
|||
|
1:1 |
Request for a subscription to Connection Monitoring Service. |
||||
|
1:1 |
Feeder Delivery for Connection Monitoring Service. |
||||
|
1:1 |
Distributor Delivery for Connection Monitoring Service. |
||||
|
1:1 |
Request for information about Connection Monitoring Service Capabilities. Answered with a ConnectionMontoringCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for Connection Monitoring Service. Answers a ConnectionMontoringCapabilitiesRequest. |
||||
7.19. The group siri:SiriConnectionServiceIndexGroup
|
|
Convenience artifact to pick out main elements of the Connection Services. |
||||
| siri:SiriConnectionTimetableIndexGroup |
1:1 |
Request for information about timetabled connections at a stop. |
|||
|
1:1 |
Subscription Request for information about Timetabled connections at a stop. |
||||
|
1:1 |
Delivery for Connection Timetable Service. |
||||
|
1:1 |
Request for information about Connection Timetable Service Capabilities. Answered with a ConnectionTimetableCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for Connection Timetable Service. Answers a ConnectionTimetableCapabilitiesRequest. |
||||
| siri:SiriConnectionMonitoringIndexGroup |
1:1 |
Request for information about changes to connections at a stop for Connection Monitoring service. |
|||
|
1:1 |
Request for a subscription to Connection Monitoring Service. |
||||
|
1:1 |
Feeder Delivery for Connection Monitoring Service. |
||||
|
1:1 |
Distributor Delivery for Connection Monitoring Service. |
||||
|
1:1 |
Request for information about Connection Monitoring Service Capabilities. Answered with a ConnectionMontoringCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for Connection Monitoring Service. Answers a ConnectionMontoringCapabilitiesRequest. |
||||
7.20. The complex type siri:AbstractDistributorItemStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
Inherited content is followed by own content: |
|||||
| siri:InterchangeDistributorIdentityGroup |
|
0:1 |
Reference to the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned and at which SERVICE JOURNEY INTERCHANGE takes place. A reference associated with known feeder arrival and distributor departure STOP POINTs. |
|||
|
|
0:1 |
Reference to a STOP POINT within CONNECTION link from which distributor leaves. Reference to a STOP POINT. |
|||
|
|
0:1 |
Order of visit to a stop within JOURNEY PATTERN of distributor VEHICLE JOURNEY. |
|||
|
|
0:1 |
For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation. |
|||
|
|
1:1 |
Information about the connecting Distributor (fetcher) VEHICLE JOURNEY. |
|||
|
|
0:* |
Reference to a feeder VEHICLE JOURNEY or journeys for which the Distributor (fetcher) will wait . |
|||
7.21. The complex type siri:ConnectingJourneyFilterStructure
|
|
Type for filter for connecting journeys. |
||||
|
|
1:1 |
A reference to a dated VEHICLE JOURNEY. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
|
1:1 |
Timetabled arrival time at the connection point. |
|||
7.22. The complex type siri:ConnectingTimeFilterStructure
|
|
Type for time filter for connecting journeys. |
||||
|
|
1:1 |
Feeder LINE for which data is to be supplied. |
|||
|
|
1:1 |
Feeder for which data is to be supplied. |
|||
|
|
0:1 |
Earliest managed arrival time at the connection point. |
|||
|
|
0:1 |
Latest managedarrival time at the connection point. |
|||
7.23. The complex type siri:ConnectionMonitoringCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
|
0:1 |
Capabilities of Connection Monitoring Service. |
||||
|
0:1 |
Participants permissions to use the service. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.24. The complex type siri:ConnectionMonitoringCapabilityRequestPolicyStructure
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether results returns foreign journeys only. |
|||
7.25. The complex type siri:ConnectionMonitoringDeliveriesStructure
|
|
Type for Deliveries for Connection Monitoring Service. Used in WSDL. |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:* |
Feeder Delivery for Connection Monitoring Service. |
|||
|
b |
-1:* |
Distributor Delivery for Connection Monitoring Service. |
|||
7.26. The complex type siri:ConnectionMonitoringDistributorDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:ConnectionMonitoringDistributorPayloadGroup |
|
0:* |
An action to delay the Distributor (fetcher) until a specified time. |
||
|
|
0:* |
A Change to a stop position. |
|||
|
|
0:* |
Deletion of previous connection. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.27. The complex type siri:ConnectionMonitoringFeederDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:ConnectionMonitoringFeederPayloadGroup |
0:* |
A feeder arrival at the connection point. |
|||
|
0:* |
Cancellation of a feeder arrival at a connection point. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.28. The complex type siri:ConnectionMonitoringRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:ConnectionMonitoringTopicGroup |
|
0:1 |
Forward duration for which events should be included, that is, interval before predicted arrival at the stop for which to include events: only journeys which will arrive or depart within this time span will be returned. |
||
|
|
1:1 |
CONNECTION LINK for which data is to be supplied. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Return only journeys for the specified time. |
||
|
b |
|
-1:* |
Return only the specified journeys. |
||
| siri:ConnectionMonitoringRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.29. The complex type siri:ConnectionMonitoringServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Filtering Capabilities. |
|||
|
|
0:1 |
Request Policy capabilities. |
|||
|
|
0:1 |
Subscription Policy capabilities. |
|||
|
|
0:1 |
Optional Access control capabilities. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.30. The complex type siri:ConnectionMonitoringSubscriptionRequestStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for information about changes to connections at a stop for Connection Monitoring service. |
||||
| siri:ConnectionMonitoringSubscriptionPolicyGroup |
|
0:1 |
The amount of change to the arrival time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.31. The complex type siri:DistributorDepartureCancellationStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
| siri:InterchangeDistributorIdentityGroup |
|
0:1 |
Reference to the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned and at which SERVICE JOURNEY INTERCHANGE takes place. A reference associated with known feeder arrival and distributor departure STOP POINTs. |
|||
|
|
0:1 |
Reference to a STOP POINT within CONNECTION link from which distributor leaves. Reference to a STOP POINT. |
|||
|
|
0:1 |
Order of visit to a stop within JOURNEY PATTERN of distributor VEHICLE JOURNEY. |
|||
|
|
0:1 |
For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation. |
|||
|
|
1:1 |
Information about the connecting Distributor (fetcher) VEHICLE JOURNEY. |
|||
|
|
0:* |
Reference to a feeder VEHICLE JOURNEY or journeys for which the Distributor (fetcher) will wait . |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Reason for failure of connection. (Unbounded since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.32. The complex type siri:MonitoredFeederArrivalCancellationStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Identifier of item. |
|||
|
|
0:1 |
Time until when data is valid. (since SIRI 2.0) |
|||
| siri:InterchangeFeederIdentityGroup |
|
0:1 |
Reference to the the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned. i.e. associated with known feeder arrival and distributor departure STOP POINTs. |
|||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a LINE. |
|||
|
|
1:1 |
Reference to a DIRECTION, typically outward or return. |
|||
|
|
1:1 |
Reference to a Feeder VEHICLE JOURNEY. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
|
|
0:* |
Reason for cancellation. (Unbounded since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.33. The complex type siri:MonitoredFeederArrivalStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Identifier of item. |
|||
|
|
0:1 |
Time until when data is valid. (since SIRI 2.0) |
|||
| siri:InterchangeFeederIdentityGroup |
|
0:1 |
Reference to the the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned. i.e. associated with known feeder arrival and distributor departure STOP POINTs. |
|||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Direct Cleardown identifier of connection arrival Activity that is being deleted. |
|||
|
|
1:1 |
Information about the feeder journey. |
|||
|
0:1 |
Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) |
||||
|
|
0:1 |
Number of passengers who wish to transfer at the connection. If absent, not known. |
|||
|
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
||||
|
|
0:1 |
Predicted arrival time at the connection zone. |
|||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
|
0:1 |
Latest time by which the feeder needs informationabout the connection from the distributor as to whether it will wait and for how long. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.34. The complex type siri:StoppingPositionChangedDepartureStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
| siri:InterchangeDistributorIdentityGroup |
|
0:1 |
Reference to the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned and at which SERVICE JOURNEY INTERCHANGE takes place. A reference associated with known feeder arrival and distributor departure STOP POINTs. |
|||
|
|
0:1 |
Reference to a STOP POINT within CONNECTION link from which distributor leaves. Reference to a STOP POINT. |
|||
|
|
0:1 |
Order of visit to a stop within JOURNEY PATTERN of distributor VEHICLE JOURNEY. |
|||
|
|
0:1 |
For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation. |
|||
|
|
1:1 |
Information about the connecting Distributor (fetcher) VEHICLE JOURNEY. |
|||
|
|
0:* |
Reference to a feeder VEHICLE JOURNEY or journeys for which the Distributor (fetcher) will wait . |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Description of the revised stopping position of the Distributor (fetcher) in the connection zone. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
New location from which Distributor will leave. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.35. The complex type siri:WaitProlongedDepartureStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
| siri:InterchangeDistributorIdentityGroup |
|
0:1 |
Reference to the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned and at which SERVICE JOURNEY INTERCHANGE takes place. A reference associated with known feeder arrival and distributor departure STOP POINTs. |
|||
|
|
0:1 |
Reference to a STOP POINT within CONNECTION link from which distributor leaves. Reference to a STOP POINT. |
|||
|
|
0:1 |
Order of visit to a stop within JOURNEY PATTERN of distributor VEHICLE JOURNEY. |
|||
|
|
0:1 |
For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation. |
|||
|
|
1:1 |
Information about the connecting Distributor (fetcher) VEHICLE JOURNEY. |
|||
|
|
0:* |
Reference to a feeder VEHICLE JOURNEY or journeys for which the Distributor (fetcher) will wait . |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Estimated departure time from the connection. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
7.36. The complex type complexType[siri:ConnectionMonitoringServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-78.1)
|
|
- |
||||
|
|
0:1 |
Default preview horizon used. |
|||
|
0:1 |
Whether results can be filtered by CONNECTION LINK. Default is 'true'. |
||||
|
|
0:1 |
Whether results can be filtered by journey. |
|||
|
|
0:1 |
Whether results can be filtered by time Filter of Connection. Default is ' true'. |
|||
7.37. The complex type complexType[siri:ConnectionMonitoringServiceCapabilitiesStructure]/RequestPolicy#complexType (typedef-78.2)
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether only foreign journeys are included. |
|||
7.38. The complex type element[siri:ConnectionMonitoringPermissions]#complexType (typedef-78.3)
|
|
- |
||||
|
|
0:* |
||||
8. SIRI-CT Connection Timetable Service.
8.1. The toplevel element siri:ConnectionTimetableCapabilitiesRequest
|
|
+siri:ServiceCapabilitiesRequestStructure (↔ siri:AbstractFunctionalServiceCapabilitiesRequest) |
Request for information about Connection Timetable Service Capabilities. Answered with a ConnectionTimetableCapabilitiesResponse. |
|||
8.2. The toplevel element siri:ConnectionTimetableCapabilitiesResponse
|
|
+siri:ConnectionTimetableCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Capabilities for Connection Timetable Service. Answers a ConnectionTimetableCapabilitiesRequest. |
|||
8.3. The toplevel element siri:ConnectionTimetableDelivery
|
|
+siri:ConnectionTimetableDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery for Connection Timetable Service. |
|||
8.4. The toplevel element siri:ConnectionTimetableRequest
|
|
+siri:ConnectionTimetableRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about timetabled connections at a stop. |
|||
8.5. The toplevel element siri:ConnectionTimetableServiceCapabilities
|
|
Capabilities of Connection Timetable Service. |
||||
8.6. The toplevel element siri:ConnectionTimetableSubscriptionRequest
|
|
+siri:ConnectionTimetableSubscriptionStructure (↔ siri:AbstractFunctionalServiceSubscriptionRequest) |
Subscription Request for information about Timetabled connections at a stop. |
|||
8.7. The toplevel element siri:FeederItem
|
|
Fedder/Fetcher SERVICE JOURNEY INTERCHANGE Activity. |
||||
8.8. The toplevel element siri:TimetabledFeederArrival
|
|
+siri:TimetabledFeederArrivalStructure (↔ siri:FeederItem) |
A feeder arrival at the arrival SCHEDUELD STOP POINT of the CONNECTION link . |
|||
8.9. The toplevel element siri:TimetabledFeederArrivalCancellation
|
|
Cancellation of a previously issued Feeder Arrival. |
||||
8.10. The group siri:ConnectionTimetablePayloadGroup
|
|
Feeder delivery payload content. |
||||
| siri:ConnectionTimetablePayloadGroup |
0:* |
A feeder arrival at the arrival SCHEDUELD STOP POINT of the CONNECTION link . |
|||
|
0:* |
Cancellation of a previously issued Feeder Arrival. |
||||
8.11. The group siri:ConnectionTimetableRequestPolicyGroup
|
|
Parameters that affect the request processing. |
||||
| siri:ConnectionTimetableRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
8.12. The group siri:ConnectionTimetableSunscriptionPolicyGroup
|
|
Parameters that affect the subscription processing. |
||||
8.13. The group siri:ConnectionTimetableTopicGroup
|
|
Parameters that specify the content to be returned. |
||||
| siri:ConnectionTimetableTopicGroup |
|
0:1 |
Earliest and latest time. If absent, default to the data horizon of the service. |
||
|
|
1:1 |
CONNECTION link for which data is to be supplied. |
|||
|
|
0:1 |
Feeder LINE for which data is to be supplied. |
|||
|
|
0:1 |
Feeder DIRECTION for which data is to be supplied. |
|||
8.14. The group siri:InterchangeFeederIdentityGroup
|
|
Elements identifying CALL at CONNECTION link of SERVICE JORUNEY INTERCHANGE of Feeder Journey . |
||||
| siri:InterchangeFeederIdentityGroup |
|
0:1 |
Reference to the the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned. i.e. associated with known feeder arrival and distributor departure STOP POINTs. |
|||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
8.15. The group siri:SiriConnectionTimetableIndexGroup
|
|
Convenience artifact to pick out main elements of the Connection Timetable Service. |
||||
| siri:SiriConnectionTimetableIndexGroup |
1:1 |
Request for information about timetabled connections at a stop. |
|||
|
1:1 |
Subscription Request for information about Timetabled connections at a stop. |
||||
|
1:1 |
Delivery for Connection Timetable Service. |
||||
|
1:1 |
Request for information about Connection Timetable Service Capabilities. Answered with a ConnectionTimetableCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for Connection Timetable Service. Answers a ConnectionTimetableCapabilitiesRequest. |
||||
8.16. The complex type siri:AbstractFeederItemStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Identifier of item. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Time until when data is valid. (since SIRI 2.0) |
|||
| siri:InterchangeFeederIdentityGroup |
|
0:1 |
Reference to the the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned. i.e. associated with known feeder arrival and distributor departure STOP POINTs. |
|||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
8.17. The complex type siri:ConnectionTimetableCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
|
0:1 |
Capabilities of Connection Timetable Service. |
||||
|
|
0:1 |
Participant's permissions to use the service, Only returned if requested. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
8.18. The complex type siri:ConnectionTimetableCapabilityRequestPolicyStructure
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether results returns foreign journeys only. |
|||
8.19. The complex type siri:ConnectionTimetableDeliveriesStructure
|
|
Type for Deliveries for Connection Timetable Service. Used in WSDl. |
||||
|
1:1 |
Delivery for Connection Timetable Service. |
||||
8.20. The complex type siri:ConnectionTimetableDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:ConnectionTimetablePayloadGroup |
0:* |
A feeder arrival at the arrival SCHEDUELD STOP POINT of the CONNECTION link . |
|||
|
0:* |
Cancellation of a previously issued Feeder Arrival. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
8.21. The complex type siri:ConnectionTimetableRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:ConnectionTimetableTopicGroup |
|
0:1 |
Earliest and latest time. If absent, default to the data horizon of the service. |
||
|
|
1:1 |
CONNECTION link for which data is to be supplied. |
|||
|
|
0:1 |
Feeder LINE for which data is to be supplied. |
|||
|
|
0:1 |
Feeder DIRECTION for which data is to be supplied. |
|||
| siri:ConnectionTimetableRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
8.22. The complex type siri:ConnectionTimetableServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Filtering Capabilities. |
|||
|
|
0:1 |
Request Policy capabilities. |
|||
|
|
0:1 |
Subscription Policy capabilities. |
|||
|
|
0:1 |
Optional Access control capabilities. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
8.23. The complex type siri:ConnectionTimetableSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for information about timetabled connections at a stop. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
8.24. The complex type siri:TimetabledFeederArrivalCancellationStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Reference to an Activity Element of a delivery. |
|||
|
Inherited content is followed by own content: |
|||||
| siri:InterchangeFeederIdentityGroup |
|
0:1 |
Reference to the the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned. i.e. associated with known feeder arrival and distributor departure STOP POINTs. |
|||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
|
1:1 |
Reference to a LINE. |
|||
|
|
1:1 |
Reference to a DIRECTION, typically outward or return. |
|||
|
|
1:1 |
Reference to a VEHICLE JOURNEY. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
|
|
0:* |
Reason for deletion. (Unbounded since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
8.25. The complex type siri:TimetabledFeederArrivalStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Identifier of item. |
|||
|
|
0:1 |
Time until when data is valid. (since SIRI 2.0) |
|||
| siri:InterchangeFeederIdentityGroup |
|
0:1 |
Reference to the the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. |
||
|
|
1:1 |
Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned. i.e. associated with known feeder arrival and distributor departure STOP POINTs. |
|||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Information about the feeder journey. |
|||
|
|
1:1 |
Planned arrival time at the connection point. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
8.26. The complex type complexType[siri:ConnectionTimetableCapabilitiesResponseStructure]/ConnectionTimetablePermissions#complexType (typedef-80.1)
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permission for a single participant or all participants to use an aspect of the service. |
|||
8.27. The complex type complexType[siri:ConnectionTimetableServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-80.2)
|
|
- |
||||
|
1:1 |
Whether results can be filtered by LINE. Default is 'true' |
||||
|
1:1 |
Whether results can be filtered by CONNECTION LINK. Default is 'true'. |
||||
8.28. The complex type complexType[siri:ConnectionTimetableServiceCapabilitiesStructure]/RequestPolicy#complexType (typedef-80.3)
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether service returns only foreign journeys. Default is 'false'. |
|||
9. SIRI DIscovery Services for SCHEDULED STOP POINTs, LINEs,OPERATORs, FACILITies and feature TYPE OF VALUE codes.
9.1. Simple type definitions
|
|
Detail Levels for CONNECTION LINKs Discovery Request. (since SIRI 2.0) |
||||||||
|
|||||||||
|
|
Detail Levels for Facility Points Request. (since SIRI 2.0) |
||||||||
|
|||||||||
|
|
Detail Levels for Lines Discovery Request. (since SIRI 2.0) |
||||||||
|
|||||||||
|
|
Detail Levels for Stop Points Discovery Request. (since SIRI 2.0) |
||||||||
|
|||||||||
9.2. The toplevel element siri:ConnectionLinksDelivery
|
|
+siri:ConnectionLinksDeliveryStructure (↔ siri:AbstractDiscoveryDelivery) |
Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. (since SIRI 2.0) |
|||
9.3. The toplevel element siri:ConnectionLinksRequest
|
|
+siri:ConnectionLinksDiscoveryRequestStructure (↔ siri:AbstractDiscoveryRequest) |
Requests a list of the CONNECTION LINKs covered by a Producer. (since SIRI 2.0) |
|||
9.4. The toplevel element siri:FacilityDelivery
|
|
+siri:FacilityDeliveryStructure (↔ siri:AbstractDiscoveryDelivery) |
Returns the Facilities covered by a service. Answers a StopPointsRequest. |
|||
9.5. The toplevel element siri:FacilityRequest
|
|
+siri:FacilityRequestStructure (↔ siri:AbstractDiscoveryRequest) |
Requests a list of the Facilities covered by a Producer. |
|||
9.6. The toplevel element siri:InfoChannelDelivery
|
|
+siri:InfoChannelDeliveryStructure (↔ siri:AbstractDiscoveryDelivery) |
Returns the Info Channels covered by a service. Answers a InfoChannelRequest. |
|||
9.7. The toplevel element siri:InfoChannelRequest
|
|
+siri:InfoChannelDiscoveryRequestStructure (↔ siri:AbstractDiscoveryRequest) |
Requests a list of the Info Channels covered by a Producer. |
|||
9.8. The toplevel element siri:LinesDelivery
|
|
+siri:LinesDeliveryStructure (↔ siri:AbstractDiscoveryDelivery) |
Returns the LINEs covered by a web service. Answers a LINEsRequest. |
|||
9.9. The toplevel element siri:LinesRequest
|
|
+siri:LinesDiscoveryRequestStructure (↔ siri:AbstractDiscoveryRequest) |
Requests a list of the LINEs covered by a Producer. |
|||
9.10. The toplevel element siri:ProductCategoriesDelivery
|
|
+siri:ProductCategoriesDeliveryStructure (↔ siri:AbstractDiscoveryDelivery) |
Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. |
|||
9.11. The toplevel element siri:ProductCategoriesRequest
|
|
+siri:ProductCategoriesDiscoveryRequestStructure (↔ siri:AbstractDiscoveryRequest) |
Requests a list of the Product Categories covered by a Producer. |
|||
9.12. The toplevel element siri:ServiceFeaturesDelivery
|
|
+siri:ServiceFeaturesDeliveryStructure (↔ siri:AbstractDiscoveryDelivery) |
Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest. |
|||
9.13. The toplevel element siri:ServiceFeaturesRequest
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
|
1:1 |
Version number of request. Fixed |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.14. The toplevel element siri:StopPointsDelivery
|
|
+siri:StopPointsDeliveryStructure (↔ siri:AbstractDiscoveryDelivery) |
Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest. |
|||
9.15. The toplevel element siri:StopPointsRequest
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
|
1:1 |
Version number of request. Fixed |
|||
|
The element contains one of the following elements (a-c) |
|||||
| siri:StopPointsDiscoveryRequestTopicGroup |
a |
|
-0:1 |
Rectangle containing stops be returned. ((since SIRI 2.0)) |
|
|
b |
|
-0:1 |
Circle containing stops be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) |
||
|
c |
|
-0:1 |
Filter the results to include only stops associated with the PLACE . ((since SIRI 2.0)) |
||
|
|
0:1 |
Filter the results to include only stops run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Filter the results to include only stops for the given LINE. ((since SIRI 2.0)) |
|||
| siri:StopPointsDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.16. The toplevel element siri:VehicleFeaturesDelivery
|
|
+siri:VehicleFeaturesDeliveryStructure (↔ siri:AbstractDiscoveryDelivery) |
Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. |
|||
9.17. The toplevel element siri:VehicleFeaturesRequest
|
|
+siri:VehicleFeaturesRequestStructure (↔ siri:AbstractDiscoveryRequest) |
Requests a list of the Vehicle Features covered by a Producer. |
|||
9.18. The group siri:ConnectionLinksDiscoveryRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of ConnectionLinks returned. (since SIRI 2.0) |
||||
| siri:ConnectionLinksDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
9.19. The group siri:ConnectionLinksDiscoveryRequestTopicGroup
|
|
Parameters that specify the CONNECTION LINKs to be returned. (since SIRI 2.0) |
||||
|
The element contains none or one of the following elements (a) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ac) |
|||||
| siri:ConnectionLinksDiscoveryRequestTopicGroup |
aa |
|
-1:1 |
Rectangle containing stops of ConnectionLinks be returned. |
|
|
ab |
|
-1:1 |
Circle containing stops for ConnectionLinks be returned. Point indicates centre, precision indicates radius |
||
|
ac |
|
-1:1 |
Filter the results to include only ConnectionLinks for stops assoicated with the place . |
||
|
|
0:1 |
Filter the results to include only ConnectionLinks for stops assoicated with the specified line. |
|||
|
|
0:1 |
Filter the results to include only Stop d run by the specified OPERATOR. |
|||
9.20. The group siri:FacilityRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. (since SIRI 2.0) |
||||
| siri:FacilityRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
9.21. The group siri:FacilityRequestTopicGroup
|
|
Parameters that specify the Facilities to be returned. (since SIRI 2.0) |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:FacilityRequestTopicGroup |
a |
|
-0:1 |
Rectangle containing Facilities be returned. ((since SIRI 2.0)) |
|
|
b |
|
-0:1 |
Filter the results to include only Facilities associated with the TOPOGRAPHIC PLACE . ((since SIRI 2.0)) |
||
|
|
0:1 |
Filter the results to include only Facilities run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Filter the results to include only Facilities for the given LINE. ((since SIRI 2.0)) |
|||
9.22. The group siri:LinesDiscoveryRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of Linesreturned. (since SIRI 2.0) |
||||
| siri:LinesDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
9.23. The group siri:LinesDiscoveryRequestTopicGroup
|
|
Parameters that specify the LINEs to be returned. (since SIRI 2.0) |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ac) |
|||||
| siri:LinesDiscoveryRequestTopicGroup |
aa |
|
-1:1 |
Rectangle containing stops of lines be returned. ((since SIRI 2.0)) |
|
|
ab |
|
-1:1 |
Circle containing stops for lines be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) |
||
|
ac |
|
-1:1 |
Filter the results to include only lines for stops assoicated with the place . ((since SIRI 2.0)) |
||
|
b |
|
-1:1 |
Reference to line for which details are to be returned (v2.0) |
||
|
|
0:1 |
Filter the results to include only Stop d run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
9.24. The group siri:ProductCategoriesRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. (since SIRI 2.0) |
||||
| siri:ProductCategoriesRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
9.25. The group siri:SiriDiscoveryIndexGroup
|
|
Convenience artifact to pick out main elements of the Estimated Timetable Service. |
||||
|
The element contains one of the following elements (a-h) |
|||||
| siri:SiriReferenceDiscoveryRequestGroup |
a |
-1:1 |
Requests a list of the STOP POINTs and places covered by a Producer. |
||
|
b |
-1:1 |
Requests a list of the LINEs covered by a Producer. |
|||
|
c |
-1:1 |
Requests a list of the Service Features covered by a Producer. |
|||
|
d |
-1:1 |
Requests a list of the Product Categories covered by a Producer. |
|||
|
e |
-1:1 |
Requests a list of the Vehicle Features covered by a Producer. |
|||
|
f |
-1:1 |
Requests a list of the Info Channels covered by a Producer. |
|||
|
g |
-1:1 |
Requests a list of the Facilities covered by a Producer. |
|||
|
h |
-1:1 |
Requests a list of the CONNECTION LINKs covered by a Producer. (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-h) |
|||||
| siri:SiriDiscoveryReferenceDeliveryGroup |
a |
-1:1 |
Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest. |
||
|
b |
-1:1 |
Returns the LINEs covered by a web service. Answers a LINEsRequest. |
|||
|
c |
-1:1 |
Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. |
|||
|
d |
-1:1 |
Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest. |
|||
|
e |
-1:1 |
Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. |
|||
|
f |
-1:1 |
Returns the Info Channels covered by a service. Answers a InfoChannelRequest. |
|||
|
g |
-1:1 |
Returns the Facilities covered by a service. Answers a StopPointsRequest. |
|||
|
h |
-1:1 |
Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. (since SIRI 2.0) |
|||
9.26. The group siri:SiriDiscoveryReferenceDeliveryGroup
|
|
Responses with reference data for use in service requests. |
||||
|
The element contains one of the following elements (a-h) |
|||||
| siri:SiriDiscoveryReferenceDeliveryGroup |
a |
-1:1 |
Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest. |
||
|
b |
-1:1 |
Returns the LINEs covered by a web service. Answers a LINEsRequest. |
|||
|
c |
-1:1 |
Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. |
|||
|
d |
-1:1 |
Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest. |
|||
|
e |
-1:1 |
Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. |
|||
|
f |
-1:1 |
Returns the Info Channels covered by a service. Answers a InfoChannelRequest. |
|||
|
g |
-1:1 |
Returns the Facilities covered by a service. Answers a StopPointsRequest. |
|||
|
h |
-1:1 |
Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. (since SIRI 2.0) |
|||
9.27. The group siri:SiriReferenceDiscoveryRequestGroup
|
|
Requests for reference data for use in service requests. |
||||
|
The element contains one of the following elements (a-h) |
|||||
| siri:SiriReferenceDiscoveryRequestGroup |
a |
-1:1 |
Requests a list of the STOP POINTs and places covered by a Producer. |
||
|
b |
-1:1 |
Requests a list of the LINEs covered by a Producer. |
|||
|
c |
-1:1 |
Requests a list of the Service Features covered by a Producer. |
|||
|
d |
-1:1 |
Requests a list of the Product Categories covered by a Producer. |
|||
|
e |
-1:1 |
Requests a list of the Vehicle Features covered by a Producer. |
|||
|
f |
-1:1 |
Requests a list of the Info Channels covered by a Producer. |
|||
|
g |
-1:1 |
Requests a list of the Facilities covered by a Producer. |
|||
|
h |
-1:1 |
Requests a list of the CONNECTION LINKs covered by a Producer. (since SIRI 2.0) |
|||
9.28. The group siri:StopPointsDiscoveryRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of stops returned. (since SIRI 2.0) |
||||
| siri:StopPointsDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
9.29. The group siri:StopPointsDiscoveryRequestTopicGroup
|
|
Parameters that specify the STOP POINTs to be returned. (since SIRI 2.0) |
||||
|
The element contains one of the following elements (a-c) |
|||||
| siri:StopPointsDiscoveryRequestTopicGroup |
a |
|
-0:1 |
Rectangle containing stops be returned. ((since SIRI 2.0)) |
|
|
b |
|
-0:1 |
Circle containing stops be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) |
||
|
c |
|
-0:1 |
Filter the results to include only stops associated with the PLACE . ((since SIRI 2.0)) |
||
|
|
0:1 |
Filter the results to include only stops run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Filter the results to include only stops for the given LINE. ((since SIRI 2.0)) |
|||
9.30. The group siri:VehicleFeaturesRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. (since SIRI 2.0) |
||||
| siri:VehicleFeaturesRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
9.31. The complex type siri:ConnectionLinksDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed. |
|||
|
0:* |
SCHEDULED CONNECTION LINK definition. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.32. The complex type siri:ConnectionLinksDiscoveryRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
|
The element contains none or one of the following elements (a) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ac) |
|||||
| siri:ConnectionLinksDiscoveryRequestTopicGroup |
aa |
|
-1:1 |
Rectangle containing stops of ConnectionLinks be returned. |
|
|
ab |
|
-1:1 |
Circle containing stops for ConnectionLinks be returned. Point indicates centre, precision indicates radius |
||
|
ac |
|
-1:1 |
Filter the results to include only ConnectionLinks for stops assoicated with the place . |
||
|
|
0:1 |
Filter the results to include only ConnectionLinks for stops assoicated with the specified line. |
|||
|
|
0:1 |
Filter the results to include only Stop d run by the specified OPERATOR. |
|||
| siri:ConnectionLinksDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.33. The complex type siri:FacilityDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed. |
|||
|
|
0:* |
Facility Definition. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.34. The complex type siri:FacilityRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
|
The element contains one of the following elements (a-b) |
|||||
| siri:FacilityRequestTopicGroup |
a |
|
-0:1 |
Rectangle containing Facilities be returned. ((since SIRI 2.0)) |
|
|
b |
|
-0:1 |
Filter the results to include only Facilities associated with the TOPOGRAPHIC PLACE . ((since SIRI 2.0)) |
||
|
|
0:1 |
Filter the results to include only Facilities run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Filter the results to include only Facilities for the given LINE. ((since SIRI 2.0)) |
|||
| siri:FacilityRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.35. The complex type siri:InfoChannelDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed. |
|||
|
0:* |
Info Channel supported by Producer service. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.36. The complex type siri:InfoChannelDiscoveryRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.37. The complex type siri:LinesDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed. |
|||
|
0:* |
Information about LINEs covered by server. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.38. The complex type siri:LinesDiscoveryRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ac) |
|||||
| siri:LinesDiscoveryRequestTopicGroup |
aa |
|
-1:1 |
Rectangle containing stops of lines be returned. ((since SIRI 2.0)) |
|
|
ab |
|
-1:1 |
Circle containing stops for lines be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) |
||
|
ac |
|
-1:1 |
Filter the results to include only lines for stops assoicated with the place . ((since SIRI 2.0)) |
||
|
b |
|
-1:1 |
Reference to line for which details are to be returned (v2.0) |
||
|
|
0:1 |
Filter the results to include only Stop d run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
| siri:LinesDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.39. The complex type siri:ProductCategoriesDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed. |
|||
|
0:* |
Category for classification of a journey as a Product |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.40. The complex type siri:ProductCategoriesDiscoveryRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:ProductCategoriesRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.41. The complex type siri:ServiceFeaturesDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed. |
|||
|
0:* |
Service Feature description. |
||||
9.42. The complex type siri:ServiceFeaturesDiscoveryRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.43. The complex type siri:StopPointsDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
|
0:* |
SCHEDULED STOP POINT definition. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.44. The complex type siri:StopPointsDiscoveryRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
|
The element contains one of the following elements (a-c) |
|||||
| siri:StopPointsDiscoveryRequestTopicGroup |
a |
|
-0:1 |
Rectangle containing stops be returned. ((since SIRI 2.0)) |
|
|
b |
|
-0:1 |
Circle containing stops be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) |
||
|
c |
|
-0:1 |
Filter the results to include only stops associated with the PLACE . ((since SIRI 2.0)) |
||
|
|
0:1 |
Filter the results to include only stops run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Filter the results to include only stops for the given LINE. ((since SIRI 2.0)) |
|||
| siri:StopPointsDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.45. The complex type siri:VehicleFeaturesDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed. |
|||
|
0:* |
Vehicle Feature description. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.46. The complex type siri:VehicleFeaturesRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:VehicleFeaturesRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.47. The complex type element[siri:StopPointsRequest]#complexType (typedef-73.1)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
|
1:1 |
Version number of request. Fixed |
|||
|
The element contains one of the following elements (a-c) |
|||||
| siri:StopPointsDiscoveryRequestTopicGroup |
a |
|
-0:1 |
Rectangle containing stops be returned. ((since SIRI 2.0)) |
|
|
b |
|
-0:1 |
Circle containing stops be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) |
||
|
c |
|
-0:1 |
Filter the results to include only stops associated with the PLACE . ((since SIRI 2.0)) |
||
|
|
0:1 |
Filter the results to include only stops run by the specified OPERATOR. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Filter the results to include only stops for the given LINE. ((since SIRI 2.0)) |
|||
| siri:StopPointsDiscoveryRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. (since SIRI 2.0) |
||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
9.48. The complex type element[siri:ServiceFeaturesRequest]#complexType (typedef-73.2)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
|
|
1:1 |
Version number of request. Fixed |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
10. SIRI-ET Estimated Timetable Service.
10.1. Simple type definitions
|
|
Detail Levels for Estimated Timetable Request. |
||||||||||
|
|||||||||||
10.2. The toplevel element siri:EstimatedTimetableCapabilitiesRequest
|
|
+siri:ServiceCapabilitiesRequestStructure (↔ siri:AbstractFunctionalServiceCapabilitiesRequest) |
Request for information about Estimated Timetable Service Capabilities. Answered with a EstimatedTimetableCapabilitiesResponse. |
|||
10.3. The toplevel element siri:EstimatedTimetableCapabilitiesResponse
|
|
+siri:EstimatedTimetableCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Capabilities for Estimated Timetable Service. Answers a EstimatedTimetableCapabilitiesRequest. |
|||
10.4. The toplevel element siri:EstimatedTimetableDelivery
|
|
+siri:EstimatedTimetableDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery for Estimated Timetable Service. |
|||
10.5. The toplevel element siri:EstimatedTimetablePermissions
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permission for a single participant or all participants to use an aspect of the service. |
|||
10.6. The toplevel element siri:EstimatedTimetableRequest
|
|
+siri:EstimatedTimetableRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about the estimated timetable. |
|||
10.7. The toplevel element siri:EstimatedTimetableServiceCapabilities
|
|
Capabilities of Estimated TimetableService. |
||||
10.8. The toplevel element siri:EstimatedTimetableSubscriptionRequest
|
|
+siri:EstimatedTimetableSubscriptionStructure (↔ siri:AbstractFunctionalServiceSubscriptionRequest) |
Request for a subscription to the Estimated Timetable Service. |
|||
10.9. The group siri:EstimatedTimetablePayloadGroup
|
|
Payload part of Estimated Timetable Delivery. |
||||
| siri:EstimatedTimetablePayloadGroup |
|
1:* |
Estimated Journeys of a common TIMETABLE VERSION FRAME, grouped by timetable version. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
10.10. The group siri:EstimatedTimetableRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. |
||||
| siri:EstimatedTimetableRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
0:1 |
Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (SIRI 2.0) |
|||
10.11. The group siri:EstimatedTimetableSubscriptionPolicyGroup
|
|
Parameters that affect the subscription publishing and notification processing. |
||||
| siri:EstimatedTimetableSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of data, or only provide updates to the previously returned data i.e. changes to the expected deviation (delay or early time). Default is 'true'. If true only changes at the first stop will be returned and the client must interpolate the If false each subscription response will contain the full information as specified in this request (+(since SIRI 2.0)). |
||
|
|
0:1 |
The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a timetable is changed by 30 seconds - an update will only be sent when the timetable is changed by at least least 2 minutes. (OPtional from SIRI 2.0) |
|||
|
|
0:1 |
Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. (since SIRI 2.1) - 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. The server will automatically proceed with 'false' if capability is not supported. - 'true': Can be requested if the data traffic is to be reduced and an immediate transmissions is not required in any of the consumer systems. 'true' specifies that the data producer should skip RECORDED CALL updates (if capability is supported after all), i.e., deliver them with the next update instead. - No specification: Default value 'false' applies (don't skip updates of recorded data). |
|||
|
|
0:1 |
Indicates whether ONLY actual arrival-/departure times should be delivered. In other words, whether all updates related to ESTIMATED CALL should be skipped. (since SIRI 2.1) - 'false': Specifies that the data producer should transmit ESTIMATED and RECORDED CALL data as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. The server will automatically proceed with 'false' if capability is not supported. - 'true': Can be requested if a consumer system is only interested in the actual times / recorded events because it only wants to check the performance for example. 'true' specifies that the data producer should only deliver RECORDED CALL udpates and skip ESTIMATED CALL updates (if capability is supported after all), i.e., deliver ESTIMATED CALL updates only with the next RECORDED CALL update. - No specification: Default value 'false' applies (don't skip updates of estimated data). |
|||
10.12. The group siri:EstimatedTimetableTopicGroup
|
|
Parameters that specify the content to be returned. |
||||
| siri:EstimatedTimetableTopicGroup |
|
0:1 |
Forward duration for which journeys should be included. For subscriptions, this duration is a continuously rolling window from the present time. For immediate requests, this duration is measured from the time of the request. |
||
|
|
0:1 |
Communicate only differences to the timetable specified by this version of the timetable. |
|||
|
|
0:* |
Filter the results to include journeys for only the specified OPERATORs. |
|||
|
|
0:1 |
Filter the results to include only VEHICLEs along the given LINEs. |
|||
|
|
0:* |
Filter the results to include only journeys of the specified VEHICLE MODE. (since SIRI 2.1) |
|||
|
|
0:* |
Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. (since SIRI 2.1) |
|||
|
|
0:* |
Filter the results to include only journeys with a CALL at the specified STOP POINT. (since SIRI 2.1) |
|||
10.13. The group siri:SiriEstimatedTimetableIndexGroup
|
|
Convenience artifact to pick out main elements of the Estimated Timetable Service. |
||||
| siri:SiriEstimatedTimetableIndexGroup |
1:1 |
Request for information about the estimated timetable. |
|||
|
1:1 |
Request for a subscription to the Estimated Timetable Service. |
||||
|
1:1 |
Delivery for Estimated Timetable Service. |
||||
|
1:1 |
Request for information about Estimated Timetable Service Capabilities. Answered with a EstimatedTimetableCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for Estimated Timetable Service. Answers a EstimatedTimetableCapabilitiesRequest. |
||||
10.14. The complex type siri:EstimatedTimetableCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
||||
|
0:1 |
Capabilities of Estimated TimetableService. |
||||
|
0:1 |
Participant's permissions to use the service. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
10.15. The complex type siri:EstimatedTimetableCapabilityRequestPolicyStructure
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether results returns foreign journeys only. |
|||
10.16. The complex type siri:EstimatedTimetableDeliveriesStructure
|
|
Type for Deliveries for Real-time Timetable Service. Used in WSDL. |
||||
|
1:* |
Delivery for Estimated Timetable Service. |
||||
10.17. The complex type siri:EstimatedTimetableDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:EstimatedTimetablePayloadGroup |
|
1:* |
Estimated Journeys of a common TIMETABLE VERSION FRAME, grouped by timetable version. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
10.18. The complex type siri:EstimatedTimetableRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:EstimatedTimetableTopicGroup |
|
0:1 |
Forward duration for which journeys should be included. For subscriptions, this duration is a continuously rolling window from the present time. For immediate requests, this duration is measured from the time of the request. |
||
|
|
0:1 |
Communicate only differences to the timetable specified by this version of the timetable. |
|||
|
|
0:* |
Filter the results to include journeys for only the specified OPERATORs. |
|||
|
|
0:1 |
Filter the results to include only VEHICLEs along the given LINEs. |
|||
|
|
0:* |
Filter the results to include only journeys of the specified VEHICLE MODE. (since SIRI 2.1) |
|||
|
|
0:* |
Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. (since SIRI 2.1) |
|||
|
|
0:* |
Filter the results to include only journeys with a CALL at the specified STOP POINT. (since SIRI 2.1) |
|||
| siri:EstimatedTimetableRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
0:1 |
Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. (SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
10.19. The complex type siri:EstimatedTimetableServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Filtering Capabilities. |
|||
|
|
0:1 |
Request Policy capabilities. |
|||
|
|
0:1 |
Subscription Policy capabilities. |
|||
|
|
0:1 |
Optional Access control capabilities. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
10.20. The complex type siri:EstimatedTimetableSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for information about the estimated timetable. |
||||
| siri:EstimatedTimetableSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of data, or only provide updates to the previously returned data i.e. changes to the expected deviation (delay or early time). Default is 'true'. If true only changes at the first stop will be returned and the client must interpolate the If false each subscription response will contain the full information as specified in this request (+(since SIRI 2.0)). |
||
|
|
0:1 |
The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a timetable is changed by 30 seconds - an update will only be sent when the timetable is changed by at least least 2 minutes. (OPtional from SIRI 2.0) |
|||
|
|
0:1 |
Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. (since SIRI 2.1) - 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. The server will automatically proceed with 'false' if capability is not supported. - 'true': Can be requested if the data traffic is to be reduced and an immediate transmissions is not required in any of the consumer systems. 'true' specifies that the data producer should skip RECORDED CALL updates (if capability is supported after all), i.e., deliver them with the next update instead. - No specification: Default value 'false' applies (don't skip updates of recorded data). |
|||
|
|
0:1 |
Indicates whether ONLY actual arrival-/departure times should be delivered. In other words, whether all updates related to ESTIMATED CALL should be skipped. (since SIRI 2.1) - 'false': Specifies that the data producer should transmit ESTIMATED and RECORDED CALL data as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. The server will automatically proceed with 'false' if capability is not supported. - 'true': Can be requested if a consumer system is only interested in the actual times / recorded events because it only wants to check the performance for example. 'true' specifies that the data producer should only deliver RECORDED CALL udpates and skip ESTIMATED CALL updates (if capability is supported after all), i.e., deliver ESTIMATED CALL updates only with the next RECORDED CALL update. - No specification: Default value 'false' applies (don't skip updates of estimated data). |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
10.21. The complex type siri:EstimatedVersionFrameStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
Version Identifier. |
||||
|
1:* |
A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. |
||||
|
0:* |
A real-time SERVICE JOURNEY INTERCHANGE that may be made between the stops of two monitored journeys. It includes the current real-time predicted transfer and wait times. (since SIRI 2.0) |
||||
10.22. The complex type group[siri:EstimatedTimetableTopicGroup]/Lines#complexType (typedef-83.1)
|
|
- |
||||
|
|
1:* |
Include only vehicles along the given LINE. |
|||
10.23. The complex type complexType[siri:EstimatedTimetableServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-83.2)
|
|
- |
||||
|
|
0:1 |
Preview interval available for estimations. |
|||
|
1:1 |
Whether results can be filtered by OPERATOR. Default is 'true'. |
||||
|
1:1 |
Whether results can be filtered by LINE. Default is 'true' |
||||
|
0:1 |
Whether results can be filtered by VEHICLE MODE. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether results can be filtered by SCHEDULED STOP POINT. Default is 'true'. |
||||
|
|
0:1 |
Whether results can be filtered by TIMETABLE VERSION Default is 'true'. |
|||
10.24. The complex type complexType[siri:EstimatedTimetableServiceCapabilitiesStructure]/RequestPolicy#complexType (typedef-83.3)
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
10.25. The complex type element[siri:EstimatedTimetablePermissions]#complexType (typedef-83.4)
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permission for a single participant or all participants to use an aspect of the service. |
|||
11. SIRI-FM Facility Monitoring Service.
11.1. The toplevel element siri:FacilityCondition
|
|
Condition of a Facility that is being monitored. |
||||
11.2. The toplevel element siri:FacilityMonitoringCapabilitiesRequest
|
|
+siri:ServiceCapabilitiesRequestStructure (↔ siri:AbstractFunctionalServiceCapabilitiesRequest) |
Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
|||
11.3. The toplevel element siri:FacilityMonitoringCapabilitiesResponse
|
|
+siri:FacilityMonitoringCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. |
|||
11.4. The toplevel element siri:FacilityMonitoringDelivery
|
|
+siri:FacilityMonitoringDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery for Vehicle Monitoring Service. |
|||
11.5. The toplevel element siri:FacilityMonitoringPermissions
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
||||
11.6. The toplevel element siri:FacilityMonitoringRequest
|
|
+siri:FacilityMonitoringRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about Facilities status. |
|||
11.7. The toplevel element siri:FacilityMonitoringServiceCapabilities
|
|
Capabilities of Vehicle Monitoring Service. |
||||
11.8. The toplevel element siri:FacilityMonitoringSubscriptionRequest
|
|
+siri:FacilityMonitoringSubscriptionStructure (↔ siri:AbstractFunctionalServiceSubscriptionRequest) |
Request for a subscription to the Vehicle Monitoring Service. |
|||
11.9. The group siri:FacilityLocationGroup
|
|
Parameters to filter Facility Monitoring requests, based on the facility location . |
||||
| siri:FacilityLocationGroup |
0:* |
Reference to a Facility. |
|||
|
0:* |
Classification of facilities into arbitrary Facility categories. SIRI provides a recommended set of values covering most usages. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
|
0:1 |
Reference to a LINE. |
||||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:1 |
Reference to a CONNECTION link |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 |
||
|
b |
-1:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
|
0:1 |
Reference to a VEHICLE. |
||||
|
|
0:1 |
Reference to a STOP PLACE. |
|||
|
|
0:1 |
Reference to a STOP PLACE component. |
|||
|
0:1 |
Reference to a SITE |
||||
11.10. The group siri:FacilityMonitoringPayloadGroup
|
|
Payload part of Vehicle Monitoring delivery. |
||||
| siri:FacilityMonitoringPayloadGroup |
0:* |
Condition of a Facility that is being monitored. |
|||
11.11. The group siri:FacilityMonitoringRequestPolicyGroup
|
|
Parameters that affect the request processing. |
||||
| siri:FacilityMonitoringRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
The maximum number of facility status in a given delivery. The most recent n Events within the look ahead window are included. |
|||
11.12. The group siri:FacilityMonitoringSubscriptionPolicyGroup
|
|
Parameters that affect the subscription publishing and notification processing. |
||||
| siri:FacilityMonitoringSubscriptionPolicyGroup |
|
0:1 |
Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. If false or omitted, each subscription response will contain the full information as specified in this request. |
||
11.13. The group siri:FacilityMonitoringTopicGroup
|
|
Parameters that specify the content to be returned. |
||||
| siri:FacilityMonitoringTopicGroup |
|
0:1 |
Forward duration for which Facilities status change: only status change which will occur within this time span will be returned. |
||
|
|
0:1 |
Start time for PreviewInterval. If absent, then current time is assumed. |
|||
| siri:FacilityLocationGroup |
0:* |
Reference to a Facility. |
|||
|
0:* |
Classification of facilities into arbitrary Facility categories. SIRI provides a recommended set of values covering most usages. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
|
0:1 |
Reference to a LINE. |
||||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:1 |
Reference to a CONNECTION link |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 |
||
|
b |
-1:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
|
0:1 |
Reference to a VEHICLE. |
||||
|
|
0:1 |
Reference to a STOP PLACE. |
|||
|
|
0:1 |
Reference to a STOP PLACE component. |
|||
|
0:1 |
Reference to a SITE |
||||
| siri:FacilityMonitoringTopicGroup |
|
0:* |
Filter only for facility changes that affect the following accessibility needs. |
||
11.14. The group siri:FacilityMonitoringVolumeGroup
|
|
Elements for volume control. |
||||
| siri:FacilityMonitoringVolumeGroup |
|
0:1 |
Whether a maximum number of Facility Status to include can be specified. Default is 'false'. |
||
11.15. The group siri:SiriFacilityMonitoringServiceIndexGroup
|
|
Convenience artifact to pick out main elements of the Facility Monitoring Service. |
||||
| siri:SiriFacilityMonitoringServiceIndexGroup |
1:1 |
Request for information about Facilities status. |
|||
|
1:1 |
Request for a subscription to the Vehicle Monitoring Service. |
||||
|
1:1 |
Delivery for Vehicle Monitoring Service. |
||||
|
1:1 |
Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. |
||||
11.16. The complex type siri:AccessibilityNeedsFilterStructure
|
|
Type for information about Accessibility Facilities status. |
||||
|
|
1:* |
User need to be monitored. |
|||
11.17. The complex type siri:FacilityMonitoringCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
|
0:1 |
Capabilities of Vehicle Monitoring Service. |
||||
|
0:1 |
Participant's permissions to use the service. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
11.18. The complex type siri:FacilityMonitoringDeliveriesStructure
|
|
Type for Deliveries for VEHICLE monitoring services Used in WSDL. |
||||
|
1:* |
Delivery for Vehicle Monitoring Service. |
||||
11.19. The complex type siri:FacilityMonitoringDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:FacilityMonitoringPayloadGroup |
0:* |
Condition of a Facility that is being monitored. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
11.20. The complex type siri:FacilityMonitoringRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:FacilityMonitoringTopicGroup |
|
0:1 |
Forward duration for which Facilities status change: only status change which will occur within this time span will be returned. |
||
|
|
0:1 |
Start time for PreviewInterval. If absent, then current time is assumed. |
|||
| siri:FacilityLocationGroup |
0:* |
Reference to a Facility. |
|||
|
0:* |
Classification of facilities into arbitrary Facility categories. SIRI provides a recommended set of values covering most usages. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
|
0:1 |
Reference to a LINE. |
||||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:1 |
Reference to a CONNECTION link |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 |
||
|
b |
-1:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
|
0:1 |
Reference to a VEHICLE. |
||||
|
|
0:1 |
Reference to a STOP PLACE. |
|||
|
|
0:1 |
Reference to a STOP PLACE component. |
|||
|
0:1 |
Reference to a SITE |
||||
| siri:FacilityMonitoringTopicGroup |
|
0:* |
Filter only for facility changes that affect the following accessibility needs. |
||
| siri:FacilityMonitoringRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
The maximum number of facility status in a given delivery. The most recent n Events within the look ahead window are included. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
11.21. The complex type siri:FacilityMonitoringServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Filtering Capabilities. |
|||
|
|
0:1 |
Request Policy capabilities. |
|||
|
|
0:1 |
Subscription Policy capabilities. |
|||
|
|
0:1 |
Optional Access control capabilities. |
|||
|
|
0:1 |
Optional Response capabilities. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
11.22. The complex type siri:FacilityMonitoringServicePermissionStructure
|
|
Type for Abstract Permission. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. |
||
|
b |
|
-1:1 |
Permission applies to specified participant. |
||
|
|
0:1 |
Permissions for general capabilities. |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
The OPERATOR data that the participant may access. |
||||
|
1:1 |
The LINEs that the participant may access. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
11.23. The complex type siri:FacilityMonitoringSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for information about Facilities status. |
||||
| siri:FacilityMonitoringSubscriptionPolicyGroup |
|
0:1 |
Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. If false or omitted, each subscription response will contain the full information as specified in this request. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
11.24. The complex type element[siri:LinePermissions]#complexType (typedef-21.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this LINE. |
||
11.25. The complex type element[siri:OperatorPermissions]#complexType (typedef-21.2)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this OPERATOR. |
||
11.26. The complex type complexType[siri:AbstractPermissionStructure]/GeneralCapabilities#complexType (typedef-45.1)
|
|
- |
||||
|
|
1:1 |
Participant may make direct requests for data. Default is 'true'. |
|||
|
|
1:1 |
Participant may create subscriptions. Default True. |
|||
11.27. The complex type complexType[siri:FacilityMonitoringServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-75.1)
|
|
- |
||||
|
|
1:1 |
Default preview interval. Default is 60 minutes. |
|||
|
1:1 |
Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'. |
||||
|
|
1:1 |
Whether results can be filtered by location. Fixed as 'true'. |
|||
|
0:1 |
Whether results can be filtered by VEHICLE. Default is 'false'. |
||||
|
0:1 |
Whether results can be filtered by LINE. Default is 'true' |
||||
|
0:1 |
Whether results can be filtered by SCHEDULED STOP POINT. Default is 'true'. |
||||
|
0:1 |
Whether results can be filtered by VEHICLE JOURNEY. Default is 'false'. |
||||
|
0:1 |
Whether results can be filtered by CONNECTION LINK. Default is 'true'. |
||||
|
0:1 |
Whether results can be filtered by SERVICE JOURNEY INTERCHANGE. Default is 'false'. |
||||
|
|
0:1 |
Whether results can be filtered by Specific Needs. Default is 'true'. |
|||
11.28. The complex type complexType[siri:FacilityMonitoringServiceCapabilitiesStructure]/RequestPolicy#complexType (typedef-75.2)
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
| siri:FacilityMonitoringVolumeGroup |
|
0:1 |
Whether a maximum number of Facility Status to include can be specified. Default is 'false'. |
||
11.29. The complex type complexType[siri:FacilityMonitoringServiceCapabilitiesStructure]/AccessControl#complexType (typedef-75.3)
|
|
Type for Common Access control capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether access control of requests is supported. Default is 'false'. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
If access control is supported, whether access control by OPERATOR is supported. Default is 'true'. |
||||
|
0:1 |
If access control is supported, whether access control by LINE is supported. Default is 'true'. |
||||
11.30. The complex type complexType[siri:FacilityMonitoringServiceCapabilitiesStructure]/ResponseFeatures#complexType (typedef-75.4)
|
|
- |
||||
|
|
0:1 |
Whether result supports remedy information. Default is 'false' |
|||
|
|
0:1 |
Whether result supports facility location information. Default is 'true'. |
|||
11.31. The complex type element[siri:FacilityMonitoringPermissions]#complexType (typedef-75.5)
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
||||
12. SIRI-GM General Message Service.
12.1. Simple type definitions
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an Info Message. |
12.2. The toplevel element siri:GeneralMessage
|
|
An informative message. |
||||
12.3. The toplevel element siri:GeneralMessageCancellation
|
|
A revocation of a previous message. |
||||
12.4. The toplevel element siri:GeneralMessageCapabilitiesRequest
|
|
+siri:ServiceCapabilitiesRequestStructure (↔ siri:AbstractFunctionalServiceCapabilitiesRequest) |
Request for information about General Message Service Capabilities. Answered with a GeneralMessageCapabilitiesResponse. |
|||
12.5. The toplevel element siri:GeneralMessageCapabilitiesResponse
|
|
+siri:GeneralMessageCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Capabilities for General Message Service. Answers a GeneralMessageCapabilitiesResponse. |
|||
12.6. The toplevel element siri:GeneralMessageDelivery
|
|
+siri:GeneralMessageDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery for General Message Service. |
|||
12.7. The toplevel element siri:GeneralMessagePermissions
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permission or a single particpant or all participants. |
|||
12.8. The toplevel element siri:GeneralMessageRequest
|
|
+siri:GeneralMessageRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about general information messages affecting stops, vehicles or services. |
|||
12.9. The toplevel element siri:GeneralMessageServiceCapabilities
|
|
Capabilities of General Message Service. |
||||
12.10. The toplevel element siri:GeneralMessageSubscriptionRequest
|
|
+siri:GeneralMessageSubscriptionStructure (↔ siri:AbstractFunctionalServiceSubscriptionRequest) |
Request for a subscription to General Message Service. |
|||
12.11. The group siri:GeneralMessagePayloadGroup
|
|
General Message payload content. |
||||
| siri:GeneralMessagePayloadGroup |
0:* |
An informative message. |
|||
|
0:* |
A revocation of a previous message. |
||||
12.12. The group siri:GeneralMessageRequestPolicyGroup
|
|
Parameters that affect the request processing. |
||||
| siri:GeneralMessageRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
12.13. The group siri:GeneralMessageTopicGroup
|
|
Parameters that affect the request processing. |
||||
| siri:GeneralMessageTopicGroup |
|
0:* |
Referenceto an Info Channel for which messages are to be returned. |
||
12.14. The group siri:InfoMessageGroup
|
|
Extra information provided on general message notifcation that can be used to filter messages. |
||||
| siri:InfoMessageGroup |
|
1:1 |
Unique identifier of message. |
||
|
|
0:1 |
Optional version number of update to previosu message. |
|||
|
|
0:1 |
Info Channel to which message belongs. |
|||
12.15. The group siri:SiriGeneralMessageIndexGroup
|
|
Convenience artefact to pick out main elements of the General Message Service. |
||||
| siri:SiriGeneralMessageIndexGroup |
1:1 |
Request for information about general information messages affecting stops, vehicles or services. |
|||
|
1:1 |
Request for a subscription to General Message Service. |
||||
|
1:1 |
Delivery for General Message Service. |
||||
|
1:1 |
Request for information about General Message Service Capabilities. Answered with a GeneralMessageCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for General Message Service. Answers a GeneralMessageCapabilitiesResponse. |
||||
12.16. The complex type siri:GeneralMessageCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
|
0:1 |
Capabilities of General Message Service. |
||||
|
0:1 |
Participant's permissions to use the service. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
12.17. The complex type siri:GeneralMessageCapabilityAccessControlStructure
|
|
Type for Common Access control capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether access control of requests is supported. Default is 'false'. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
If access control is supported, whether access control by LINE is supported. Default is 'true'. |
|||
12.18. The complex type siri:GeneralMessageDeliveriesStructure
|
|
Type for Deliveries. Used in WSDL. |
||||
|
1:* |
Delivery for General Message Service. |
||||
12.19. The complex type siri:GeneralMessageDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:GeneralMessagePayloadGroup |
0:* |
An informative message. |
|||
|
0:* |
A revocation of a previous message. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
12.20. The complex type siri:GeneralMessageRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:GeneralMessageTopicGroup |
|
0:* |
Referenceto an Info Channel for which messages are to be returned. |
||
| siri:GeneralMessageRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
12.21. The complex type siri:GeneralMessageServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Filtering Capabilities. |
|||
|
|
0:1 |
Request Policiy capabilities. |
|||
|
|
0:1 |
Optional Access control capabilities. |
|||
12.22. The complex type siri:GeneralMessageServicePermissionStructure
|
|
Type for Abstract Permission. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. |
||
|
b |
|
-1:1 |
Permission applies to specified participant. |
||
|
|
0:1 |
Permissions for general capabilities. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
The monitoring points that the participant may access. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
12.23. The complex type siri:GeneralMessageSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for information about general information messages affecting stops, vehicles or services. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
12.24. The complex type siri:InfoChannelPermissionStructure
|
|
Type for Abstract Permission Topic. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether the participant may access this topic. Default is 'true'. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to an Info Channel to which permission applies. |
|||
12.25. The complex type siri:InfoMessageCancellationStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Reference to an Activity Element of a delivery. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Identifier of message. Unique within service and Producer participant. |
|||
|
|
0:1 |
Info Channel to which message belongs. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
12.26. The complex type siri:InfoMessageRefStructure
|
|
Type for identifier of an Info Message. |
||||
12.27. The complex type siri:InfoMessageStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Identifier of item. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a format of the Content. If absent, free text. |
|||
| siri:InfoMessageGroup |
|
1:1 |
Unique identifier of message. |
||
|
|
0:1 |
Optional version number of update to previosu message. |
|||
|
|
0:1 |
Info Channel to which message belongs. |
|||
|
|
0:1 |
Time until when message is valid. If absent unopen ended. |
|||
|
0:1 |
Reference to a SITUATION associated with the element. |
||||
|
|
1:1 |
Message Content. Format is specified by Format Ref. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
12.28. The complex type complexType[siri:AbstractPermissionStructure]/GeneralCapabilities#complexType (typedef-45.1)
|
|
- |
||||
|
|
1:1 |
Participant may make direct requests for data. Default is 'true'. |
|||
|
|
1:1 |
Participant may create subscriptions. Default True. |
|||
12.29. The complex type complexType[siri:GeneralMessageServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-82.1)
|
|
- |
||||
|
|
1:1 |
Default preview interval. Default is 60 minutes. |
|||
|
|
0:1 |
Whether results can be filtered by InfoChannel, departures. Default is 'true'. |
|||
12.30. The complex type element[siri:GeneralMessagePermissions]#complexType (typedef-82.2)
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permission or a single particpant or all participants. |
|||
12.31. The complex type complexType[siri:GeneralMessageServicePermissionStructure]/InfoChannelPermissions#complexType (typedef-82.3)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this InfoChannel. |
||
13. SIRI-Model Dated Vehicle Joruney.
13.1. Simple type definitions
|
|
xs:boolean: (empty restriction) |
Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. (since SIRI 2.1) |
|||||||
|
|
Nature of Interchange management. |
||||||||
|
|||||||||
13.2. The toplevel element siri:AimedArrivalTimeOfFeeder
|
|
|
Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) |
|||
13.3. The toplevel element siri:AimedDepartureTimeOfDistributor
|
|
|
Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) |
|||
13.4. The toplevel element siri:DatedCall
|
|
Complete sequence of stops along the route path, in calling order. |
||||
13.5. The toplevel element siri:DatedVehicleJourney
|
|
A planned VEHICLE JOURNEY taking place on a particular date. |
||||
13.6. The toplevel element siri:DistributorDepartureStopRef
|
|
SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0) |
||||
13.7. The toplevel element siri:DistributorRef
|
|
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
13.8. The toplevel element siri:DistributorStopOrder
|
|
|
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
|||
13.9. The toplevel element siri:DistributorVisitNumber
|
|
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. |
||||
13.10. The toplevel element siri:ExtraInterchange
|
|
|
Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. (since SIRI 2.1) |
|||
13.11. The toplevel element siri:FeederArrivalStopRef
|
|
SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0) |
||||
13.12. The toplevel element siri:FeederRef
|
|
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
13.13. The toplevel element siri:FeederStopOrder
|
|
|
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
|||
13.14. The toplevel element siri:FeederVisitNumber
|
|
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. |
||||
13.15. The toplevel element siri:InterchangeCode
|
|
Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0) |
||||
13.16. The toplevel element siri:ReasonForRemoval
|
|
The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. (since SIRI 2.1) |
||||
13.17. The group siri:ConnectionDurationGroup
|
|
Times for making SERVICE JOURNEY INTERCHANGE. |
||||
| siri:ConnectionDurationGroup |
|
0:1 |
Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor. |
||
|
|
0:1 |
Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration. |
|||
|
|
0:1 |
Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration and a standard weighting. |
|||
|
|
0:1 |
Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE. If absent, use DefaultDuration and a standard impaired travel speed. |
|||
13.18. The group siri:DatedServiceInfoGroup
|
|
General info elements that apply to all journeys of timetable version unless overriden. |
||||
| siri:DatedServiceInfoGroup |
|
0:* |
Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (since SIRI 2.0) |
||
|
|
0:* |
Description of the destination stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Additional Text associated with LINE. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Whether journey is first or last jouurney of day. (since SIRI 2.0) |
|||
13.19. The group siri:InterchangePropertyGroup
|
|
Properties of SERVICE JOURNEY INTERCHANGE. |
||||
| siri:InterchangePropertyGroup |
|
0:1 |
Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. |
||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. |
|||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'. |
|||
13.20. The group siri:InterchangeTimesGroup
|
|
Time Elements for SERVICE JOURNEY INTERCHANGE. |
||||
| siri:InterchangeWaitTimeGroup |
|
0:1 |
Standard wait time for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 |
|||
|
|
0:1 |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) |
|||
| siri:InterchangeTransferDurationGroup |
|
0:1 |
Standard transfer duration for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Minimum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
|
0:1 |
Maximum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
13.21. The group siri:InterchangeTransferDurationGroup
|
|
Elements for INTERCHANGE TRANSFER duration. |
||||
| siri:InterchangeTransferDurationGroup |
|
0:1 |
Standard transfer duration for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Minimum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
|
0:1 |
Maximum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
13.22. The group siri:InterchangeWaitTimeGroup
|
|
Elements for INTERCHANGE WAIT TIME. |
||||
| siri:InterchangeWaitTimeGroup |
|
0:1 |
Standard wait time for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 |
|||
|
|
0:1 |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) |
|||
13.23. The group siri:TimetableAlterationGroup
|
|
If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference. |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
| siri:TimetableAlterationGroup |
a |
|
-1:1 |
Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 |
|
|
b |
-1:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Whether this journey is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition. |
||
|
b |
|
-0:1 |
Whether this journey is a cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. |
||
13.24. The group siri:TimetableRealtimeInfoGroup
|
|
Additional descriptive properties of service. |
||||
| siri:TimetableRealtimeInfoGroup |
|
0:1 |
Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable. |
||
|
|
0:1 |
Whether VEHICLE JOURNEYs of LINE are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable. |
|||
13.25. The complex type siri:AbstractServiceJourneyInterchangeStructure
|
|
A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0) |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0) |
|||
|
b |
-0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
|||
|
0:1 |
Reference to a CONNECTION link |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. (since SIRI 2.1) |
|||
|
b |
|
-0:1 |
|||
|
0:1 |
The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. (since SIRI 2.1) |
||||
|
0:1 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
0:1 |
SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0) |
||||
|
0:1 |
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) |
||||
|
0:1 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
0:1 |
SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0) |
||||
|
0:1 |
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) |
||||
| siri:InterchangePropertyGroup |
|
0:1 |
Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. |
||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. |
|||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'. |
|||
| siri:InterchangeWaitTimeGroup |
|
0:1 |
Standard wait time for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 |
|||
|
|
0:1 |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) |
|||
| siri:InterchangeTransferDurationGroup |
|
0:1 |
Standard transfer duration for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Minimum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
|
0:1 |
Maximum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
13.26. The complex type siri:ContextualisedConnectionLinkStructure
|
|
Connection between two stops within a connection area. Used within the context of one or other end. |
||||
|
|
0:1 |
Identifier of CONNECTION LINk. |
|||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:1 |
Name of SCHEDULED STOP POINT. |
||||
| siri:ConnectionDurationGroup |
|
0:1 |
Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor. |
||
|
|
0:1 |
Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration. |
|||
|
|
0:1 |
Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration and a standard weighting. |
|||
|
|
0:1 |
Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE. If absent, use DefaultDuration and a standard impaired travel speed. |
|||
13.27. The complex type siri:DatedCallStructure
|
|
Type for Planned VEHICLE JOURNEY Stop (Production Timetable Service). |
||||
| siri:StopPointInSequenceGroup |
1:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Whether this DATED CALL is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition. |
||
|
b |
|
-0:1 |
Whether this DATED CALL is a cancellation of a previously announced call (or planned according to the long-term timetable). Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. |
||
| siri:CallPropertyGroup |
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
|||
|
|
0:1 |
Whether this is a Hail and Ride Stop. Default is 'false'. |
|||
|
|
0:1 |
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. |
|||
|
|
0:* |
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0) |
|||
|
|
0:* |
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. |
|||
|
|
0:* |
Text annotation that applies to this call. |
|||
| siri:AimedVehicleArrivalGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:AimedVehicleDepartureGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:AimedCallGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
For frequency based services, target interval between vehicles at stop. |
||||
|
|
0:* |
Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes) |
|||
|
|
0:* |
Information on any planned feeder connections. SIRI 2.0 |
|||
|
|
0:* |
Information on any planned distributor connections. SIRI 2.0 |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
13.28. The complex type siri:DatedVehicleJourneyStructure
|
|
Type for Planned VEHICLE JOURNEY (Production Timetable Service). |
||||
|
|
0:1 |
Identifier for a VEHICLE JOURNEY. |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
| siri:TimetableAlterationGroup |
a |
|
-1:1 |
Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 |
|
|
b |
-1:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Whether this journey is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition. |
||
|
b |
|
-0:1 |
Whether this journey is a cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. |
||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:JourneyInfoGroup |
|
0:* |
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) |
||
|
0:* |
Additional descriptive text associated with journey. Inherited property. |
||||
|
|
0:1 |
Contact details for use by members of public. (since SIRI 2.0) |
|||
|
|
0:1 |
Contact details for use by operational staff. (since SIRI 2.0) |
|||
| siri:DatedServiceInfoGroup |
|
0:* |
Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (since SIRI 2.0) |
||
|
|
0:* |
Description of the destination stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Additional Text associated with LINE. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Whether journey is first or last jouurney of day. (since SIRI 2.0) |
|||
| siri:TimetableRealtimeInfoGroup |
|
0:1 |
Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable. |
||
|
|
0:1 |
Whether VEHICLE JOURNEYs of LINE are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable. |
|||
| siri:DatedTrainOperationalInfoGroup |
|
0:* |
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. |
||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
| siri:DatedOperationalInfoGroup |
0:1 |
Reference to a VEHICLE. |
|||
| siri:DatedTrainOperationalInfoGroup |
|
0:1 |
TRAIN NUMBERs for journey. (since SIRI 2.0) |
||
|
|
0:1 |
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. |
|||
| siri:JourneyFormationGroup |
|
0:1 |
|||
|
|
0:1 |
||||
|
|
0:1 |
||||
|
|
1:1 |
Complete sequence of stops along the route path, in calling order. |
|||
|
|
0:1 |
Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
13.29. The complex type siri:FromServiceJourneyInterchangeStructure
|
|
A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0) |
||||
|
Base type content is restricted, resulting in the following own content: |
|||||
|
0:1 |
Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0) |
||||
|
0:1 |
Reference to a CONNECTION link |
||||
|
1:1 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
1:1 |
SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0) |
||||
|
0:1 |
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) |
||||
|
0:0 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
0:0 |
SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0) |
||||
|
0:0 |
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) |
||||
| siri:InterchangePropertyGroup |
|
0:1 |
Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. |
||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. |
|||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'. |
|||
| siri:InterchangeWaitTimeGroup |
|
0:1 |
Standard wait time for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 |
|||
|
|
0:1 |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) |
|||
| siri:InterchangeTransferDurationGroup |
|
0:1 |
Standard transfer duration for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Minimum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
|
0:1 |
Maximum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
13.30. The complex type siri:RemovedDatedVehicleJourneyStructure
|
|
Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. (since SIRI 2.1) |
||||
|
|
1:1 |
A reference to the DATED VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer. |
|||
|
|
0:1 |
Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. |
|||
|
|
0:1 |
TRAIN NUMBERs for journey. |
|||
|
1:1 |
The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. (since SIRI 2.1) |
||||
13.31. The complex type siri:RemovedServiceJourneyInterchangeStructure
|
|
A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0) |
||||
|
Base type content is restricted, resulting in the following own content: |
|||||
|
1:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
|
0:1 |
Reference to a CONNECTION link |
||||
|
1:1 |
The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. (since SIRI 2.1) |
||||
|
1:1 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
1:1 |
SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0) |
||||
|
0:1 |
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) |
||||
|
1:1 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
1:1 |
SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0) |
||||
|
0:1 |
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
13.32. The complex type siri:ServiceJourneyInterchangeStructure
|
|
A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0) |
||||
|
Base type content is restricted, resulting in the following own content: |
|||||
|
0:1 |
Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0) |
||||
|
0:1 |
Reference to a CONNECTION link |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. (since SIRI 2.1) |
|||
|
b |
|
-0:1 |
|||
|
1:1 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
1:1 |
SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0) |
||||
|
0:1 |
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) |
||||
|
1:1 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
1:1 |
SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0) |
||||
|
0:1 |
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) |
||||
| siri:InterchangePropertyGroup |
|
0:1 |
Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. |
||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. |
|||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'. |
|||
| siri:InterchangeWaitTimeGroup |
|
0:1 |
Standard wait time for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 |
|||
|
|
0:1 |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) |
|||
| siri:InterchangeTransferDurationGroup |
|
0:1 |
Standard transfer duration for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Minimum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
|
0:1 |
Maximum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
13.33. The complex type siri:TargetedInterchangeStructure
|
|
Planned Connection between two VEHICLE JOURNEYs. |
||||
|
0:1 |
Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0) |
||||
|
|
1:1 |
Reference to a (dated) distributor VEHICLE JOURNEY. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. |
||
|
b |
|
-1:1 |
Link to Interchange stop from which the distributor journey departs. If omitted: the distributor journey stop is the same as the feeder journey stop, i.e. that of theh dated call. |
||
|
0:1 |
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. |
||||
|
|
0:1 |
For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation. |
|||
| siri:InterchangePropertyGroup |
|
0:1 |
Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. |
||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. |
|||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'. |
|||
| siri:InterchangeWaitTimeGroup |
|
0:1 |
Standard wait time for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 |
|||
|
|
0:1 |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) |
|||
| siri:InterchangeTransferDurationGroup |
|
0:1 |
Standard transfer duration for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Minimum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
|
0:1 |
Maximum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
13.34. The complex type siri:ToServiceJourneyInterchangeStructure
|
|
A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0) |
||||
|
Base type content is restricted, resulting in the following own content: |
|||||
|
0:1 |
Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0) |
||||
|
0:1 |
Reference to a CONNECTION link |
||||
|
0:0 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
0:0 |
SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0) |
||||
|
0:0 |
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) |
||||
|
1:1 |
Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||||
|
1:1 |
SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0) |
||||
|
0:1 |
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. |
||||
|
0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||||
|
0:1 |
Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) |
||||
| siri:InterchangePropertyGroup |
|
0:1 |
Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. |
||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. |
|||
|
|
0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'. |
|||
| siri:InterchangeWaitTimeGroup |
|
0:1 |
Standard wait time for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 |
|||
|
|
0:1 |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) |
|||
| siri:InterchangeTransferDurationGroup |
|
0:1 |
Standard transfer duration for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Minimum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
|
0:1 |
Maximum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
13.35. The complex type group[siri:JourneyFormationGroup]/TrainElements#complexType (typedef-25.2)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-1:1 |
An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1) |
|||
13.36. The complex type group[siri:JourneyFormationGroup]/Trains#complexType (typedef-25.3)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1) |
|||
13.37. The complex type group[siri:JourneyFormationGroup]/CompoundTrains#complexType (typedef-25.4)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1) TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. |
|||
13.38. The complex type group[siri:DatedTrainOperationalInfoGroup]/TrainNumbers#complexType (typedef-39.6)
|
|
- |
||||
|
|
1:* |
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 |
|||
13.39. The complex type group[siri:DatedTrainOperationalInfoGroup]/JourneyParts#complexType (typedef-39.7)
|
|
- |
||||
|
|
1:* |
Information about Parts of JOURNEY (since SIRI 2.0) |
|||
13.40. The complex type complexType[siri:DatedVehicleJourneyStructure]/DatedCalls#complexType (typedef-40.1)
|
|
- |
||||
|
2:* |
Complete sequence of stops along the route path, in calling order. |
||||
13.41. The complex type complexType[siri:RemovedDatedVehicleJourneyStructure]/TrainNumbers#complexType (typedef-40.2)
|
|
- |
||||
|
|
1:* |
TRAIN NUMBER assigned to VEHICLE JOURNEY. |
|||
14. SIRI-ET Estimated Timetable Service.
14.1. Simple type definitions
|
|
xs:boolean: (empty restriction) |
This CALL is a cancellation of a previously announced call. |
14.2. The toplevel element siri:EstimatedCall
|
|
Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. If IsCompleteStopSequence is false, may be just those stops that are altered. |
||||
14.3. The toplevel element siri:EstimatedServiceJourneyInterchange
|
|
A real-time SERVICE JOURNEY INTERCHANGE that may be made between the stops of two monitored journeys. It includes the current real-time predicted transfer and wait times. (since SIRI 2.0) |
||||
14.4. The toplevel element siri:EstimatedVehicleJourney
|
|
A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. |
||||
14.5. The toplevel element siri:ExtraCall
|
|
|
This CALL is an addition to the respective journey in the production timetable or to the previously sent prediction. If omitted: CALL is planned. |
|||
14.6. The toplevel element siri:RecordedCall
|
|
Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0) |
||||
14.7. The group siri:CallRealTimeInfoGroup
|
|
Information relating to real-time properties of call. |
||||
| siri:CallRealTimeInfoGroup |
0:1 |
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. |
|||
|
0:1 |
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) |
||||
|
0:1 |
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. |
||||
14.8. The group siri:EstimatedTimetableAlterationGroup
|
|
If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference. |
||||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ab) |
|||||
| siri:EstimatedTimetableAlterationGroup |
aa |
|
-1:1 |
Identifer of a VEHICLE JOURNEY within data Horizon of a service. |
|
|
ab |
|
-1:1 |
Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable. DEPRECATED from SIRI 2.0 |
||
|
a |
|
-0:1 |
Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops. |
||
|
b |
|
-1:1 |
If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. DEPRECATED from SIRI 2.0 |
||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Whether this VEHICLE JOURNEY is an addition to the planning data already sent. Default is 'false': i.e. not an additional journey. |
||
|
b |
|
-0:1 |
Whether this VEHICLE JOURNEY is a deletion of a previous scheduled journey. Default is 'false': this is not a VEHICLE JOURNEY that has been cancelled. An Extra Journey may be deleted. |
||
14.9. The group siri:RecordedCallGroup
|
|
Information relating to recorded real-time properties of call. |
||||
| siri:CallPropertyGroup |
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
|||
|
|
0:1 |
Whether this is a Hail and Ride Stop. Default is 'false'. |
|||
|
|
0:1 |
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. |
|||
|
|
0:* |
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0) |
|||
|
|
0:* |
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. |
|||
| siri:CallNoteGroup |
|
0:* |
Text annotation that applies to this CALL. |
||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
| siri:RecordedCallGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
0:1 |
Estimated time of arriival of VEHICLE at stop . |
||||
|
0:1 |
Observed time of arrival of VEHICLE at stop. |
||||
| siri:MonitoredStopArrivalStatusGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:1 |
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:RecordedCallGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
||||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Observed time of departure of VEHICLE from stop. |
||||
|
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
||||
|
0:1 |
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
||||
|
0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:HeadwayIntervalGroup |
0:1 |
For frequency based services, target interval between vehicles at stop. |
|||
|
0:1 |
For frequency based services, expected interval between vehicles at stop. |
||||
| siri:RecordedCallGroup |
0:1 |
For frequency based services, observed interval between vehicles at stop. |
|||
14.10. The complex type siri:EstimatedCallStructure
|
|
Type for real-time info about a VEHICLE JOURNEY Stop. |
||||
| siri:StopPointInSequenceGroup |
1:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
-0:1 |
This CALL is an addition to the respective journey in the production timetable or to the previously sent prediction. If omitted: CALL is planned. |
|||
|
b |
|
-0:1 |
|||
| siri:CallRealTimeInfoGroup |
0:1 |
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. |
|||
|
0:1 |
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) |
||||
|
0:1 |
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. |
||||
| siri:CallPropertyGroup |
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
|||
|
|
0:1 |
Whether this is a Hail and Ride Stop. Default is 'false'. |
|||
|
|
0:1 |
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. |
|||
|
|
0:* |
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0) |
|||
|
|
0:* |
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. |
|||
| siri:CallNoteGroup |
|
0:* |
Text annotation that applies to this CALL. |
||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
| siri:OnwardVehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
a |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
|
a |
|
-0:1 |
Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.1) |
||
|
a |
|
-0:1 |
Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) |
||
|
b |
|
-1:1 |
If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' (ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true" (iii) drop/omit ExpectedArrivalTime (iv) set ArrivalStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) |
||
| siri:MonitoredStopArrivalStatusGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:1 |
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:OnwardVehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
a |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
|
a |
|
-0:1 |
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time (since SIRI 2.0). |
||
|
a |
|
-0:1 |
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. (since SIRI 2.0) |
||
|
a |
|
-0:1 |
Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) |
||
|
b |
|
-1:1 |
If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' (ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true" (iii) drop/omit ExpectedDepartureTime (iv) set DepartureStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) |
||
| siri:PassengerDepartureTimesGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
||||
| siri:MonitoredStopDepartureStatusGroup |
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
|||
|
0:1 |
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
The element contains one of the following element sequences (a-b) |
|||||
|
a |
-0:* |
Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1) |
|||
|
a |
-0:* |
Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:HeadwayIntervalGroup |
0:1 |
For frequency based services, target interval between vehicles at stop. |
|||
|
0:1 |
For frequency based services, expected interval between vehicles at stop. |
||||
| siri:StopProximityGroup |
|
0:1 |
Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. (since SIRI 2.0). |
||
|
|
0:1 |
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. (since SIRI 2.0). |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
14.11. The complex type siri:EstimatedServiceJourneyInterchangeStructure
|
|
Type for Estimated SERVICE JOURNEY INTERCHANGE. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
|
a |
-1:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
|||
|
b |
|
-0:1 |
Identifier of ESTIMATED SERVICE JOURNEY INTERCHANGE in case it is an addition to the plan. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. (since SIRI 2.0) |
||
|
b |
|
-1:1 |
Reference to a connecting feeder VEHICLE JOURNEY. (since SIRI 2.0) |
||
|
b |
|
-0:1 |
SCHEDULED STOP POINT at which feeder journey arrives. Assuming, for example, that the feeder is redirected to another QUAY by a dispositive measure in order to shorten the transfer time, how do we communicate this change in the interchange? If the STOP POINTs are modelled QUAY accurate, FeederArrivalStopRef should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). (since SIRI 2.1) |
||
|
b |
|
-0:1 |
Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. |
||
|
b |
|
-0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) |
||
|
b |
|
-1:1 |
Reference to a connecting distributor VEHICLE JOURNEY. (since SIRI 2.0) |
||
|
b |
|
-0:1 |
SCHEDULED STOP POINT at which distributor journey departs. Assuming that the distributor is directed to another QUAY (and that STOP POINTs are modelled QUAY accurate), DistributorDepartureStopRef should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). (since SIRI 2.1) |
||
|
b |
|
-0:1 |
Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. |
||
|
b |
|
-0:1 |
For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) |
||
| siri:InterchangePropertyGroup |
b |
|
-0:1 |
Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection. |
|
|
b |
|
-0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed. |
||
|
b |
|
-0:1 |
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'. |
||
|
|
0:1 |
Whether this interchange is planned, updated, additional or cancelled. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Distributor will not wait, i.e., connection is not guaranteed or broken. SIRI 2.0 |
||
|
b |
|
-1:1 |
Details about how (long) the distributor services may be held in order to guarantee the connection. (since SIRI 2.0) |
||
|
|
0:1 |
Time at which feeder VEHICLE is expected to arrive. (since SIRI 2.1) |
|||
|
|
0:1 |
Time at which distributor VEHICLE is expected to depart. (since SIRI 2.0) |
|||
|
|
0:1 |
Whether connection monitoring is active or not for this connection. (since SIRI 2.0) |
|||
| siri:InterchangeWaitTimeGroup |
|
0:1 |
Standard wait time for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0 |
|||
|
|
0:1 |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) |
|||
| siri:InterchangeTransferDurationGroup |
|
0:1 |
Standard transfer duration for INTERCHANGE. SIRI v2,0 |
||
|
|
0:1 |
Minimum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
|
0:1 |
Maximum transfer duration for INTERCHANGE. SIRI v2,0 |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
14.12. The complex type siri:EstimatedVehicleJourneyStructure
|
|
Type for Real-time info about a VEHICLE JOURNEY. |
||||
|
|
0:1 |
Time at which data of individual journey was recorded if differet from that of frame. ((since SIRI 2.0).) |
|||
| siri:LineIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a LINE DIRECTION DIRECTION, typically outward or return. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ab) |
|||||
| siri:EstimatedTimetableAlterationGroup |
aa |
|
-1:1 |
Identifer of a VEHICLE JOURNEY within data Horizon of a service. |
|
|
ab |
|
-1:1 |
Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable. DEPRECATED from SIRI 2.0 |
||
|
a |
|
-0:1 |
Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops. |
||
|
b |
|
-1:1 |
If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. DEPRECATED from SIRI 2.0 |
||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Whether this VEHICLE JOURNEY is an addition to the planning data already sent. Default is 'false': i.e. not an additional journey. |
||
|
b |
|
-0:1 |
Whether this VEHICLE JOURNEY is a deletion of a previous scheduled journey. Default is 'false': this is not a VEHICLE JOURNEY that has been cancelled. An Extra Journey may be deleted. |
||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:JourneyInfoGroup |
|
0:* |
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) |
||
|
0:* |
Additional descriptive text associated with journey. Inherited property. |
||||
|
|
0:1 |
Contact details for use by members of public. (since SIRI 2.0) |
|||
|
|
0:1 |
Contact details for use by operational staff. (since SIRI 2.0) |
|||
| siri:JourneyEndTimesGroup |
|
0:1 |
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. |
||
|
|
0:1 |
Timetabled departure time from Origin. |
|||
|
|
0:1 |
Timetabled arrival time at Destination. |
|||
|
0:1 |
Whether journey is first or last journey of day. (since SIRI 2.0) |
||||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
| siri:JourneyProgressGroup |
|
0:1 |
Whether there is real-time information available for journey. Default is 'true'. It is recommended to specify a MonitoringError if Monitored is set to 'false'. |
||
|
|
0:1 |
If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. MonitoringError must not be used if Monitored is omitted or set to 'true'. |
|||
| siri:ProgressDataQualityGroup |
|
0:1 |
Whether the VEHICLE iis in traffic congestion. If not, present, not known. |
||
|
|
0:1 |
Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'. |
|||
|
0:1 |
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. |
||||
|
0:1 |
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) |
||||
|
|
0:1 |
System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. |
|||
|
|
0:1 |
Confidence QUALITY LEVEL of data. Default is 'reliable'. |
|||
| siri:ProgressDataGroup |
|
0:1 |
Current geospatial location of VEHICLE. Measured to front of vehicle. |
||
|
|
0:1 |
Time at which location was recorded. If not present assume that the recorded at time on the containing delivery. |
|||
|
|
0:1 |
Bearing in compass degrees in which VEHICLE is heading. |
|||
|
|
0:1 |
Rate of progress of VEHICLE. Default is 'normal' |
|||
|
|
0:1 |
Velocity of VEHICLE. EIther actual speed or average speed may be used. (since SIRI 2.0) |
|||
|
|
0:1 |
Whether the engine of the vehicle is on. Default is 'true' (since SIRI 2.0) |
|||
|
0:1 |
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. |
||||
|
|
0:1 |
Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. |
|||
|
|
0:* |
An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0) |
|||
|
|
0:1 |
An classification of the progress state of running of this VEHICLE JOURNEY. (since SIRI 2.0) |
|||
| siri:TrainOperationalInfoGroup |
|
0:* |
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. |
||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
| siri:OperationalInfoGroup |
0:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a VEHICLE. |
||||
|
|
0:* |
Refercence to other VEHICLE Journeys ((since SIRI 2.0)) |
|||
|
|
0:1 |
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. (since SIRI 2.0) |
|||
|
|
0:1 |
The name oo the Driver or Crew (since SIRI 2.0) |
|||
| siri:TrainOperationalInfoGroup |
|
0:1 |
TRAIN NUMBERs for journey. (since SIRI 2.0) |
||
|
|
0:1 |
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. |
|||
| siri:JourneyFormationGroup |
|
0:1 |
|||
|
|
0:1 |
||||
|
|
0:1 |
||||
|
|
0:1 |
Complete sequence of stops already visited along the route path, in calling order. Only used if observed stop data is being recorded. (SIRI 2.0) |
|||
|
|
0:1 |
Complete sequence of stops along the route path, in calling order. Normally this is only the onwards stops from the vehicle's current position. |
|||
|
|
0:1 |
Whether the above call sequence is complete, i.e. represents every CALL of the SERVICE PATTERN and so can be used to replace a previous call sequence. Default is 'false'. |
|||
|
|
0:1 |
Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
14.13. The complex type siri:RecordedCallStructure
|
|
Type for recroded Real-time info about a VEHICLE JOURNEY Stop. |
||||
| siri:StopPointInSequenceGroup |
1:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
-0:1 |
This CALL is an addition to the respective journey in the production timetable or to the previously sent prediction. If omitted: CALL is planned. |
|||
|
b |
|
-0:1 |
|||
| siri:CallRealTimeInfoGroup |
0:1 |
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. |
|||
|
0:1 |
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) |
||||
|
0:1 |
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. |
||||
| siri:CallPropertyGroup |
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
|||
|
|
0:1 |
Whether this is a Hail and Ride Stop. Default is 'false'. |
|||
|
|
0:1 |
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. |
|||
|
|
0:* |
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0) |
|||
|
|
0:* |
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. |
|||
| siri:CallNoteGroup |
|
0:* |
Text annotation that applies to this CALL. |
||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
| siri:RecordedCallGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
0:1 |
Estimated time of arriival of VEHICLE at stop . |
||||
|
0:1 |
Observed time of arrival of VEHICLE at stop. |
||||
| siri:MonitoredStopArrivalStatusGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:1 |
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:RecordedCallGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
||||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Observed time of departure of VEHICLE from stop. |
||||
|
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
||||
|
0:1 |
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
||||
|
0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:HeadwayIntervalGroup |
0:1 |
For frequency based services, target interval between vehicles at stop. |
|||
|
0:1 |
For frequency based services, expected interval between vehicles at stop. |
||||
| siri:RecordedCallGroup |
0:1 |
For frequency based services, observed interval between vehicles at stop. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
14.14. The complex type siri:WillWaitStructure
|
|
Type for Will Wait details |
||||
|
|
1:1 |
Time up until which the distributor will wait. (since SIRI 2.0) |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
DEPRECATED since SIRI 2.1 |
||
|
b |
|
-0:1 |
Whether an acknowledgement has been received that the driver will wait. (since SIRI 2.1) |
||
14.15. The complex type complexType[siri:EstimatedVehicleJourneyStructure]/RecordedCalls#complexType (typedef-19.1)
|
|
- |
||||
|
1:* |
Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0) |
||||
14.16. The complex type complexType[siri:EstimatedVehicleJourneyStructure]/EstimatedCalls#complexType (typedef-19.2)
|
|
- |
||||
|
1:* |
Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. If IsCompleteStopSequence is false, may be just those stops that are altered. |
||||
14.17. The complex type group[siri:JourneyFormationGroup]/TrainElements#complexType (typedef-25.2)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-1:1 |
An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1) |
|||
14.18. The complex type group[siri:JourneyFormationGroup]/Trains#complexType (typedef-25.3)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1) |
|||
14.19. The complex type group[siri:JourneyFormationGroup]/CompoundTrains#complexType (typedef-25.4)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1) TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. |
|||
14.20. The complex type group[siri:TrainOperationalInfoGroup]/TrainNumbers#complexType (typedef-39.4)
|
|
- |
||||
|
|
1:* |
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 |
|||
14.21. The complex type group[siri:TrainOperationalInfoGroup]/JourneyParts#complexType (typedef-39.5)
|
|
- |
||||
|
|
1:* |
Information about Parts of JOURNEY (since SIRI 2.0) |
|||
15. SIRi Facilities
15.1. Simple type definitions
|
|
Values for Access Facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Accomodation Facility: TPEG pti_table 23. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Assistance Facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for FareClass Facility: TPEG pti_table 23. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Hire Facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Luggage Facility: TPEG pti_table 23. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Mobility Facility: TPEG pti_table 23. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Nuisance Facility: TPEG pti_table 23. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Access Facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for PassengerComms Facility: TPEG pti_table 23. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Passenger Information Facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Refreshment Facility: TPEG pti_table 23. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Reserved Space Facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Retail Facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Sanitary Facility: TPEG pti_table 23. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Values for Ticketing Facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
15.2. The toplevel element siri:AccessFacility
|
|
Classification of Access Facility. |
||||
15.3. The toplevel element siri:AccommodationFacility
|
|
Classification of Accomodation Facility type - Tpeg pti23. |
||||
15.4. The toplevel element siri:AssistanceFacility
|
|
Classification of Assistance Facility. |
||||
15.5. The toplevel element siri:FareClassFacility
|
|
Classification of FareClass Facility type - Tpeg pti23. |
||||
15.6. The toplevel element siri:HireFacility
|
|
Classification of Hire Facility. |
||||
15.7. The toplevel element siri:LuggageFacility
|
|
Classification of Luggage Facility type - Tpeg pti23. |
||||
15.8. The toplevel element siri:MobilityFacility
|
|
Classification of Mobility Facility type - Tpeg pti23. |
||||
15.9. The toplevel element siri:NuisanceFacility
|
|
Classification of Nuisance Facility type - Tpeg pti23. |
||||
15.10. The toplevel element siri:ParkingFacility
|
|
Classification of Access Facility. |
||||
15.11. The toplevel element siri:PassengerCommsFacility
|
|
Classification of PassengerComms Facility type - Tpeg pti23. |
||||
15.12. The toplevel element siri:PassengerInformationFacility
|
|
Classification of PassengerInfo Facility type - Tpeg pti23. |
||||
15.13. The toplevel element siri:RefreshmentFacility
|
|
Classification of Refreshment Facility type - Tpeg pti23. |
||||
15.14. The toplevel element siri:ReservedSpaceFacility
|
|
Classification of Reserved Space Facility. |
||||
15.15. The toplevel element siri:RetailFacility
|
|
Classification of Retail Facility. |
||||
15.16. The toplevel element siri:SanitaryFacility
|
|
Classification of Sanitary Facility type - Tpeg pti23. |
||||
15.17. The toplevel element siri:TicketingFacility
|
|
Classification of Ticketing Facility type - Tpeg pti23. |
||||
15.18. The group siri:AllFacilitiesGroup
|
|
Facilities that apply to stops. |
||||
| siri:CommonFacilityGroup |
0:* |
Classification of FareClass Facility type - Tpeg pti23. |
|||
|
0:* |
Classification of Ticketing Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Nuisance Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Mobility Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of PassengerInfo Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of PassengerComms Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Refreshment Facility type - Tpeg pti23. |
||||
|
|
0:* |
Classification of Access Facility. |
|||
|
0:* |
Classification of Sanitary Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Luggage Facility type - Tpeg pti23. |
||||
| siri:ServiceFacilityGroup |
0:* |
Classification of Accomodation Facility type - Tpeg pti23. |
|||
| siri:AllFacilitiesGroup |
0:* |
Classification of Assistance Facility. |
|||
|
0:* |
Classification of Hire Facility. |
||||
15.19. The group siri:CommonFacilityGroup
|
|
tructured Classification Elements. Corresponds to TPEG 18 Event Reason. |
||||
| siri:CommonFacilityGroup |
0:* |
Classification of FareClass Facility type - Tpeg pti23. |
|||
|
0:* |
Classification of Ticketing Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Nuisance Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Mobility Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of PassengerInfo Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of PassengerComms Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Refreshment Facility type - Tpeg pti23. |
||||
|
|
0:* |
Classification of Access Facility. |
|||
|
0:* |
Classification of Sanitary Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Luggage Facility type - Tpeg pti23. |
||||
15.20. The group siri:ServiceFacilityGroup
|
|
Facilities that apply to services. |
||||
| siri:CommonFacilityGroup |
0:* |
Classification of FareClass Facility type - Tpeg pti23. |
|||
|
0:* |
Classification of Ticketing Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Nuisance Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Mobility Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of PassengerInfo Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of PassengerComms Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Refreshment Facility type - Tpeg pti23. |
||||
|
|
0:* |
Classification of Access Facility. |
|||
|
0:* |
Classification of Sanitary Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Luggage Facility type - Tpeg pti23. |
||||
| siri:ServiceFacilityGroup |
0:* |
Classification of Accomodation Facility type - Tpeg pti23. |
|||
15.21. The group siri:StopFacilityGroup
|
|
Facilities that apply to stops. |
||||
| siri:CommonFacilityGroup |
0:* |
Classification of FareClass Facility type - Tpeg pti23. |
|||
|
0:* |
Classification of Ticketing Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Nuisance Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Mobility Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of PassengerInfo Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of PassengerComms Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Refreshment Facility type - Tpeg pti23. |
||||
|
|
0:* |
Classification of Access Facility. |
|||
|
0:* |
Classification of Sanitary Facility type - Tpeg pti23. |
||||
|
0:* |
Classification of Luggage Facility type - Tpeg pti23. |
||||
| siri:StopFacilityGroup |
0:* |
Classification of Assistance Facility. |
|||
|
0:* |
Classification of Hire Facility. |
||||
15.22. The complex type siri:AllFacilitiesFeatureStructure
|
|
Description of the features of any of the available facilities. |
||||
|
The element contains one of the following elements (a-p) |
|||||
|
a |
-1:1 |
Classification of Access Facility. |
|||
|
b |
-1:1 |
Classification of Accomodation Facility type - Tpeg pti23. |
|||
|
c |
-1:1 |
Classification of Assistance Facility. |
|||
|
d |
-1:1 |
Classification of FareClass Facility type - Tpeg pti23. |
|||
|
e |
-1:1 |
Classification of Hire Facility. |
|||
|
f |
-1:1 |
Classification of Luggage Facility type - Tpeg pti23. |
|||
|
g |
-1:1 |
Classification of Mobility Facility type - Tpeg pti23. |
|||
|
h |
-1:1 |
Classification of Nuisance Facility type - Tpeg pti23. |
|||
|
i |
-1:1 |
Classification of Access Facility. |
|||
|
j |
-1:1 |
Classification of PassengerComms Facility type - Tpeg pti23. |
|||
|
k |
-1:1 |
Classification of PassengerInfo Facility type - Tpeg pti23. |
|||
|
l |
-1:1 |
Classification of Refreshment Facility type - Tpeg pti23. |
|||
|
m |
-1:1 |
Classification of Reserved Space Facility. |
|||
|
n |
-1:1 |
Classification of Retail Facility. |
|||
|
o |
-1:1 |
Classification of Sanitary Facility type - Tpeg pti23. |
|||
|
p |
-1:1 |
Classification of Ticketing Facility type - Tpeg pti23. |
|||
16. SIRi Facility model elemenys
16.1. Simple type definitions
|
|
Allowed values for units of what is counted bay: parking bay for cars, bicycle, scooter, etc otherSpaces: any other kind of spaces: lockers, standing spaces, toilets, etc. devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheelchair, etc.) vehicles: any type of vehicles (cycle, car, scooter, hoverboard, motorbike, etc.) kW (kiloWatt) or kWh (kiloWatt-hour): means that an available or consumed power is measured mAh (milliAmpere per hour): typically used for battery charging level litres and cubicMeters: means that a volume is measured squareMeters: means that a surface is measured meters: means that a distance is measured kg (kilogram): means that a mass is measured A (Ampere): means that an electric current is measured C (degree Celsius): means that a temperature is measured other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Allowed values for trend of a counting. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Allowed values for TypeOfCounting. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Generic category of a facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a Faclility. |
|||||||||||||||||||||||||||||||||
|
|
Allowed values for changes to the status of a facility. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Allowed values for the status of a MONITORED FACILITY. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRI. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
|
|
Allowed values for actions to remedy a facility change. |
||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||
16.2. The toplevel element siri:FacilityChangeElement
|
|
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
16.3. The toplevel element siri:FacilityConditionElement
|
|
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
16.4. The toplevel element siri:FacilityRef
|
|
Reference to a Facility. |
||||
16.5. The group siri:DisruptionGroup
|
|
Elements describing nature of disruption. |
||||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
16.6. The group siri:FacilityAccessibilityGroup
|
|
Group of Facility accessibility elements. |
||||
| siri:FacilityAccessibilityGroup |
|
0:1 |
Limitation of facility. |
||
|
|
0:1 |
Suitabilities of facility for specific passenger needs. |
|||
16.7. The group siri:FacilityScheduleRefGroup
|
|
Group of Facility accessibility elements. |
||||
| siri:FacilityScheduleRefGroup |
0:1 |
Reference to a LINE. |
|||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:1 |
Reference to a VEHICLE. |
||||
| siri:TrainFormationReferenceGroup |
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
|||
|
0:1 |
Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) |
||||
| siri:FacilityScheduleRefGroup |
0:1 |
Reference to a DATED VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a CONNECTION link |
||||
|
0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
16.8. The group siri:FacilityStopPlaceRefGroup
|
|
Group of Facility accessibility elements. |
||||
| siri:FacilityStopPlaceRefGroup |
|
0:1 |
Reference to a STOP PLACE. |
||
|
|
0:1 |
System identifier of STOP PLACE component. Unique at least within STOP PLACE and concrete component type. |
|||
16.9. The complex type siri:AnnotatedFacilityStructure
|
|
Summary information about Facility. Used in DISCOVERY. |
||||
|
1:1 |
Reference to a Facility. |
||||
|
|
0:1 |
Whether real-time data is available for the stop. Default is 'true'. |
|||
|
|
0:1 |
Description of the facility (without its status) |
|||
16.10. The complex type siri:EquipmentAvailabilityStructure
|
|
Type for Availaibility Change of EQUIPMENT. |
||||
|
|
0:1 |
Reference to an EQUIPMENT. |
|||
|
|
0:* |
Description of EQUIPMENT. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Reference to a TYPE OF EQUIPMENT. |
|||
|
|
0:1 |
Period for which change to EQUIPMENT status applies applies. If omitted, indefinite period. |
|||
|
|
1:1 |
Availability status of the EQUIPMENT. Default is 'notAvailable'. |
|||
|
|
0:1 |
Service Features associated with equipment. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
16.11. The complex type siri:FacilityChangeStructure
|
|
Type for change to equipment availability. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
|
0:1 |
Availability change for Equipment item. |
|||
|
0:1 |
Reference to a SITUATION associated with the element. |
||||
|
|
0:1 |
Effect of change on impaired access users. |
|||
16.12. The complex type siri:FacilityConditionStructure
|
|
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Facility affected by condition. |
||
|
b |
-1:1 |
Reference to a Facility. |
|||
|
|
1:1 |
Status of Facility. |
|||
|
|
0:* |
||||
|
|
0:1 |
New position of the Facility referenced by the FacilityRef or described in the FacilityStructure |
|||
|
0:1 |
Reference to a SITUATION associated with the element. |
||||
|
|
0:1 |
Setup action to remedy the change of the facility status (if partialy or totaly anavailable) |
|||
|
|
0:1 |
Description of the mechanism used to monitor the change of the facility status. |
|||
|
|
0:1 |
Period (duration) of the status change for the facility. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
16.13. The complex type siri:FacilityLocationStructure
|
|
Location of the MONITORED FACILITY. |
||||
| siri:FacilityScheduleRefGroup |
0:1 |
Reference to a LINE. |
|||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:1 |
Reference to a VEHICLE. |
||||
| siri:TrainFormationReferenceGroup |
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
|||
|
0:1 |
Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) |
||||
| siri:FacilityScheduleRefGroup |
0:1 |
Reference to a DATED VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a CONNECTION link |
||||
|
0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
| siri:FacilityStopPlaceRefGroup |
|
0:1 |
Reference to a STOP PLACE. |
||
|
|
0:1 |
System identifier of STOP PLACE component. Unique at least within STOP PLACE and concrete component type. |
|||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
16.14. The complex type siri:FacilityRefStructure
|
|
Type for identifier of a Faclility. |
||||
16.15. The complex type siri:FacilityStatusStructure
|
|
Description of the status of a MONITORED FACILITY. |
||||
|
|
1:1 |
Status of the facility. |
|||
|
|
0:* |
Description of the facility Status. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Accessibility of the facility. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
16.16. The complex type siri:FacilityStructure
|
|
Type for description of the MONITORED FACILITY itself. |
||||
|
|
0:1 |
Identfier of Facility. |
|||
|
|
0:* |
Textual description of the facility. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Type of facility (several types may be associated to a single facility) |
|||
|
|
0:1 |
Features of service. |
|||
|
|
0:1 |
Refererence to identifier of owner of facility. |
|||
|
|
0:1 |
Textual description of the owner of the facility. |
|||
|
|
0:1 |
When Facility is normally avaialble. If not specified, default is 'always'. Values are Logically ANDed together. |
|||
|
|
0:1 |
Describes where the facility is located. The location is a Transmodel object reference or an NeTEx object reference. |
|||
| siri:FacilityAccessibilityGroup |
|
0:1 |
Limitation of facility. |
||
|
|
0:1 |
Suitabilities of facility for specific passenger needs. |
|||
|
|
0:1 |
Accessibility of the facility. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
16.17. The complex type siri:MobilityDisruptionStructure
|
|
Type for effect of EQUIPMENT availability change on impaired access users. |
||||
|
|
1:1 |
Whether stop or service is accessible to mobility impaired users. This may be further qualified by one or more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or stepFreeAccess. |
|||
|
0:* |
Classification of Access Facility. |
||||
16.18. The complex type siri:MonitoredCountingStructure
|
|
Monitored counted values. |
||||
|
|
1:1 |
Nature of what is counted. |
|||
|
|
0:1 |
Unit of type for what is being counted |
|||
|
|
0:1 |
Open ended type or refined classification of what is counted (complement to the information coming from the facility type itself) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Counted value |
||
|
b |
|
-1:1 |
Value as a percentage (0.0 to 100.0) of the maximum possible value |
||
|
|
0:1 |
Trend of the count |
|||
|
|
0:1 |
Accuracy of the count, as a percentage (0.0 to 100.0), the percentage being a + or - maximum deviation from the provided value |
|||
|
|
0:* |
Description of what is counted |
|||
|
|
0:1 |
List of the IDs of the counted items: usefull mainly for reservation and detailed information purposes |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
16.19. The complex type siri:MonitoringInformationStructure
|
|
Allowed values for the monitoring conditions (frequency of measurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. |
||||
|
|
0:1 |
Mean time interval between two measurements. |
|||
|
|
0:1 |
How monitoring is automatic, manual, etc. |
|||
|
|
0:1 |
When the monitoring is in effect. If absent always. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
16.20. The complex type siri:MonitoringValidityConditionStructure
|
|
Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. |
||||
|
|
0:* |
Date and tme range within which condition is available. |
|||
|
|
0:* |
Monitoring period within a single day (monitoring may not be available at night, or may ony occur at certain time of day for manual monitoring, etc.). Several periods can be defined. |
|||
|
|
0:* |
Days type for monitoring availability. |
|||
|
|
0:* |
Holiday type for monitoring availability. |
|||
16.21. The complex type siri:RemedyStructure
|
|
Description of the remedy to the change of a facility status (mainly when it becomes partially or totally anavailable) |
||||
|
|
0:1 |
Type of the remedy (repair/replacement/remove) |
|||
|
|
0:* |
Description of the set up remedy in natural language. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Validity period for the remedy |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
16.22. The complex type siri:TypeOfVehicleFuelStructure
|
|
Classification of vehicle energy type. See Transmodel TypeOfFuel. (since SIRI 2.1) |
||||
|
|
1:1 |
Values for vehicle fuel type. Use of 'other' requires the additional open ended OtherTypeOfFuel to be filled. |
|||
|
|
0:1 |
An arbitrary vehicle fuel classification. |
|||
16.23. The complex type complexType[siri:FacilityStructure]/Features#complexType (typedef-35.1)
|
|
- |
||||
|
|
1:* |
Description of the feauture of the facility. Several features may be associated to a single facility. |
|||
16.24. The complex type group[siri:FacilityAccessibilityGroup]/Limitations#complexType (typedef-35.2)
|
|
- |
||||
| acsb:MobilityLimitationGroup |
1:1 |
Whether a PLACE / SITE ELEMENT is wheelchair accessible. Default is 'false'. |
|||
|
0:1 |
Whether a PLACE / SITE ELEMENT has step free access. Default is 'unknown'. |
||||
|
0:1 |
Whether a PLACE / SITE ELEMENT has escalator free access. Default is 'unknown'. |
||||
|
0:1 |
Whether a PLACE / SITE ELEMENT has lift free access. Default is 'unknown'. |
||||
| acsb:SensoryLimitationGroup |
0:1 |
Whether a PLACE / SITE ELEMENT is wheelchair accessible. Default is 'false'. |
|||
|
0:1 |
Whether a PLACE / SITE ELEMENT has Visual signals available for the visually impaired. |
||||
16.25. The complex type group[siri:FacilityAccessibilityGroup]/Suitabilities#complexType (typedef-35.3)
|
|
- |
||||
|
|
1:* |
Type of specific need for wich the facility is appropriate. |
|||
16.26. The complex type complexType[siri:MonitoredCountingStructure]/CountedItemsIdList#complexType (typedef-35.4)
|
|
- |
||||
|
|
1:* |
IDs of a counted item |
|||
16.27. The complex type complexType[siri:FacilityConditionStructure]/MonitoredCounting#complexType (typedef-35.5)
|
|
Monitored counted values. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Nature of what is counted. |
|||
|
|
0:1 |
Unit of type for what is being counted |
|||
|
|
0:1 |
Open ended type or refined classification of what is counted (complement to the information coming from the facility type itself) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Counted value |
||
|
b |
|
-1:1 |
Value as a percentage (0.0 to 100.0) of the maximum possible value |
||
|
|
0:1 |
Trend of the count |
|||
|
|
0:1 |
Accuracy of the count, as a percentage (0.0 to 100.0), the percentage being a + or - maximum deviation from the provided value |
|||
|
|
0:* |
Description of what is counted |
|||
|
|
0:1 |
List of the IDs of the counted items: usefull mainly for reservation and detailed information purposes |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
16.28. The complex type complexType[siri:EquipmentAvailabilityStructure]/EquipmentFeatures#complexType (typedef-35.6)
|
|
- |
||||
|
|
1:* |
Service or Stop features associated with equipment. Recommended values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
|||
17. siri_feature_support.xsd
17.1. Simple type definitions
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a StopFeature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a TYPE OF PRODUCT CATEGORY. |
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a ServiceCategory. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a Vehicle Feature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
17.2. The toplevel element siri:FeatureRef
|
|
Classification of facilities into arbitrary Facility categories. SIRI provides a recommended set of values covering most usages. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
17.3. The toplevel element siri:ServiceFeatureRef
|
|
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
17.4. The complex type siri:FeatureRefStructure
|
|
Type for identifier of a StopFeature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
17.5. The complex type siri:ProductCategoryRefStructure
|
|
Type for identifier of a TYPE OF PRODUCT CATEGORY. |
||||
17.6. The complex type siri:ServiceFeatureRefStructure
|
|
Type for identifier of a ServiceCategory. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
17.7. The complex type siri:VehicleFeatureRefStructure
|
|
Type for identifier of a Vehicle Feature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
18. SIRI-CT Interchange journey Connection Timetable Service.
18.1. The complex type siri:InterchangeJourneyStructure
|
|
Type for feeder or Distributor Journey info about a VEHICLE JOURNEY. |
||||
| siri:JourneyIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a DIRECTION, typically outward or return. |
|||
|
|
0:1 |
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
| siri:JourneyInfoGroup |
|
0:* |
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) |
||
|
0:* |
Additional descriptive text associated with journey. Inherited property. |
||||
|
|
0:1 |
Contact details for use by members of public. (since SIRI 2.0) |
|||
|
|
0:1 |
Contact details for use by operational staff. (since SIRI 2.0) |
|||
| siri:JourneyEndTimesGroup |
|
0:1 |
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. |
||
|
|
0:1 |
Timetabled departure time from Origin. |
|||
|
|
0:1 |
Timetabled arrival time at Destination. |
|||
|
0:1 |
Whether journey is first or last journey of day. (since SIRI 2.0) |
||||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
| siri:OperationalInfoGroup |
0:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a VEHICLE. |
||||
|
|
0:* |
Refercence to other VEHICLE Journeys ((since SIRI 2.0)) |
|||
|
|
0:1 |
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. (since SIRI 2.0) |
|||
|
|
0:1 |
The name oo the Driver or Crew (since SIRI 2.0) |
|||
|
|
0:1 |
Whether there is real-time information available for journey. Default is 'true'. |
|||
|
|
0:1 |
On a Distributor journey, a timetabled departure time of the VEHICLE JOURNEY from the CONNECTION LINK for the SERVICE JOURNEY INTERCHANGE. On a Feeder journey a Timetabled arrival time of the VEHICLE JOURNEY at the CONNECTION link for the SERVICE JOURNEY INTERCHANGE. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
19. SIRI Common Journey Model.
19.1. Simple type definitions
|
|
Union({xs:language}, {xs:string: (empty restriction)}) |
- |
19.2. The toplevel element siri:ActualArrivalTime
|
|
|
Observed time of arrival of VEHICLE at stop. |
|||
19.3. The toplevel element siri:ActualDepartureTime
|
|
|
Observed time of departure of VEHICLE from stop. |
|||
19.4. The toplevel element siri:ActualHeadwayInterval
|
|
For frequency based services, observed interval between vehicles at stop. |
||||
19.5. The toplevel element siri:AimedArrivalTime
|
|
|
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
19.6. The toplevel element siri:AimedDepartureTime
|
|
|
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
19.7. The toplevel element siri:AimedFlexibleArea
|
|
Area that encompasses the scheduled flexible stop locations according to the planned timetable. (since SIRI 2.1) |
||||
19.8. The toplevel element siri:AimedFlexibleAreaRef
|
|
Reference to the scheduled location or flexible area. (since SIRI 2.1) |
||||
19.9. The toplevel element siri:AimedHeadwayInterval
|
|
For frequency based services, target interval between vehicles at stop. |
||||
19.10. The toplevel element siri:AimedLatestPassengerAccessTime
|
|
|
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
19.11. The toplevel element siri:AimedLocationName
|
|
Name or description (e.g. address) of the scheduled location or flexible area. (since SIRI 2.1) |
||||
19.12. The toplevel element siri:ArrivalBoardingActivity
|
|
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
19.13. The toplevel element siri:ArrivalCancellationReason
|
|
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
19.14. The toplevel element siri:ArrivalFormationAssignment
|
|
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
19.15. The toplevel element siri:ArrivalOperatorRefs
|
|
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
19.16. The toplevel element siri:ArrivalOrientationRelativeToQuay
|
|
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
19.17. The toplevel element siri:ArrivalPlatformName
|
|
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
19.18. The toplevel element siri:ArrivalProximityText
|
|
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
19.19. The toplevel element siri:ArrivalStatus
|
|
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
||||
19.20. The toplevel element siri:CompoundTrain
|
|
Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1) TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. |
||||
19.21. The toplevel element siri:DepartureBoardingActivity
|
|
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
19.22. The toplevel element siri:DepartureCancellationReason
|
|
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
19.23. The toplevel element siri:DepartureFormationAssignment
|
|
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
19.24. The toplevel element siri:DepartureOperatorRefs
|
|
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
19.25. The toplevel element siri:DepartureOrientationRelativeToQuay
|
|
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
19.26. The toplevel element siri:DeparturePlatformName
|
|
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
19.27. The toplevel element siri:DepartureProximityText
|
|
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
19.28. The toplevel element siri:DepartureStatus
|
|
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
||||
19.29. The toplevel element siri:DestinationName
|
|
The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public. Note when used in a CALL, this is the Dynamic Destination Display: since vehicles can change their destination during a journey, the destination included here should be what the VEHICLE will display when it reaches the stop. |
||||
19.30. The toplevel element siri:Direction
|
|
Description of a DIRECTION. |
||||
19.31. The toplevel element siri:ExpectedArrivalTime
|
|
|
Estimated time of arriival of VEHICLE at stop . |
|||
19.32. The toplevel element siri:ExpectedDepartureCapacities
|
|
Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
||||
19.33. The toplevel element siri:ExpectedDepartureOccupancy
|
|
Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1) |
||||
19.34. The toplevel element siri:ExpectedDepartureTime
|
|
|
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
19.35. The toplevel element siri:ExpectedHeadwayInterval
|
|
For frequency based services, expected interval between vehicles at stop. |
||||
19.36. The toplevel element siri:ExpectedLatestPassengerAccessTime
|
|
|
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
19.37. The toplevel element siri:FirstOrLastJourney
|
|
Whether journey is first or last journey of day. (since SIRI 2.0) |
||||
19.38. The toplevel element siri:FormationCondition
|
|
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
||||
19.39. The toplevel element siri:JourneyNote
|
|
Additional descriptive text associated with journey. Inherited property. |
||||
19.40. The toplevel element siri:Occupancy
|
|
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. |
||||
19.41. The toplevel element siri:OriginName
|
|
The name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. |
||||
19.42. The toplevel element siri:PredictionInaccurate
|
|
|
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. |
|||
19.43. The toplevel element siri:PredictionInaccurateReason
|
|
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) |
||||
19.44. The toplevel element siri:QuayType
|
|
Indicates the type of a nested QUAY in case of detailed STOP PLACE models. A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. (since SIRI 2.1) |
||||
19.45. The toplevel element siri:RecordedDepartureCapacities
|
|
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
||||
19.46. The toplevel element siri:RecordedDepartureOccupancy
|
|
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
||||
19.47. The toplevel element siri:RelatedJourney
|
|
Refers to the JOURNEY to which the current JOURNEY is related. (since SIRI 2.1) |
||||
19.48. The toplevel element siri:Train
|
|
A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1) |
||||
19.49. The toplevel element siri:TrainComponent
|
|
Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. (since SIRI 2.1) |
||||
19.50. The toplevel element siri:TrainElement
|
|
An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1) |
||||
19.51. The toplevel element siri:TrainInCompoundTrain
|
|
Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. (since SIRI 2.1) |
||||
19.52. The toplevel element siri:ViaName
|
|
Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
||||
19.53. The group siri:AimedCallGroup
|
|
Elements describing the targeted CALL of a VEHICLE at a stop. |
||||
| siri:AimedVehicleArrivalGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:AimedVehicleDepartureGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:AimedCallGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
For frequency based services, target interval between vehicles at stop. |
||||
19.54. The group siri:AimedVehicleArrivalGroup
|
|
Elements describing the arrival of a VEHICLE at a stop. |
||||
| siri:AimedVehicleArrivalGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
19.55. The group siri:AimedVehicleDepartureGroup
|
|
Elements describing the departure of a VEHICLE from a stop. |
||||
| siri:AimedVehicleDepartureGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
19.56. The group siri:BoardingPositionAssignmentGroup
|
|
Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. (since SIRI 2.1) |
||||
| siri:BoardingPositionAssignmentGroup |
|
0:1 |
Physical BOARDING POSITION to use according to the planned timetable. |
||
|
|
0:* |
Scheduled BOARDING POSITION name. Can be used to indicate boarding position change. |
|||
|
|
0:1 |
Physical BOARDING POSITION to use according to the real-time prediction. |
|||
|
|
0:* |
Expected BOARDING POSITION name. Can be used to indicate real-time prediction. |
|||
|
|
0:1 |
Actually recorded BOARDING POSITION. Can be used to indicate the actually used boarding position. |
|||
|
|
0:* |
Recorded BOARDING POSITION name. Can be used to indicate the actually used boarding position. |
|||
19.57. The group siri:CallNoteGroup
|
|
Annotations of the CALL. |
||||
| siri:CallNoteGroup |
|
0:* |
Text annotation that applies to this CALL. |
||
19.58. The group siri:CallPropertyGroup
|
|
Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. |
||||
| siri:CallPropertyGroup |
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
|||
|
|
0:1 |
Whether this is a Hail and Ride Stop. Default is 'false'. |
|||
|
|
0:1 |
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. |
|||
|
|
0:* |
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0) |
|||
|
|
0:* |
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. |
|||
19.59. The group siri:DatedOperationalInfoGroup
|
|
Operational information about the monitored VEHICLE JOURNEY. |
||||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
| siri:DatedOperationalInfoGroup |
0:1 |
Reference to a VEHICLE. |
|||
19.60. The group siri:FlexibleStopLocationGroup
|
|
Elements for location of flexible stops or service that allows pickup anywhere in a designated area. (since SIRI 2.1) |
||||
| siri:FlexibleStopLocationGroup |
0:1 |
Area that encompasses the scheduled flexible stop locations according to the planned timetable. (since SIRI 2.1) |
|||
|
0:1 |
Reference to the scheduled location or flexible area. (since SIRI 2.1) |
||||
|
0:* |
Name or description (e.g. address) of the scheduled location or flexible area. (since SIRI 2.1) |
||||
|
|
0:1 |
Area that encompasses the expected flexible stop locations according to the real-time prediction. |
|||
|
|
0:1 |
||||
|
|
0:* |
Name or description (e.g. address) of the expected location or flexible area. |
|||
|
|
0:1 |
Area that encompasses the actually recorded flexible stop locations. |
|||
|
|
0:1 |
||||
|
|
0:* |
Name or description (e.g. address) of the actually recorded location or flexible area. |
|||
19.61. The group siri:FormationStatusInfoGroup
|
|
Elements for FormationStatus that further describe the status of the formation, e.g. whether the accessibility has changed. (since SIRI 2.1) |
||||
| siri:FormationStatusInfoGroup |
|
0:* |
Description of the status of a formation or a vehicle within the formation. |
||
|
|
0:1 |
Accessibility of the formation or a vehicle within the formation. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
19.62. The group siri:HeadwayIntervalGroup
|
|
Elements describing the HEADWAY INTERVALs. |
||||
| siri:HeadwayIntervalGroup |
0:1 |
For frequency based services, target interval between vehicles at stop. |
|||
|
0:1 |
For frequency based services, expected interval between vehicles at stop. |
||||
19.63. The group siri:JourneyEndNamesGroup
|
|
End names for journey. |
||||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
19.64. The group siri:JourneyEndTimesGroup
|
|
Call times for journey. |
||||
| siri:JourneyEndTimesGroup |
|
0:1 |
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. |
||
|
|
0:1 |
Timetabled departure time from Origin. |
|||
|
|
0:1 |
Timetabled arrival time at Destination. |
|||
|
0:1 |
Whether journey is first or last journey of day. (since SIRI 2.0) |
||||
19.65. The group siri:JourneyFormationGroup
|
|
Groups relevant elements of the formation model that are used on JOURNEY level. The TRAIN conceptual model represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs. Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. (since SIRI 2.1) |
||||
| siri:JourneyFormationGroup |
|
0:1 |
|||
|
|
0:1 |
||||
|
|
0:1 |
||||
19.66. The group siri:JourneyInfoGroup
|
|
Elements describing a VEHICLE JOURNEY. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul DATED VEHICLE JOURNEYs of the timetable. Each real-time journey (e.g. ESTIMATED VEHICLE JOURNEY or MONITORED VEHICLE JORUNEY) takes its values from the DATED VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. |
||||
| siri:JourneyInfoGroup |
|
0:* |
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) |
||
|
0:* |
Additional descriptive text associated with journey. Inherited property. |
||||
|
|
0:1 |
Contact details for use by members of public. (since SIRI 2.0) |
|||
|
|
0:1 |
Contact details for use by operational staff. (since SIRI 2.0) |
|||
19.67. The group siri:JourneyRelationInfoGroup
|
|
Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. (since SIRI 2.1) |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:JourneyRelationInfoGroup |
a |
|
-1:1 |
Information about the stop at which the JOURNEY is related to another JOURNEY. (since SIRI 2.1) |
|
|
b |
|
-1:1 |
Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. (since SIRI 2.1) |
||
19.68. The group siri:MonitoredStopArrivalStatusGroup
|
|
Elements describing the arrival status of a VEHICLE at a stop. |
||||
| siri:MonitoredStopArrivalStatusGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:1 |
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
19.69. The group siri:MonitoredStopDepartureStatusGroup
|
|
Elements describing the departure status of a VEHICLE from a stop. |
||||
| siri:MonitoredStopDepartureStatusGroup |
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
|||
|
0:1 |
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
The element contains one of the following element sequences (a-b) |
|||||
|
a |
-0:* |
Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1) |
|||
|
a |
-0:* |
Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
19.70. The group siri:OccupancyScopeFilterGroup
|
|
The intersection of supplied elements describes the extent that the Occupancy values applies to. (since SIRI 2.1) Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) are available here, but a stop-centric filtering (measurement in a sector or at a position on a QUAY) can be achieved indirectly via Arrival-/DepartureFormationAssignment. |
||||
| siri:TrainFormationReferenceGroup |
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
|||
|
0:1 |
Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) |
||||
| siri:OccupancyScopeFilterGroup |
|
0:1 |
Fare class in VEHICLE for which occupancy or capacities are specified. |
||
|
|
0:1 |
Adult, child, wheelchair etc. |
|||
19.71. The group siri:OccupancyValuesGroup
|
|
Occupancy values applying to indicated scope. (since SIRI 2.1) |
||||
| siri:OccupancyValuesGroup |
|
0:1 |
An approximate figure of how occupied or full a VEHICLE and its parts are, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. More accurate data can be provided by the individual occupancies or capacities below. |
||
|
|
0:1 |
Utilised percentage of maximum payload after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of alighting passengers for this vehicle journey at this STOP POINT. |
|||
|
|
0:1 |
Total number of boarding passengers for this vehicle journey at this STOP POINT. |
|||
|
|
0:1 |
Total number of passengers on-board after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of special places, e.g. seats for the disabled or lounge seats, that are occupied after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of pushchairs on-board after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of wheelchairs on-board after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of prams on-board after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. |
|||
19.72. The group siri:OnwardsCallGroup
|
|
Elements describing the CALL. Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. |
||||
| siri:OnwardVehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
a |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
|
a |
|
-0:1 |
Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.1) |
||
|
a |
|
-0:1 |
Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) |
||
|
b |
|
-1:1 |
If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' (ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true" (iii) drop/omit ExpectedArrivalTime (iv) set ArrivalStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) |
||
| siri:MonitoredStopArrivalStatusGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:1 |
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:OnwardVehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
a |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
|
a |
|
-0:1 |
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time (since SIRI 2.0). |
||
|
a |
|
-0:1 |
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. (since SIRI 2.0) |
||
|
a |
|
-0:1 |
Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) |
||
|
b |
|
-1:1 |
If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' (ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true" (iii) drop/omit ExpectedDepartureTime (iv) set DepartureStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) |
||
| siri:PassengerDepartureTimesGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
||||
| siri:MonitoredStopDepartureStatusGroup |
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
|||
|
0:1 |
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
The element contains one of the following element sequences (a-b) |
|||||
|
a |
-0:* |
Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1) |
|||
|
a |
-0:* |
Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:HeadwayIntervalGroup |
0:1 |
For frequency based services, target interval between vehicles at stop. |
|||
|
0:1 |
For frequency based services, expected interval between vehicles at stop. |
||||
| siri:StopProximityGroup |
|
0:1 |
Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. (since SIRI 2.0). |
||
|
|
0:1 |
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. (since SIRI 2.0). |
|||
19.73. The group siri:OnwardVehicleArrivalTimesGroup
|
|
Elements for Arrival in onward CALl. |
||||
| siri:OnwardVehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
a |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
|
a |
|
-0:1 |
Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.1) |
||
|
a |
|
-0:1 |
Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) |
||
|
b |
|
-1:1 |
If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' (ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true" (iii) drop/omit ExpectedArrivalTime (iv) set ArrivalStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) |
||
19.74. The group siri:OnwardVehicleDepartureTimesGroup
|
|
Elements for departure in ONWARD CALL. |
||||
| siri:OnwardVehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
a |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
|
a |
|
-0:1 |
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time (since SIRI 2.0). |
||
|
a |
|
-0:1 |
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. (since SIRI 2.0) |
||
|
a |
|
-0:1 |
Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) |
||
|
b |
|
-1:1 |
If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' (ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true" (iii) drop/omit ExpectedDepartureTime (iv) set DepartureStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) |
||
19.75. The group siri:OperationalBlockGroup
|
|
Operational information about the monitored VEHICLE JOURNEY. |
||||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
19.76. The group siri:OperationalInfoGroup
|
|
Operational information about the monitored VEHICLE JOURNEY. |
||||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
| siri:OperationalInfoGroup |
0:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a VEHICLE. |
||||
|
|
0:* |
Refercence to other VEHICLE Journeys ((since SIRI 2.0)) |
|||
|
|
0:1 |
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. (since SIRI 2.0) |
|||
|
|
0:1 |
The name oo the Driver or Crew (since SIRI 2.0) |
|||
19.77. The group siri:PassengerCapacityGroup
|
|
Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a VEHICLE at a given stop, i.e., the number of seats available. (since SIRI 2.1) |
||||
| siri:PassengerCapacityGroup |
|
0:1 |
The total capacity of the vehicle in number of passengers. |
||
|
|
0:1 |
The seating capacity of the vehicle in number of passengers. |
|||
|
|
0:1 |
The standing capacity of the vehicle in number of passengers. |
|||
|
|
0:1 |
The number of special places on the vehicle, e.g. seats for the disabled or lounge seats. |
|||
|
|
0:1 |
The number of push chair places on the vehicle. |
|||
|
|
0:1 |
The number of wheelchair places on the vehicle. |
|||
|
|
0:1 |
The number of places on the vehicle that are suitable for prams. |
|||
|
|
0:1 |
The number of bicycle racks on the vehicle. |
|||
19.78. The group siri:PassengerDepartureTimesGroup
|
|
Passenger arrival times at STOP PLACE in order to meet VEHICLE departure times for CALL. |
||||
| siri:PassengerDepartureTimesGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
||||
19.79. The group siri:QuayAssignmentGroup
|
|
Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. (since SIRI 2.1) |
||||
| siri:QuayAssignmentGroup |
|
0:1 |
Physical QUAY to use according to the planned timetable. (since SIRI 2.0) |
||
|
|
0:* |
Scheduled Platform name. Can be used to indicate platfrom change. (since SIRI 2.0) |
|||
|
|
0:1 |
Physical QUAY to use according to the real-time prediction. (since SIRI 2.0) |
|||
|
|
0:* |
Expected Platform name. Can be used to indicate real-time prediction. (since SIRI 2.1) |
|||
|
|
0:1 |
Physical QUAY actually used. (since SIRI 2.0) |
|||
|
|
0:* |
Actual Platform name. Can be used to indicate recorded platform. (since SIRI 2.1) |
|||
|
0:1 |
Indicates the type of a nested QUAY in case of detailed STOP PLACE models. A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. (since SIRI 2.1) |
||||
19.80. The group siri:StopProximityGroup
|
|
Elements describing the distance from the stop of a VEHICLE. (since SIRI 2.0). |
||||
| siri:StopProximityGroup |
|
0:1 |
Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. (since SIRI 2.0). |
||
|
|
0:1 |
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. (since SIRI 2.0). |
|||
19.81. The group siri:TrainComponentGroup
|
|
Elements for a TRAIN COMPONENT. (since SIRI 2.1) |
||||
| siri:TrainComponentGroup |
|
0:1 |
Specifies how the TRAIN ELEMENT is labeled within the context of the TRAIN. This advertised label or number, e.g. "Carriage B" or "23", can be used for seat reservations and passenger orientation. |
||
|
|
0:1 |
Description of TRAIN COMPONENT, e.g. "Front Carriage 1st Class". |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-1:1 |
An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1) |
|||
|
|
0:1 |
Whether orientation of TRAIN ELEMENT within TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). |
|||
19.82. The group siri:TrainElementGroup
|
|
Elements for a TRAIN ELEMENT. (since SIRI 2.1) |
||||
| siri:TrainElementGroup |
|
0:1 |
Type of TRAIN ELEMENT. |
||
|
|
0:1 |
Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12-digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches. |
|||
|
0:1 |
List of FARE CLASSes. (since SIRI 2.1) |
||||
19.83. The group siri:TrainGroup
|
|
Elements for TRAIN. (since SIRI 2.1) |
||||
| siri:TrainGroup |
|
0:1 |
Number of cars needed in TRAIN. |
||
|
|
0:1 |
Nature of TRAIN size, e.g "short", "long", "normal". Default is "normal". |
|||
|
|
0:1 |
Ordered collection of TRAIN COMPONENTs making up the TRAIN. |
|||
19.84. The group siri:TrainInCompoundTrainGroup
|
|
Elements for a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
||||
| siri:TrainInCompoundTrainGroup |
|
0:1 |
Specifies how the TRAIN is labeled within the context of the COMPOUND TRAIN. This advertised label or number, e.g. the individual TRAIN NUMBER, can be used for seat reservations and passenger orientation. |
||
|
|
0:1 |
Description of TRAIN IN COMPOUND TRAIN. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-1:1 |
A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1) |
|||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
| siri:TrainInCompoundTrainGroup |
|
0:1 |
Whether orientation of TRAIN within COMPOUND TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). |
||
|
|
0:1 |
Specifies whether a passage from/to an adjacent TRAIN is possible for passengers. |
|||
19.85. The group siri:VehicleAccessibilityRequirementsGroup
|
|
Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. (since SIRI 2.1) |
||||
| siri:VehicleAccessibilityRequirementsGroup |
|
0:1 |
Whether Vehicle is low floor to facilitate access by the mobility impaired. |
||
|
|
0:1 |
Whether vehicle has lift or ramp to facilitate wheelchair access. |
|||
|
|
0:1 |
Whether vehicle has hoist for wheelchair access. |
|||
19.86. The group siri:VehicleArrivalTimesGroup
|
|
Arrival times for CALL. |
||||
| siri:VehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of arrival of VEHICLE at stop. |
|||
|
b |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
19.87. The group siri:VehicleDepartureTimesGroup
|
|
Departure times for CALL. |
||||
| siri:VehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of departure of VEHICLE from stop. |
|||
|
b |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
19.88. The group siri:VehicleDimensionsGroup
|
|
Dimension elements for a VEHICLE TYPE. (since SIRI 2.1) |
||||
| siri:VehicleDimensionsGroup |
|
0:1 |
The length of a VEHICLE of the type. |
||
|
|
0:1 |
The width of a VEHICLE of the type. |
|||
|
|
0:1 |
The length of a VEHICLE of the type. |
|||
|
|
0:1 |
The weight of a VEHICLE of the type. |
|||
19.89. The group siri:VehicleJourneyInfoGroup
|
|
Common information about a VEHICLE JOURNEY. (Similar to VDV TripInfo) |
||||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
| siri:JourneyInfoGroup |
|
0:* |
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) |
||
|
0:* |
Additional descriptive text associated with journey. Inherited property. |
||||
|
|
0:1 |
Contact details for use by members of public. (since SIRI 2.0) |
|||
|
|
0:1 |
Contact details for use by operational staff. (since SIRI 2.0) |
|||
| siri:JourneyEndTimesGroup |
|
0:1 |
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. |
||
|
|
0:1 |
Timetabled departure time from Origin. |
|||
|
|
0:1 |
Timetabled arrival time at Destination. |
|||
|
0:1 |
Whether journey is first or last journey of day. (since SIRI 2.0) |
||||
19.90. The group siri:VehicleTypeGroup
|
|
Elements for a VEHICLE TYPE. (since SIRI 2.1) |
||||
| siri:VehicleTypeGroup |
|
0:1 |
Name of VEHICLE TYPE. |
||
|
|
0:1 |
Short Name of VEHICLE TYPE. |
|||
|
|
0:1 |
Description of VEHICLE TYPE. |
|||
|
|
0:1 |
||||
| siri:VehicleTypePropertiesGroup |
|
0:1 |
Whether vehicles of the type have a reversing direction. |
||
|
|
0:1 |
Whether vehicles of the type are self-propelled. |
|||
|
|
0:1 |
The type of fuel used by a vehicle of the type. |
|||
|
|
0:1 |
Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). |
|||
|
|
0:1 |
Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. |
|||
| siri:VehicleAccessibilityRequirementsGroup |
|
0:1 |
Whether Vehicle is low floor to facilitate access by the mobility impaired. |
||
|
|
0:1 |
Whether vehicle has lift or ramp to facilitate wheelchair access. |
|||
|
|
0:1 |
Whether vehicle has hoist for wheelchair access. |
|||
| siri:VehicleDimensionsGroup |
|
0:1 |
The length of a VEHICLE of the type. |
||
|
|
0:1 |
The width of a VEHICLE of the type. |
|||
|
|
0:1 |
The length of a VEHICLE of the type. |
|||
|
|
0:1 |
The weight of a VEHICLE of the type. |
|||
| siri:VehicleTypeGroup |
|
0:1 |
Facilities of VEHICLE TYPE. |
||
19.91. The group siri:VehicleTypePropertiesGroup
|
|
Property elements for the abstract VEHICLE TYPE. (since SIRI 2.1) |
||||
| siri:VehicleTypePropertiesGroup |
|
0:1 |
Whether vehicles of the type have a reversing direction. |
||
|
|
0:1 |
Whether vehicles of the type are self-propelled. |
|||
|
|
0:1 |
The type of fuel used by a vehicle of the type. |
|||
|
|
0:1 |
Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). |
|||
|
|
0:1 |
Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. |
|||
| siri:VehicleAccessibilityRequirementsGroup |
|
0:1 |
Whether Vehicle is low floor to facilitate access by the mobility impaired. |
||
|
|
0:1 |
Whether vehicle has lift or ramp to facilitate wheelchair access. |
|||
|
|
0:1 |
Whether vehicle has hoist for wheelchair access. |
|||
| siri:VehicleDimensionsGroup |
|
0:1 |
The length of a VEHICLE of the type. |
||
|
|
0:1 |
The width of a VEHICLE of the type. |
|||
|
|
0:1 |
The length of a VEHICLE of the type. |
|||
|
|
0:1 |
The weight of a VEHICLE of the type. |
|||
19.92. The complex type siri:AbstractCallStructure
|
|
Type for Abstract CALL at stop. |
||||
| siri:StopPointInSequenceGroup |
1:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
19.93. The complex type siri:AbstractMonitoredCallStructure
|
|
Type for Abstract CALL at stop. |
||||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
19.94. The complex type siri:CompoundTrainStructure
|
|
Type for COMPOUND TRAIN. (since SIRI 2.1) |
||||
|
|
0:1 |
Identifier for COMPOUND TRAIN. |
|||
| siri:VehicleTypeGroup |
|
0:1 |
Name of VEHICLE TYPE. |
||
|
|
0:1 |
Short Name of VEHICLE TYPE. |
|||
|
|
0:1 |
Description of VEHICLE TYPE. |
|||
|
|
0:1 |
||||
| siri:VehicleTypePropertiesGroup |
|
0:1 |
Whether vehicles of the type have a reversing direction. |
||
|
|
0:1 |
Whether vehicles of the type are self-propelled. |
|||
|
|
0:1 |
The type of fuel used by a vehicle of the type. |
|||
|
|
0:1 |
Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). |
|||
|
|
0:1 |
Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. |
|||
| siri:VehicleAccessibilityRequirementsGroup |
|
0:1 |
Whether Vehicle is low floor to facilitate access by the mobility impaired. |
||
|
|
0:1 |
Whether vehicle has lift or ramp to facilitate wheelchair access. |
|||
|
|
0:1 |
Whether vehicle has hoist for wheelchair access. |
|||
| siri:VehicleDimensionsGroup |
|
0:1 |
The length of a VEHICLE of the type. |
||
|
|
0:1 |
The width of a VEHICLE of the type. |
|||
|
|
0:1 |
The length of a VEHICLE of the type. |
|||
|
|
0:1 |
The weight of a VEHICLE of the type. |
|||
| siri:VehicleTypeGroup |
|
0:1 |
Facilities of VEHICLE TYPE. |
||
|
|
0:1 |
Ordered collection of TRAINs making up the COMPOUND TRAIN. |
|||
19.95. The complex type siri:DestinationStructure
|
|
Type for Information about a DESTINATION. |
||||
|
|
1:1 |
Identifer of Destinatioin |
|||
|
|
1:* |
Name of Destination |
|||
19.96. The complex type siri:DirectionStructure
|
|
Type for DIRECTION. |
||||
|
|
1:1 |
Identifer of DIRECTION, |
|||
|
|
0:* |
Description of DIRECTION. (Unbounded since SIRI 2.0) |
|||
19.97. The complex type siri:FormationAssignmentStructure
|
|
Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). (since SIRI 2.1) |
||||
| siri:TrainFormationReferenceGroup |
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
|||
|
0:1 |
Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) |
||||
|
|
0:1 |
Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors. |
|||
|
|
1:* |
References to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from. If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENTs), and a TRAIN COMPONENT spans over multiple sectors of the QUAY, the FORMATION ASSIGNMENT must reference all of them (in multiple STOP ASSIGNMENTs). |
|||
19.98. The complex type siri:FormationConditionStructure
|
|
Type for FORMATION CONDITION. (since SIRI 2.1) |
||||
| siri:TrainFormationReferenceGroup |
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
|||
|
0:1 |
Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Status of formation, e.g., whether it has changed compared to the plan, certain VEHICLEs or features are missing or extra VEHICLEs are added. |
||
|
b |
|
-1:1 |
Status of a VEHICLE within formation, e.g., whether a VEHICLE is open, booked or has defective doors. |
||
|
0:1 |
Reference to a SITUATION associated with the element. |
||||
|
|
0:1 |
Information on recommendations for passengers on how to deal with the formation change. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
19.99. The complex type siri:FormationStatusStructure
|
|
Description of the status of a monitored formation. |
||||
|
|
1:1 |
Status of the formation. |
|||
| siri:FormationStatusInfoGroup |
|
0:* |
Description of the status of a formation or a vehicle within the formation. |
||
|
|
0:1 |
Accessibility of the formation or a vehicle within the formation. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
19.100. The complex type siri:GroupReservationStructure
|
|
Used to specify that a travel group has booked a section of the vehicle for a part of the journey, and if so under what name. (since SIRI 2.1) |
||||
|
|
1:1 |
Name for which the travel group has made the reservation. |
|||
|
|
1:1 |
Number of seats that the group has booked. |
|||
19.101. The complex type siri:JourneyRelationsStructure
|
|
Provides information about relations to other journeys. (since SIRI 2.1) |
||||
|
|
1:* |
||||
19.102. The complex type siri:JourneyRelationStructure
|
|
- |
||||
|
|
1:1 |
Specifies the type of the relation, e.g., joining, splitting, replacement etc. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
| siri:JourneyRelationInfoGroup |
a |
|
-1:1 |
Information about the stop at which the JOURNEY is related to another JOURNEY. (since SIRI 2.1) |
|
|
b |
|
-1:1 |
Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. (since SIRI 2.1) |
||
|
1:* |
Refers to the JOURNEY to which the current JOURNEY is related. (since SIRI 2.1) |
||||
19.103. The complex type siri:OnwardCallsStructure
|
|
Type for CALLing pattern for JOURNEY PATTERN. |
||||
|
|
1:* |
||||
19.104. The complex type siri:OnwardCallStructure
|
|
Type for Abstract CALL at stop. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) |
||||
|
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
||||
| siri:OnwardVehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
a |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
|
a |
|
-0:1 |
Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.1) |
||
|
a |
|
-0:1 |
Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) |
||
|
b |
|
-1:1 |
If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' (ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true" (iii) drop/omit ExpectedArrivalTime (iv) set ArrivalStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) |
||
| siri:MonitoredStopArrivalStatusGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:1 |
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:OnwardVehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
|
a |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
|
a |
|
-0:1 |
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time (since SIRI 2.0). |
||
|
a |
|
-0:1 |
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. (since SIRI 2.0) |
||
|
a |
|
-0:1 |
Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) |
||
|
b |
|
-1:1 |
If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer: (i) set Monitored to 'false' (ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true" (iii) drop/omit ExpectedDepartureTime (iv) set DepartureStatus to 'noReport' However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer. To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1) |
||
| siri:PassengerDepartureTimesGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
||||
| siri:MonitoredStopDepartureStatusGroup |
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
|||
|
0:1 |
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
The element contains one of the following element sequences (a-b) |
|||||
|
a |
-0:* |
Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1) |
|||
|
a |
-0:* |
Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:HeadwayIntervalGroup |
0:1 |
For frequency based services, target interval between vehicles at stop. |
|||
|
0:1 |
For frequency based services, expected interval between vehicles at stop. |
||||
| siri:StopProximityGroup |
|
0:1 |
Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. (since SIRI 2.0). |
||
|
|
0:1 |
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. (since SIRI 2.0). |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
19.105. The complex type siri:PassageBetweenTrainsStructure
|
|
Indicates whether passengers have access to adjacent TRAINs or TRAIN COMPONENTs within a COMPOUND TRAIN, i.e., whether passage between those wagons/coaches is possible. (since SIRI 2.1) |
||||
|
1:1 |
Reference to a TRAIN. (since SIRI 2.1) |
||||
|
0:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
||||
|
|
1:1 |
||||
19.106. The complex type siri:PassengerCapacityStructure
|
|
Real-time capacities of a VEHICLE (by fare class), i.e., number of available seats. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
||||
| siri:TrainFormationReferenceGroup |
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
|||
|
0:1 |
Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) |
||||
| siri:OccupancyScopeFilterGroup |
|
0:1 |
Fare class in VEHICLE for which occupancy or capacities are specified. |
||
|
|
0:1 |
Adult, child, wheelchair etc. |
|||
| siri:PassengerCapacityGroup |
|
0:1 |
The total capacity of the vehicle in number of passengers. |
||
|
|
0:1 |
The seating capacity of the vehicle in number of passengers. |
|||
|
|
0:1 |
The standing capacity of the vehicle in number of passengers. |
|||
|
|
0:1 |
The number of special places on the vehicle, e.g. seats for the disabled or lounge seats. |
|||
|
|
0:1 |
The number of push chair places on the vehicle. |
|||
|
|
0:1 |
The number of wheelchair places on the vehicle. |
|||
|
|
0:1 |
The number of places on the vehicle that are suitable for prams. |
|||
|
|
0:1 |
The number of bicycle racks on the vehicle. |
|||
19.107. The complex type siri:PlannedStopAssignmentStructure
|
|
Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. (since SIRI 2.0). |
||||
|
The element contains one of the following element sequences (a-b) |
|||||
|
a |
|
-0:1 |
Physical QUAY to use according to the planned timetable. (since SIRI 2.0) |
||
|
a |
|
-0:* |
Scheduled Platform name. (since SIRI 2.0) |
||
|
a |
-0:1 |
Indicates the type of a nested QUAY in case of detailed STOP PLACE models. A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. (since SIRI 2.1) |
|||
|
b |
|
-0:1 |
Physical BOARDING POSITION to use according to the planned timetable. (since SIRI 2.1) |
||
|
b |
|
-0:* |
Scheduled BOARDING POSITION name. (since SIRI 2.1) |
||
|
0:1 |
Area that encompasses the scheduled flexible stop locations according to the planned timetable. (since SIRI 2.1) |
||||
|
0:1 |
Reference to the scheduled location or flexible area. (since SIRI 2.1) |
||||
|
0:* |
Name or description (e.g. address) of the scheduled location or flexible area. (since SIRI 2.1) |
||||
19.108. The complex type siri:PredictionQualityStructure
|
|
Type for Prediction Quality quantifcation. |
||||
|
|
1:1 |
An approxiimate characterisation of prediction quality as one of five values. (since SIRI 2.0) |
|||
|
|
0:1 |
Percentile associated with range as specified by lower and upper bound. (since SIRI 2.0) |
|||
|
|
0:1 |
Lower bound on time of prediction for confidence level if different from defaults. (since SIRI 2.0) |
|||
|
|
0:1 |
Upper bound on time of prediction for confidence level if different from defaults. (since SIRI 2.0) |
|||
19.109. The complex type siri:ProgressBetweenStopsStructure
|
|
Type for Progress between stops. |
||||
|
|
0:1 |
The total distance in metres between the previous stop and the next stop. |
|||
|
|
0:1 |
Percentage along link that VEHICLE has travelled. |
|||
19.110. The complex type siri:RecommendedActionStructure
|
|
Description of the recommended action for passengers on how to deal with changes, for example of the TRAIN formation. |
||||
|
|
1:1 |
Type of the recommendation, e.g. 'unknown', 'replacement' or 'otherRoute'. |
|||
|
|
0:* |
Description of the recommended action in natural language. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
19.111. The complex type siri:RelatedCallStructure
|
|
Type for Abstract CALL at stop. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:StopPointInSequenceGroup |
1:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
||||
|
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
||||
19.112. The complex type siri:RelatedJourneyPartStructure
|
|
Type for a reference to JOURNEY PART. (since SIRI 2.0) |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Reference to a JOURNEY part. (since SIRI 2.0) |
|||
|
|
0:1 |
Train Number for JOURNEY PART (since SIRI 2.0) |
|||
|
|
0:1 |
OPERATOR of JOURNEY PART. (since SIRI 2.0) |
|||
|
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
||||
| siri:JourneyPartViewGroup |
|
1:1 |
Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. |
||
|
|
1:1 |
Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. |
|||
|
|
0:1 |
Time at which the related JOURNEY PART begins. |
|||
|
|
0:1 |
Time at which the related JOURNEY PART ends. |
|||
19.113. The complex type siri:RelatedJourneyStructure
|
|
Type for a reference to a connecting journey. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. |
|||
|
|
0:1 |
Identify a VEHICLE JOURNEY indirectly by origin and destination as well as the scheduled times at these stops. |
|||
|
|
0:1 |
Reference to LINE of journey. |
|||
|
|
0:1 |
Reference to TRAIN NUMBER of journey. |
|||
|
|
0:1 |
Reference to OPERATOR of journey. |
|||
|
|
0:1 |
PARTICIPANT reference that identifies data producer of journey. |
|||
|
Inherited content is followed by own content: |
|||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:JourneyRelationInfoGroup |
a |
|
-1:1 |
Information about the stop at which the JOURNEY is related to another JOURNEY. (since SIRI 2.1) |
|
|
b |
|
-1:1 |
Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. (since SIRI 2.1) |
||
19.114. The complex type siri:SimpleContactStructure
|
|
Type for Simple Contact Details. |
||||
|
|
0:1 |
Phone number (since SIRI 2.0) |
|||
|
|
0:1 |
Url for contact (since SIRI 2.0) |
|||
19.115. The complex type siri:StopAssignmentStructure
|
|
Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. (since SIRI 2.0). |
||||
|
The element contains one of the following element sequences (a-b) |
|||||
| siri:QuayAssignmentGroup |
a |
|
-0:1 |
Physical QUAY to use according to the planned timetable. (since SIRI 2.0) |
|
|
a |
|
-0:* |
Scheduled Platform name. Can be used to indicate platfrom change. (since SIRI 2.0) |
||
|
a |
|
-0:1 |
Physical QUAY to use according to the real-time prediction. (since SIRI 2.0) |
||
|
a |
|
-0:* |
Expected Platform name. Can be used to indicate real-time prediction. (since SIRI 2.1) |
||
|
a |
|
-0:1 |
Physical QUAY actually used. (since SIRI 2.0) |
||
|
a |
|
-0:* |
Actual Platform name. Can be used to indicate recorded platform. (since SIRI 2.1) |
||
|
a |
-0:1 |
Indicates the type of a nested QUAY in case of detailed STOP PLACE models. A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. (since SIRI 2.1) |
|||
| siri:BoardingPositionAssignmentGroup |
b |
|
-0:1 |
Physical BOARDING POSITION to use according to the planned timetable. |
|
|
b |
|
-0:* |
Scheduled BOARDING POSITION name. Can be used to indicate boarding position change. |
||
|
b |
|
-0:1 |
Physical BOARDING POSITION to use according to the real-time prediction. |
||
|
b |
|
-0:* |
Expected BOARDING POSITION name. Can be used to indicate real-time prediction. |
||
|
b |
|
-0:1 |
Actually recorded BOARDING POSITION. Can be used to indicate the actually used boarding position. |
||
|
b |
|
-0:* |
Recorded BOARDING POSITION name. Can be used to indicate the actually used boarding position. |
||
| siri:FlexibleStopLocationGroup |
0:1 |
Area that encompasses the scheduled flexible stop locations according to the planned timetable. (since SIRI 2.1) |
|||
|
0:1 |
Reference to the scheduled location or flexible area. (since SIRI 2.1) |
||||
|
0:* |
Name or description (e.g. address) of the scheduled location or flexible area. (since SIRI 2.1) |
||||
|
|
0:1 |
Area that encompasses the expected flexible stop locations according to the real-time prediction. |
|||
|
|
0:1 |
||||
|
|
0:* |
Name or description (e.g. address) of the expected location or flexible area. |
|||
|
|
0:1 |
Area that encompasses the actually recorded flexible stop locations. |
|||
|
|
0:1 |
||||
|
|
0:* |
Name or description (e.g. address) of the actually recorded location or flexible area. |
|||
19.116. The complex type siri:TrainComponentStructure
|
|
Type for TRAIN COMPONENT. (since SIRI 2.1) |
||||
|
|
0:1 |
Identifier for TRAIN COMPONENT. |
|||
|
|
1:1 |
Specifies the order of the TRAIN ELEMENT within the TRAIN. The locomotive would ideally have ORDER '1', the first wagon/coach attached to the locomotive ORDER '2' and so on. |
|||
| siri:TrainComponentGroup |
|
0:1 |
Specifies how the TRAIN ELEMENT is labeled within the context of the TRAIN. This advertised label or number, e.g. "Carriage B" or "23", can be used for seat reservations and passenger orientation. |
||
|
|
0:1 |
Description of TRAIN COMPONENT, e.g. "Front Carriage 1st Class". |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-1:1 |
An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1) |
|||
|
|
0:1 |
Whether orientation of TRAIN ELEMENT within TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). |
|||
19.117. The complex type siri:TrainElementStructure
|
|
Type for TRAIN ELEMENT. (since SIRI 2.1) |
||||
|
|
1:1 |
Identifier for TRAIN ELEMENT. |
|||
| siri:TrainElementGroup |
|
0:1 |
Type of TRAIN ELEMENT. |
||
|
|
0:1 |
Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12-digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches. |
|||
|
0:1 |
List of FARE CLASSes. (since SIRI 2.1) |
||||
| siri:VehicleTypeGroup |
|
0:1 |
Name of VEHICLE TYPE. |
||
|
|
0:1 |
Short Name of VEHICLE TYPE. |
|||
|
|
0:1 |
Description of VEHICLE TYPE. |
|||
|
|
0:1 |
||||
| siri:VehicleTypePropertiesGroup |
|
0:1 |
Whether vehicles of the type have a reversing direction. |
||
|
|
0:1 |
Whether vehicles of the type are self-propelled. |
|||
|
|
0:1 |
The type of fuel used by a vehicle of the type. |
|||
|
|
0:1 |
Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). |
|||
|
|
0:1 |
Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. |
|||
| siri:VehicleAccessibilityRequirementsGroup |
|
0:1 |
Whether Vehicle is low floor to facilitate access by the mobility impaired. |
||
|
|
0:1 |
Whether vehicle has lift or ramp to facilitate wheelchair access. |
|||
|
|
0:1 |
Whether vehicle has hoist for wheelchair access. |
|||
| siri:VehicleDimensionsGroup |
|
0:1 |
The length of a VEHICLE of the type. |
||
|
|
0:1 |
The width of a VEHICLE of the type. |
|||
|
|
0:1 |
The length of a VEHICLE of the type. |
|||
|
|
0:1 |
The weight of a VEHICLE of the type. |
|||
| siri:VehicleTypeGroup |
|
0:1 |
Facilities of VEHICLE TYPE. |
||
19.118. The complex type siri:TrainInCompoundTrainStructure
|
|
Type for a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
||||
|
|
0:1 |
Identifier for TRAIN IN COMPOUND TRAIN. |
|||
|
|
1:1 |
Specifies the order of the TRAIN within the COMPOUND TRAIN. |
|||
| siri:TrainInCompoundTrainGroup |
|
0:1 |
Specifies how the TRAIN is labeled within the context of the COMPOUND TRAIN. This advertised label or number, e.g. the individual TRAIN NUMBER, can be used for seat reservations and passenger orientation. |
||
|
|
0:1 |
Description of TRAIN IN COMPOUND TRAIN. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-1:1 |
A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1) |
|||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
| siri:TrainInCompoundTrainGroup |
|
0:1 |
Whether orientation of TRAIN within COMPOUND TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel). |
||
|
|
0:1 |
Specifies whether a passage from/to an adjacent TRAIN is possible for passengers. |
|||
19.119. The complex type siri:TrainStructure
|
|
Type for TRAIN. (since SIRI 2.1) |
||||
|
|
0:1 |
Identifier for TRAIN. |
|||
| siri:VehicleTypeGroup |
|
0:1 |
Name of VEHICLE TYPE. |
||
|
|
0:1 |
Short Name of VEHICLE TYPE. |
|||
|
|
0:1 |
Description of VEHICLE TYPE. |
|||
|
|
0:1 |
||||
| siri:VehicleTypePropertiesGroup |
|
0:1 |
Whether vehicles of the type have a reversing direction. |
||
|
|
0:1 |
Whether vehicles of the type are self-propelled. |
|||
|
|
0:1 |
The type of fuel used by a vehicle of the type. |
|||
|
|
0:1 |
Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN). |
|||
|
|
0:1 |
Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry. |
|||
| siri:VehicleAccessibilityRequirementsGroup |
|
0:1 |
Whether Vehicle is low floor to facilitate access by the mobility impaired. |
||
|
|
0:1 |
Whether vehicle has lift or ramp to facilitate wheelchair access. |
|||
|
|
0:1 |
Whether vehicle has hoist for wheelchair access. |
|||
| siri:VehicleDimensionsGroup |
|
0:1 |
The length of a VEHICLE of the type. |
||
|
|
0:1 |
The width of a VEHICLE of the type. |
|||
|
|
0:1 |
The length of a VEHICLE of the type. |
|||
|
|
0:1 |
The weight of a VEHICLE of the type. |
|||
| siri:VehicleTypeGroup |
|
0:1 |
Facilities of VEHICLE TYPE. |
||
| siri:TrainGroup |
|
0:1 |
Number of cars needed in TRAIN. |
||
|
|
0:1 |
Nature of TRAIN size, e.g "short", "long", "normal". Default is "normal". |
|||
|
|
0:1 |
Ordered collection of TRAIN COMPONENTs making up the TRAIN. |
|||
19.120. The complex type siri:VehicleInFormationStatusStructure
|
|
Description of the status of a monitored vehicle. |
||||
|
|
1:1 |
Status of vehicle. |
|||
| siri:FormationStatusInfoGroup |
|
0:* |
Description of the status of a formation or a vehicle within the formation. |
||
|
|
0:1 |
Accessibility of the formation or a vehicle within the formation. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
19.121. The complex type siri:VehicleOccupancyStructure
|
|
Real-time occupancies of a VEHICLE (by fare class). Could be feedback from an automatic passenger counting system (APC) or estimated values from statistics. (since SIRI 2.1) |
||||
| siri:TrainFormationReferenceGroup |
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
|||
|
0:1 |
Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) |
||||
| siri:OccupancyScopeFilterGroup |
|
0:1 |
Fare class in VEHICLE for which occupancy or capacities are specified. |
||
|
|
0:1 |
Adult, child, wheelchair etc. |
|||
| siri:OccupancyValuesGroup |
|
0:1 |
An approximate figure of how occupied or full a VEHICLE and its parts are, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. More accurate data can be provided by the individual occupancies or capacities below. |
||
|
|
0:1 |
Utilised percentage of maximum payload after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of alighting passengers for this vehicle journey at this STOP POINT. |
|||
|
|
0:1 |
Total number of boarding passengers for this vehicle journey at this STOP POINT. |
|||
|
|
0:1 |
Total number of passengers on-board after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of special places, e.g. seats for the disabled or lounge seats, that are occupied after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of pushchairs on-board after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of wheelchairs on-board after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of prams on-board after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT. |
|||
|
|
0:1 |
Total number of booked seats from individual and group reservations. |
|||
|
|
0:* |
Reservations of travel groups, i.e., name of group and number of seats booked. |
|||
19.122. The complex type siri:VehicleOrientationRelativeToQuay
|
|
A restriction of W3C XML Schema's string that requires at least one character of text. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
lang (as an attribute name) denotes an attribute whose value is a language code for the natural language of the content of any element; its value is inherited. This name is reserved by virtue of its definition in the XML specification. Notes Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See BCP 47 at http://www.rfc-editor.org/rfc/bcp/bcp47.txt and the IANA language subtag registry at http://www.iana.org/assignments/language-subtag-registry for further information. The union allows for the 'un-declaration' of xml:lang with the empty string. |
|||
19.123. The complex type siri:ViaNameStructure
|
|
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Reference to a TOPOGRAPHIC PLACE. |
|||
|
|
0:* |
Names of place used to help identify the LINE. |
|||
|
|
0:* |
Short name of TOPOGRAPHIC PLACE. Should only be included if the detail level was requested. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Relative priority to give to VIA name in displays. 1=high. Default is 2. (since SIRI 2.0) |
|||
19.124. The complex type group[siri:JourneyRelationInfoGroup]/JourneyParts#complexType (typedef-25.1)
|
|
- |
||||
|
|
1:* |
Information about related parts of JOURNEY. (since SIRI 2.1) |
|||
19.125. The complex type group[siri:JourneyFormationGroup]/TrainElements#complexType (typedef-25.2)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-1:1 |
An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1) |
|||
19.126. The complex type group[siri:JourneyFormationGroup]/Trains#complexType (typedef-25.3)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1) |
|||
19.127. The complex type group[siri:JourneyFormationGroup]/CompoundTrains#complexType (typedef-25.4)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1) TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. |
|||
19.128. The complex type group[siri:TrainGroup]/TrainComponents#complexType (typedef-25.5)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
|||
|
b |
-1:1 |
Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. (since SIRI 2.1) |
|||
19.129. The complex type complexType[siri:CompoundTrainStructure]/TrainsInCompoundTrain#complexType (typedef-25.6)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
b |
-1:1 |
Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. (since SIRI 2.1) |
|||
19.130. The complex type group[siri:TrainInCompoundTrainGroup]/Passages#complexType (typedef-25.7)
|
|
- |
||||
|
|
1:2 |
||||
19.131. The complex type group[siri:VehicleTypeGroup]/Facilities#complexType (typedef-25.8)
|
|
- |
||||
|
The element contains one or more of the following elements (a-c) |
|||||
|
a |
-1:1 |
Vehicle Feature description. |
|||
|
b |
|
-1:1 |
|||
|
c |
-1:1 |
Reference to a Facility. |
|||
19.132. The complex type group[siri:VehicleTypePropertiesGroup]/MaximumPassengerCapacities#complexType (typedef-25.9)
|
|
- |
||||
|
|
1:* |
||||
20. SIRI Journey Model Identifiers.
20.1. Simple type definitions
|
|
Allowed types activity for Alighting. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an BLOCK. |
|||||||||||||||||||||||
|
|
Allowed types activity for Boarding and Alighting. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
Classification of the timeliness of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. (since SIRI 2.1) |
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a COURSE OF JOURNEY (Run). |
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a data VERSION FRAME. |
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a Dated VEHICLE JOURNEY. |
|||||||||||||||||||||||
|
|
Allowed types activity for Boarding. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. (since SIRI 2.1) |
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a Realtime VEHICLE JOURNEY. Used for adhoc journeys. |
|||||||||||||||||||||||
|
|
Values for Fare Class Facility. (since SIRI 2.1) |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
List of values for FARE CLASSes. (since SIRI 2.1) |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
Allowed types activity for FirstOrLastJourney. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
Allowed values for FORMATION CHANGE CODE. (since SIRI 2.1) |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifer of a SERVICE JOURNEY INTERCHANGE. |
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an JOURNEY PART |
|||||||||||||||||||||||
|
|
Allowed types of relation between JOURNEYs. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
Allowed values for PredictionInaccurateReason, i.e., possible reasons for a change in prediction (in)accuracy. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
Classification of the rate of progress of VEHICLE according a fixed list of values. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
Classification of the quality of the prediction of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are stiull classified as on-time. Applications may use this to guide their own presentation of times. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. (since SIRI 2.1) |
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. (since SIRI 2.1) |
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). (since SIRI 2.1) |
|||||||||||||||||||||||
|
|
Allowed values for TYPE OF TRAIN ELEMENT. (since SIRI 2.1) |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. (since SIRI 2.1) |
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an TRAIN NUMBER |
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of Train Part. |
|||||||||||||||||||||||
|
|
Allowed values for TRAIN SIZE. (since SIRI 2.1) |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
Allowed values for TYPE OF FUEL. (since SIRI 2.1) |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. (since SIRI 2.1) |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
Allowed values for VEHICLE IN FORMATION STATUS CODE. (since SIRI 2.1) |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a VEHICLE JOURNEY. |
|||||||||||||||||||||||
|
|
Classification of the State of the VEHICLE JOURNEY according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
||||||||||||||||||||||||
|
|||||||||||||||||||||||||
20.2. The toplevel element siri:CompoundTrainRef
|
|
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
||||
20.3. The toplevel element siri:DatedVehicleJourneyRef
|
|
Reference to a DATED VEHICLE JOURNEY. |
||||
20.4. The toplevel element siri:DestinationRef
|
|
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
20.5. The toplevel element siri:EntranceToVehicleRef
|
|
Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) |
||||
20.6. The toplevel element siri:FareClass
|
|
Classification of FARE CLASSes. (since SIRI 2.1) |
||||
20.7. The toplevel element siri:FareClasses
|
|
List of FARE CLASSes. (since SIRI 2.1) |
||||
20.8. The toplevel element siri:InterchangeRef
|
|
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
20.9. The toplevel element siri:OriginRef
|
|
Reference to the origin SCHEDULED STOP POINT of the journey. |
||||
20.10. The toplevel element siri:TrainComponentRef
|
|
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
||||
20.11. The toplevel element siri:TrainElementRef
|
|
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
||||
20.12. The toplevel element siri:TrainInCompoundTrainRef
|
|
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
||||
20.13. The toplevel element siri:TrainRef
|
|
Reference to a TRAIN. (since SIRI 2.1) |
||||
20.14. The toplevel element siri:VehicleJourneyRef
|
|
Reference to a VEHICLE JOURNEY. |
||||
20.15. The toplevel element siri:ViaRef
|
|
Reference to a SCHEDULED STOP POINT that is a VIA point on the journey. |
||||
20.16. The group siri:BasicServiceInfoGroup
|
|
Information that classifies journey. |
||||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
20.17. The group siri:JourneyIdentityGroup
|
|
Elements identifying VEHICLE JOURNEY. |
||||
| siri:JourneyIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a DIRECTION, typically outward or return. |
|||
|
|
0:1 |
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. |
|||
20.18. The group siri:MonitoredJourneyIdentityGroup
|
|
Elements identifying a VEHICLE JOURNEY. LINE and DIRECTION will be same as for journey unless overridden. |
||||
| siri:MonitoredJourneyIdentityGroup |
|
0:1 |
Reference to LINE of journey. |
||
|
|
0:1 |
Reference to DIRECTION of journey. |
|||
|
|
0:1 |
A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. |
|||
20.19. The group siri:ServiceInfoGroup
|
|
Elements classifying the Service or journey. Values for these elements can be specified on a timetabled schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each monitored journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. |
||||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
20.20. The group siri:TrainFormationReferenceGroup
|
|
Groups together the relevant references needed in a formation. (since SIRI 2.1) Has the following uses: - Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. - If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. - In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced. |
||||
| siri:TrainFormationReferenceGroup |
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-0:1 |
Reference to a TRAIN COMPONENT. (since SIRI 2.1) |
|||
|
0:1 |
Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) |
||||
20.21. The complex type siri:BlockRefStructure
|
|
Type for identifier of an BLOCK. |
||||
20.22. The complex type siri:CompoundTrainRefStructure
|
|
Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. (since SIRI 2.1) |
||||
20.23. The complex type siri:ConnectingJourneyRefStructure
|
|
Type for a reference to a connecting journey. |
||||
|
|
0:1 |
A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. |
|||
|
|
0:1 |
Identify a VEHICLE JOURNEY indirectly by origin and destination as well as the scheduled times at these stops. |
|||
|
|
0:1 |
Reference to LINE of journey. |
|||
|
|
0:1 |
Reference to TRAIN NUMBER of journey. |
|||
|
|
0:1 |
Reference to OPERATOR of journey. |
|||
|
|
0:1 |
PARTICIPANT reference that identifies data producer of journey. |
|||
20.24. The complex type siri:CourseOfJourneyRefStructure
|
|
Type for identifier of a COURSE OF JOURNEY (Run). |
||||
20.25. The complex type siri:DataFrameRefStructure
|
|
Type for identifier of a data VERSION FRAME. |
||||
20.26. The complex type siri:DatedVehicleJourneyIndirectRefStructure
|
|
Type for Origin and Destination stop of a VEHICLE JOURNEY. |
||||
|
|
1:1 |
The origin is used to help identify the VEHICLE JOURNEY. |
|||
|
|
1:1 |
Departure time from origin SCHEDULED STOP POINT. |
|||
|
|
1:1 |
The destination is used to help identify the VEHICLE JOURNEY. |
|||
|
|
1:1 |
Arrival time at destination SCHEDULED STOP POINT. |
|||
20.27. The complex type siri:DatedVehicleJourneyRefStructure
|
|
Type for identifier of a Dated VEHICLE JOURNEY. |
||||
20.28. The complex type siri:DestinationRefStructure
|
|
Type for identifier of a DESTINATION. |
||||
20.29. The complex type siri:EntranceToVehicleRefStructure
|
|
Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. (since SIRI 2.1) |
||||
20.30. The complex type siri:FramedVehicleJourneyRefStructure
|
|
Type for identifer of a VEHICLE JOURNEY within data Horizon of a service. |
||||
|
|
1:1 |
identifier of data frame within particpant service. Used to ensure that the Reference to a DATED VEGICLE JOURNEY is unique with the data horizon of the service. Often the OperationalDayType is used for this purpose. |
|||
|
|
1:1 |
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. |
|||
20.31. The complex type siri:InterchangeRefStructure
|
|
Type for identifer of a SERVICE JOURNEY INTERCHANGE. |
||||
20.32. The complex type siri:JourneyPartRefStructure
|
|
Type for identifier of an JOURNEY PART |
||||
20.33. The complex type siri:TrainComponentRefStructure
|
|
Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. (since SIRI 2.1) |
||||
20.34. The complex type siri:TrainElementRefStructure
|
|
Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). (since SIRI 2.1) |
||||
20.35. The complex type siri:TrainInCompoundTrainRefStructure
|
|
Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. (since SIRI 2.1) |
||||
20.36. The complex type siri:TrainNumberRefStructure
|
|
Type for identifier of an TRAIN NUMBER |
||||
20.37. The complex type siri:TrainPartRefStructure
|
|
Type for identifier of Train Part. |
||||
20.38. The complex type siri:TrainRefStructure
|
|
Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. (since SIRI 2.1) |
||||
20.39. The complex type siri:VehicleJourneyRefStructure
|
|
Type for identifier of a VEHICLE JOURNEY. |
||||
21. siri_modelPermissions.xsd
21.1. The toplevel element siri:CheckConnectionLinkRef
|
|
|
If access control is supported, whether access control by CONNECTION link is supported. Default is 'true'. |
|||
21.2. The toplevel element siri:CheckLineRef
|
|
|
If access control is supported, whether access control by LINE is supported. Default is 'true'. |
|||
21.3. The toplevel element siri:CheckMonitoringRef
|
|
|
If access control is supported, whether access control by monitoring point (LOGICAL DISPLAY) is supported. Default is 'true'. |
|||
21.4. The toplevel element siri:CheckOperatorRef
|
|
|
If access control is supported, whether access control by OPERATOR is supported. Default is 'true'. |
|||
21.5. The toplevel element siri:ConnectionLinkPermissions
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this CONNECTION link. |
||
21.6. The toplevel element siri:FilterByConnectionLinkRef
|
|
|
Whether results can be filtered by CONNECTION LINK. Default is 'true'. |
|||
21.7. The toplevel element siri:FilterByDestination
|
|
|
Whether results can be filtered by DESTINATION. Default is 'false'. |
|||
21.8. The toplevel element siri:FilterByDirectionRef
|
|
|
Whether results can be filtered by DIRECTION Default is 'true'. |
|||
21.9. The toplevel element siri:FilterByFacilityRef
|
|
|
Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'. |
|||
21.10. The toplevel element siri:FilterByInterchangeRef
|
|
|
Whether results can be filtered by SERVICE JOURNEY INTERCHANGE. Default is 'false'. |
|||
21.11. The toplevel element siri:FilterByLineRef
|
|
|
Whether results can be filtered by LINE. Default is 'true' |
|||
21.12. The toplevel element siri:FilterByMonitoringRef
|
|
|
Whether results can be filtered by Monitoring point (LOGICAL DISPLAY). Fixed as 'true'. |
|||
21.13. The toplevel element siri:FilterByOperatorRef
|
|
|
Whether results can be filtered by OPERATOR. Default is 'true'. |
|||
21.14. The toplevel element siri:FilterByProductCategoryRef
|
|
|
Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. (since SIRI 2.1) |
|||
21.15. The toplevel element siri:FilterByStopPointRef
|
|
|
Whether results can be filtered by SCHEDULED STOP POINT. Default is 'true'. |
|||
21.16. The toplevel element siri:FilterByValidityPeriod
|
|
|
Whether results can be filtered by VALIDITY PERIOD. Default is 'true'. |
|||
21.17. The toplevel element siri:FilterByVehicleJourneyRef
|
|
|
Whether results can be filtered by VEHICLE JOURNEY. Default is 'false'. |
|||
21.18. The toplevel element siri:FilterByVehicleMode
|
|
|
Whether results can be filtered by VEHICLE MODE. Default is 'true'. (since SIRI 2.1) |
|||
21.19. The toplevel element siri:FilterByVehicleRef
|
|
|
Whether results can be filtered by VEHICLE. Default is 'false'. |
|||
21.20. The toplevel element siri:LinePermissions
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this LINE. |
||
21.21. The toplevel element siri:OperatorPermissions
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this OPERATOR. |
||
21.22. The toplevel element siri:ProductionTimetablePermission
|
|
Permission for a single participant or all participants to use an aspect of the service. |
||||
21.23. The complex type siri:ConnectionCapabilityAccessControlStructure
|
|
Type for Common Access control capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether access control of requests is supported. Default is 'false'. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
If access control is supported, whether access control by OPERATOR is supported. Default is 'true'. |
||||
|
0:1 |
If access control is supported, whether access control by LINE is supported. Default is 'true'. |
||||
|
0:1 |
If access control is supported, whether access control by CONNECTION link is supported. Default is 'true'. |
||||
21.24. The complex type siri:ConnectionLinkPermissionStructure
|
|
Type for Abstract Permission Topic. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether the participant may access this topic. Default is 'true'. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a CONNECTION link for which permission is made. |
|||
21.25. The complex type siri:ConnectionServicePermissionStructure
|
|
Type for Abstract Permission. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. |
||
|
b |
|
-1:1 |
Permission applies to specified participant. |
||
|
|
0:1 |
Permissions for general capabilities. |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
The OPERATOR data that the participant may access. |
||||
|
1:1 |
The LINEs that the participant may access. |
||||
|
1:1 |
The CONNECTION links that the participant may access. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
21.26. The complex type siri:LinePermissionStructure
|
|
Type for Abstract Permission Topic. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether the participant may access this topic. Default is 'true'. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a LINE. whose data participant is allowed to access. |
|||
|
|
0:* |
Reference to a DIRECTION of LINE. that participant is allowed to access. |
|||
21.27. The complex type siri:MonitoringCapabilityAccessControlStructure
|
|
Type for Common Access control capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether access control of requests is supported. Default is 'false'. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
If access control is supported, whether access control by OPERATOR is supported. Default is 'true'. |
||||
|
0:1 |
If access control is supported, whether access control by LINE is supported. Default is 'true'. |
||||
|
0:1 |
If access control is supported, whether access control by monitoring point (LOGICAL DISPLAY) is supported. Default is 'true'. |
||||
21.28. The complex type siri:OperatorPermissionStructure
|
|
Type for Abstract Permission Topic. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether the participant may access this topic. Default is 'true'. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to an OPERATOR whose data participant is allowed to access. |
|||
21.29. The complex type siri:PermissionsStructure
|
|
Type for abstract permissions. |
||||
|
|
0:1 |
Version of permission set. |
|||
21.30. The complex type siri:StopMonitorPermissionStructure
|
|
Type for Abstract Permission Topic. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether the participant may access this topic. Default is 'true'. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a Stop Monitoring point (LOGICAL DISPLAY) to which permission applies. |
|||
21.31. The complex type element[siri:LinePermissions]#complexType (typedef-21.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this LINE. |
||
21.32. The complex type element[siri:OperatorPermissions]#complexType (typedef-21.2)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this OPERATOR. |
||
21.33. The complex type element[siri:ConnectionLinkPermissions]#complexType (typedef-21.3)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this CONNECTION link. |
||
21.34. The complex type complexType[siri:AbstractPermissionStructure]/GeneralCapabilities#complexType (typedef-45.1)
|
|
- |
||||
|
|
1:1 |
Participant may make direct requests for data. Default is 'true'. |
|||
|
|
1:1 |
Participant may create subscriptions. Default True. |
|||
22. SIRI TRANSPORT MODEs
22.1. Simple type definitions
|
|
Values for Air ModesOfTransport: TPEG pti_table_08 and pts_table_108. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for Bus ModesOfTransport: TPEG pti_table_05, pts_table_105 and loc_table_10. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for Coach ModesOfTransport: TPEG pti_table_03 and pts_table_103. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for Funicular ModesOfTransport: TPEG pti_table_10. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for Metro ModesOfTransport: TPEG pti_table_04 and pts_table_104. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for Rail ModesOfTransport: TPEG pti_table_02, pts_table_102 "RailwayService" and train link loc_table_13. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for SelfDrive ModesOfTransport: TPEG pti_table_12. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for Taxi ModesOfTransport: TPEG pti_table_11. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for Telecabin ModesOfTransport: TPEG pti_table_09, pts_table_109 and loc_table_14. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for Tram ModesOfTransport: TPEG pti_table_06, pts_table_104 and loc_table_12. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for ModesOfTransport : TPEG Pti01 and Pts001 "ModeOfTransport". |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for Water ModesOfTransport: TPEG pti_table_07 and pts_table_107. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
22.2. The toplevel element siri:AirSubmode
|
|
TPEG Pti08 and Pts108 "AirService" submodes. |
||||
22.3. The toplevel element siri:BusSubmode
|
|
TPEG Pti05 and Pts105 "BusService" submodes. |
||||
22.4. The toplevel element siri:CoachSubmode
|
|
TPEG Pti03 and Pts103 "CoachService" submodes. |
||||
22.5. The toplevel element siri:FunicularSubmode
|
|
TPEG pti10 Funicular submodes. |
||||
22.6. The toplevel element siri:MetroSubmode
|
|
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
||||
22.7. The toplevel element siri:RailSubmode
|
|
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
||||
22.8. The toplevel element siri:SelfDriveSubmode
|
|
TPEG pti12 SelfDrive submodes. |
||||
22.9. The toplevel element siri:TaxiSubmode
|
|
TPEG pti11 Taxi submodes. |
||||
22.10. The toplevel element siri:TelecabinSubmode
|
|
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
||||
22.11. The toplevel element siri:TramSubmode
|
|
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
||||
22.12. The toplevel element siri:VehicleMode
|
|
Vehicle mode or mode of transport. |
||||
22.13. The toplevel element siri:WaterSubmode
|
|
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
||||
22.14. The group siri:ModeChoiceGroup
|
|
Transport Sub Modes. |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ai) |
|||||
| siri:PtModeChoiceGroup |
aa |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
ab |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
ac |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
ad |
-1:1 |
TPEG pti10 Funicular submodes. |
|||
|
ae |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
af |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
ag |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
|
ah |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
ai |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
|
In case of choice 'b', the element contains one of the following elements (ba-bb) |
|||||
| siri:PersonalModeChoiceGroup |
ba |
-1:1 |
TPEG pti11 Taxi submodes. |
||
|
bb |
-1:1 |
TPEG pti12 SelfDrive submodes. |
|||
22.15. The group siri:PersonalModeChoiceGroup
|
|
Non-PT Road Submodes. |
||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:PersonalModeChoiceGroup |
a |
-1:1 |
TPEG pti11 Taxi submodes. |
||
|
b |
-1:1 |
TPEG pti12 SelfDrive submodes. |
|||
22.16. The group siri:PtModeChoiceGroup
|
|
PT Transport Sub Modes. |
||||
|
The element contains one of the following elements (a-i) |
|||||
| siri:PtModeChoiceGroup |
a |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
b |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
c |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
d |
-1:1 |
TPEG pti10 Funicular submodes. |
|||
|
e |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
f |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
g |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
|
h |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
i |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
22.17. The group siri:PtNetworkModeChoiceGroup
|
|
Submode of mode. |
||||
|
The element contains one of the following elements (a-h) |
|||||
| siri:PtNetworkModeChoiceGroup |
a |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
b |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
c |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
d |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
e |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
f |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
g |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
|
h |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
23. SIRI MONITORED VEHICLE JOURNEY Model.
23.1. The group siri:CallRailGroup
|
|
Elements describing theProperties specific to a rail CALLs. |
||||
| siri:CallRailGroup |
|
0:1 |
Whether VEHICLE will reverse at stop. Default is 'false'. |
||
|
|
0:1 |
For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform. If so Boarding Activity of arrival and deparure should be passthrough. |
|||
|
|
0:1 |
Status of signal clearance for TRAIN. This may affect the prioritiisition and emphasis given to arrival or departure on displays - e.g. cleared trains appear first, flashing in green. |
|||
23.2. The group siri:CallRealtimeGroup
|
|
Elements describing the Real-time CALL properties. |
||||
| siri:CallRealtimeGroup |
0:1 |
Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) |
|||
|
|
0:1 |
Exact location that VEHICLE will take up / or has taken at STOP POINT. |
|||
23.3. The group siri:DatedTrainOperationalInfoGroup
|
|
Operational information about the monitored VEHICLE JOURNEY. |
||||
| siri:DatedTrainOperationalInfoGroup |
|
0:* |
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. |
||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
| siri:DatedOperationalInfoGroup |
0:1 |
Reference to a VEHICLE. |
|||
| siri:DatedTrainOperationalInfoGroup |
|
0:1 |
TRAIN NUMBERs for journey. (since SIRI 2.0) |
||
|
|
0:1 |
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. |
|||
| siri:JourneyFormationGroup |
|
0:1 |
|||
|
|
0:1 |
||||
|
|
0:1 |
||||
23.4. The group siri:JourneyPartViewGroup
|
|
If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). (since SIRI 2.1) |
||||
| siri:JourneyPartViewGroup |
|
1:1 |
Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. |
||
|
|
1:1 |
Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. |
|||
|
|
0:1 |
Time at which the related JOURNEY PART begins. |
|||
|
|
0:1 |
Time at which the related JOURNEY PART ends. |
|||
23.5. The group siri:JourneyProgressGroup
|
|
Elements describing the real-time progress of a monitored VEHICLE JOURNEY. |
||||
| siri:JourneyProgressGroup |
|
0:1 |
Whether there is real-time information available for journey. Default is 'true'. It is recommended to specify a MonitoringError if Monitored is set to 'false'. |
||
|
|
0:1 |
If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. MonitoringError must not be used if Monitored is omitted or set to 'true'. |
|||
| siri:ProgressDataQualityGroup |
|
0:1 |
Whether the VEHICLE iis in traffic congestion. If not, present, not known. |
||
|
|
0:1 |
Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'. |
|||
|
0:1 |
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. |
||||
|
0:1 |
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) |
||||
|
|
0:1 |
System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. |
|||
|
|
0:1 |
Confidence QUALITY LEVEL of data. Default is 'reliable'. |
|||
| siri:ProgressDataGroup |
|
0:1 |
Current geospatial location of VEHICLE. Measured to front of vehicle. |
||
|
|
0:1 |
Time at which location was recorded. If not present assume that the recorded at time on the containing delivery. |
|||
|
|
0:1 |
Bearing in compass degrees in which VEHICLE is heading. |
|||
|
|
0:1 |
Rate of progress of VEHICLE. Default is 'normal' |
|||
|
|
0:1 |
Velocity of VEHICLE. EIther actual speed or average speed may be used. (since SIRI 2.0) |
|||
|
|
0:1 |
Whether the engine of the vehicle is on. Default is 'true' (since SIRI 2.0) |
|||
|
0:1 |
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. |
||||
|
|
0:1 |
Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. |
|||
|
|
0:* |
An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0) |
|||
|
|
0:1 |
An classification of the progress state of running of this VEHICLE JOURNEY. (since SIRI 2.0) |
|||
23.6. The group siri:MonitoredCallArrivalTimesGroup
|
|
Arrival times for CALL. |
||||
| siri:VehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of arrival of VEHICLE at stop. |
|||
|
b |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
| siri:MonitoredCallArrivalTimesGroup |
|
0:1 |
Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.0) |
||
23.7. The group siri:MonitoredCallDepartureTimesGroup
|
|
Departure times for CALL. |
||||
| siri:VehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of departure of VEHICLE from stop. |
|||
|
b |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
| siri:MonitoredCallDepartureTimesGroup |
|
0:1 |
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. (since SIRI 2.0). |
||
|
|
0:1 |
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. (since SIRI 2.0) |
|||
|
|
0:1 |
Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. (since SIRI 2.0) |
|||
23.8. The group siri:MonitoredCallGroup
|
|
Elements for a monitored CALL. |
||||
| siri:CallRealtimeGroup |
0:1 |
Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) |
|||
|
|
0:1 |
Exact location that VEHICLE will take up / or has taken at STOP POINT. |
|||
| siri:CallRailGroup |
|
0:1 |
Whether VEHICLE will reverse at stop. Default is 'false'. |
||
|
|
0:1 |
For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform. If so Boarding Activity of arrival and deparure should be passthrough. |
|||
|
|
0:1 |
Status of signal clearance for TRAIN. This may affect the prioritiisition and emphasis given to arrival or departure on displays - e.g. cleared trains appear first, flashing in green. |
|||
| siri:CallPropertyGroup |
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
|||
|
|
0:1 |
Whether this is a Hail and Ride Stop. Default is 'false'. |
|||
|
|
0:1 |
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. |
|||
|
|
0:* |
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0) |
|||
|
|
0:* |
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. |
|||
| siri:CallNoteGroup |
|
0:* |
Text annotation that applies to this CALL. |
||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
| siri:VehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of arrival of VEHICLE at stop. |
|||
|
b |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
| siri:MonitoredCallArrivalTimesGroup |
|
0:1 |
Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.0) |
||
| siri:MonitoredStopArrivalStatusGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:1 |
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:VehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of departure of VEHICLE from stop. |
|||
|
b |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
| siri:MonitoredCallDepartureTimesGroup |
|
0:1 |
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. (since SIRI 2.0). |
||
|
|
0:1 |
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. (since SIRI 2.0) |
|||
|
|
0:1 |
Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. (since SIRI 2.0) |
|||
| siri:PassengerDepartureTimesGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
||||
| siri:MonitoredStopDepartureStatusGroup |
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
|||
|
0:1 |
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
The element contains one of the following element sequences (a-b) |
|||||
|
a |
-0:* |
Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1) |
|||
|
a |
-0:* |
Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:HeadwayIntervalGroup |
0:1 |
For frequency based services, target interval between vehicles at stop. |
|||
|
0:1 |
For frequency based services, expected interval between vehicles at stop. |
||||
| siri:StopProximityGroup |
|
0:1 |
Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. (since SIRI 2.0). |
||
|
|
0:1 |
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. (since SIRI 2.0). |
|||
23.9. The group siri:MonitoredCallingPatternGroup
|
|
The service pattern of a monitored VEHICLE JOURNEY. CALLs should be assigned to one of three groups according to the vehicle's current position. |
||||
| siri:MonitoredCallingPatternGroup |
|
0:1 |
Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits. Should only be included if the detail level was requested. |
||
|
|
0:1 |
Monitored CALL at the current stop. For SIRI-SM this is the stop for which data is requested. For SIRI-VM this is the most recent stop visited by the VEHICLE. |
|||
|
|
0:1 |
Information on CALLs at the intermediate stops beyond the current stop, up to and including the destination, in order of visits. Should only be included if the detail level was requested. |
|||
|
|
0:1 |
Whether the above CALL sequence is complete, i.e. represents every CALL of the ROUTE and so can be used to replace a previous CALL sequence. Default is 'false'. |
|||
23.10. The group siri:ProgressDataGroup
|
|
Elements describing the real-time progress of a journey. |
||||
| siri:ProgressDataGroup |
|
0:1 |
Current geospatial location of VEHICLE. Measured to front of vehicle. |
||
|
|
0:1 |
Time at which location was recorded. If not present assume that the recorded at time on the containing delivery. |
|||
|
|
0:1 |
Bearing in compass degrees in which VEHICLE is heading. |
|||
|
|
0:1 |
Rate of progress of VEHICLE. Default is 'normal' |
|||
|
|
0:1 |
Velocity of VEHICLE. EIther actual speed or average speed may be used. (since SIRI 2.0) |
|||
|
|
0:1 |
Whether the engine of the vehicle is on. Default is 'true' (since SIRI 2.0) |
|||
|
0:1 |
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. |
||||
|
|
0:1 |
Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. |
|||
|
|
0:* |
An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0) |
|||
|
|
0:1 |
An classification of the progress state of running of this VEHICLE JOURNEY. (since SIRI 2.0) |
|||
23.11. The group siri:ProgressDataQualityGroup
|
|
Elements describing the qua;ity of real-time progress data of a journey. |
||||
| siri:ProgressDataQualityGroup |
|
0:1 |
Whether the VEHICLE iis in traffic congestion. If not, present, not known. |
||
|
|
0:1 |
Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'. |
|||
|
0:1 |
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. |
||||
|
0:1 |
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) |
||||
|
|
0:1 |
System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. |
|||
|
|
0:1 |
Confidence QUALITY LEVEL of data. Default is 'reliable'. |
|||
23.12. The group siri:ServicePointsGroup
|
|
Elements describing the main places bewteen which a VEHICLE JOURNEY runs. |
||||
| siri:ServicePointsGroup |
|
0:1 |
Origin of the VEHICLE JOURNEY. |
||
|
|
0:* |
VIA points for VEHICLE JOURNEY |
|||
|
|
0:1 |
Destination of VEHICLE JOURNEY. |
|||
23.13. The group siri:StopArrivalGroup
|
|
Elements describing the the arrival of a VEHICLE at a stop. |
||||
| siri:VehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of arrival of VEHICLE at stop. |
|||
|
b |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
| siri:MonitoredCallArrivalTimesGroup |
|
0:1 |
Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.0) |
||
| siri:MonitoredStopArrivalStatusGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:1 |
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
23.14. The group siri:StopDepartureGroup
|
|
Elements describing the the departure of a VEHICLE from a stop. |
||||
| siri:VehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of departure of VEHICLE from stop. |
|||
|
b |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
| siri:MonitoredCallDepartureTimesGroup |
|
0:1 |
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. (since SIRI 2.0). |
||
|
|
0:1 |
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. (since SIRI 2.0) |
|||
|
|
0:1 |
Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. (since SIRI 2.0) |
|||
| siri:PassengerDepartureTimesGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
||||
| siri:MonitoredStopDepartureStatusGroup |
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
|||
|
0:1 |
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
The element contains one of the following element sequences (a-b) |
|||||
|
a |
-0:* |
Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1) |
|||
|
a |
-0:* |
Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
23.15. The group siri:TrainOperationalInfoGroup
|
|
Operational information about the monitored VEHICLE JOURNEY. |
||||
| siri:TrainOperationalInfoGroup |
|
0:* |
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. |
||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
| siri:OperationalInfoGroup |
0:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a VEHICLE. |
||||
|
|
0:* |
Refercence to other VEHICLE Journeys ((since SIRI 2.0)) |
|||
|
|
0:1 |
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. (since SIRI 2.0) |
|||
|
|
0:1 |
The name oo the Driver or Crew (since SIRI 2.0) |
|||
| siri:TrainOperationalInfoGroup |
|
0:1 |
TRAIN NUMBERs for journey. (since SIRI 2.0) |
||
|
|
0:1 |
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. |
|||
| siri:JourneyFormationGroup |
|
0:1 |
|||
|
|
0:1 |
||||
|
|
0:1 |
||||
23.16. The complex type siri:DatedJourneyPartInfoStructure
|
|
Type for a reference to JOURNEY PART. (since SIRI 2.1) |
||||
|
|
0:1 |
Reference to a JOURNEY part. |
|||
|
|
0:1 |
Train Number for JOURNEY PART. |
|||
|
|
0:1 |
OPERATOR of JOURNEY PART. |
|||
|
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
||||
| siri:JourneyPartViewGroup |
|
1:1 |
Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. |
||
|
|
1:1 |
Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. |
|||
|
|
0:1 |
Time at which the related JOURNEY PART begins. |
|||
|
|
0:1 |
Time at which the related JOURNEY PART ends. |
|||
23.17. The complex type siri:JourneyPartInfoStructure
|
|
Type for a reference to JOURNEY PART. (since SIRI 2.0) |
||||
|
|
0:1 |
Reference to a JOURNEY part. (since SIRI 2.0) |
|||
|
|
0:1 |
Train Number for JOURNEY PART (since SIRI 2.0) |
|||
|
|
0:1 |
OPERATOR of JOURNEY PART. (since SIRI 2.0) |
|||
|
0:1 |
Reference to a COMPOUND TRAIN. (since SIRI 2.1) |
||||
| siri:JourneyPartViewGroup |
|
1:1 |
Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. |
||
|
|
1:1 |
Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. |
|||
|
|
0:1 |
Time at which the related JOURNEY PART begins. |
|||
|
|
0:1 |
Time at which the related JOURNEY PART ends. |
|||
23.18. The complex type siri:MonitoredCallStructure
|
|
Type for Abstract CALL at stop. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
Inherited content is followed by own content: |
|||||
| siri:CallRealtimeGroup |
0:1 |
Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) |
|||
|
|
0:1 |
Exact location that VEHICLE will take up / or has taken at STOP POINT. |
|||
| siri:CallRailGroup |
|
0:1 |
Whether VEHICLE will reverse at stop. Default is 'false'. |
||
|
|
0:1 |
For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform. If so Boarding Activity of arrival and deparure should be passthrough. |
|||
|
|
0:1 |
Status of signal clearance for TRAIN. This may affect the prioritiisition and emphasis given to arrival or departure on displays - e.g. cleared trains appear first, flashing in green. |
|||
| siri:CallPropertyGroup |
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
|||
|
|
0:1 |
Whether this is a Hail and Ride Stop. Default is 'false'. |
|||
|
|
0:1 |
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. |
|||
|
|
0:* |
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0) |
|||
|
|
0:* |
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. |
|||
| siri:CallNoteGroup |
|
0:* |
Text annotation that applies to this CALL. |
||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
| siri:VehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of arrival of VEHICLE at stop. |
|||
|
b |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
| siri:MonitoredCallArrivalTimesGroup |
|
0:1 |
Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.0) |
||
| siri:MonitoredStopArrivalStatusGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:1 |
Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0) |
||||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:VehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of departure of VEHICLE from stop. |
|||
|
b |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
| siri:MonitoredCallDepartureTimesGroup |
|
0:1 |
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected Departure time. (since SIRI 2.0). |
||
|
|
0:1 |
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. (since SIRI 2.0) |
|||
|
|
0:1 |
Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. (since SIRI 2.0) |
|||
| siri:PassengerDepartureTimesGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
||||
| siri:MonitoredStopDepartureStatusGroup |
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
|||
|
0:1 |
Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1) |
||||
|
0:1 |
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0) |
||||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1) Examples: - "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D". - "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). It is advised to specify a reference point that is meaningful for passengers on location. |
||||
|
The element contains one of the following element sequences (a-b) |
|||||
|
a |
-0:* |
Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1) |
|||
|
a |
-0:* |
Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
|||
|
b |
-0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
|||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:HeadwayIntervalGroup |
0:1 |
For frequency based services, target interval between vehicles at stop. |
|||
|
0:1 |
For frequency based services, expected interval between vehicles at stop. |
||||
| siri:StopProximityGroup |
|
0:1 |
Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. (since SIRI 2.0). |
||
|
|
0:1 |
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. (since SIRI 2.0). |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
23.19. The complex type siri:MonitoredVehicleJourneyStructure
|
|
Type for Monitored VEHICLE JOURNEY. |
||||
| siri:MonitoredJourneyIdentityGroup |
|
0:1 |
Reference to LINE of journey. |
||
|
|
0:1 |
Reference to DIRECTION of journey. |
|||
|
|
0:1 |
A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
| siri:JourneyInfoGroup |
|
0:* |
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) |
||
|
0:* |
Additional descriptive text associated with journey. Inherited property. |
||||
|
|
0:1 |
Contact details for use by members of public. (since SIRI 2.0) |
|||
|
|
0:1 |
Contact details for use by operational staff. (since SIRI 2.0) |
|||
| siri:JourneyEndTimesGroup |
|
0:1 |
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. |
||
|
|
0:1 |
Timetabled departure time from Origin. |
|||
|
|
0:1 |
Timetabled arrival time at Destination. |
|||
|
0:1 |
Whether journey is first or last journey of day. (since SIRI 2.0) |
||||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
| siri:JourneyProgressGroup |
|
0:1 |
Whether there is real-time information available for journey. Default is 'true'. It is recommended to specify a MonitoringError if Monitored is set to 'false'. |
||
|
|
0:1 |
If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. MonitoringError must not be used if Monitored is omitted or set to 'true'. |
|||
| siri:ProgressDataQualityGroup |
|
0:1 |
Whether the VEHICLE iis in traffic congestion. If not, present, not known. |
||
|
|
0:1 |
Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'. |
|||
|
0:1 |
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. |
||||
|
0:1 |
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) |
||||
|
|
0:1 |
System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. |
|||
|
|
0:1 |
Confidence QUALITY LEVEL of data. Default is 'reliable'. |
|||
| siri:ProgressDataGroup |
|
0:1 |
Current geospatial location of VEHICLE. Measured to front of vehicle. |
||
|
|
0:1 |
Time at which location was recorded. If not present assume that the recorded at time on the containing delivery. |
|||
|
|
0:1 |
Bearing in compass degrees in which VEHICLE is heading. |
|||
|
|
0:1 |
Rate of progress of VEHICLE. Default is 'normal' |
|||
|
|
0:1 |
Velocity of VEHICLE. EIther actual speed or average speed may be used. (since SIRI 2.0) |
|||
|
|
0:1 |
Whether the engine of the vehicle is on. Default is 'true' (since SIRI 2.0) |
|||
|
0:1 |
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. |
||||
|
|
0:1 |
Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. |
|||
|
|
0:* |
An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0) |
|||
|
|
0:1 |
An classification of the progress state of running of this VEHICLE JOURNEY. (since SIRI 2.0) |
|||
| siri:TrainOperationalInfoGroup |
|
0:* |
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. |
||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
| siri:OperationalInfoGroup |
0:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a VEHICLE. |
||||
|
|
0:* |
Refercence to other VEHICLE Journeys ((since SIRI 2.0)) |
|||
|
|
0:1 |
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. (since SIRI 2.0) |
|||
|
|
0:1 |
The name oo the Driver or Crew (since SIRI 2.0) |
|||
| siri:TrainOperationalInfoGroup |
|
0:1 |
TRAIN NUMBERs for journey. (since SIRI 2.0) |
||
|
|
0:1 |
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. |
|||
| siri:JourneyFormationGroup |
|
0:1 |
|||
|
|
0:1 |
||||
|
|
0:1 |
||||
| siri:MonitoredCallingPatternGroup |
|
0:1 |
Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits. Should only be included if the detail level was requested. |
||
|
|
0:1 |
Monitored CALL at the current stop. For SIRI-SM this is the stop for which data is requested. For SIRI-VM this is the most recent stop visited by the VEHICLE. |
|||
|
|
0:1 |
Information on CALLs at the intermediate stops beyond the current stop, up to and including the destination, in order of visits. Should only be included if the detail level was requested. |
|||
|
|
0:1 |
Whether the above CALL sequence is complete, i.e. represents every CALL of the ROUTE and so can be used to replace a previous CALL sequence. Default is 'false'. |
|||
23.20. The complex type siri:PreviousCallsStructure
|
|
Type for Ordered list of CALLs at previous stop. |
||||
|
|
1:* |
||||
23.21. The complex type siri:PreviousCallStructure
|
|
Type for Abstract CALL at stop. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) |
||||
| siri:VehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of arrival of VEHICLE at stop. |
|||
|
b |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
| siri:VehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of departure of VEHICLE from stop. |
|||
|
b |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
|
0:* |
Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1) |
||||
|
0:* |
Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1) |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
23.22. The complex type siri:TrainBlockPartStructure
|
|
Type for BLOCK part elements of VEHICLE JOURNEY. |
||||
|
|
1:1 |
Total number of BLOCK parts making up the train of which this is part. |
|||
|
|
1:1 |
Reference to a train BLOCK part. |
|||
|
|
0:* |
Description of position of train BLOCK part within Train to guide passengers where to find it. E.g. 'Front four coaches'. |
|||
23.23. The complex type group[siri:JourneyFormationGroup]/TrainElements#complexType (typedef-25.2)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-1:1 |
An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1) |
|||
23.24. The complex type group[siri:JourneyFormationGroup]/Trains#complexType (typedef-25.3)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1) |
|||
23.25. The complex type group[siri:JourneyFormationGroup]/CompoundTrains#complexType (typedef-25.4)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1) TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. |
|||
23.26. The complex type group[siri:ServicePointsGroup]/Origin#complexType (typedef-39.1)
|
|
- |
||||
|
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
||||
|
0:1 |
The name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. |
||||
23.27. The complex type group[siri:ServicePointsGroup]/Via#complexType (typedef-39.2)
|
|
- |
||||
|
0:1 |
Reference to a SCHEDULED STOP POINT that is a VIA point on the journey. |
||||
|
0:1 |
Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
||||
|
|
0:1 |
Relative priority for incliding via in displays. 1 Is high 3 is low. (since SIRI 2.0) |
|||
23.28. The complex type group[siri:ServicePointsGroup]/Destination#complexType (typedef-39.3)
|
|
- |
||||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
0:1 |
The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public. Note when used in a CALL, this is the Dynamic Destination Display: since vehicles can change their destination during a journey, the destination included here should be what the VEHICLE will display when it reaches the stop. |
||||
23.29. The complex type group[siri:TrainOperationalInfoGroup]/TrainNumbers#complexType (typedef-39.4)
|
|
- |
||||
|
|
1:* |
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 |
|||
23.30. The complex type group[siri:TrainOperationalInfoGroup]/JourneyParts#complexType (typedef-39.5)
|
|
- |
||||
|
|
1:* |
Information about Parts of JOURNEY (since SIRI 2.0) |
|||
23.31. The complex type group[siri:DatedTrainOperationalInfoGroup]/TrainNumbers#complexType (typedef-39.6)
|
|
- |
||||
|
|
1:* |
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 |
|||
23.32. The complex type group[siri:DatedTrainOperationalInfoGroup]/JourneyParts#complexType (typedef-39.7)
|
|
- |
||||
|
|
1:* |
Information about Parts of JOURNEY (since SIRI 2.0) |
|||
24. OPERATOR types for SIRi.
24.1. Simple type definitions
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an OPERATOR Code. |
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an OrganisationCode. |
24.2. The complex type siri:OperatorRefStructure
|
|
Type for identifier of an OPERATOR Code. |
||||
24.3. The complex type siri:OrganisationRefStructure
|
|
Type for identifier of an OrganisationCode. |
||||
25. siri_reference.xsd
25.1. Simple type definitions
|
|
Union of VEHICLE and continuous MODEs. |
||||||||||||||||||||||
|
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a BOARDING POSITION (location on a QUAY where passengers can actually board/alight). |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a BRANDING. (since SIRI 2.1) |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Identifier of a Stop for Direct Cleardown. Suitable for radio transmission over a constrained bandwidth channel. This may be a separate code from the full stop identifier. |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a CONNECTION link |
|||||||||||||||||||||
|
|
MODEs of transport applicable to private and non-timetabled transport. |
||||||||||||||||||||||
|
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a DESTINATION. |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Identifier of a DIRECTION. |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Identifier of a DRIVER |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a FLEXIBLE AREA (area that encompasses the stop location of a flexible service). |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Identifier of a GROUP OF LINEs |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an Info Channel. |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a JOURNEY PATTERN. |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a LINE |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Identifier of a monitoring point. May correspond to a SCHEDULED STOP POINT or represent a group of Stops other Timing Points (i.e. LOGICAL DISPLAY) |
|||||||||||||||||||||
|
|
Passenger load status of a VEHICLE - GTFS-R / TPEG Pts045 |
||||||||||||||||||||||
|
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a QUAY (Platform, Bay, etc). |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a Route. |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Identifier of a ROUTE LINk. |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Identifier of a SITE |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a STOP AREA. |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a SCHEDULED STOP POINT. |
|||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Identifier of a VEHICLE. |
|||||||||||||||||||||
|
|
MODEs of transport applicable to timetabled public transport. |
||||||||||||||||||||||
|
|||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a Version. |
|||||||||||||||||||||
|
|
xs:positiveInteger: (empty restriction) |
Type for Stop Visit. |
|||||||||||||||||||||
25.2. The toplevel element siri:ConnectionLinkRef
|
|
Reference to a CONNECTION link |
||||
25.3. The toplevel element siri:JourneyPatternRef
|
|
Reference to a JOURNEY PATTERN. |
||||
25.4. The toplevel element siri:LineRef
|
|
Reference to a LINE. |
||||
25.5. The toplevel element siri:Order
|
|
|
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
|||
25.6. The toplevel element siri:PublishedLineName
|
|
Name or Number by which the LINEis known to the public. |
||||
25.7. The toplevel element siri:RouteName
|
|
Description of route by which it can be recogniozed. |
||||
25.8. The toplevel element siri:SiteRef
|
|
Reference to a SITE |
||||
25.9. The toplevel element siri:StopPointName
|
|
Name of SCHEDULED STOP POINT. |
||||
25.10. The toplevel element siri:StopPointRef
|
|
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
25.11. The toplevel element siri:TimingPoint
|
|
|
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
|||
25.12. The toplevel element siri:VehicleAtStop
|
|
|
Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) |
|||
25.13. The toplevel element siri:VehicleRef
|
|
Reference to a VEHICLE. |
||||
25.14. The toplevel element siri:VersionRef
|
|
Version Identifier. |
||||
25.15. The toplevel element siri:VisitNumber
|
|
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
25.16. The group siri:ContextualisedStopPointInSequenceGroup
|
|
Elements identifying Ordered visit to a stop within calling sequence of a SERVICE PATTERN. |
||||
| siri:ContextualisedStopPointInSequenceGroup |
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
25.17. The group siri:JourneyPatternInfoGroup
|
|
Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the journey. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each monitored journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. |
||||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
25.18. The group siri:JourneyPatternRefGroup
|
|
Elements describing the ROUTE and JOURNEY PATTERN Identfiers associated with a journey. |
||||
25.19. The group siri:LineDirectionGroup
|
|
Elements for a LINE and DIRECTION. |
||||
| siri:LineDirectionGroup |
|
1:1 |
Line Reference. |
||
|
|
0:1 |
Direction Reference. |
|||
25.20. The group siri:LineIdentityGroup
|
|
Elements for identifying a LINE and DIRECTION. |
||||
| siri:LineIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a LINE DIRECTION DIRECTION, typically outward or return. |
|||
25.21. The group siri:PublishedLineGroup
|
|
Elements describing the LINEand DESTINATION of a journey. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each real-time journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. |
||||
| siri:PublishedLineGroup |
0:* |
Name or Number by which the LINEis known to the public. |
|||
|
|
0:* |
Description of the destination stop (vehicle signage), if different from the that in timetable - the DESTINATION DISPLAY. Can be overwritten section by section by the entry in an individual CALL. |
|||
25.22. The group siri:StopPointGroup
|
|
Elements for a SCHEDULED STOP POINT. |
||||
| siri:StopPointGroup |
|
1:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||
|
|
0:* |
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) |
|||
25.23. The group siri:StopPointInSequenceGroup
|
|
Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN. |
||||
| siri:StopPointInSequenceGroup |
1:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:* |
Name of SCHEDULED STOP POINT. |
||||
25.24. The complex type siri:BoardingPositionRefStructure
|
|
Type for identifier of a BOARDING POSITION (location on a QUAY where passengers can actually board/alight). |
||||
25.25. The complex type siri:BrandingRefStructure
|
|
Type for identifier of a BRANDING. (since SIRI 2.1) |
||||
25.26. The complex type siri:BrandingStructure
|
|
An arbitrary marketing classification. (since SIRI 2.1) |
||||
|
|
1:1 |
Identity of BRANDING. |
|||
| siri:TypeOfValueGroup |
|
0:1 |
Name of TYPE OF VALUE. |
||
|
|
0:1 |
Short Name for TYPE OF VALUE. |
|||
|
|
0:1 |
Description of TYPE OF VALUE. |
|||
|
|
0:1 |
Default image for TYPE OF VALUE. |
|||
|
|
0:1 |
Default URL for TYPE OF VALUE. |
|||
|
|
0:1 |
Arbitrary code (usually the technical part of the identifier). |
|||
25.27. The complex type siri:ClearDownRefStructure
|
|
Identifier of a Stop for Direct Cleardown. Suitable for radio transmission over a constrained bandwidth channel. This may be a separate code from the full stop identifier. |
||||
25.28. The complex type siri:ConnectionLinkRefStructure
|
|
Type for identifier of a CONNECTION link |
||||
25.29. The complex type siri:DirectionRefStructure
|
|
Identifier of a DIRECTION. |
||||
25.30. The complex type siri:DriverRefStructure
|
|
Identifier of a DRIVER |
||||
25.31. The complex type siri:FlexibleAreaRefStructure
|
|
Type for identifier of a FLEXIBLE AREA (area that encompasses the stop location of a flexible service). |
||||
25.32. The complex type siri:GroupOfLinesRefStructure
|
|
Identifier of a GROUP OF LINEs |
||||
25.33. The complex type siri:InfoChannelRefStructure
|
|
Type for identifier of an Info Channel. |
||||
25.34. The complex type siri:JourneyPatternRefStructure
|
|
Type for identifier of a JOURNEY PATTERN. |
||||
25.35. The complex type siri:JourneyPlaceRefStructure
|
|
|
- |
|||
25.36. The complex type siri:LineDirectionStructure
|
|
Type for LINEand DIRECTION. |
||||
| siri:LineDirectionGroup |
|
1:1 |
Line Reference. |
||
|
|
0:1 |
Direction Reference. |
|||
25.37. The complex type siri:LineRefStructure
|
|
Type for identifier of a LINE |
||||
25.38. The complex type siri:ModesStructure
|
|
Type for Transport MODEs. |
||||
|
|
1:1 |
if true, listed modes to be excluded from list. |
|||
|
|
1:* |
A method of transportation such as bus, rail, etc. |
|||
25.39. The complex type siri:MonitoringRefStructure
|
|
Identifier of a monitoring point. May correspond to a SCHEDULED STOP POINT or represent a group of Stops other Timing Points (i.e. LOGICAL DISPLAY) |
||||
25.40. The complex type siri:NoteStructure
|
|
DataType for a NOTICe. |
||||
|
0:1 |
Reference to a SITUATION associated with the element. |
||||
|
0:1 |
Reference to a SITUATION associated with the element. |
||||
|
0:1 |
Reference to a SITUATION. Elements are retained as atomic elements. |
||||
|
|
0:1 |
Text annotation that applies to an element. |
|||
25.41. The complex type siri:PlaceNameStructure
|
|
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
||||
|
|
0:1 |
Reference to a TOPOGRAPHIC PLACE. |
|||
|
|
0:* |
Names of place used to help identify the LINE. |
|||
|
|
0:* |
Short name of TOPOGRAPHIC PLACE. Should only be included if the detail level was requested. |
|||
25.42. The complex type siri:QuayRefStructure
|
|
Type for identifier of a QUAY (Platform, Bay, etc). |
||||
25.43. The complex type siri:RouteLinkRefStructure
|
|
Identifier of a ROUTE LINk. |
||||
25.44. The complex type siri:RouteRefStructure
|
|
Type for identifier of a Route. |
||||
25.45. The complex type siri:SiteRefStructure
|
|
Identifier of a SITE |
||||
25.46. The complex type siri:StopAreaRefStructure
|
|
Type for identifier of a STOP AREA. |
||||
25.47. The complex type siri:StopPointRefStructure
|
|
Type for identifier of a SCHEDULED STOP POINT. |
||||
25.48. The complex type siri:VehicleRefStructure
|
|
Identifier of a VEHICLE. |
||||
25.49. The complex type siri:VersionRefStructure
|
|
Type for identifier of a Version. |
||||
26. SIRI-SX Situation Model.
26.1. Simple type definitions
|
|
Values for TPEG Pts039 - AdviceType, with some additional values |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Values for Audience. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Type for allowed values of DelayBand. Based on Datex2, with some additional values. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Values for image content. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Values for image content. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Type for Quality of data indication. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for Publication status. |
|||||||||||||||||||||||||||||||||||||||
|
|
Values for Type of Source. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Values for ScopeType - TPEG Pts36, AlertForType with additional values |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Values for Sensitivity. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Values for Type of Source. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Values for Entry Status. |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
- |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
- |
||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||
|
|
Union({xs:language}, {xs:string: (empty restriction)}) |
- |
|||||||||||||||||||||||||||||||||||||||
26.2. The toplevel element siri:PtSituationElement
|
|
Type for individual IPT ncident. |
||||
26.3. The toplevel element siri:RoadSituationElement
|
|
Type for individual IPT ncident. |
||||
26.4. The group siri:ClassifierGroup
|
|
Structured Classification Elements using TPEG Pts038 AlertCause. |
||||
|
The element contains one of the following elements (a-g) |
|||||
| siri:TpegReasonGroup |
a |
-1:1 |
TPEG Pts38: AlertCause. |
||
|
b |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
e |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
f |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
|
g |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). |
|||
|
The element contains one of the following elements (a-d) |
|||||
| siri:TpegSubReasonGroup |
a |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
||
|
b |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
| siri:ReasonGroup |
|
0:1 |
Structured classification of Public Event, from which a standardized message can be generated. |
||
|
|
0:* |
Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) |
|||
| siri:ClassifierGroup |
0:1 |
Severity of Incident - TPEG Pti26. Default is 'normal'. |
|||
|
|
0:1 |
Arbitrary rating of priority 1-High. |
|||
|
|
0:1 |
Confidentiality of SITUATION. |
|||
|
|
0:1 |
Intended audience of SITUATION. |
|||
|
|
0:1 |
Nature of scope, e.g. general, network. |
|||
|
0:1 |
Scope of incident - TPEG Pti27 ReportType |
||||
|
|
0:1 |
Whether the SITUATION was planned (eg engineering works) or unplanned (eg service alteration). Default is 'false', i.e. unplanned. |
|||
|
|
0:1 |
Arbitrary application specific classifiers. |
|||
|
|
0:1 |
Additional reasons |
|||
26.5. The group siri:ConditionGroup
|
|
Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message! |
||||
| siri:ConditionGroup |
0:* |
Classification of effect on service. TPEG PTS043 ServiceStatus |
|||
|
|
0:* |
Textual classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. |
|||
26.6. The group siri:Datex2ManagementGroup
|
|
Datex2 SITUATION management elements. |
||||
| siri:Datex2ManagementGroup |
|
1:1 |
A unique alphanumeric reference (either an external reference or GUID) of the SITUATIONRecord object (the first version of the record) that was created by the original supplier. |
||
|
|
0:1 |
The date/time that the SITUATIONRecord object (the first version of the record) was created by the original supplier. |
|||
|
|
0:1 |
The date/time that the information represented by the current version of the SITUATIONRecord was observed by the original (potentially external) source of the information. |
|||
|
|
0:1 |
Each record within a SITUATION may iterate through a series of versions during its life time. The SITUATION record version uniquely identifies the version of a particular record within a SITUATION. It is generated and used by systems external to DATEX 2. |
|||
|
|
0:1 |
The date/time that this current version of the SITUATIONRecord was written into the database of the supplier which is involved in the data exchange. |
|||
|
|
1:1 |
The date/time that the current version of the SITUATION Record was written into the database of the original supplier in the supply chain. |
|||
26.7. The group siri:Datex2OtherGroup
|
|
Datex2 Tarffic element. |
||||
| siri:Datex2OtherGroup |
|
0:1 |
|||
|
|
0:1 |
||||
|
|
0:1 |
||||
26.8. The group siri:Datex2RoadGroup
|
|
Datex2 Trrffic element road. |
||||
| siri:Datex2RoadGroup |
|
0:1 |
Impact of Road SITUATION as specified by Datex2. |
||
|
|
0:1 |
Impact of Road SITUATION as specified by Datex2 model. |
|||
|
|
0:* |
Datex 2 comments for public use. |
|||
|
|
0:* |
Ccomments not for public use. |
|||
|
|
0:1 |
Datex 2 model of where event ois taking place on the road. |
|||
26.9. The group siri:Datex2SituationGroup
|
|
Datex2 SITUATION common elements. |
||||
| siri:Datex2SituationGroup |
|
0:1 |
An assessment of the degree of likelihood that the reported event will occur. |
||
|
|
0:1 |
||||
|
|
0:1 |
||||
26.10. The group siri:DescriptionGroup
|
|
Text description of SITUATION. Some or all of this may have been generated from the other structured content elements. Where text has been overriden this is indicated. |
||||
| siri:DescriptionGroup |
|
0:1 |
Default language. |
||
|
|
0:* |
Summary of SITUATION. If absent should be generated from structure elements / and or by condensing Description. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). |
|||
|
|
0:* |
Further advice to passengers. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
For internal information only, not passenger relevant |
|||
|
|
0:1 |
Any images associated with SITUATION. |
|||
|
|
0:1 |
Hyperlinks to other resources associated with SITUATION. |
|||
26.11. The group siri:PtBodyGroup
|
|
Body of SITUATION. |
||||
| siri:PtBodyGroup |
|
0:1 |
Structured model identifiying parts of transport network affected by SITUATION. OPERATOR and NETWORK values will be defaulted to values in general Context unless explicitly overridden. |
||
|
|
0:1 |
Structured model describing effect of the SITUATION on PT system. |
|||
|
|
0:1 |
Structured model describing distribution actions to handle SITUATION. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. |
|||
26.12. The group siri:PtSituationBodyGroup
|
|
Body of SITUATION. |
||||
| siri:StatusGroup |
|
0:1 |
Whether the SITUATION has been verified. |
||
|
|
0:1 |
ProgressStatus. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. |
|||
|
|
0:1 |
Assessement of likely correctness of data. Default is reliable |
|||
|
|
0:1 |
Whether SITUATION is real or a test. |
|||
|
|
0:1 |
Likellihood of a future situation happening. |
|||
|
|
0:* |
Publishing status one of a specified set of substates to which a SITUATION can be assigned. |
|||
| siri:TemporalGroup |
|
1:* |
Overall inclusive Period of applicability of SITUATION. |
||
|
|
0:1 |
situation applies only on the repeated day types within the overall validity period(s). For example Sunday. |
|||
|
|
0:* |
Publication Window for SITUATION if different from validity period. |
|||
|
The element contains one of the following elements (a-g) |
|||||
| siri:TpegReasonGroup |
a |
-1:1 |
TPEG Pts38: AlertCause. |
||
|
b |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
e |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
f |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
|
g |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). |
|||
|
The element contains one of the following elements (a-d) |
|||||
| siri:TpegSubReasonGroup |
a |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
||
|
b |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
| siri:ReasonGroup |
|
0:1 |
Structured classification of Public Event, from which a standardized message can be generated. |
||
|
|
0:* |
Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) |
|||
| siri:ClassifierGroup |
0:1 |
Severity of Incident - TPEG Pti26. Default is 'normal'. |
|||
|
|
0:1 |
Arbitrary rating of priority 1-High. |
|||
|
|
0:1 |
Confidentiality of SITUATION. |
|||
|
|
0:1 |
Intended audience of SITUATION. |
|||
|
|
0:1 |
Nature of scope, e.g. general, network. |
|||
|
0:1 |
Scope of incident - TPEG Pti27 ReportType |
||||
|
|
0:1 |
Whether the SITUATION was planned (eg engineering works) or unplanned (eg service alteration). Default is 'false', i.e. unplanned. |
|||
|
|
0:1 |
Arbitrary application specific classifiers. |
|||
|
|
0:1 |
Additional reasons |
|||
| siri:DescriptionGroup |
|
0:1 |
Default language. |
||
|
|
0:* |
Summary of SITUATION. If absent should be generated from structure elements / and or by condensing Description. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). |
|||
|
|
0:* |
Further advice to passengers. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
For internal information only, not passenger relevant |
|||
|
|
0:1 |
Any images associated with SITUATION. |
|||
|
|
0:1 |
Hyperlinks to other resources associated with SITUATION. |
|||
| siri:PtBodyGroup |
|
0:1 |
Structured model identifiying parts of transport network affected by SITUATION. OPERATOR and NETWORK values will be defaulted to values in general Context unless explicitly overridden. |
||
|
|
0:1 |
Structured model describing effect of the SITUATION on PT system. |
|||
|
|
0:1 |
Structured model describing distribution actions to handle SITUATION. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. |
|||
26.13. The group siri:ReasonGroup
|
|
Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! |
||||
|
The element contains one of the following elements (a-g) |
|||||
| siri:TpegReasonGroup |
a |
-1:1 |
TPEG Pts38: AlertCause. |
||
|
b |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
e |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
f |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
|
g |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). |
|||
|
The element contains one of the following elements (a-d) |
|||||
| siri:TpegSubReasonGroup |
a |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
||
|
b |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
| siri:ReasonGroup |
|
0:1 |
Structured classification of Public Event, from which a standardized message can be generated. |
||
|
|
0:* |
Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) |
|||
26.14. The group siri:RoadBodyGroup
|
|
Datex 2 SITUATION. |
||||
| siri:RoadBodyGroup |
|
0:1 |
Structured model identifiying parts of transport network affected by SITUATION. OPERATOR and Network values will be defaulted to values in general Context unless explicitly overridden. |
||
|
|
0:1 |
Structured model describing effect of the SITUATION on PT system. |
|||
|
|
0:1 |
Structured model describing distribution actions to handle SITUATION. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. |
|||
|
|
0:1 |
Datex2 SITUATION Record. |
|||
26.15. The group siri:RoadSituationBodyGroup
|
|
Body of SITUATION. |
||||
| siri:StatusGroup |
|
0:1 |
Whether the SITUATION has been verified. |
||
|
|
0:1 |
ProgressStatus. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. |
|||
|
|
0:1 |
Assessement of likely correctness of data. Default is reliable |
|||
|
|
0:1 |
Whether SITUATION is real or a test. |
|||
|
|
0:1 |
Likellihood of a future situation happening. |
|||
|
|
0:* |
Publishing status one of a specified set of substates to which a SITUATION can be assigned. |
|||
| siri:TemporalGroup |
|
1:* |
Overall inclusive Period of applicability of SITUATION. |
||
|
|
0:1 |
situation applies only on the repeated day types within the overall validity period(s). For example Sunday. |
|||
|
|
0:* |
Publication Window for SITUATION if different from validity period. |
|||
|
The element contains one of the following elements (a-g) |
|||||
| siri:TpegReasonGroup |
a |
-1:1 |
TPEG Pts38: AlertCause. |
||
|
b |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
e |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
f |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
|
g |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). |
|||
|
The element contains one of the following elements (a-d) |
|||||
| siri:TpegSubReasonGroup |
a |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
||
|
b |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
| siri:ReasonGroup |
|
0:1 |
Structured classification of Public Event, from which a standardized message can be generated. |
||
|
|
0:* |
Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) |
|||
| siri:ClassifierGroup |
0:1 |
Severity of Incident - TPEG Pti26. Default is 'normal'. |
|||
|
|
0:1 |
Arbitrary rating of priority 1-High. |
|||
|
|
0:1 |
Confidentiality of SITUATION. |
|||
|
|
0:1 |
Intended audience of SITUATION. |
|||
|
|
0:1 |
Nature of scope, e.g. general, network. |
|||
|
0:1 |
Scope of incident - TPEG Pti27 ReportType |
||||
|
|
0:1 |
Whether the SITUATION was planned (eg engineering works) or unplanned (eg service alteration). Default is 'false', i.e. unplanned. |
|||
|
|
0:1 |
Arbitrary application specific classifiers. |
|||
|
|
0:1 |
Additional reasons |
|||
| siri:DescriptionGroup |
|
0:1 |
Default language. |
||
|
|
0:* |
Summary of SITUATION. If absent should be generated from structure elements / and or by condensing Description. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). |
|||
|
|
0:* |
Further advice to passengers. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
For internal information only, not passenger relevant |
|||
|
|
0:1 |
Any images associated with SITUATION. |
|||
|
|
0:1 |
Hyperlinks to other resources associated with SITUATION. |
|||
| siri:RoadBodyGroup |
|
0:1 |
Structured model identifiying parts of transport network affected by SITUATION. OPERATOR and Network values will be defaulted to values in general Context unless explicitly overridden. |
||
|
|
0:1 |
Structured model describing effect of the SITUATION on PT system. |
|||
|
|
0:1 |
Structured model describing distribution actions to handle SITUATION. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. |
|||
|
|
0:1 |
Datex2 SITUATION Record. |
|||
26.16. The group siri:SituationInfoGroup
|
|
situation Informatiion. |
||||
| siri:SituationInfoGroup |
|
0:1 |
Associations with other SITUATIONs. |
||
|
|
1:1 |
Information about source of information, that is, where the agent using the capture client obtained an item of information, or in the case of an automated feed, an identifier of the specific feed. Can be used to obtain updates, verify details or otherwise assess relevance. |
|||
26.17. The group siri:SituationSourceDetailsGroup
|
|
Group of source details. |
||||
| siri:SituationSourceDetailsGroup |
|
0:1 |
Email of Supplier of information. |
||
|
|
0:1 |
Phone number of Supplier of information. |
|||
|
|
0:1 |
Fax number of Supplier of information. |
|||
|
|
0:1 |
Information was obtained from a web site URL of site and/or page. |
|||
|
|
0:1 |
Other information about source. |
|||
26.18. The group siri:StatusGroup
|
|
Status elements. |
||||
| siri:StatusGroup |
|
0:1 |
Whether the SITUATION has been verified. |
||
|
|
0:1 |
ProgressStatus. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. |
|||
|
|
0:1 |
Assessement of likely correctness of data. Default is reliable |
|||
|
|
0:1 |
Whether SITUATION is real or a test. |
|||
|
|
0:1 |
Likellihood of a future situation happening. |
|||
|
|
0:* |
Publishing status one of a specified set of substates to which a SITUATION can be assigned. |
|||
26.19. The group siri:TemporalGroup
|
|
Elements affecting temporal scope of SITUATION. |
||||
| siri:TemporalGroup |
|
1:* |
Overall inclusive Period of applicability of SITUATION. |
||
|
|
0:1 |
situation applies only on the repeated day types within the overall validity period(s). For example Sunday. |
|||
|
|
0:* |
Publication Window for SITUATION if different from validity period. |
|||
26.20. The complex type siri:AbstractSituationElementStructure
|
|
Type for abstract EntryAbstract type. |
||||
|
|
1:1 |
Time of creation of SITUATION. |
|||
| siri:SituationBaseIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created SITUATION. Provides namespace for Participant If absent proided from context. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
1:1 |
Identifier of SITUATION within a Participant. Exclude versionr. |
||||
| siri:SituationUpdateIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
|
0:1 |
Unique identifier of update version within a SITUATION Number Omit if reference to the base SITUATION. |
|||
26.21. The complex type siri:AffectedRoadsStructure
|
|
Type for Location model for scope of SITUATION or effect. |
||||
|
|
0:1 |
Refereences to road network locations affected by the SITUATION. |
|||
|
|
0:* |
Description of affected road. |
|||
26.22. The complex type siri:AffectedRoadStructure
|
|
Type for Raod scope for scope of SITUATION or effect. |
||||
|
|
0:1 |
Affected Road as described by a Date2x location. |
|||
| siri:ProjectionGroup |
|
0:1 |
GIs projection of Section. NB Line here means Geometry Polyline, not Transmodel Transport Line. |
||
|
|
0:1 |
Offset from start or end of section to use when projecting. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
26.23. The complex type siri:AffectsScopeStructure
|
|
Type for Location model for scope of SITUATION or effect. |
||||
|
|
0:1 |
Affected overall Geographic scope. |
|||
|
|
0:1 |
Affected OPERATORs, If absent, taken from context. If present, any OPERATORs stated completely replace those from context. |
|||
|
|
0:1 |
Networks affected by SITUATION. |
|||
|
|
0:1 |
STOP POINTs affected by SITUATION. |
|||
|
|
0:1 |
Places other than STOP POINTs affected by SITUATION. |
|||
|
|
0:1 |
Places other than STOP POINTs affected by SITUATION. |
|||
|
|
0:1 |
Specific journeys affected by SITUATION. |
|||
|
|
0:1 |
Specific vehicles affected by SITUATION. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Roads affected by. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
26.24. The complex type siri:BlockingStructure
|
|
Type for blocking. |
||||
|
|
0:1 |
Whether information about parts of the NETWORK identified by AffectsScope should be blocked from the Journey Planner. Default is false; do not suppress. |
|||
|
|
0:1 |
Whether information about parts of the NETWORK identified by AffectsScope should be blocked from real-time departure info systems. Default is false; do not suppress. |
|||
26.25. The complex type siri:BoardingStructure
|
|
Type for boarding restrictions. |
||||
|
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
|||
|
|
0:1 |
Type of boarding allowed at stop. Default is 'Boarding'. |
|||
26.26. The complex type siri:DefaultedTextStructure
|
|
A restriction of W3C XML Schema's string that requires at least one character of text. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
lang (as an attribute name) denotes an attribute whose value is a language code for the natural language of the content of any element; its value is inherited. This name is reserved by virtue of its definition in the XML specification. Notes Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See BCP 47 at http://www.rfc-editor.org/rfc/bcp/bcp47.txt and the IANA language subtag registry at http://www.iana.org/assignments/language-subtag-registry for further information. The union allows for the 'un-declaration' of xml:lang with the empty string. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Whether the text value has been overridden from the generated default. Default is 'true'. |
|||
26.27. The complex type siri:DelaysStructure
|
|
Type for easement info. |
||||
|
|
0:1 |
Time band into which delay will fall. |
|||
|
|
0:1 |
Category of delay. |
|||
|
|
0:1 |
Additional journey time needed to overcome disruption. |
|||
26.28. The complex type siri:EasementsStructure
|
|
Type for easement info. |
||||
|
|
0:1 |
Ticket restriction conditiosn in effect. TPEG pti table pti25. |
|||
|
|
0:* |
Description of fare exceptions allowed because of disruption. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Refernce to a fare exceptions code that is allowed because of the disruption. An easement may relax a fare condition, for exampel "You may use your metro ticket on the bus', or 'You may use your bus ticket in teh metro between these two stops'. |
|||
26.29. The complex type siri:ImageStructure
|
|
Type for image. |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Reference to an image. |
||
|
b |
|
-1:1 |
Embedded image. |
||
|
|
0:1 |
Categorisation of image content. |
|||
26.30. The complex type siri:InfoLinkStructure
|
|
Type for a general hyperlink. |
||||
|
|
1:1 |
URI for link. |
|||
|
|
0:* |
Label for Link. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Image to use when presenting hyperlink. |
|||
|
|
0:1 |
Categorisation of link content. |
|||
26.31. The complex type siri:OptionalTrafficElementStructure
|
|
An event which is not planned by the traffic OPERATOR, which is affecting, or has the potential to affect traffic flow. This SIRI-SX element embeds the Datex2 TrafficElement, making all elements optional because they may alternatvielky be specified by common SIRI-SRX SITUATION elements. |
||||
| siri:Datex2ManagementGroup |
|
1:1 |
A unique alphanumeric reference (either an external reference or GUID) of the SITUATIONRecord object (the first version of the record) that was created by the original supplier. |
||
|
|
0:1 |
The date/time that the SITUATIONRecord object (the first version of the record) was created by the original supplier. |
|||
|
|
0:1 |
The date/time that the information represented by the current version of the SITUATIONRecord was observed by the original (potentially external) source of the information. |
|||
|
|
0:1 |
Each record within a SITUATION may iterate through a series of versions during its life time. The SITUATION record version uniquely identifies the version of a particular record within a SITUATION. It is generated and used by systems external to DATEX 2. |
|||
|
|
0:1 |
The date/time that this current version of the SITUATIONRecord was written into the database of the supplier which is involved in the data exchange. |
|||
|
|
1:1 |
The date/time that the current version of the SITUATION Record was written into the database of the original supplier in the supply chain. |
|||
| siri:Datex2SituationGroup |
|
0:1 |
An assessment of the degree of likelihood that the reported event will occur. |
||
|
|
0:1 |
||||
|
|
0:1 |
||||
| siri:Datex2RoadGroup |
|
0:1 |
Impact of Road SITUATION as specified by Datex2. |
||
|
|
0:1 |
Impact of Road SITUATION as specified by Datex2 model. |
|||
|
|
0:* |
Datex 2 comments for public use. |
|||
|
|
0:* |
Ccomments not for public use. |
|||
|
|
0:1 |
Datex 2 model of where event ois taking place on the road. |
|||
| siri:Datex2OtherGroup |
|
0:1 |
|||
|
|
0:1 |
||||
|
|
0:1 |
||||
26.32. The complex type siri:PtAdviceStructure
|
|
Type for (structured) advice. The AdviceType enumerated value can be used to generate standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message! Alternatively, AdviceRef can be used to reference a (complete) standardised advisory message. |
||||
|
|
0:1 |
Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. |
|||
|
|
0:1 |
Structured classification of advice for passengers in the given SITUATION, from which a standardized message can be generated. |
|||
|
|
0:* |
Textual classification of advice, from which a standardized message can be generated. Not normally needed, except when AdviceType is absent. |
|||
|
|
0:* |
Further textual advice to passengers. (Unbounded since SIRI 2.0) |
|||
26.33. The complex type siri:PtConsequencesStructure
|
|
Type for list of effects. |
||||
|
|
1:* |
Nature of the effect to disrupt (or restore) service, and further details. |
|||
26.34. The complex type siri:PtConsequenceStructure
|
|
Type for disruption. |
||||
|
|
0:* |
Period of effect of disruption, if different from that of SITUATION. |
|||
| siri:ConditionGroup |
0:* |
Classification of effect on service. TPEG PTS043 ServiceStatus |
|||
|
|
0:* |
Textual classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. |
|||
|
|
0:1 |
Severity of disruption if different from that of SITUATION. TPEG pti26 |
|||
|
|
0:1 |
Parts of transport network affected by disruption if different from that of SITUATION. |
|||
|
|
0:1 |
Effect on different passenger needs. |
|||
|
|
0:1 |
Advice to passengers. |
|||
|
|
0:1 |
How Disruption should be handled in Info systems. |
|||
|
|
0:1 |
Change to normal boarding activity allowed at stop. |
|||
|
|
0:1 |
||||
|
|
0:1 |
Information on casualties. |
|||
|
|
0:* |
Description of fare exceptions allowed because of disruption. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
26.35. The complex type siri:PtSituationElementStructure
|
|
Type for abstract EntryAbstract type. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time of creation of SITUATION. |
|||
| siri:SituationBaseIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created SITUATION. Provides namespace for Participant If absent proided from context. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
1:1 |
Identifier of SITUATION within a Participant. Exclude versionr. |
||||
| siri:SituationUpdateIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
|
0:1 |
Unique identifier of update version within a SITUATION Number Omit if reference to the base SITUATION. |
|||
| siri:SituationInfoGroup |
|
0:1 |
Associations with other SITUATIONs. |
||
|
|
1:1 |
Information about source of information, that is, where the agent using the capture client obtained an item of information, or in the case of an automated feed, an identifier of the specific feed. Can be used to obtain updates, verify details or otherwise assess relevance. |
|||
|
|
0:1 |
Time at which SITUATION element was versioned. Once versioned, no further changes can be made. |
|||
|
Inherited content is followed by own content: |
|||||
| siri:StatusGroup |
|
0:1 |
Whether the SITUATION has been verified. |
||
|
|
0:1 |
ProgressStatus. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. |
|||
|
|
0:1 |
Assessement of likely correctness of data. Default is reliable |
|||
|
|
0:1 |
Whether SITUATION is real or a test. |
|||
|
|
0:1 |
Likellihood of a future situation happening. |
|||
|
|
0:* |
Publishing status one of a specified set of substates to which a SITUATION can be assigned. |
|||
| siri:TemporalGroup |
|
1:* |
Overall inclusive Period of applicability of SITUATION. |
||
|
|
0:1 |
situation applies only on the repeated day types within the overall validity period(s). For example Sunday. |
|||
|
|
0:* |
Publication Window for SITUATION if different from validity period. |
|||
|
The element contains one of the following elements (a-g) |
|||||
| siri:TpegReasonGroup |
a |
-1:1 |
TPEG Pts38: AlertCause. |
||
|
b |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
e |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
f |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
|
g |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). |
|||
|
The element contains one of the following elements (a-d) |
|||||
| siri:TpegSubReasonGroup |
a |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
||
|
b |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
| siri:ReasonGroup |
|
0:1 |
Structured classification of Public Event, from which a standardized message can be generated. |
||
|
|
0:* |
Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) |
|||
| siri:ClassifierGroup |
0:1 |
Severity of Incident - TPEG Pti26. Default is 'normal'. |
|||
|
|
0:1 |
Arbitrary rating of priority 1-High. |
|||
|
|
0:1 |
Confidentiality of SITUATION. |
|||
|
|
0:1 |
Intended audience of SITUATION. |
|||
|
|
0:1 |
Nature of scope, e.g. general, network. |
|||
|
0:1 |
Scope of incident - TPEG Pti27 ReportType |
||||
|
|
0:1 |
Whether the SITUATION was planned (eg engineering works) or unplanned (eg service alteration). Default is 'false', i.e. unplanned. |
|||
|
|
0:1 |
Arbitrary application specific classifiers. |
|||
|
|
0:1 |
Additional reasons |
|||
| siri:DescriptionGroup |
|
0:1 |
Default language. |
||
|
|
0:* |
Summary of SITUATION. If absent should be generated from structure elements / and or by condensing Description. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). |
|||
|
|
0:* |
Further advice to passengers. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
For internal information only, not passenger relevant |
|||
|
|
0:1 |
Any images associated with SITUATION. |
|||
|
|
0:1 |
Hyperlinks to other resources associated with SITUATION. |
|||
| siri:PtBodyGroup |
|
0:1 |
Structured model identifiying parts of transport network affected by SITUATION. OPERATOR and NETWORK values will be defaulted to values in general Context unless explicitly overridden. |
||
|
|
0:1 |
Structured model describing effect of the SITUATION on PT system. |
|||
|
|
0:1 |
Structured model describing distribution actions to handle SITUATION. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
26.36. The complex type siri:ReferencesStructure
|
|
Type for references. |
||||
|
|
1:* |
A reference to another SITUATION with an indication of the nature of the association, e.g. a cause, a result, an update. Note that a Entry that is an update, i.e. has the same IdentifierNumber but a later version number as a previous Entry alway has a supercedes relationship and this does not need to be expliciitly coded. |
|||
26.37. The complex type siri:RelatedSituationStructure
|
|
Type for a reference. |
||||
|
|
1:1 |
Time of creation of 'related to' assocation. |
|||
| siri:SituationBaseIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created SITUATION. Provides namespace for Participant If absent proided from context. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
1:1 |
Identifier of SITUATION within a Participant. Exclude versionr. |
||||
| siri:SituationUpdateIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
|
0:1 |
Unique identifier of update version within a SITUATION Number Omit if reference to the base SITUATION. |
|||
|
|
0:1 |
A single string that identifiers the referenced SITUATION. |
|||
|
|
0:1 |
Relationship of refercence to the referncing SITUATION e. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
26.38. The complex type siri:RoadSituationElementStructure
|
|
Type for abstract EntryAbstract type. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time of creation of SITUATION. |
|||
| siri:SituationBaseIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created SITUATION. Provides namespace for Participant If absent proided from context. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
1:1 |
Identifier of SITUATION within a Participant. Exclude versionr. |
||||
| siri:SituationUpdateIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
|
0:1 |
Unique identifier of update version within a SITUATION Number Omit if reference to the base SITUATION. |
|||
| siri:SituationInfoGroup |
|
0:1 |
Associations with other SITUATIONs. |
||
|
|
1:1 |
Information about source of information, that is, where the agent using the capture client obtained an item of information, or in the case of an automated feed, an identifier of the specific feed. Can be used to obtain updates, verify details or otherwise assess relevance. |
|||
|
|
0:1 |
Time at which SITUATION element was versioned. Once versioned, no further changes can be made. |
|||
|
Inherited content is followed by own content: |
|||||
| siri:StatusGroup |
|
0:1 |
Whether the SITUATION has been verified. |
||
|
|
0:1 |
ProgressStatus. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. |
|||
|
|
0:1 |
Assessement of likely correctness of data. Default is reliable |
|||
|
|
0:1 |
Whether SITUATION is real or a test. |
|||
|
|
0:1 |
Likellihood of a future situation happening. |
|||
|
|
0:* |
Publishing status one of a specified set of substates to which a SITUATION can be assigned. |
|||
| siri:TemporalGroup |
|
1:* |
Overall inclusive Period of applicability of SITUATION. |
||
|
|
0:1 |
situation applies only on the repeated day types within the overall validity period(s). For example Sunday. |
|||
|
|
0:* |
Publication Window for SITUATION if different from validity period. |
|||
|
The element contains one of the following elements (a-g) |
|||||
| siri:TpegReasonGroup |
a |
-1:1 |
TPEG Pts38: AlertCause. |
||
|
b |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
e |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
f |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
|
g |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). |
|||
|
The element contains one of the following elements (a-d) |
|||||
| siri:TpegSubReasonGroup |
a |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
||
|
b |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
| siri:ReasonGroup |
|
0:1 |
Structured classification of Public Event, from which a standardized message can be generated. |
||
|
|
0:* |
Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) |
|||
| siri:ClassifierGroup |
0:1 |
Severity of Incident - TPEG Pti26. Default is 'normal'. |
|||
|
|
0:1 |
Arbitrary rating of priority 1-High. |
|||
|
|
0:1 |
Confidentiality of SITUATION. |
|||
|
|
0:1 |
Intended audience of SITUATION. |
|||
|
|
0:1 |
Nature of scope, e.g. general, network. |
|||
|
0:1 |
Scope of incident - TPEG Pti27 ReportType |
||||
|
|
0:1 |
Whether the SITUATION was planned (eg engineering works) or unplanned (eg service alteration). Default is 'false', i.e. unplanned. |
|||
|
|
0:1 |
Arbitrary application specific classifiers. |
|||
|
|
0:1 |
Additional reasons |
|||
| siri:DescriptionGroup |
|
0:1 |
Default language. |
||
|
|
0:* |
Summary of SITUATION. If absent should be generated from structure elements / and or by condensing Description. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Description of SITUATION. Should not repeat any strap line included in Summary. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0). |
|||
|
|
0:* |
Further advice to passengers. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
For internal information only, not passenger relevant |
|||
|
|
0:1 |
Any images associated with SITUATION. |
|||
|
|
0:1 |
Hyperlinks to other resources associated with SITUATION. |
|||
| siri:RoadBodyGroup |
|
0:1 |
Structured model identifiying parts of transport network affected by SITUATION. OPERATOR and Network values will be defaulted to values in general Context unless explicitly overridden. |
||
|
|
0:1 |
Structured model describing effect of the SITUATION on PT system. |
|||
|
|
0:1 |
Structured model describing distribution actions to handle SITUATION. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. |
|||
|
|
0:1 |
Datex2 SITUATION Record. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
26.39. The complex type siri:SituationElementStructure
|
|
Type for abstract EntryAbstract type. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time of creation of SITUATION. |
|||
| siri:SituationBaseIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created SITUATION. Provides namespace for Participant If absent proided from context. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
1:1 |
Identifier of SITUATION within a Participant. Exclude versionr. |
||||
| siri:SituationUpdateIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
|
0:1 |
Unique identifier of update version within a SITUATION Number Omit if reference to the base SITUATION. |
|||
|
Inherited content is followed by own content: |
|||||
| siri:SituationInfoGroup |
|
0:1 |
Associations with other SITUATIONs. |
||
|
|
1:1 |
Information about source of information, that is, where the agent using the capture client obtained an item of information, or in the case of an automated feed, an identifier of the specific feed. Can be used to obtain updates, verify details or otherwise assess relevance. |
|||
|
|
0:1 |
Time at which SITUATION element was versioned. Once versioned, no further changes can be made. |
|||
26.40. The complex type siri:SituationSourceStructure
|
|
Type for a source, i.e. provider of information. |
||||
|
|
0:1 |
Country of origin of source element. |
|||
|
|
1:1 |
Nature of Source. |
|||
| siri:SituationSourceDetailsGroup |
|
0:1 |
Email of Supplier of information. |
||
|
|
0:1 |
Phone number of Supplier of information. |
|||
|
|
0:1 |
Fax number of Supplier of information. |
|||
|
|
0:1 |
Information was obtained from a web site URL of site and/or page. |
|||
|
|
0:1 |
Other information about source. |
|||
|
|
0:1 |
Nature of method used to get Source. |
|||
|
|
0:1 |
Reference to an Agent, i.e. Capture client user who input a SITUATION. Available for use in intranet exchange of SITUATIONs. |
|||
|
|
0:1 |
Name of for source. |
|||
|
|
0:1 |
Job title of Source. |
|||
|
|
0:1 |
Time of communication of message, if different from creation time. |
|||
|
|
0:1 |
External system reference to SITUATION. |
|||
|
|
0:1 |
Electronic file / attachment containing information about SITUATION. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
26.41. The complex type complexType[siri:AffectsScopeStructure]/StopPlaces#complexType (typedef-24.10)
|
|
- |
||||
|
|
1:* |
STOP PLACE affected by SITUATION. |
|||
26.42. The complex type complexType[siri:AffectsScopeStructure]/Places#complexType (typedef-24.11)
|
|
- |
||||
|
|
1:* |
Place affected by SITUATION. |
|||
26.43. The complex type complexType[siri:AffectsScopeStructure]/VehicleJourneys#complexType (typedef-24.12)
|
|
- |
||||
|
|
1:* |
Journeys affected by the SITUATION. |
|||
26.44. The complex type complexType[siri:AffectsScopeStructure]/Vehicles#complexType (typedef-24.13)
|
|
- |
||||
|
|
1:* |
Vehicles affected by the SITUATION. ((since SIRI 2.0)) |
|||
26.45. The complex type group[siri:DescriptionGroup]/Images#complexType (typedef-24.14)
|
|
- |
||||
|
|
1:* |
Image description. |
|||
26.46. The complex type group[siri:DescriptionGroup]/Images/Image#complexType (typedef-24.15)
|
|
Type for image. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Reference to an image. |
||
|
b |
|
-1:1 |
Embedded image. |
||
|
|
0:1 |
Categorisation of image content. |
|||
26.47. The complex type group[siri:DescriptionGroup]/InfoLinks#complexType (typedef-24.16)
|
|
- |
||||
|
|
1:* |
Hyperlink description. |
|||
26.48. The complex type complexType[siri:PtConsequenceStructure]/Suitabilities#complexType (typedef-24.17)
|
|
- |
||||
|
|
1:* |
Effect on a passenger need. |
|||
26.49. The complex type group[siri:TemporalGroup]/Repetitions#complexType (typedef-24.2)
|
|
- |
||||
|
1:* |
Day on which a SITUATION may apply - TPEG Pti34 DayType |
||||
26.50. The complex type group[siri:ClassifierGroup]/SecondaryReasons#complexType (typedef-24.4)
|
|
- |
||||
|
|
1:1 |
Reason |
|||
26.51. The complex type group[siri:ClassifierGroup]/SecondaryReasons/Reason#complexType (typedef-24.5)
|
|
- |
||||
|
The element contains one of the following elements (a-g) |
|||||
| siri:TpegReasonGroup |
a |
-1:1 |
TPEG Pts38: AlertCause. |
||
|
b |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
e |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
f |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
|
g |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). |
|||
|
The element contains one of the following elements (a-d) |
|||||
| siri:TpegSubReasonGroup |
a |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
||
|
b |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
| siri:ReasonGroup |
|
0:1 |
Structured classification of Public Event, from which a standardized message can be generated. |
||
|
|
0:* |
Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) |
|||
26.52. The complex type complexType[siri:AffectsScopeStructure]/Operators#complexType (typedef-24.6)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
All OPERATORs. |
||
|
b |
|
-1:* |
Operators of services affected by SITUATION. |
||
26.53. The complex type complexType[siri:AffectsScopeStructure]/Networks#complexType (typedef-24.7)
|
|
- |
||||
|
|
1:* |
Networks and Route(s) affected by SITUATION. |
|||
26.54. The complex type complexType[siri:AffectsScopeStructure]/Networks/AffectedNetwork#complexType (typedef-24.8)
|
|
Type for information about the parts of the network affected by an incident. If not explicitly overridden, modes and submodes will be defaulted to any values present in the general context. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:* |
Operators of LINEs affected by incident. Overrides any value specified for (i) General Context. |
|||
|
|
0:1 |
Network of affected LINE. If absent, may be taken from context. |
|||
|
|
0:* |
Name of Network. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. (Unbounded since SIRI 2.0) |
|||
| siri:AffectedModeGroup |
0:1 |
Vehicle mode or mode of transport. |
|||
|
The element contains one of the following elements (a-h) |
|||||
| siri:PtNetworkModeChoiceGroup |
a |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
b |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
c |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
d |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
e |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
f |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
g |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
|
h |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
| siri:AffectedModeGroup |
|
0:1 |
|||
|
The element contains one of the following elements (a-d) |
|||||
|
a |
|
-1:1 |
All LINEs in the network are affected. |
||
|
b |
|
-1:* |
Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. |
||
|
c |
|
-1:* |
Only some COMMON SECTIONs are affected, LINE level information not available. |
||
|
d |
|
-1:* |
Information about the indvidual LINEs in the network that are affected. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) In the general context. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
26.55. The complex type complexType[siri:AffectsScopeStructure]/StopPoints#complexType (typedef-24.9)
|
|
- |
||||
|
|
1:* |
STOP POINT affected by SITUATION. |
|||
27. SIRI-SX Situation Actions.
27.1. Simple type definitions
|
|
Values for Progress Status. |
||||||
|
|||||||
|
|
Values for perspectives. |
||||||
|
|||||||
27.2. The toplevel element siri:ManualAction
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
27.3. The toplevel element siri:NotifyByEmailAction
|
|
Action: Publish SITUATION to a named workgroup or individual user by email. |
||||
27.4. The toplevel element siri:NotifyByPagerAction
|
|
Action: Publish SITUATION To pager. |
||||
27.5. The toplevel element siri:NotifyBySmsAction
|
|
Action: Publish SITUATION to an individual user by SMS. |
||||
27.6. The toplevel element siri:NotifyUserAction
|
|
Action: Publish SITUATION To User by other means. |
||||
27.7. The toplevel element siri:PassengerInformationAction
|
|
|||||
27.8. The toplevel element siri:PublishToAlertsAction
|
|
Action: Publish SITUATION To Alert channel. |
||||
27.9. The toplevel element siri:PublishToDisplayAction
|
|
Action: Publish SITUATION To Display channel. |
||||
27.10. The toplevel element siri:PublishToMobileAction
|
|
Action: Publish SITUATION To Mobile Applications. |
||||
27.11. The toplevel element siri:PublishToTvAction
|
|
Action: Publish SITUATION To TV channel. |
||||
27.12. The toplevel element siri:PublishToWebAction
|
|
Action: Publish SITUATION To Web channel. |
||||
27.13. The group siri:ActionsGroup
|
|
Allowed actions to perform to distribute SITUATION. |
||||
| siri:ActionsGroup |
0:* |
Action: Publish SITUATION To Web channel. |
|||
|
0:* |
Action: Publish SITUATION To Mobile Applications. |
||||
|
0:* |
Action: Publish SITUATION To TV channel. |
||||
|
0:* |
Action: Publish SITUATION To Alert channel. |
||||
|
0:* |
Action: Publish SITUATION To Display channel. |
||||
|
0:* |
Action: Publish SITUATION to Manual publication channel. |
||||
|
0:* |
Action: Publish SITUATION to a named workgroup or individual user by email. |
||||
|
0:* |
Action: Publish SITUATION to an individual user by SMS. |
||||
|
0:* |
Action: Publish SITUATION To pager. |
||||
|
0:* |
Action: Publish SITUATION To User by other means. |
||||
27.14. The complex type siri:ActionDataStructure
|
|
Type for list of SITUATIONs. |
||||
|
|
1:1 |
Name of action data Element. |
|||
|
|
1:1 |
Data type of action data. |
|||
|
|
1:* |
Value for action. |
|||
|
|
0:* |
Display prompt for presenting action to user. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Defines the information area where the action has to be published. |
|||
27.15. The complex type siri:ActionsStructure
|
|
Type for list of actions. |
||||
| siri:ActionsGroup |
0:* |
Action: Publish SITUATION To Web channel. |
|||
|
0:* |
Action: Publish SITUATION To Mobile Applications. |
||||
|
0:* |
Action: Publish SITUATION To TV channel. |
||||
|
0:* |
Action: Publish SITUATION To Alert channel. |
||||
|
0:* |
Action: Publish SITUATION To Display channel. |
||||
|
0:* |
Action: Publish SITUATION to Manual publication channel. |
||||
|
0:* |
Action: Publish SITUATION to a named workgroup or individual user by email. |
||||
|
0:* |
Action: Publish SITUATION to an individual user by SMS. |
||||
|
0:* |
Action: Publish SITUATION To pager. |
||||
|
0:* |
Action: Publish SITUATION To User by other means. |
||||
|
|
0:* |
Description of the whole action to be published. >SIRI 2.0 |
|||
|
|
0:1 |
Extension point. |
|||
27.16. The complex type siri:ConsequenceContentStructure
|
|
- |
||||
|
|
1:* |
Consequence of passenger information action in a specific language. |
|||
|
|
0:1 |
Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. 1 = highest priority. |
|||
27.17. The complex type siri:DescriptionContentStructure
|
|
- |
||||
|
|
1:* |
Description of passenger information action in a specific language. Should not repeat any strap line included in Summary. |
|||
|
|
0:1 |
Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. 1 = highest priority. |
|||
27.18. The complex type siri:DurationContentStructure
|
|
- |
||||
|
|
1:* |
Indicates the currently expected duration of a SITUATION in a specific language. An estimation should be given here, because an indefinite duration is not helpful to the passenger. The duration can be adjusted at any time, if the traffic operator has additional information. |
|||
27.19. The complex type siri:ManualActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
27.20. The complex type siri:NotifyByEmailActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
|
0:1 |
Whether reminders should be sent. |
|||
|
|
0:1 |
Whether a clearing notice should be displayed. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Email address to which notice should be sent. |
|||
27.21. The complex type siri:NotifyByPagerActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
|
0:1 |
Whether reminders should be sent. |
|||
|
|
0:1 |
Whether a clearing notice should be displayed. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Reference to a pager group to be notified. |
|||
|
|
0:1 |
Pager number of pager to be notified. |
|||
27.22. The complex type siri:NotifyBySmsActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
|
0:1 |
Whether reminders should be sent. |
|||
|
|
0:1 |
Whether a clearing notice should be displayed. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
MSISDN of user to which to send messages. |
|||
|
|
0:1 |
Whether content is flagged as subject to premium charge. Default is 'false'. |
|||
27.23. The complex type siri:NotifyUserActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
|
0:1 |
Whether reminders should be sent. |
|||
|
|
0:1 |
Whether a clearing notice should be displayed. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Workgroup of user to be notified. |
|||
|
|
0:1 |
Name of user to be notified. |
|||
|
|
0:1 |
Reference to a user to be notified. |
|||
27.24. The complex type siri:ParameterisedActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
27.25. The complex type siri:PassengerInformationActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to the action number within the incident concept. |
|||
|
|
1:1 |
The time of the last update. This must be the timestamp of the original data source and not that of an intermediate system, such as a data hub. This timestamp has to be changed by the source system with every update. |
|||
|
|
0:1 |
The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation |
|||
|
|
0:1 |
The system which created this passenger information. If absent, the same system as the PtSituationElement.ParticipantRef. |
|||
|
|
0:1 |
The organisation which owns this passenger information. |
|||
|
|
1:* |
Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. |
|||
|
|
0:1 |
Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. 1 = highest priority. |
|||
|
|
1:* |
The actual, structured passenger information for a specific TextualContentSize. |
|||
27.26. The complex type siri:PublishingActionStructure
|
|
Type for description of the whole action to be published (extends SIRI-SX v2.0p). |
||||
|
|
1:1 |
Defines the information area where the action has to be published. |
|||
|
1:* |
|||||
27.27. The complex type siri:PublishToAlertsActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
|
0:1 |
Whether reminders should be sent. |
|||
|
|
0:1 |
Whether a clearing notice should be displayed. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Send as email alert. |
|||
|
|
0:1 |
Send as mobile alert by SMS or WAP push. |
|||
27.28. The complex type siri:PublishToDisplayActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Include in SITUATION lists on station displays. |
|||
|
|
0:1 |
Include onboard displays. |
|||
27.29. The complex type siri:PublishToMobileActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Include in SITUATION lists on mobile site. Default is 'true'. |
|||
|
|
0:1 |
Include in home page on mobile site. Default is 'false'. |
|||
27.30. The complex type siri:PublishToTvActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Publish to Ceefax. Default is 'true'. |
|||
|
|
0:1 |
Publish to Teletext. Default is 'true'. |
|||
27.31. The complex type siri:PublishToWebActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Include in SITUATION lists on web site. Default is 'true'. |
|||
|
|
0:1 |
Include on home page on web site. Default is 'false'. |
|||
|
|
0:1 |
Include in moving ticker band. Default is 'false'. |
|||
|
|
0:* |
Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specified as Action data. (SIRI 2.1) |
|||
27.32. The complex type siri:PushedActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether reminders should be sent. |
|||
|
|
0:1 |
Whether a clearing notice should be displayed. |
|||
27.33. The complex type siri:ReasonContentStructure
|
|
- |
||||
|
|
1:* |
Reason of passenger information action in a specific language. |
|||
27.34. The complex type siri:RecommendationContentStructure
|
|
- |
||||
|
|
1:* |
Recommendation of passenger information action in a specific language. |
|||
|
|
0:1 |
Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. 1 = highest priority. |
|||
27.35. The complex type siri:RemarkContentStructure
|
|
- |
||||
|
|
1:* |
Further remark to passengers, e,g, "For more information call xy". |
|||
|
|
0:1 |
Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. 1 = highest priority. |
|||
27.36. The complex type siri:SimpleActionStructure
|
|
Type for list of SITUATIONs. |
||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
27.37. The complex type siri:SummaryContentStructure
|
|
- |
||||
|
|
1:* |
Summary of passenger information action in a specific language. |
|||
27.38. The complex type siri:TextualContentStructure
|
|
- |
||||
|
|
0:1 |
Class of size, e.g. L (large), M (medium), S (small) |
|||
| siri:ActionsGroup |
0:* |
Action: Publish SITUATION To Web channel. |
|||
|
0:* |
Action: Publish SITUATION To Mobile Applications. |
||||
|
0:* |
Action: Publish SITUATION To TV channel. |
||||
|
0:* |
Action: Publish SITUATION To Alert channel. |
||||
|
0:* |
Action: Publish SITUATION To Display channel. |
||||
|
0:* |
Action: Publish SITUATION to Manual publication channel. |
||||
|
0:* |
Action: Publish SITUATION to a named workgroup or individual user by email. |
||||
|
0:* |
Action: Publish SITUATION to an individual user by SMS. |
||||
|
0:* |
Action: Publish SITUATION To pager. |
||||
|
0:* |
Action: Publish SITUATION To User by other means. |
||||
|
|
1:1 |
Content for summary of a passenger information action |
|||
|
|
0:1 |
Content for reason of a passenger information action |
|||
|
|
0:* |
Content for n descriptions of a passenger information action. For hiding / sorting descriptions in end devices, a description priority can be set. |
|||
|
|
0:* |
Content for n consequences of a passenger information action. For hiding / sorting descriptions in end devices, a consequence priority can be set. |
|||
|
|
0:* |
Content for n recommendations of a passenger information action. For hiding / sorting descriptions in end devices, a recommendation priority can be set. |
|||
|
|
0:1 |
Content for the duration of a passenger information action. |
|||
|
|
0:* |
Content for n remarks of a passenger information action, e,g, "For more information call xy". For hiding / sorting descriptions in end devices, a remark priority can be set. |
|||
|
|
0:* |
Hyperlinks to other resources associated with SITUATION. |
|||
|
|
0:* |
Any images associated with SITUATION. |
|||
|
|
0:* |
for internal information only, not passenger relevant |
|||
27.39. The complex type complexType[siri:PushedActionStructure]/BeforeNotices#complexType (typedef-16.1)
|
|
- |
||||
|
|
0:* |
Intervals before validity start date to send reminders. |
|||
27.40. The complex type complexType[siri:ActionDataStructure]/PublishAtScope#complexType (typedef-16.2)
|
|
- |
||||
|
|
1:1 |
||||
|
|
1:1 |
||||
27.41. The complex type element[siri:ManualAction]#complexType (typedef-16.3)
|
|
Type for list of SITUATIONs. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Processing Status of action at time of SITUATION publication. Default is 'open'. |
|||
|
|
0:1 |
Description of action. |
|||
|
|
0:* |
Data associated with action. |
|||
|
|
0:* |
Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. |
|||
27.42. The complex type complexType[siri:PublishingActionStructure]/PublishAtScope#complexType (typedef-16.4)
|
|
- |
||||
|
|
1:1 |
||||
|
|
1:1 |
||||
28. SIRI-SX Situation Scope.
28.1. Simple type definitions
|
|
Values for AccessibilityFeature - TPEG Pts040 and IFOPT |
||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an advisory NOTICE |
|||||||||||||||||||||||||||||||||||||||||||
|
|
Values for DIRECTION of CONNECTION link or SERVCIE JOURNEY INTERCHANGE. |
||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an OPERATOR Code. |
|||||||||||||||||||||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of an OPERATOR Code. |
|||||||||||||||||||||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for ideifier of a Route section. |
|||||||||||||||||||||||||||||||||||||||||||
|
|
Values for STOP PLACE types - TPEG Pts041 and IFOPT |
||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a ZONe. |
|||||||||||||||||||||||||||||||||||||||||||
28.2. The group siri:AffectedModeGroup
|
|
Mode Submode. Overrides any value sspecified for (i) Affected Network (ii) General Context. |
||||
| siri:AffectedModeGroup |
0:1 |
Vehicle mode or mode of transport. |
|||
|
The element contains one of the following elements (a-h) |
|||||
| siri:PtNetworkModeChoiceGroup |
a |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
b |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
c |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
d |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
e |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
f |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
g |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
|
h |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
| siri:AffectedModeGroup |
|
0:1 |
|||
28.3. The group siri:AffectedStopArrivalGroup
|
|
Elements describing the arrival of a VEHICLE at a SCHEDULED STOP POINT. |
||||
| siri:VehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of arrival of VEHICLE at stop. |
|||
|
b |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
| siri:AffectedStopArrivalGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:* |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
28.4. The group siri:AffectedStopDepartureGroup
|
|
Elements describing the departure of a VEHICLE from a SCHEDULED STOP POINT. |
||||
| siri:VehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of departure of VEHICLE from stop. |
|||
|
b |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
| siri:AffectedStopDepartureGroup |
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
|||
|
0:* |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
28.5. The group siri:LineGroup
|
|
Line to which link connects. |
||||
| siri:LineGroup |
1:1 |
Reference to a LINE. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
28.6. The group siri:ProjectionGroup
|
|
- |
||||
| siri:ProjectionGroup |
|
0:1 |
GIs projection of Section. NB Line here means Geometry Polyline, not Transmodel Transport Line. |
||
|
|
0:1 |
Offset from start or end of section to use when projecting. |
|||
28.7. The complex type siri:AdviceRefStructure
|
|
Type for identifier of an advisory NOTICE |
||||
28.8. The complex type siri:AffectedCallStructure
|
|
Type for an SCHEDULED STOP POINT affected by a SITUATION. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
|
0:1 |
Alternative private code of stop. |
|||
|
|
0:* |
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Type of stop type. Normally implicit in VEHICLE mode. TPEG table pti 17_4 |
|||
|
|
0:1 |
Spatial coordinates of STOP POINT. Derivable from StopRef. |
|||
|
|
0:1 |
Reference of STOP PLACE related to this affected StopPoint. |
|||
|
|
0:* |
Name of STOP PLACE related to this affected StopPoint. (Unbounded to allow a text for every language) |
|||
|
|
0:1 |
Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. |
|||
|
|
0:1 |
Reference to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. |
|||
|
|
0:* |
Name of locality in which stop is found. Derivable from LocalityRef. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Assessment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. |
|||
|
|
0:* |
Status of STOP |
|||
|
|
0:1 |
CONNECTION links from stop. |
|||
|
|
0:1 |
Used to restrict stop points to some lines |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Order of visit to stop within JOURNEY PATTERN of journey. |
|||
|
|
0:* |
Status of CALL TPEG 13_6 |
|||
| siri:CallRealtimeGroup |
0:1 |
Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) |
|||
|
|
0:1 |
Exact location that VEHICLE will take up / or has taken at STOP POINT. |
|||
| siri:CallPropertyGroup |
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
|||
|
|
0:1 |
Whether this is a Hail and Ride Stop. Default is 'false'. |
|||
|
|
0:1 |
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'. |
|||
|
|
0:* |
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0) |
|||
|
|
0:* |
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey. |
|||
| siri:VehicleArrivalTimesGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of arrival of VEHICLE at stop. |
|||
|
b |
-0:1 |
Estimated time of arriival of VEHICLE at stop . |
|||
| siri:AffectedStopArrivalGroup |
0:1 |
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. |
|||
|
0:* |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
| siri:VehicleDepartureTimesGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:1 |
Observed time of departure of VEHICLE from stop. |
|||
|
b |
-0:1 |
Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting. |
|||
| siri:AffectedStopDepartureGroup |
0:1 |
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times. |
|||
|
0:* |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
| siri:HeadwayIntervalGroup |
0:1 |
For frequency based services, target interval between vehicles at stop. |
|||
|
0:1 |
For frequency based services, expected interval between vehicles at stop. |
||||
|
|
0:1 |
||||
28.9. The complex type siri:AffectedConnectionLinkStructure
|
|
Type for a reference Information about a CONNECTION link from a given stop that is affected by a SITUATION. |
||||
|
|
0:* |
Reference to a CONNECTION link affected by a SITUATION. |
|||
|
|
0:1 |
Name of CONNECTION link affected by a SITUATION. |
|||
|
The element contains none or one of the following elements (a) or element sequences (b) |
|||||
|
a |
|
-1:1 |
|||
| siri:LineGroup |
b |
-1:1 |
Reference to a LINE. |
||
|
b |
-0:* |
Name or Number by which the LINEis known to the public. |
|||
|
b |
|
-0:1 |
Reference to other connecting STOP POINT of a CONNECTION link. If blank, both feeder and distributor vehicles go to same stop. Reference to a STOP POINT. |
||
|
b |
|
-0:* |
Name of other connecting STOP POINT of a CONNECTION link. Derivable from StopRef. (Unbounded since SIRI 2.0) |
||
|
b |
|
-0:1 |
Zone in which connecting stop lies. |
||
|
|
0:1 |
Direction of SERVICE JOURNEY INTERCHANGE. Default is 'both'. |
|||
|
|
0:* |
PATH LINKs affected by a SITUATION. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.10. The complex type siri:AffectedFacilityStructure
|
|
Type for information about a FACILITY affected by an SITUATION. (since SIRI 2.0) |
||||
|
0:1 |
Reference to a Facility. |
||||
|
|
0:1 |
Identifier of stop point at which availability first applies. |
|||
|
|
0:1 |
Identifier of stop point at which availability last applies. |
|||
|
|
0:* |
Name of FACILITY. |
|||
|
|
0:* |
Status of Facility |
|||
|
0:* |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.11. The complex type siri:AffectedInterchangeStructure
|
|
Information about a SERVICE JOURNEY INTERCHANGE at CONNECTION link from a given SCHEDULED STOP POINT. |
||||
|
|
0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE affected by a SITUATION. |
|||
|
|
0:1 |
Identifier of STOP POINT of a stop at which VEHICLE JOURNEY meets for interchange If blank, same stop as destination. Reference to a STOP POINT. |
|||
|
|
0:* |
Name of other Connecting STOP POINT of a connection. Derivable from InterchangeStopRef. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Reference to connecting VEHICLE JOURNEY affected by a SITUATION. |
|||
|
0:1 |
Status of a SERVICE JOURNEY INTERCHANGE - TPEG Pti31 InterchangeStatus |
||||
|
|
0:* |
Reference to a CONNECTION Link affected by a SITUATION. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.12. The complex type siri:AffectedLineStructure
|
|
Information about the individual LINEs in the network that are affected by a SITUATION. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) in the general context. |
||||
|
|
0:* |
Restricts the affected scope to the specified operators of LINEs that are affected by the situation. Overrides any value specified for (i) Affected Network (ii) General Context. |
|||
| siri:LineGroup |
1:1 |
Reference to a LINE. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:* |
Restricts the affected scope to the specified origins |
|||
|
|
0:* |
Restricts the affected scope to the specified DESTINATIONs |
|||
|
|
0:* |
DIRECTIONs affected. |
|||
|
|
0:1 |
Restricts the affected scope to the specified ROUTEs |
|||
|
|
0:1 |
Restricts the affected scope to the specified LINE SECTIONs |
|||
|
|
0:1 |
Restricts the affected scope to the specified SCHEDULED STOP POINTs |
|||
|
|
0:1 |
Restricts the affected scope to the specified STOP PLACEs |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.13. The complex type siri:AffectedModesStructure
|
|
Type for TRANSPORT MODEs affecetd by a SITUATION. |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
All known modes for stop. |
||
|
b |
|
-0:* |
Mode affected by SITUATION. |
||
28.14. The complex type siri:AffectedNetworkStructure
|
|
Type for information about the parts of the network affected by an incident. If not explicitly overridden, modes and submodes will be defaulted to any values present in the general context. |
||||
|
|
0:* |
Operators of LINEs affected by incident. Overrides any value specified for (i) General Context. |
|||
|
|
0:1 |
Network of affected LINE. If absent, may be taken from context. |
|||
|
|
0:* |
Name of Network. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. (Unbounded since SIRI 2.0) |
|||
| siri:AffectedModeGroup |
0:1 |
Vehicle mode or mode of transport. |
|||
|
The element contains one of the following elements (a-h) |
|||||
| siri:PtNetworkModeChoiceGroup |
a |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
b |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
c |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
d |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
e |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
f |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
g |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
|
h |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
| siri:AffectedModeGroup |
|
0:1 |
|||
|
The element contains one of the following elements (a-d) |
|||||
|
a |
|
-1:1 |
All LINEs in the network are affected. |
||
|
b |
|
-1:* |
Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. |
||
|
c |
|
-1:* |
Only some COMMON SECTIONs are affected, LINE level information not available. |
||
|
d |
|
-1:* |
Information about the indvidual LINEs in the network that are affected. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) In the general context. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.15. The complex type siri:AffectedOperatorStructure
|
|
Type for Annotated reference to an OPERATOR affected by a SITUATION. |
||||
|
|
0:1 |
Reference to an OPERATOR. |
|||
|
|
0:* |
Public Name of OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short Name for OPERATOR. Can be derived from OperatorRef. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
OPERATIONAL UNIT responsible for managing services. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.16. The complex type siri:AffectedPathLinkStructure
|
|
Information about a CONNECTION link from a given stop affected by a SITUATION. |
||||
|
|
0:* |
Identifier of CONNECTION link. |
|||
|
|
0:* |
Description of Link. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Nature of CONNECTION link. |
|||
|
|
0:* |
Description of a DIRECTION of CONNECTION link. |
|||
| siri:ProjectionGroup |
|
0:1 |
GIs projection of Section. NB Line here means Geometry Polyline, not Transmodel Transport Line. |
||
|
|
0:1 |
Offset from start or end of section to use when projecting. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.17. The complex type siri:AffectedPlaceStructure
|
|
Type for annotated references to a TOPOGRAPHIC PLACE. |
||||
|
|
0:1 |
Reference to a SITE or TOPOGRAPHIC PLACE (Locality). |
|||
|
|
0:1 |
Alternative identifier of SITE or TOPOGRAPHIC PLACE |
|||
|
|
0:* |
Name of SITE or TOPOGRAPHIC PLACE (locality) in which stop is found. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Spatial coordinates of STOP POINT. Derivable from StopRef. |
|||
|
|
0:1 |
Category of TOPOGRAPHIC PLACE or SITE. |
|||
|
|
0:* |
Reference to an EQUIPMENT found at SITE. |
|||
|
|
0:1 |
Changes to accessibility for SITE. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.18. The complex type siri:AffectedRouteStructure
|
|
An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. |
||||
|
|
0:1 |
Reference to a ROUTE affected by SITUATION. |
|||
|
|
0:* |
DIRECTIONS affected by SITUATION. |
|||
|
|
0:1 |
Sections of ROUTE affected by SITUATION. |
|||
|
|
0:1 |
Stop Poins of the ROUTE. Can be either all or only affected by SITUATION. |
|||
|
|
0:1 |
ROUTE LINKs affected by SITUATION. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.19. The complex type siri:AffectedSectionStructure
|
|
Type for information about the SECTIONs affected by a SITUATION. |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a section of ROUTE affected by a SITUATION. |
||
|
b |
|
-1:1 |
An indirect reference to a COMMON SECTION by stating the stop point ref of the first and last POINT IN JOURNEY PATTERN of the section in question. Intermediate POINTs should be added if necessary to distinguish different sections having the same start and end point and is a means to exclude sections not containing those stop points. |
||
| siri:ProjectionGroup |
|
0:1 |
GIs projection of Section. NB Line here means Geometry Polyline, not Transmodel Transport Line. |
||
|
|
0:1 |
Offset from start or end of section to use when projecting. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.20. The complex type siri:AffectedStopPlaceComponentStructure
|
|
Type for information about the quays affected by an SITUATION. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Disruption of accessibility. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a STOP PLACE. |
|||
|
|
0:* |
Name of component. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Type of Component. |
|||
| ifopt:PlaceProjectionGroup |
0:1 |
Points may be defined in tagged format or using GM coordinates element. |
|||
|
0:1 |
Projection as a geospatial polyline. |
||||
|
0:1 |
PROJECTION onto a geospatial zone. |
||||
|
|
0:1 |
Further qualifcation of affected part of Link projection, |
|||
|
|
0:1 |
Type of AccessFeature (+SIRI.20) |
|||
|
|
0:1 |
Facilities available for component (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.21. The complex type siri:AffectedStopPlaceElementStructure
|
|
Type for information about the quays affected by an SITUATION. |
||||
|
|
0:1 |
Disruption of accessibility. |
|||
28.22. The complex type siri:AffectedStopPlaceStructure
|
|
Type for information about the quays affected by an SITUATION. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Disruption of accessibility. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Identifier of STOP PLACE affected by SITUATION. |
|||
|
|
0:* |
Name of STOP PLACE. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Type of STOP PLACE. |
|||
|
|
0:1 |
Facilities available for VEHICLE JOURNEY (since SIRI 2.0) |
|||
|
|
0:1 |
Quays affected by SITUATION. |
|||
|
|
0:1 |
PathLinks affected by SITUATION. |
|||
|
|
0:1 |
Used to restrict STOP PLACEs to some lines |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.23. The complex type siri:AffectedStopPointStructure
|
|
Type for an SCHEDULED STOP POINT affected by a SITUATION. |
||||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
|
0:1 |
Alternative private code of stop. |
|||
|
|
0:* |
Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Type of stop type. Normally implicit in VEHICLE mode. TPEG table pti 17_4 |
|||
|
|
0:1 |
Spatial coordinates of STOP POINT. Derivable from StopRef. |
|||
|
|
0:1 |
Reference of STOP PLACE related to this affected StopPoint. |
|||
|
|
0:* |
Name of STOP PLACE related to this affected StopPoint. (Unbounded to allow a text for every language) |
|||
|
|
0:1 |
Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. |
|||
|
|
0:1 |
Reference to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. |
|||
|
|
0:* |
Name of locality in which stop is found. Derivable from LocalityRef. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Assessment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. |
|||
|
|
0:* |
Status of STOP |
|||
|
|
0:1 |
CONNECTION links from stop. |
|||
|
|
0:1 |
Used to restrict stop points to some lines |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.24. The complex type siri:AffectedVehicleJourneyStructure
|
|
Type for information about a VEHICLE JOURNEY affected by a SITUATION. |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Refercence to a VEHICLE JOURENY framed by the day. SIRI 2.0 |
||
|
b |
|
-1:* |
DEPRECATED (SIRI 2.1) - use only FramedVehicleJourneyRef |
||
|
|
0:* |
Reference to a specific DATED VEHICLE JOURNEY affected by a SITUATION. |
|||
|
|
0:* |
Name of journey affected by a SITUATION. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
OPERATOR of LINE affected by SITUATION. |
|||
|
|
0:1 |
Reference to the LINE of the journey affected by an SITUATION. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
DIRECTION of LINE in which journey runs. |
|||
|
|
0:1 |
BLOCK which journey runs. (since SIRI 2.0) |
|||
|
|
0:1 |
TRAIN NUMBERs for journey. (since SIRI 2.0) |
|||
|
|
0:1 |
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. |
|||
|
|
0:* |
Restricts the affected scope to the specified origins from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] |
|||
|
|
0:* |
Restricts the affected scope to the specified DESTINATIONs |
|||
|
|
0:* |
ROUTE affected by the SITUATION. |
|||
|
|
0:1 |
Timetabled departure tme of journey from Origin. |
|||
|
|
0:1 |
Timetabled arrival time of journey at Destination. |
|||
|
|
0:* |
DESTINATION name shown for journey at the origin. Can be Used to identify journey for user. (since SIRI 2.0), |
|||
|
|
0:* |
DESTINATION name shown for journey at the origin. Can be Used to identify journey for user. (since SIRI 2.0) |
|||
|
|
0:1 |
Accessibility Disruption status ofto JOURNEY, as affected by Situation. |
|||
|
|
0:* |
Status of service for this Vehicle Journey - TPEG value. Multiple Conditions can be valid at the same time. (since SIRI 2.0) |
|||
|
|
0:1 |
CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type] |
|||
|
|
0:1 |
Facilities available for VEHICLE JOURNEY (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.25. The complex type siri:AffectedVehicleStructure
|
|
Type for information about a VEHICLE affected by an SITUATION. |
||||
|
|
1:1 |
Reference to a specific VEHICLE affected by an SITUATION. |
|||
|
|
0:* |
Registration plate of VEHICLE |
|||
|
|
0:1 |
(Mobile) phone number on which the vehicle can be called |
|||
|
|
0:1 |
Internet protocol address of the VEHICLE in form 000.000.000.000 |
|||
|
|
0:1 |
Radio address of the VEHICLE |
|||
|
|
0:1 |
Reference to VEHICLE JOURNEY framed by the day which the VEHICLE is running. |
|||
|
|
0:1 |
Location where the VEHICLE was when the situation arose |
|||
|
|
0:1 |
Current Location of the VEHICLE |
|||
|
|
0:1 |
Current Accessibility assessment of vehicle. |
|||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
|
|
0:* |
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCK PARTs, there will be a separate delivery for each BLOCK PART and this element will indicate the vehicles that the journey part uses. |
|||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
|
|
0:1 |
Whether the VEHICLE is in traffic congestion. If not, present, not known. |
|||
|
|
0:1 |
Whether the panic alarm on the VEHICLE is activated. Default is 'false'. |
|||
|
|
0:1 |
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
28.26. The complex type siri:CasualtiesStructure
|
|
Type for Information on casualties. |
||||
|
|
0:1 |
Number of fatalities. |
|||
|
|
0:1 |
Number of injured presons. |
|||
28.27. The complex type siri:NetworkRefStructure
|
|
Type for identifier of an OPERATOR Code. |
||||
28.28. The complex type siri:NetworkStructure
|
|
Type for Annotated reference to a NETWORK affected by a SITUATION. |
||||
|
|
0:1 |
Reference to a NETWORK. |
|||
|
|
0:* |
Name of NETWORK. Can be derived from NetworkRef. (Unbounded since SIRI 2.0) |
|||
| siri:AffectedModeGroup |
0:1 |
Vehicle mode or mode of transport. |
|||
|
The element contains one of the following elements (a-h) |
|||||
| siri:PtNetworkModeChoiceGroup |
a |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
b |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
c |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
d |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
e |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
f |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
g |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
|
h |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
| siri:AffectedModeGroup |
|
0:1 |
|||
28.29. The complex type siri:OffsetStructure
|
|
Type for information about the LINEs affected by a SITUATION. |
||||
|
|
0:1 |
Distance in metres from start of link at which SITUATION is to be shown. I f absent use start of link. |
|||
|
|
0:1 |
Distance in metres from end of link at which SITUATION is to be shown. I f absent use end of link. |
|||
28.30. The complex type siri:OperationalUnitRefStructure
|
|
Type for identifier of an OPERATOR Code. |
||||
28.31. The complex type siri:SectionRefStructure
|
|
Type for identifier of a LINE |
||||
28.32. The complex type siri:ZoneRefStructure
|
|
Type for identifier of a ZONe. |
||||
28.33. The complex type complexType[siri:AffectedStopPointStructure]/ConnectionLinks#complexType (typedef-33.1)
|
|
- |
||||
|
|
1:* |
CONNECTION LINKs from stop that are affected by the SITUATION. |
|||
28.34. The complex type complexType[siri:AffectedRouteStructure]/StopPoints#complexType (typedef-33.10)
|
|
- |
||||
|
|
0:1 |
Indicates whether the list of STOP POINTS contains all STOP POINTS of ROUTE or only affected by SITUATION. |
|||
|
|
1:1 |
Stop Point of the ROUTE |
|||
|
|
0:1 |
GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. |
|||
28.35. The complex type complexType[siri:AffectedRouteStructure]/RouteLinks#complexType (typedef-33.11)
|
|
- |
||||
|
|
1:* |
||||
28.36. The complex type complexType[siri:AffectedVehicleJourneyStructure]/TrainNumbers#complexType (typedef-33.12)
|
|
- |
||||
|
|
1:* |
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 |
|||
28.37. The complex type complexType[siri:AffectedVehicleJourneyStructure]/JourneyParts#complexType (typedef-33.13)
|
|
- |
||||
|
|
1:* |
Information about Parts of JOURNEY (since SIRI 2.0) |
|||
28.38. The complex type complexType[siri:AffectedVehicleJourneyStructure]/Calls#complexType (typedef-33.14)
|
|
- |
||||
|
|
1:* |
||||
28.39. The complex type complexType[siri:AffectedVehicleJourneyStructure]/Facilities#complexType (typedef-33.15)
|
|
- |
||||
|
|
1:* |
Facililitiy available for VEHICLE JOURNEY (since SIRI 2.0) |
|||
28.40. The complex type complexType[siri:AffectedCallStructure]/AffectedInterchanges#complexType (typedef-33.16)
|
|
- |
||||
|
|
0:* |
||||
28.41. The complex type complexType[siri:AffectedStopPlaceStructure]/AffectedFacilities#complexType (typedef-33.17)
|
|
- |
||||
|
|
1:* |
Facililitiy available for VEHICLE JOURNEY (since SIRI 2.0) |
|||
28.42. The complex type complexType[siri:AffectedStopPlaceStructure]/AffectedComponents#complexType (typedef-33.18)
|
|
- |
||||
|
|
0:* |
Quay affected by SITUATION. |
|||
28.43. The complex type complexType[siri:AffectedStopPlaceStructure]/AffectedNavigationPaths#complexType (typedef-33.19)
|
|
- |
||||
|
|
1:* |
||||
28.44. The complex type complexType[siri:AffectedStopPointStructure]/Lines#complexType (typedef-33.2)
|
|
- |
||||
|
|
1:* |
||||
28.45. The complex type complexType[siri:AffectedStopPlaceStructure]/Lines#complexType (typedef-33.20)
|
|
- |
||||
|
|
1:* |
||||
28.46. The complex type complexType[siri:AffectedStopPlaceComponentStructure]/AffectedFacilities#complexType (typedef-33.21)
|
|
- |
||||
|
|
1:* |
Facility available for VEHICLE JOURNEY (since SIRI 2.0) |
|||
28.47. The complex type complexType[siri:AffectedModesStructure]/Mode#complexType (typedef-33.3)
|
|
- |
||||
| siri:AffectedModeGroup |
0:1 |
Vehicle mode or mode of transport. |
|||
|
The element contains one of the following elements (a-h) |
|||||
| siri:PtNetworkModeChoiceGroup |
a |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
b |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
c |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
d |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
e |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
f |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
g |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
|
h |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
| siri:AffectedModeGroup |
|
0:1 |
|||
28.48. The complex type complexType[siri:AffectedLineStructure]/Routes#complexType (typedef-33.4)
|
|
- |
||||
|
|
1:* |
Route affected by Situation. |
|||
28.49. The complex type complexType[siri:AffectedLineStructure]/Sections#complexType (typedef-33.5)
|
|
- |
||||
|
|
1:* |
||||
28.50. The complex type complexType[siri:AffectedLineStructure]/StopPoints#complexType (typedef-33.6)
|
|
- |
||||
|
|
1:* |
||||
28.51. The complex type complexType[siri:AffectedLineStructure]/StopPlaces#complexType (typedef-33.7)
|
|
- |
||||
|
|
1:* |
||||
28.52. The complex type complexType[siri:AffectedSectionStructure]/IndirectSectionRef#complexType (typedef-33.8)
|
|
- |
||||
|
The element contains one of the following elements (a-c) |
|||||
|
a |
|
-1:1 |
Used to indicate the SCHEDULED stop point at the start of the SECTION |
||
|
b |
|
-1:1 |
Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as start of the SECTION |
||
|
c |
|
-1:1 |
Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as start of the SECTION |
||
|
The element contains none or more of the following elements (a-c) |
|||||
|
a |
|
-1:1 |
An intermediate Stop POINT of the SECTION that must be part of SECTION |
||
|
b |
|
-1:1 |
Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated StopPlace must be part of the SECTION |
||
|
c |
|
-1:1 |
Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated QUAY must be part of the SECTION |
||
|
The element contains one of the following elements (a-c) |
|||||
|
a |
|
-1:1 |
Used to indicate the SCHEDULED stop point at the end of the SECTION |
||
|
b |
|
-1:1 |
Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as end of the SECTION |
||
|
c |
|
-1:1 |
Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as end of the SECTION |
||
28.53. The complex type complexType[siri:AffectedRouteStructure]/Sections#complexType (typedef-33.9)
|
|
- |
||||
|
|
1:* |
Sections of ROUTE that is affected by SITUATION. |
|||
29. SIRI-SX Situation Classifiers.
29.1. Simple type definitions
|
|
Values for Predictability Status. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for TPEG Pts43 ServiceStatus, with additional values from Pti013 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for TPEG Pti26 - Severity |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for TPEG Pti032 - VerificationStatus |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
- |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
- |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29.2. The toplevel element siri:Condition
|
|
Classification of effect on service. TPEG PTS043 ServiceStatus |
||||
29.3. The toplevel element siri:Predictability
|
|
- |
||||
29.4. The toplevel element siri:Severity
|
|
Severity of Incident - TPEG Pti26. Default is 'normal'. |
||||
29.5. The toplevel element siri:VerificationStatus
|
|
- |
||||
30. SIRI-SX Situation IDentifiers.
30.1. Simple type definitions
|
|
xs:string: (empty restriction) |
Type for identifier of a SITUATION. Includes the Participant identifier and version components of the identifier. |
30.2. The toplevel element siri:SituationFullRef
|
|
Reference to a SITUATION. Elements are retained as atomic elements. |
||||
30.3. The toplevel element siri:SituationNumber
|
|
Identifier of SITUATION within a Participant. Exclude versionr. |
||||
30.4. The toplevel element siri:SituationRef
|
|
Reference to a SITUATION associated with the element. |
||||
30.5. The toplevel element siri:SituationSimpleRef
|
|
Reference to a SITUATION associated with the element. |
||||
30.6. The group siri:SituationBaseIdentityGroup
|
|
Type for reference to a SITUATION or an update to a SITUATION. Participant ref is optional and may be supplied from context. |
||||
| siri:SituationBaseIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created SITUATION. Provides namespace for Participant If absent proided from context. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
1:1 |
Identifier of SITUATION within a Participant. Exclude versionr. |
||||
30.7. The group siri:SituationFullIdentityGroup
|
|
Type for reference to a SITUATION or an update to a SITUATION. Participant ref is optional and may be supplied from context. |
||||
| siri:SituationFullIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as. |
||
|
|
1:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. |
|||
|
1:1 |
Identifier of SITUATION within a Participant. Exclude versionr. |
||||
30.8. The group siri:SituationReferenceGroup
|
|
References to a SITUATION. |
||||
| siri:SituationReferenceGroup |
0:* |
Reference to a SITUATION associated with the element. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
30.10. The group siri:SituationUpdateIdentityGroup
|
|
Type for reference to a SITUATION or an update to a SITUATION. Participant ref is optional and may be supplied from context. |
||||
| siri:SituationUpdateIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
|
0:1 |
Unique identifier of update version within a SITUATION Number Omit if reference to the base SITUATION. |
|||
30.11. The complex type siri:EntryQualifierStructure
|
|
|
- |
|||
30.12. The complex type siri:SituationFullRefStructure
|
|
Type for reference to a SITUATION. |
||||
| siri:SituationFullIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as. |
||
|
|
1:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. |
|||
|
1:1 |
Identifier of SITUATION within a Participant. Exclude versionr. |
||||
| siri:SituationUpdateIdentityGroup |
|
0:1 |
Unique identifier of a Country of a Participant who created Update SITUATION element. Provides namespace for VersionParticipant If absent same as. |
||
|
|
0:1 |
Unique identifier of a Participant. Provides namespace for SITUATION. If absent provdied from context. |
|||
|
|
0:1 |
Unique identifier of update version within a SITUATION Number Omit if reference to the base SITUATION. |
|||
30.13. The complex type siri:SituationRefStructure
|
|
Type for reference to a SITUATION. |
||||
|
0:1 |
Reference to a SITUATION associated with the element. |
||||
|
0:1 |
Reference to a SITUATION. Elements are retained as atomic elements. |
||||
30.15. The complex type siri:SituationSimpleRefStructure
|
|
Type for identifier of a SITUATION. Includes the Participant identifier and version components of the identifier. |
||||
30.16. The complex type siri:SituationVersion
|
|
|
- |
|||
31. siri_situationReasons.xsd
31.1. Simple type definitions
|
|
Values for TPEG Pts38 - AlertCause, plus additional values from TPEG Pti19/20/21/22 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
31.2. The toplevel element siri:AlertCause
|
|
TPEG Pts38: AlertCause. |
||||
31.3. The toplevel element siri:EnvironmentReason
|
|
|
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
31.4. The toplevel element siri:EnvironmentSubReason
|
|
|
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
31.5. The toplevel element siri:EquipmentReason
|
|
|
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
31.6. The toplevel element siri:EquipmentSubReason
|
|
|
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
31.7. The toplevel element siri:MiscellaneousReason
|
|
|
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
31.8. The toplevel element siri:MiscellaneousSubReason
|
|
|
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
31.9. The toplevel element siri:PersonnelReason
|
|
|
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
31.10. The toplevel element siri:PersonnelSubReason
|
|
|
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
31.11. The toplevel element siri:UndefinedReason
|
|
|
DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). |
|||
31.12. The toplevel element siri:UnknownReason
|
|
|
DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). |
|||
31.13. The group siri:TpegReasonGroup
|
|
Structured Classification Elements. |
||||
|
The element contains one of the following elements (a-g) |
|||||
| siri:TpegReasonGroup |
a |
-1:1 |
TPEG Pts38: AlertCause. |
||
|
b |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
e |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
f |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
|
g |
-1:1 |
DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). |
|||
31.14. The group siri:TpegSubReasonGroup
|
|
DEPRECATED since SIRI 2.1 - use only AlertCause. |
||||
|
The element contains one of the following elements (a-d) |
|||||
| siri:TpegSubReasonGroup |
a |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) |
||
|
b |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) |
|||
|
c |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) |
|||
|
d |
-1:1 |
DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) |
|||
32. siri_situationServiceTypes.xsd
32.1. Simple type definitions
|
|
Values for Values for TPEG Pti024 - BookingStatus |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for TPEG Pti31 - InterchangeStatus |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for TPEG Pti27 - ReportType |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for ROUTE POINT type that correspond to TPEG Pts44: StopPlaceUsage (Pti15: deprecated since SIRI 2.1). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for TPEG Pts017 - ServiceDeliveryPointType |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for TPEG Pti025 - TicketRestrictionType |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Values for TPEG Pti033 - TimetableType |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
32.2. The toplevel element siri:BookingStatusType
|
|
Booking Status - TPEG Pti024. |
||||
32.3. The toplevel element siri:InterchangeStatusType
|
|
Status of a SERVICE JOURNEY INTERCHANGE - TPEG Pti31 InterchangeStatus |
||||
32.4. The toplevel element siri:ReportType
|
|
Scope of incident - TPEG Pti27 ReportType |
||||
32.5. The toplevel element siri:RoutePointType
|
|
Type for ROUTE POINT. |
||||
32.6. The toplevel element siri:StopPointType
|
|
STOP POINT type - TPEG Pts017, ServiceDeliveryPointType |
||||
32.7. The toplevel element siri:TicketRestrictionType
|
|
Ticket restrictions - TPEG Pti025 |
||||
32.8. The toplevel element siri:TimetableType
|
|
Timetable type - TPEG Pti033. |
||||
33. SIRI-ST TargetedVehicleJourney for Stop Timetable Service.
33.1. The toplevel element siri:TargetedCall
|
|
Information about the call at the stop. |
||||
33.2. The toplevel element siri:TargetedVehicleJourney
|
|
Timetabled VEHICLE JOURNEY. |
||||
33.3. The group siri:TargetedCallGroup
|
|
Elements for a targeted call. |
||||
| siri:TargetedCallGroup |
|
0:1 |
Reference to a SCHEDULED STOP POINT. Normally this will omitted as will be the same as the monitoring point. |
||
|
1:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
||||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:AimedVehicleArrivalGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:AimedVehicleDepartureGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:AimedCallGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
For frequency based services, target interval between vehicles at stop. |
||||
33.4. The complex type siri:TargetedCallStructure
|
|
Type for a targeted call. |
||||
| siri:TargetedCallGroup |
|
0:1 |
Reference to a SCHEDULED STOP POINT. Normally this will omitted as will be the same as the monitoring point. |
||
|
1:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
|
0:1 |
For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. |
||||
|
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
||||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:AimedVehicleArrivalGroup |
0:1 |
Target arrival time of VEHICLE at stop according to latest working timetable. |
|||
|
0:1 |
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is: (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL. |
||||
|
0:1 |
Type of alighting allowed at stop. Default is 'Alighting'. |
||||
|
|
0:* |
Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0). |
|||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0). |
||||
| siri:AimedVehicleDepartureGroup |
0:1 |
Target departure time of VEHICLE from stop according to latest working timetable. |
|||
|
0:1 |
Departure QUAY (bay or platform) name. Default taken from planned timetable. |
||||
|
0:1 |
Nature of boarding allowed at stop. Default is 'Boarding'. |
||||
|
|
0:* |
||||
|
0:* |
Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1) |
||||
|
0:* |
OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0). |
||||
| siri:AimedCallGroup |
0:1 |
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0) |
|||
|
0:1 |
For frequency based services, target interval between vehicles at stop. |
||||
33.5. The complex type siri:TargetedVehicleJourneyStructure
|
|
Type for a targeted VEHICLE JOURNEY. |
||||
| siri:JourneyIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a DIRECTION, typically outward or return. |
|||
|
|
0:1 |
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
| siri:JourneyInfoGroup |
|
0:* |
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) |
||
|
0:* |
Additional descriptive text associated with journey. Inherited property. |
||||
|
|
0:1 |
Contact details for use by members of public. (since SIRI 2.0) |
|||
|
|
0:1 |
Contact details for use by operational staff. (since SIRI 2.0) |
|||
| siri:JourneyEndTimesGroup |
|
0:1 |
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. |
||
|
|
0:1 |
Timetabled departure time from Origin. |
|||
|
|
0:1 |
Timetabled arrival time at Destination. |
|||
|
0:1 |
Whether journey is first or last journey of day. (since SIRI 2.0) |
||||
|
0:1 |
Information about the call at the stop. |
||||
34. siri_time.xsd
34.1. Simple type definitions
|
|
Values for TPEG Pti34 - DayType |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Subset of TPEG Pti34 - DayType |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Allowed values for EndTime Precision |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Allowed values for EndTime Status. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Subset of TPEG Pti34 - DayType |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
34.2. The toplevel element siri:DayType
|
|
Day on which a SITUATION may apply - TPEG Pti34 DayType |
||||
34.3. The complex type siri:ClosedTimeRangeStructure
|
|
Type for a range of times. Both start and end time are required. |
||||
|
|
1:1 |
The (inclusive) start time. |
|||
|
|
1:1 |
The (inclusive) end time. |
|||
|
|
0:1 |
Precision with which to interpret the inclusive end time. Default is to the second. |
|||
34.4. The complex type siri:ClosedTimestampRangeStructure
|
|
Type for a range of date and times. Both start and end time are required. |
||||
|
|
1:1 |
The (inclusive) start date and time. |
|||
|
|
1:1 |
The (inclusive) end date and time. |
|||
34.5. The complex type siri:HalfOpenTimeRangeStructure
|
|
Type for a range of times. Start time must be specified, end time is optional. |
||||
|
|
1:1 |
The (inclusive) start time. |
|||
|
|
0:1 |
The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". |
|||
34.6. The complex type siri:HalfOpenTimestampInputRangeStructure
|
|
Type for a range of date times. Start time must be specified, end time is optional. |
||||
|
|
1:1 |
The (inclusive) start time stamp. |
|||
|
|
0:1 |
The (inclusive) end time stamp. |
|||
|
|
0:1 |
Precision with which to interpret the inclusive end time. Default is to the second. (Siri 2.0++) |
|||
34.7. The complex type siri:HalfOpenTimestampOutputRangeStructure
|
|
Type for a range of date times. Start time must be specified, end time is optional. |
||||
|
|
1:1 |
The (inclusive) start time stamp. |
|||
|
|
0:1 |
The (inclusive) end time stamp. If omitted, the range end is open-ended, that is, it should be interpreted as defined by end time status. |
|||
|
|
0:1 |
If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++) |
|||
35. SIRI subschema with view of SCHEDULED CONNECTION LINKS for use in Connection Link Discovery service
35.1. The toplevel element siri:AnnotatedConnectionLinkRef
|
|
SCHEDULED CONNECTION LINK definition. |
||||
35.2. The complex type siri:AnnotatedConnectionLinkStructure
|
|
View of a SCHEDULED CONNECTION LINK description. |
||||
|
|
1:1 |
Identifer of the connection link. DetailLevel=minimum |
|||
|
|
0:1 |
Identifer of the feeder's stop. DetailLevel=normal |
|||
|
|
0:1 |
Identifer of the distributor's stop. DetailLevel=normal |
|||
|
|
0:1 |
Whether real-time data is available for the connection link. Default is 'true'. DetailLevel=minimum |
|||
|
|
0:* |
Name of SCHEDULED CONNECTION LINK. DetailLevel=minimum |
|||
|
|
0:* |
Name of the feeder's stop. DetailLevel=full |
|||
|
|
0:* |
Name of the distributor's stop. DetailLevel=full |
|||
|
|
0:1 |
Web page associated with connection link. DetailLevel=full |
|||
36. SIRI subschema with view of classifiers for use in Discovery service
36.1. The toplevel element siri:ProductCategory
|
|
Category for classification of a journey as a Product |
||||
36.2. The toplevel element siri:ServiceFeature
|
|
Service Feature description. |
||||
36.3. The toplevel element siri:VehicleFeature
|
|
Vehicle Feature description. |
||||
36.4. The complex type siri:ProductCategoryStructure
|
|
Type for TYPE OF PRODUCT CATEGORY description. |
||||
|
|
1:1 |
Identifier of TYPE OF PRODUCT CATEGORY classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. |
|||
|
|
1:* |
Name of classification (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Icon used to represent TYPE OF PRODUCT CATEGORY. |
|||
36.5. The complex type siri:ServiceFeatureStructure
|
|
Type for Service Feature description. |
||||
|
|
1:1 |
Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. |
|||
|
|
1:* |
Name of classification. (Unbounded since SIRI 2.0) |
|||
|
|
1:1 |
Icon associated with feature. |
|||
36.6. The complex type siri:VehicleFeaturesStructure
|
|
Type for description of feature of VEHICLE. |
||||
|
|
1:1 |
Identifier of feature of VEHICLE. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. |
|||
|
|
1:* |
Name of feature of VEHICLE. (Unbounded since SIRI 2.0) |
|||
|
|
1:1 |
Icon used to represent feature of VEHICLE. |
|||
37. SIRI subschema with view of Info channel for use in Discovery service
37.1. The toplevel element siri:InfoChannel
|
|
Info Channel supported by Producer service. |
||||
37.2. The complex type siri:InfoChannelStructure
|
|
Type for Info Channels description. |
||||
|
|
1:1 |
Identifier of classification. |
|||
|
|
1:1 |
Name of Info Channel. |
|||
|
|
1:1 |
Icon associated with Info Channel. |
|||
38. SIRI subschema with view of LINE for use in Discovery service
38.1. The toplevel element siri:AnnotatedLineRef
|
|
Information about LINEs covered by server. |
||||
38.2. The toplevel element siri:Destination
|
|
Description of a DESTINATION. |
||||
38.3. The complex type siri:AnnotatedDestinationStructure
|
|
Type for DESTINATION and place name. |
||||
|
|
1:1 |
||||
|
|
1:* |
Name of destination TOPOGRAPHIC PLACE. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Direction in which destination lies. relatoive to currernt stop SIRI 2.0 |
|||
38.4. The complex type siri:AnnotatedLineStructure
|
|
Summary information about a LINE type. |
||||
|
|
1:1 |
Identifier of LINE. |
|||
|
|
1:* |
Name of LINE. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Whether the LINE has real-time info. Default is 'true'. |
|||
|
|
0:1 |
DESTINATIONs to which the LINE runs. Detail level is 'normal' |
|||
|
|
0:1 |
DIRECTIONs and Stops for the LINE. 'normal' |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
38.5. The complex type siri:RouteDirectionStructure
|
|
Type for DIRECTION. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Identifer of DIRECTION, |
|||
|
|
0:* |
Description of DIRECTION. (Unbounded since SIRI 2.0) |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
JourneyPatterns in Direction of route (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
38.6. The complex type siri:StopPointInPatternStructure
|
|
View of a SCHEDULED STOP POINT description. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Identifer of the stop. |
|||
|
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
||||
|
|
0:1 |
Whether real-time data is available for the stop. Default is 'true'. Detail level is 'normal'. |
|||
|
|
0:* |
Name of SCHEDULED STOP POINT. Detail level is 'normal'. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs. +SIRI.v2.0 |
|||
|
|
0:1 |
Service features of stop. Detail level is 'full' |
|||
|
|
0:1 |
LINEs that use stop. Detail level is 'full' |
|||
|
|
0:1 |
Coordinates to use to show stop as a poitn on map. Detail level is 'normal'.+SIRI.v2.0 |
|||
|
|
0:1 |
Web page associated with Stop. Detail level is 'full'+SIRI.v2.0 |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Order of STOP POINT in route (since SIRI 2.0) |
|||
|
|
0:1 |
Plot of points from this stop to next Stop. Detail level is 'full'. (since SIRI 2.0) |
|||
|
|
0:1 |
GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
38.7. The complex type complexType[siri:AnnotatedStopPointStructure]/Features#complexType (typedef-2.1)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Description of Service features of stop. |
||
|
b |
-1:1 |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
|||
38.8. The complex type complexType[siri:AnnotatedStopPointStructure]/Lines#complexType (typedef-2.2)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Reference to a LINE that calls at stop. |
||
|
b |
|
-1:1 |
Reference to a LINE that calls at stop. and its direction (since SIRI 2.0) |
||
38.9. The complex type complexType[siri:AnnotatedLineStructure]/Destinations#complexType (typedef-5.1)
|
|
- |
||||
|
1:* |
Description of a DESTINATION. |
||||
38.10. The complex type complexType[siri:AnnotatedLineStructure]/Directions#complexType (typedef-5.2)
|
|
- |
||||
|
|
1:* |
Directions of Route |
|||
38.11. The complex type complexType[siri:RouteDirectionStructure]/JourneyPatterns#complexType (typedef-5.3)
|
|
- |
||||
|
|
1:* |
JourneyPattern. (since SIRI 2.0) |
|||
38.12. The complex type complexType[siri:RouteDirectionStructure]/JourneyPatterns/JourneyPattern#complexType (typedef-5.4)
|
|
- |
||||
|
0:1 |
Reference to a JOURNEY PATTERN. |
||||
|
|
0:* |
Name Of Journety Pattern (SIRI 2.0) |
|||
|
|
0:1 |
Ordered collection of STOP POINTs the LINE and direction . Detail level is 'stops'. (since SIRI 2.0) |
|||
38.13. The complex type complexType[siri:RouteDirectionStructure]/JourneyPatterns/JourneyPattern/StopsInPattern#complexType (typedef-5.5)
|
|
- |
||||
|
|
2:* |
Stop within Route of LINE. Detail level is 'stop' (since SIRI 2.0) |
|||
39. SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service
39.1. The toplevel element siri:AnnotatedStopPointRef
|
|
SCHEDULED STOP POINT definition. |
||||
39.2. The complex type siri:AnnotatedStopPointStructure
|
|
View of a SCHEDULED STOP POINT description. |
||||
|
|
1:1 |
Identifer of the stop. |
|||
|
0:1 |
Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. |
||||
|
|
0:1 |
Whether real-time data is available for the stop. Default is 'true'. Detail level is 'normal'. |
|||
|
|
0:* |
Name of SCHEDULED STOP POINT. Detail level is 'normal'. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs. +SIRI.v2.0 |
|||
|
|
0:1 |
Service features of stop. Detail level is 'full' |
|||
|
|
0:1 |
LINEs that use stop. Detail level is 'full' |
|||
|
|
0:1 |
Coordinates to use to show stop as a poitn on map. Detail level is 'normal'.+SIRI.v2.0 |
|||
|
|
0:1 |
Web page associated with Stop. Detail level is 'full'+SIRI.v2.0 |
|||
39.3. The complex type complexType[siri:AnnotatedStopPointStructure]/Features#complexType (typedef-2.1)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Description of Service features of stop. |
||
|
b |
-1:1 |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
|||
39.4. The complex type complexType[siri:AnnotatedStopPointStructure]/Lines#complexType (typedef-2.2)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Reference to a LINE that calls at stop. |
||
|
b |
|
-1:1 |
Reference to a LINE that calls at stop. and its direction (since SIRI 2.0) |
||
40. SIRI-PT DATED JOURNEY Model view.
40.1. The toplevel element siri:DatedTimetableVersionFrame
|
|
A TIMETABLE FRAME to run on a specified date. |
||||
40.2. The toplevel element siri:ProductionTimetableCapabilitiesRequest
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
|
1:1 |
Version number of request. Fixed. |
|||
|
|
0:1 |
Whether to include the requestors permissions in the response. Only applies if Access control capability supported. Default is 'false'. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.3. The toplevel element siri:ProductionTimetableCapabilitiesResponse
|
|
+siri:ProductionTimetableCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Capabilities for ProductionTimetable Service. Answers a Answered with a ProductionTimetableCapabilitiesRequest. |
|||
40.4. The toplevel element siri:ProductionTimetableDelivery
|
|
+siri:ProductionTimetableDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery for Production Timetable Service. |
|||
40.5. The toplevel element siri:ProductionTimetablePermissions
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:* |
Permission for a single participant or all participants to use an aspect of the service. |
||||
40.6. The toplevel element siri:ProductionTimetableRequest
|
|
+siri:ProductionTimetableRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for daily production timetables. |
|||
40.7. The toplevel element siri:ProductionTimetableServiceCapabilities
|
|
Capabilities of ProductionTimetableService. |
||||
40.8. The toplevel element siri:ProductionTimetableSubscriptionRequest
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
1:1 |
Request for daily production timetables. |
||||
| siri:ProductionTimetableSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.9. The group siri:ProductionTimetablePayloadGroup
|
|
Payload part of Production Timetable delivery. |
||||
| siri:ProductionTimetablePayloadGroup |
0:* |
A TIMETABLE FRAME to run on a specified date. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.10. The group siri:ProductionTimetableRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. |
||||
| siri:ProductionTimetableRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
0:1 |
Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
|
0:1 |
Whether to return the whole timetable, or just differences from the inidicated version. Default is 'false'. |
|||
40.11. The group siri:ProductionTimetableSubscriptionPolicyGroup
|
|
Parameters that affect the subscription content. |
||||
| siri:ProductionTimetableSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request. |
||
40.12. The group siri:ProductionTimetableTopicGroup
|
|
Parameters that specify the content to be returned. |
||||
| siri:ProductionTimetableTopicGroup |
|
0:1 |
|||
|
|
0:1 |
Communicate only differences to the timetable specified by this VERSION of the TIMETABLe. |
|||
|
|
0:* |
Filter the results to include journeys for only the specified OPERATORs. |
|||
|
|
0:1 |
Filter the results to include only vehicles along the given LINEs. |
|||
|
|
0:* |
Filter the results to include only journeys of the specified VEHICLE MODE. (since SIRI 2.1) |
|||
|
|
0:* |
Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. (since SIRI 2.1) |
|||
|
|
0:* |
Filter the results to include only journeys with a CALL at the specified STOP POINT. (since SIRI 2.1) |
|||
40.13. The group siri:SiriProductionTimetableIndexGroup
|
|
Convenience artefact to pick out main elements of the Production Timetable Service. |
||||
| siri:SiriProductionTimetableIndexGroup |
1:1 |
Request for daily production timetables. |
|||
|
1:1 |
Request for a subscription to the Production Timetable Service. |
||||
|
1:1 |
Delivery for Production Timetable Service. |
||||
|
1:1 |
Request for information about ProductionTimetable Service Capabilities. Answered with a ProductionTimetableCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for ProductionTimetable Service. Answers a Answered with a ProductionTimetableCapabilitiesRequest. |
||||
40.14. The complex type siri:DatedTimetableVersionFrameStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Timetable Version. |
|||
|
|
0:1 |
||||
|
|
0:1 |
Minimum interval at which updates for this DATED TIMETABLE VERSION FRAME can be sent. (since SIRI 2.1) |
|||
| siri:LineIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a LINE DIRECTION DIRECTION, typically outward or return. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:DatedServiceInfoGroup |
|
0:* |
Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (since SIRI 2.0) |
||
|
|
0:* |
Description of the destination stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Additional Text associated with LINE. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Whether journey is first or last jouurney of day. (since SIRI 2.0) |
|||
| siri:TimetableRealtimeInfoGroup |
|
0:1 |
Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable. |
||
|
|
0:1 |
Whether VEHICLE JOURNEYs of LINE are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable. |
|||
|
|
0:* |
Complete list of all planned VEHICLE JOURNEYs for this LINE and DIRECTION. |
|||
|
|
0:* |
List of all removed VEHICLE JOURNEYs for this LINE and DIRECTION. A data producer may silently remove a journey from the plan if it was previously provided in error. Careful: Removal is different from Cancellation. Minimal information, or no information at all, of a RemovedDatedVehicleJourney or the removal itself must be communicated to the passengers, i.e., it is "silently" removed. A Cancellation, on the other hand, is possibly the most important information to provide to the passengers. It is strongly advised to only use this feature in cases where a journey was sent in error and it can be assumed that as few passengers as possible have seen the erroneous information to avoid confusion. (since SIRI 2.1) |
|||
|
|
0:* |
Connection paramters for a SERVICE JOURNEY INTERCHANGE between a feeder and distributor journey. SIRI 2.0 |
|||
|
|
0:* |
List of all removed SERVICE JOURNEY INTERCHANGEs. A data producer may silently remove an interchange from the plan if it was previously provided in error. Careful: Removal is different from Cancellation. Minimal information, or no information at all, of a RemovedServiceJourneyInterchange or the removal itself must be communicated to the passengers, i.e., it is "silently" removed. A Cancellation, on the other hand, is possibly the most important information to provide to the passengers. It is strongly advised to only use this feature in cases where an interchange was sent in error and it can be assumed that as few passengers as possible have seen the erroneous information to avoid confusion. (since SIRI 2.1) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.15. The complex type siri:ProductionTimetableCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. fixed. |
|||
|
0:1 |
Capabilities of ProductionTimetableService. |
||||
|
0:1 |
Participant's permissions to use the service. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.16. The complex type siri:ProductionTimetableCapabilityRequestPolicyStructure
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether results returns foreign journeys only. |
|||
40.17. The complex type siri:ProductionTimetableDeliveriesStructure
|
|
Type for deliveries of production timetable service. Used in WSDL. |
||||
|
1:* |
Delivery for Production Timetable Service. |
||||
40.18. The complex type siri:ProductionTimetableDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. fixed. |
|||
| siri:ProductionTimetablePayloadGroup |
0:* |
A TIMETABLE FRAME to run on a specified date. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.19. The complex type siri:ProductionTimetableRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed. |
|||
| siri:ProductionTimetableTopicGroup |
|
0:1 |
|||
|
|
0:1 |
Communicate only differences to the timetable specified by this VERSION of the TIMETABLe. |
|||
|
|
0:* |
Filter the results to include journeys for only the specified OPERATORs. |
|||
|
|
0:1 |
Filter the results to include only vehicles along the given LINEs. |
|||
|
|
0:* |
Filter the results to include only journeys of the specified VEHICLE MODE. (since SIRI 2.1) |
|||
|
|
0:* |
Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. (since SIRI 2.1) |
|||
|
|
0:* |
Filter the results to include only journeys with a CALL at the specified STOP POINT. (since SIRI 2.1) |
|||
| siri:ProductionTimetableRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
0:1 |
Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) |
||||
|
|
0:1 |
Whether to return the whole timetable, or just differences from the inidicated version. Default is 'false'. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.20. The complex type siri:ProductionTimetableServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Filtering Capabilities. |
|||
|
|
0:1 |
Request Policiy capabilities. |
|||
|
|
0:1 |
Subscription Policy capabilities. |
|||
|
|
0:1 |
Optional Access control capabilities. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.21. The complex type siri:ProductionTimetableSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for daily production timetables. |
||||
| siri:ProductionTimetableSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.22. The complex type siri:TimetableValidityPeriod
|
|
Type for a range of date and times. Both start and end time are required. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
The (inclusive) start date and time. |
|||
|
|
1:1 |
The (inclusive) end date and time. |
|||
40.23. The complex type group[siri:ProductionTimetableTopicGroup]/Lines#complexType (typedef-74.1)
|
|
- |
||||
|
|
1:* |
Iinclude only vehicles along the given LINE. |
|||
40.24. The complex type element[siri:ProductionTimetableSubscriptionRequest]#complexType (typedef-74.2)
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
1:1 |
Request for daily production timetables. |
||||
| siri:ProductionTimetableSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.25. The complex type element[siri:ProductionTimetableCapabilitiesRequest]#complexType (typedef-74.3)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
|
1:1 |
Version number of request. Fixed. |
|||
|
|
0:1 |
Whether to include the requestors permissions in the response. Only applies if Access control capability supported. Default is 'false'. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
40.26. The complex type complexType[siri:ProductionTimetableServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-74.4)
|
|
- |
||||
|
1:1 |
Whether results can be filtered by VALIDITY PERIOD. Default is 'true'. |
||||
|
1:1 |
Whether results can be filtered by OPERATOR. Default is 'true'. |
||||
|
1:1 |
Whether results can be filtered by LINE. Default is 'true' |
||||
|
0:1 |
Whether results can be filtered by VEHICLE MODE. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. (since SIRI 2.1) |
||||
|
0:1 |
Whether results can be filtered by SCHEDULED STOP POINT. Default is 'true'. |
||||
|
|
1:1 |
Whether results can be filtered by TIMETABLE VERSION Default is 'true'. |
|||
40.27. The complex type complexType[siri:ProductionTimetableServiceCapabilitiesStructure]/RequestPolicy#complexType (typedef-74.5)
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
40.28. The complex type complexType[siri:ProductionTimetableServiceCapabilitiesStructure]/SubscriptionPolicy#complexType (typedef-74.6)
|
|
- |
||||
|
|
1:1 |
Whether incremental updates can be specified for updates Default is ' true'. |
|||
40.29. The complex type element[siri:ProductionTimetablePermissions]#complexType (typedef-74.7)
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:* |
Permission for a single participant or all participants to use an aspect of the service. |
||||
41. SIRI-SX Situation Exchange Service.
41.1. The toplevel element siri:IncludedSituationExchangeDelivery
|
|
+siri:SituationExchangeDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery of Situation Exchange Service included as supplement to main functional service delivery. |
|||
41.2. The toplevel element siri:SituationExchangeCapabilitiesRequest
|
|
+siri:ServiceCapabilitiesRequestStructure (↔ siri:AbstractFunctionalServiceCapabilitiesRequest) |
Request for information about Situation Exchange Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
|||
41.3. The toplevel element siri:SituationExchangeCapabilitiesResponse
|
|
+siri:SituationExchangeCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Capabilities for Situation Exchange Service. Answers a VehicleMontoringCapabilitiesRequest. |
|||
41.4. The toplevel element siri:SituationExchangeDelivery
|
|
+siri:SituationExchangeDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery for Situation Exchange Service. |
|||
41.5. The toplevel element siri:SituationExchangePermissions
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
||||
41.6. The toplevel element siri:SituationExchangeRequest
|
|
+siri:SituationExchangeRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about Facilities status. |
|||
41.7. The toplevel element siri:SituationExchangeServiceCapabilities
|
|
Capabilities of Situation Exchange Service. Answers a SituationExchangeCapabilitiesRequest. |
||||
41.8. The toplevel element siri:SituationExchangeSubscriptionRequest
|
|
+siri:SituationExchangeSubscriptionStructure (↔ siri:AbstractFunctionalServiceSubscriptionRequest) |
Request for a subscription to the Situation Exchange Service. |
|||
41.9. The group siri:SiriSituationExchangeServiceIndexGroup
|
|
Convenience artifact to pick out main elements of the Situation Exchange Service. |
||||
| siri:SiriSituationExchangeServiceIndexGroup |
1:1 |
Request for information about Facilities status. |
|||
|
1:1 |
Request for a subscription to the Situation Exchange Service. |
||||
|
1:1 |
Delivery for Situation Exchange Service. |
||||
|
1:1 |
Request for information about Situation Exchange Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for Situation Exchange Service. Answers a VehicleMontoringCapabilitiesRequest. |
||||
41.10. The group siri:SituationClassifierFilterGroup
|
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Classifiers. Logically ANDed with other values. |
||||
| siri:SituationClassifierFilterGroup |
|
0:1 |
Severity filter value to apply: only SITUATIONs with a severity greater than or equal to the specified value will be returned. See TPEG severities. Default is 'normal'. |
||
|
|
0:* |
Types of SITUATION to include. |
|||
|
|
0:1 |
Whether just planned, unplanned or both SITUATIONs will be returned. |
|||
|
|
0:1 |
Arbitrary application specific classifiers. Only SITUATIONs that match these keywords will be returned. |
|||
41.11. The group siri:SituationExchangePayloadGroup
|
|
Payload part of Situation Exchange Service delivery. |
||||
| siri:SituationExchangePayloadGroup |
|
0:1 |
Default context for common properties of SITUATIONs, Values specified apply to all SITUATIONs unless overridden. Can be used optionally to reduce file bulk. |
||
|
|
0:1 |
SITUATIONs in Delivery. |
|||
41.12. The group siri:SituationExchangeRequestPolicyGroup
|
|
Parameters that affect the request processing. |
||||
| siri:SituationExchangeRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
The maximum number of SITUATION elements to return in a given delivery. The most recent n Events within the look ahead window are included. |
|||
41.13. The group siri:SituationExchangeSubscriptionPolicyGroup
|
|
Parameters that affect the subscription publishing and notification processing. |
||||
| siri:SituationExchangeSubscriptionPolicyGroup |
|
0:1 |
Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. If false or omitted, each subscription response will contain the full information as specified in this request. |
||
41.14. The group siri:SituationExchangeTopicGroup
|
|
Parameters that specify the content to be returned. Logically ANDed with other values. |
||||
| siri:TemporalSubscriptionGroup |
|
0:1 |
Forward duration for which SITUATIONs should be included, that is, only SITUATIONs that start before the end of this window time will be included. |
||
|
|
0:1 |
Start time for selecting SITUATIONs to be sent. Only SITUATIONs or updates created after this time will be sent. This enables a restart without resending everything. |
|||
| siri:TemporalContentFilterGroup |
|
0:1 |
Temporal scope of Situations be included in response. The Situations must be valid within the specified period of time. (since SIRI 2.0) |
||
|
|
0:1 |
Only incidents that are currently within their publication window shouldbe included. Otherwose all incidents will be included. Default is false |
|||
| siri:AffectedModeGroup |
0:1 |
Vehicle mode or mode of transport. |
|||
|
The element contains one of the following elements (a-h) |
|||||
| siri:PtNetworkModeChoiceGroup |
a |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
b |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
c |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
d |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
e |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
f |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
g |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
|
h |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
| siri:AffectedModeGroup |
|
0:1 |
|||
| siri:SituationClassifierFilterGroup |
|
0:1 |
Severity filter value to apply: only SITUATIONs with a severity greater than or equal to the specified value will be returned. See TPEG severities. Default is 'normal'. |
||
|
|
0:* |
Types of SITUATION to include. |
|||
|
|
0:1 |
Whether just planned, unplanned or both SITUATIONs will be returned. |
|||
|
|
0:1 |
Arbitrary application specific classifiers. Only SITUATIONs that match these keywords will be returned. |
|||
| siri:SituationStatusFilterGroup |
|
0:1 |
Whether incident has been verified or not If not specified return all. |
||
|
|
0:* |
Workflow Progress Status. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. If not specified return open, published closing and closed. l. |
|||
|
|
0:1 |
Whether SITUATION is real or a test. If not specified return all. |
|||
| siri:SituationNetworkFilterGroup |
|
0:1 |
Referance to an OPERATOR. If unspecified, all OPERATOR.s. |
||
|
|
0:* |
OPERATIONAL UNIT responsible for managing services. |
|||
|
|
0:1 |
Reference to a NETWORK. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:* |
Reference to a LINE. |
|||
|
b |
|
-0:1 |
Filter the results to include only situations along the given LINEs. |
||
|
0:* |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:* |
Reference to a CONNECTION link |
||||
|
0:* |
Reference to a Facility. |
||||
| siri:SituationStopPlaceFilterGroup |
|
0:1 |
Reference to a STOP PLACE. |
||
|
|
0:1 |
Reference to part of a STOP PLACE. (since SIRI 2.0) |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
| siri:SituationJourneyFilterGroup |
a |
|
-1:1 |
Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 |
|
|
b |
-1:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
|
0:1 |
Reference to a VEHICLE. |
||||
| siri:SituationPlaceFilterGroup |
|
0:1 |
Reference to a COUNTRY where incident takes place If specified only incidents that affect this place country will be returned. |
||
|
|
0:1 |
Reference to a TOPOGRAPHIC PLACE. Only incidents which are deemed to affect this place will be returned. |
|||
|
|
0:2 |
Bounding box of an arbitrary area. Only incidents geocoded as falling within area will be included. |
|||
| siri:SituationExchangeTopicGroup |
|
0:1 |
Parameters to filter Situation Exchange Service requests, based on the SITUATION Road. Logically ANDed with other values. |
||
|
|
0:* |
Parameters to filter Situation Exchange Service requests, based on specific needs . |
|||
41.15. The group siri:SituationExchangeVolumeGroup
|
|
Elements for volume control. |
||||
| siri:SituationExchangeVolumeGroup |
|
0:1 |
Whether a maximum number ofSITUATIONS to include can be specified. Default is 'false'. |
||
41.16. The group siri:SituationJourneyFilterGroup
|
|
Parameters to filter Situation Exchange Service requests, based on the VEHICLE JOURNEYs affected by the SITUATION. Logically ANDed with other values. |
||||
|
The element contains none or one of the following elements (a-b) |
|||||
| siri:SituationJourneyFilterGroup |
a |
|
-1:1 |
Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 |
|
|
b |
-1:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
|
0:1 |
Reference to a VEHICLE. |
||||
41.17. The group siri:SituationNetworkFilterGroup
|
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Network. Logically ANDed with other values. |
||||
| siri:SituationNetworkFilterGroup |
|
0:1 |
Referance to an OPERATOR. If unspecified, all OPERATOR.s. |
||
|
|
0:* |
OPERATIONAL UNIT responsible for managing services. |
|||
|
|
0:1 |
Reference to a NETWORK. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:* |
Reference to a LINE. |
|||
|
b |
|
-0:1 |
Filter the results to include only situations along the given LINEs. |
||
|
0:* |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:* |
Reference to a CONNECTION link |
||||
|
0:* |
Reference to a Facility. |
||||
41.18. The group siri:SituationPlaceFilterGroup
|
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Place. Logically ANDed with other values. |
||||
| siri:SituationPlaceFilterGroup |
|
0:1 |
Reference to a COUNTRY where incident takes place If specified only incidents that affect this place country will be returned. |
||
|
|
0:1 |
Reference to a TOPOGRAPHIC PLACE. Only incidents which are deemed to affect this place will be returned. |
|||
|
|
0:2 |
Bounding box of an arbitrary area. Only incidents geocoded as falling within area will be included. |
|||
41.19. The group siri:SituationStatusFilterGroup
|
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. |
||||
| siri:SituationStatusFilterGroup |
|
0:1 |
Whether incident has been verified or not If not specified return all. |
||
|
|
0:* |
Workflow Progress Status. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. If not specified return open, published closing and closed. l. |
|||
|
|
0:1 |
Whether SITUATION is real or a test. If not specified return all. |
|||
41.20. The group siri:SituationStopPlaceFilterGroup
|
|
Parameters to filter Situation Exchange Service requests, based on the STOP PLACEs affected SITUATIONs. Logically ANDed with other values. |
||||
| siri:SituationStopPlaceFilterGroup |
|
0:1 |
Reference to a STOP PLACE. |
||
|
|
0:1 |
Reference to part of a STOP PLACE. (since SIRI 2.0) |
|||
41.21. The group siri:TemporalContentFilterGroup
|
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. |
||||
| siri:TemporalContentFilterGroup |
|
0:1 |
Temporal scope of Situations be included in response. The Situations must be valid within the specified period of time. (since SIRI 2.0) |
||
|
|
0:1 |
Only incidents that are currently within their publication window shouldbe included. Otherwose all incidents will be included. Default is false |
|||
41.22. The group siri:TemporalSubscriptionGroup
|
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. |
||||
| siri:TemporalSubscriptionGroup |
|
0:1 |
Forward duration for which SITUATIONs should be included, that is, only SITUATIONs that start before the end of this window time will be included. |
||
|
|
0:1 |
Start time for selecting SITUATIONs to be sent. Only SITUATIONs or updates created after this time will be sent. This enables a restart without resending everything. |
|||
41.23. The complex type siri:ContextStructure
|
|
Common parameters for all SITUATIONs. |
||||
|
|
0:1 |
Reference to a Country of a Participant who published SITUATION. |
|||
|
|
1:1 |
Reference to a system publishing SITUATIONs. If SITUATIONs from other participants are included in delivery, then ParticipantRef of immediate publisher must be given here. |
|||
|
|
0:1 |
Refrence to a TOPOGRAPHIC PLACE (locality). Also Derivable from an individual StopRef. |
|||
|
|
0:* |
Name of locality in which SITUATIONs apply. Derivable from LocalityRef. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Default language of text. |
|||
|
|
0:1 |
Default context for common properties of Public Transport SITUATIONs. |
|||
|
|
0:1 |
Actions that apply to all SITUATIONs unless overridden. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
41.24. The complex type siri:NetworkContextStructure
|
|
Type for shared context. |
||||
|
|
0:* |
Default OPERATOR for SITUATIONs. |
|||
|
|
0:1 |
Default Network of affected LINEs. These values apply to all SITUATIONs unless overridden on individual instances. |
|||
41.25. The complex type siri:RoadFilterStructure
|
|
Type for Parameters to filter Situation Exchange Service requests, based on the SITUATION Road, Logically ANDed with other values. |
||||
|
|
0:1 |
Identifier or number of the road on which the reference POINT is located. |
|||
|
|
0:1 |
The DIRECTION at the reference point in terms of general destination DIRECTION. If absent both. |
|||
|
|
0:1 |
Road reference POINT identifier, unique on the specified road. |
|||
41.26. The complex type siri:SituationExchangeCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
|
0:1 |
Capabilities of Situation Exchange Service. Answers a SituationExchangeCapabilitiesRequest. |
||||
|
0:1 |
Participant's permissions to use the service. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
41.27. The complex type siri:SituationExchangeDeliveriesStructure
|
|
Type for Deliveries for Situation Exchange Service. Used in WSDL. |
||||
|
1:* |
Delivery for Situation Exchange Service. |
||||
41.28. The complex type siri:SituationExchangeDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:SituationExchangePayloadGroup |
|
0:1 |
Default context for common properties of SITUATIONs, Values specified apply to all SITUATIONs unless overridden. Can be used optionally to reduce file bulk. |
||
|
|
0:1 |
SITUATIONs in Delivery. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
41.29. The complex type siri:SituationExchangeRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:TemporalSubscriptionGroup |
|
0:1 |
Forward duration for which SITUATIONs should be included, that is, only SITUATIONs that start before the end of this window time will be included. |
||
|
|
0:1 |
Start time for selecting SITUATIONs to be sent. Only SITUATIONs or updates created after this time will be sent. This enables a restart without resending everything. |
|||
| siri:TemporalContentFilterGroup |
|
0:1 |
Temporal scope of Situations be included in response. The Situations must be valid within the specified period of time. (since SIRI 2.0) |
||
|
|
0:1 |
Only incidents that are currently within their publication window shouldbe included. Otherwose all incidents will be included. Default is false |
|||
| siri:AffectedModeGroup |
0:1 |
Vehicle mode or mode of transport. |
|||
|
The element contains one of the following elements (a-h) |
|||||
| siri:PtNetworkModeChoiceGroup |
a |
-1:1 |
TPEG Pti08 and Pts108 "AirService" submodes. |
||
|
b |
-1:1 |
TPEG Pti05 and Pts105 "BusService" submodes. |
|||
|
c |
-1:1 |
TPEG Pti03 and Pts103 "CoachService" submodes. |
|||
|
d |
-1:1 |
TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. |
|||
|
e |
-1:1 |
TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. |
|||
|
f |
-1:1 |
TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. |
|||
|
g |
-1:1 |
TPEG Pti07 and Pts107 "WaterTransportService" submodes. |
|||
|
h |
-1:1 |
TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. |
|||
| siri:AffectedModeGroup |
|
0:1 |
|||
| siri:SituationClassifierFilterGroup |
|
0:1 |
Severity filter value to apply: only SITUATIONs with a severity greater than or equal to the specified value will be returned. See TPEG severities. Default is 'normal'. |
||
|
|
0:* |
Types of SITUATION to include. |
|||
|
|
0:1 |
Whether just planned, unplanned or both SITUATIONs will be returned. |
|||
|
|
0:1 |
Arbitrary application specific classifiers. Only SITUATIONs that match these keywords will be returned. |
|||
| siri:SituationStatusFilterGroup |
|
0:1 |
Whether incident has been verified or not If not specified return all. |
||
|
|
0:* |
Workflow Progress Status. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. If not specified return open, published closing and closed. l. |
|||
|
|
0:1 |
Whether SITUATION is real or a test. If not specified return all. |
|||
| siri:SituationNetworkFilterGroup |
|
0:1 |
Referance to an OPERATOR. If unspecified, all OPERATOR.s. |
||
|
|
0:* |
OPERATIONAL UNIT responsible for managing services. |
|||
|
|
0:1 |
Reference to a NETWORK. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-0:* |
Reference to a LINE. |
|||
|
b |
|
-0:1 |
Filter the results to include only situations along the given LINEs. |
||
|
0:* |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:* |
Reference to a CONNECTION link |
||||
|
0:* |
Reference to a Facility. |
||||
| siri:SituationStopPlaceFilterGroup |
|
0:1 |
Reference to a STOP PLACE. |
||
|
|
0:1 |
Reference to part of a STOP PLACE. (since SIRI 2.0) |
|||
|
The element contains none or one of the following elements (a-b) |
|||||
| siri:SituationJourneyFilterGroup |
a |
|
-1:1 |
Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 |
|
|
b |
-1:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a SERVICE JOURNEY INTERCHANGE. |
||||
|
0:1 |
Reference to a VEHICLE. |
||||
| siri:SituationPlaceFilterGroup |
|
0:1 |
Reference to a COUNTRY where incident takes place If specified only incidents that affect this place country will be returned. |
||
|
|
0:1 |
Reference to a TOPOGRAPHIC PLACE. Only incidents which are deemed to affect this place will be returned. |
|||
|
|
0:2 |
Bounding box of an arbitrary area. Only incidents geocoded as falling within area will be included. |
|||
| siri:SituationExchangeTopicGroup |
|
0:1 |
Parameters to filter Situation Exchange Service requests, based on the SITUATION Road. Logically ANDed with other values. |
||
|
|
0:* |
Parameters to filter Situation Exchange Service requests, based on specific needs . |
|||
| siri:SituationExchangeRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
The maximum number of SITUATION elements to return in a given delivery. The most recent n Events within the look ahead window are included. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
41.30. The complex type siri:SituationExchangeServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Filtering Capabilities. |
|||
|
|
0:1 |
Request Policy capabilities. |
|||
|
|
0:1 |
Subscription Policy capabilities. |
|||
|
|
0:1 |
Optional Access control capabilities. |
|||
|
|
0:1 |
Optional Response capabilities. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
41.31. The complex type siri:SituationExchangeServicePermissionStructure
|
|
Type for Abstract Permission. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. |
||
|
b |
|
-1:1 |
Permission applies to specified participant. |
||
|
|
0:1 |
Permissions for general capabilities. |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
The OPERATOR data that the participant may access. |
||||
|
1:1 |
The LINEs that the participant may access. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
41.32. The complex type siri:SituationExchangeSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for information about Facilities status. |
||||
| siri:SituationExchangeSubscriptionPolicyGroup |
|
0:1 |
Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. If false or omitted, each subscription response will contain the full information as specified in this request. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
41.33. The complex type element[siri:LinePermissions]#complexType (typedef-21.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this LINE. |
||
41.34. The complex type element[siri:OperatorPermissions]#complexType (typedef-21.2)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this OPERATOR. |
||
41.35. The complex type complexType[siri:AbstractPermissionStructure]/GeneralCapabilities#complexType (typedef-45.1)
|
|
- |
||||
|
|
1:1 |
Participant may make direct requests for data. Default is 'true'. |
|||
|
|
1:1 |
Participant may create subscriptions. Default True. |
|||
41.36. The complex type group[siri:SituationExchangeTopicGroup]/SituationRoadFilter#complexType (typedef-81.1)
|
|
- |
||||
|
|
1:* |
||||
41.37. The complex type group[siri:SituationNetworkFilterGroup]/Lines#complexType (typedef-81.2)
|
|
- |
||||
|
|
1:* |
Filter the results to include only the given line. and direction |
|||
41.38. The complex type group[siri:SituationExchangePayloadGroup]/Situations#complexType (typedef-81.3)
|
|
- |
||||
|
|
0:* |
Description of a SITUATION. |
|||
|
0:* |
Type for individual IPT ncident. |
||||
41.39. The complex type complexType[siri:SituationExchangeServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-81.4)
|
|
- |
||||
|
|
1:1 |
Default preview interval. Default is 60 minutes. |
|||
|
0:1 |
Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'. |
||||
|
|
0:1 |
Whether results can be filtered by location. Fixed as 'true'. |
|||
|
0:1 |
Whether results can be filtered by VEHICLE. Default is 'false'. |
||||
|
|
0:1 |
Whether results can be filtered by MODE. Default is true.. ((since SIRI 2.0)) |
|||
|
|
0:1 |
Whether results can be filtered by NETWORKs. Default is 'true'. ((since SIRI 2.0)) |
|||
|
0:1 |
Whether results can be filtered by LINE. Default is 'true' |
||||
|
0:1 |
Whether results can be filtered by SCHEDULED STOP POINT. Default is 'true'. |
||||
|
|
0:1 |
Whether results can be filtered by STOP PLACE identifvier. Default is 'false'. ((since SIRI 2.0)) |
|||
|
0:1 |
Whether results can be filtered by VEHICLE JOURNEY. Default is 'false'. |
||||
|
0:1 |
Whether results can be filtered by CONNECTION LINK. Default is 'true'. |
||||
|
0:1 |
Whether results can be filtered by SERVICE JOURNEY INTERCHANGE. Default is 'false'. |
||||
|
|
0:1 |
Whether results can be filtered by Specific Needs. Default is 'true'. |
|||
|
|
0:1 |
Whether results can be filtered by Keywords. Default is 'false' |
|||
41.40. The complex type complexType[siri:SituationExchangeServiceCapabilitiesStructure]/RequestPolicy#complexType (typedef-81.5)
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
| siri:SituationExchangeVolumeGroup |
|
0:1 |
Whether a maximum number ofSITUATIONS to include can be specified. Default is 'false'. |
||
41.41. The complex type complexType[siri:SituationExchangeServiceCapabilitiesStructure]/AccessControl#complexType (typedef-81.6)
|
|
Type for Common Access control capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether access control of requests is supported. Default is 'false'. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
If access control is supported, whether access control by OPERATOR is supported. Default is 'true'. |
||||
|
0:1 |
If access control is supported, whether access control by LINE is supported. Default is 'true'. |
||||
41.42. The complex type complexType[siri:SituationExchangeServiceCapabilitiesStructure]/ResponseFeatures#complexType (typedef-81.7)
|
|
- |
||||
41.43. The complex type element[siri:SituationExchangePermissions]#complexType (typedef-81.8)
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
||||
42. SIRI-SM Stop Monitoring Service.
42.1. Simple type definitions
|
|
Classification of the service exception |
||||||||||||||||
|
|||||||||||||||||
|
|
Detail Levels for Stop Monitoring Request. |
||||||||||||||||
|
|||||||||||||||||
|
|
Visit Types to Return. |
||||||||||||||||
|
|||||||||||||||||
42.2. The toplevel element siri:MonitoredStopVisit
|
|
A visit to a stop by a VEHICLE as an arrival and /or departure. |
||||
42.3. The toplevel element siri:MonitoredStopVisitCancellation
|
|
Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop. |
||||
42.4. The toplevel element siri:ServiceException
|
|
Exceptions to service availability for all or some services SIRI 2.0 |
||||
42.5. The toplevel element siri:StopLineNotice
|
|
LINE notice for stop. |
||||
42.6. The toplevel element siri:StopLineNoticeCancellation
|
|
Reference to an previously communicated LINE notice which should now be removed from the arrival/departure board for the stop. |
||||
42.7. The toplevel element siri:StopMonitoringCapabilitiesRequest
|
|
+siri:ServiceCapabilitiesRequestStructure (↔ siri:AbstractFunctionalServiceCapabilitiesRequest) |
Request for information about Stop Monitoring Service Capabilities. Answered with StopMonitoringCapabilitiesResponse. |
|||
42.8. The toplevel element siri:StopMonitoringCapabilitiesResponse
|
|
+siri:StopMonitoringCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Capabilities for Stop Monitoring Service. Answers a StopMonitoringCapabilitiesRequest. |
|||
42.9. The toplevel element siri:StopMonitoringDelivery
|
|
+siri:StopMonitoringDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery for Stop Monitoring Service. |
|||
42.10. The toplevel element siri:StopMonitoringMultipleRequest
|
|
+siri:StopMonitoringMultipleRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop. SIRI 1.3 |
|||
42.11. The toplevel element siri:StopMonitoringPermissions
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permission for a single participant or all participants to use an aspect of the service. |
|||
42.12. The toplevel element siri:StopMonitoringRequest
|
|
+siri:StopMonitoringRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about Stop Visits, i.e. arrivals and departures at a stop. |
|||
42.13. The toplevel element siri:StopMonitoringServiceCapabilities
|
|
Capabilities of StopMonitoring Service. |
||||
42.14. The toplevel element siri:StopMonitoringSubscriptionRequest
|
|
+siri:StopMonitoringSubscriptionStructure (↔ siri:AbstractFunctionalServiceSubscriptionRequest) |
Request for a subscription to Stop Monitoring Service. |
|||
42.15. The toplevel element siri:StopNotice
|
|
Notice for stop. |
||||
42.16. The toplevel element siri:StopNoticeCancellation
|
|
Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop. |
||||
42.17. The group siri:CallPredictionConfidenceGroup
|
|
Parameters that affect the subscription publishing and notification processing. |
||||
42.18. The group siri:SiriStopMonitoringIndexGroup
|
|
Convenience artifact to pick out main elements of the Stop Monitoring Service. |
||||
| siri:SiriStopMonitoringIndexGroup |
1:1 |
Request for information about Stop Visits, i.e. arrivals and departures at a stop. |
|||
|
1:1 |
Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop. SIRI 1.3 |
||||
|
1:1 |
Request for a subscription to Stop Monitoring Service. |
||||
|
1:1 |
Delivery for Stop Monitoring Service. |
||||
|
1:1 |
Request for information about Stop Monitoring Service Capabilities. Answered with StopMonitoringCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for Stop Monitoring Service. Answers a StopMonitoringCapabilitiesRequest. |
||||
42.19. The group siri:StopMonitoringPayloadGroup
|
|
Payload part of Stop Monitoring Service delivery. |
||||
| siri:StopMonitoringPayloadGroup |
|
0:* |
Reference to a stop monitoring point (LOGICAL DISPLAY that was requested. This can a be used to return the reference to the requested Monitoring Point if there are no stop visits for the stop. Normally tere will only be one. SIRI v1.3 |
||
|
|
0:* |
Name to use to describe monitoring point (Stop or display). Normally Consumer will already have access to this in its reference data but may be included to increase utility of delivery data i to devices that do not hold reference data, e.g. for SIRI LITE services((since SIRI 2.0)). |
|||
|
0:* |
A visit to a stop by a VEHICLE as an arrival and /or departure. |
||||
|
0:* |
Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop. |
||||
|
0:* |
LINE notice for stop. |
||||
|
0:* |
Reference to an previously communicated LINE notice which should now be removed from the arrival/departure board for the stop. |
||||
|
0:* |
Notice for stop. |
||||
|
0:* |
Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop. |
||||
|
0:* |
Exceptions to service availability for all or some services SIRI 2.0 |
||||
42.20. The group siri:StopMonitoringRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of stops returned. |
||||
| siri:StopMonitoringRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
The maximum number of Stop Visits to include in a given delivery. The first n Stop Visits within the look ahead window are included. Only Visits within the Lookahead Interval are returned. The MinimumStopVisits parameter can be used to reduce the the number of entries for each LINE within the total returned. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
The minimum number of Stop Visits for a given LINE to include in a given delivery. If there are more Visits within the LookAheadInterval than allowed by MaximumStopVisits and a MinimumStopVisits value is specified, then at least the minimum number will be delivered for each LINE. I.e Stop Visits will be included even if the Stop Visits are later than those for some other LINE for which the minimum number of Stop Visits has already been supplied. This allows the Consumer to obtain at least one entry for every available LINE with vehicles approaching the stop. Only STOP Visits within the Look ahead Interval are returned. |
||
|
b |
|
-0:1 |
The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery. As for MinimumStopVisitsPerLine but with Via also taken into account. (since SIRI 2.0) |
||
|
|
0:1 |
Maximum length of text to return for text elements. Default is 30. |
|||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. |
|||
|
|
0:1 |
Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) |
|||
|
|
0:1 |
If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. |
|||
42.21. The group siri:StopMonitoringSubscriptionPolicyGroup
|
|
Parameters that affect the subscription publishing and notification processing. |
||||
| siri:StopMonitoringSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request. |
||
|
|
0:1 |
The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. |
|||
42.22. The group siri:StopMonitoringTopicGroup
|
|
Parameters that specify the content to be returned. |
||||
| siri:StopMonitoringTopicGroup |
|
0:1 |
Forward duration for which Visits should be included, that is, interval before predicted arrival at the stop for which to include Visits: only journeys which will arrive or depart within this time span will be returned. |
||
|
|
0:1 |
Start time for PreviewInterval. If absent, then current time is assumed. |
|||
|
|
1:1 |
Reference to Monitoring Point(s) about which data is requested. May be a STOP POINT, timing point, or a group of points under a single reference. |
|||
|
|
0:1 |
Filter the results to include only Stop Visits for VEHICLEs run by the specified OPERATOR. |
|||
|
|
0:1 |
Filter the results to include only Stop Visits for VEHICLEs for the given LINE. |
|||
|
|
0:1 |
Filter the results to include only Stop Visits for vehicles running in a specific relative DIRECTION, for example, "inbound" or "outbound". (Direction does not specify a destination.) |
|||
|
|
0:1 |
Filter the results to include only journeys to the DESTINATION of the journey. |
|||
|
|
0:1 |
Whether to include arrival Visits, departure Visits, or all. Default is 'all'. |
|||
42.23. The group siri:StopMonitoringVolumeGroup
|
|
Elements for volume control. |
||||
| siri:StopMonitoringVolumeGroup |
|
0:1 |
Whether Detail level filtering is supported. Default is ' false'. |
||
|
|
0:1 |
Default Detail level if non specified on request. Default Normal. |
|||
|
|
0:1 |
Whether results can be limited to a maximum number. Default is 'true'. |
|||
|
|
0:1 |
Whether results can be limited to include a minimum number per LINE. Default is 'true'. |
|||
|
|
0:1 |
Whether results can be limited to include a minimum numVIA (i.e. per JOURNEY PATTERN). (since SIRI 2.0). default is 'false'. |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of previouscalls to include can be specified. Default is 'false'. |
|||
42.24. The group siri:StopVisitCancellationIdentityGroup
|
|
External identifiers of Cancelled Stop Visit. |
||||
| siri:StopVisitCancellationIdentityGroup |
|
1:1 |
Reference to a stop monitoring point to which cancellation applies. |
||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
| siri:LineIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a LINE DIRECTION DIRECTION, typically outward or return. |
|||
| siri:StopVisitCancellationIdentityGroup |
|
0:1 |
VEHICLE JOURNEY of Stop Visit that is being cancelled. |
||
42.25. The group siri:StopVisitReferenceGroup
|
|
External identifiers of Stop Visit. |
||||
| siri:StopVisitReferenceGroup |
|
1:1 |
Reference to a stop monitoring point to which Stop Visit applies. |
||
|
|
0:1 |
Identifier associated with Stop Visit for use in direct wireless communication between bus and stop display. Cleardown codes are short arbitrary identifiers suitable for radio transmission. |
|||
42.26. The complex type siri:DeliveryVariantStructure
|
|
Type for Delivery Variant (since SIRI 2.0) |
||||
|
|
0:1 |
Classification of DELIVERY VARIANT (since SIRI 2.0). |
|||
|
|
1:1 |
Variant text. SIRI v".0 |
|||
42.27. The complex type siri:MonitoredStopVisitCancellationStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Reference to an Activity Element of a delivery. |
|||
|
Inherited content is followed by own content: |
|||||
| siri:StopVisitCancellationIdentityGroup |
|
1:1 |
Reference to a stop monitoring point to which cancellation applies. |
||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
| siri:LineIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a LINE DIRECTION DIRECTION, typically outward or return. |
|||
| siri:StopVisitCancellationIdentityGroup |
|
0:1 |
VEHICLE JOURNEY of Stop Visit that is being cancelled. |
||
|
|
0:1 |
Cleardown identifier of Stop Visit that is being deleted. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
|
|
0:* |
Reason for cancellation. (Unbounded since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.28. The complex type siri:MonitoredStopVisitStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Identifier of item. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Time until when data is valid. (since SIRI 2.0) |
|||
| siri:StopVisitReferenceGroup |
|
1:1 |
Reference to a stop monitoring point to which Stop Visit applies. |
||
|
|
0:1 |
Identifier associated with Stop Visit for use in direct wireless communication between bus and stop display. Cleardown codes are short arbitrary identifiers suitable for radio transmission. |
|||
|
|
1:1 |
Provides real-time information about the VEHICLE JOURNEY along which a VEHICLE is running. |
|||
|
|
0:* |
Text associated with Stop Visit. |
|||
|
|
0:1 |
Facility associated with stop visit |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.29. The complex type siri:ServiceExceptionStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
Reference to a LINE. |
||||
|
|
0:1 |
Reference to a LINE DIRECTION to which exception applies. |
|||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
|
0:1 |
Status of service, Service not yet started, Service ended for day, no service today, etc. |
|||
|
|
0:* |
Text explanation of service exception. |
|||
|
|
0:1 |
Reference to a SITUATION providing further information about exception |
|||
42.30. The complex type siri:StopLineNoticeCancellationStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Reference to an Activity Element of a delivery. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a stop monitoring point to which LINE notice applies. |
|||
| siri:LineIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a LINE DIRECTION DIRECTION, typically outward or return. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.31. The complex type siri:StopLineNoticeStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Identifier of item. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a stop monitoring point to which LINE notice applies. |
|||
| siri:LineIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a LINE DIRECTION DIRECTION, typically outward or return. |
|||
|
|
0:* |
Name or Number by which the LINE is known to the public. (since SIRI 2.0) |
|||
|
|
0:* |
Special text associated with LINE. |
|||
|
|
0:* |
Variant of a notice for use in a particular media channel. (since SIRI 2.0) |
|||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.32. The complex type siri:StopMonitoringCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
|
0:1 |
Capabilities of StopMonitoring Service. |
||||
|
0:1 |
Participants permissions to use the service, Only returned if requested. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.33. The complex type siri:StopMonitoringCapabilityRequestPolicyStructure
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether results can return references for stops. Default is 'true'. |
|||
|
|
0:1 |
Whether results can return names for stop. |
|||
42.34. The complex type siri:StopMonitoringDeliveriesStructure
|
|
Type for Deliveries for Stop Monitoring Service. Used in WSDL. |
||||
|
1:* |
Delivery for Stop Monitoring Service. |
||||
42.35. The complex type siri:StopMonitoringDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:StopMonitoringPayloadGroup |
|
0:* |
Reference to a stop monitoring point (LOGICAL DISPLAY that was requested. This can a be used to return the reference to the requested Monitoring Point if there are no stop visits for the stop. Normally tere will only be one. SIRI v1.3 |
||
|
|
0:* |
Name to use to describe monitoring point (Stop or display). Normally Consumer will already have access to this in its reference data but may be included to increase utility of delivery data i to devices that do not hold reference data, e.g. for SIRI LITE services((since SIRI 2.0)). |
|||
|
0:* |
A visit to a stop by a VEHICLE as an arrival and /or departure. |
||||
|
0:* |
Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop. |
||||
|
0:* |
LINE notice for stop. |
||||
|
0:* |
Reference to an previously communicated LINE notice which should now be removed from the arrival/departure board for the stop. |
||||
|
0:* |
Notice for stop. |
||||
|
0:* |
Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop. |
||||
|
0:* |
Exceptions to service availability for all or some services SIRI 2.0 |
||||
|
|
0:* |
Text associated with whole delivery. (Unbounded since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.36. The complex type siri:StopMonitoringFilterStructure
|
|
Type for an individual Stop Monitoring a Multiple Request. |
||||
| siri:StopMonitoringTopicGroup |
|
0:1 |
Forward duration for which Visits should be included, that is, interval before predicted arrival at the stop for which to include Visits: only journeys which will arrive or depart within this time span will be returned. |
||
|
|
0:1 |
Start time for PreviewInterval. If absent, then current time is assumed. |
|||
|
|
1:1 |
Reference to Monitoring Point(s) about which data is requested. May be a STOP POINT, timing point, or a group of points under a single reference. |
|||
|
|
0:1 |
Filter the results to include only Stop Visits for VEHICLEs run by the specified OPERATOR. |
|||
|
|
0:1 |
Filter the results to include only Stop Visits for VEHICLEs for the given LINE. |
|||
|
|
0:1 |
Filter the results to include only Stop Visits for vehicles running in a specific relative DIRECTION, for example, "inbound" or "outbound". (Direction does not specify a destination.) |
|||
|
|
0:1 |
Filter the results to include only journeys to the DESTINATION of the journey. |
|||
|
|
0:1 |
Whether to include arrival Visits, departure Visits, or all. Default is 'all'. |
|||
| siri:StopMonitoringRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
The maximum number of Stop Visits to include in a given delivery. The first n Stop Visits within the look ahead window are included. Only Visits within the Lookahead Interval are returned. The MinimumStopVisits parameter can be used to reduce the the number of entries for each LINE within the total returned. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
The minimum number of Stop Visits for a given LINE to include in a given delivery. If there are more Visits within the LookAheadInterval than allowed by MaximumStopVisits and a MinimumStopVisits value is specified, then at least the minimum number will be delivered for each LINE. I.e Stop Visits will be included even if the Stop Visits are later than those for some other LINE for which the minimum number of Stop Visits has already been supplied. This allows the Consumer to obtain at least one entry for every available LINE with vehicles approaching the stop. Only STOP Visits within the Look ahead Interval are returned. |
||
|
b |
|
-0:1 |
The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery. As for MinimumStopVisitsPerLine but with Via also taken into account. (since SIRI 2.0) |
||
|
|
0:1 |
Maximum length of text to return for text elements. Default is 30. |
|||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. |
|||
|
|
0:1 |
Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) |
|||
|
|
0:1 |
If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.37. The complex type siri:StopMonitoringMultipleRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
||||
|
|
1:* |
Request particulars for an individual stop as part of a list of multiple= requests. |
|||
42.38. The complex type siri:StopMonitoringRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. |
|||
| siri:StopMonitoringTopicGroup |
|
0:1 |
Forward duration for which Visits should be included, that is, interval before predicted arrival at the stop for which to include Visits: only journeys which will arrive or depart within this time span will be returned. |
||
|
|
0:1 |
Start time for PreviewInterval. If absent, then current time is assumed. |
|||
|
|
1:1 |
Reference to Monitoring Point(s) about which data is requested. May be a STOP POINT, timing point, or a group of points under a single reference. |
|||
|
|
0:1 |
Filter the results to include only Stop Visits for VEHICLEs run by the specified OPERATOR. |
|||
|
|
0:1 |
Filter the results to include only Stop Visits for VEHICLEs for the given LINE. |
|||
|
|
0:1 |
Filter the results to include only Stop Visits for vehicles running in a specific relative DIRECTION, for example, "inbound" or "outbound". (Direction does not specify a destination.) |
|||
|
|
0:1 |
Filter the results to include only journeys to the DESTINATION of the journey. |
|||
|
|
0:1 |
Whether to include arrival Visits, departure Visits, or all. Default is 'all'. |
|||
| siri:StopMonitoringRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
The maximum number of Stop Visits to include in a given delivery. The first n Stop Visits within the look ahead window are included. Only Visits within the Lookahead Interval are returned. The MinimumStopVisits parameter can be used to reduce the the number of entries for each LINE within the total returned. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
The minimum number of Stop Visits for a given LINE to include in a given delivery. If there are more Visits within the LookAheadInterval than allowed by MaximumStopVisits and a MinimumStopVisits value is specified, then at least the minimum number will be delivered for each LINE. I.e Stop Visits will be included even if the Stop Visits are later than those for some other LINE for which the minimum number of Stop Visits has already been supplied. This allows the Consumer to obtain at least one entry for every available LINE with vehicles approaching the stop. Only STOP Visits within the Look ahead Interval are returned. |
||
|
b |
|
-0:1 |
The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery. As for MinimumStopVisitsPerLine but with Via also taken into account. (since SIRI 2.0) |
||
|
|
0:1 |
Maximum length of text to return for text elements. Default is 30. |
|||
|
|
0:1 |
Level of detail to include in response. Default is 'normal'. |
|||
|
|
0:1 |
Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) |
|||
|
|
0:1 |
If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.39. The complex type siri:StopMonitoringServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Available Filtering Capabilities. |
|||
|
|
0:1 |
Available Request Policy capabilities. |
|||
|
|
0:1 |
Available Subscription Policy capabilities. |
|||
|
|
0:1 |
Available Optional Access control capabilities. |
|||
|
|
0:1 |
Available Optional Response capabilities. |
|||
42.40. The complex type siri:StopMonitoringServicePermissionStructure
|
|
Type for Abstract Permission. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. |
||
|
b |
|
-1:1 |
Permission applies to specified participant. |
||
|
|
0:1 |
Permissions for general capabilities. |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
The OPERATOR data that the participant may access. |
||||
|
1:1 |
The LINEs that the participant may access. |
||||
|
|
1:1 |
The monitoring points that the participant may access. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.41. The complex type siri:StopMonitoringSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for information about Stop Visits, i.e. arrivals and departures at a stop. |
||||
| siri:StopMonitoringSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request. |
||
|
|
0:1 |
The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.42. The complex type siri:StopNoticeCancellationStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
1:1 |
Reference to an Activity Element of a delivery. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a stop monitoring point to which Notice applies. |
|||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
|
0:1 |
In case of a delayed cancellation this time tells from when the cancellation applies. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.43. The complex type siri:StopNoticeStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
1:1 |
Identifier of item. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a stop monitoring point to which SITUATION applies. |
|||
|
0:1 |
Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
|
|
0:* |
Text associated with Stop Notice ed since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
42.44. The complex type element[siri:LinePermissions]#complexType (typedef-21.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this LINE. |
||
42.45. The complex type element[siri:OperatorPermissions]#complexType (typedef-21.2)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this OPERATOR. |
||
42.46. The complex type complexType[siri:AbstractPermissionStructure]/GeneralCapabilities#complexType (typedef-45.1)
|
|
- |
||||
|
|
1:1 |
Participant may make direct requests for data. Default is 'true'. |
|||
|
|
1:1 |
Participant may create subscriptions. Default True. |
|||
42.47. The complex type group[siri:StopMonitoringRequestPolicyGroup]/MaximumNumberOfCalls#complexType (typedef-79.1)
|
|
- |
||||
|
|
0:1 |
Maximum number of ONWARDS CALLs to include in results. Only applies if StopMonitoringDetailLevel of 'calls' specified. Zero for none. If StopMonitoringDetailLevel of 'calls' specified but MaximumNumberOfCalls.Previous absent, include all ONWARDS CALLs. |
|||
|
|
0:1 |
Maximum number of ONWARDS CALLs to include in results. Zero for none. Only applies if StopMonitoringDetailLevel of 'calls'specified. Zero for none. If StopMonitoringDetailLevel of 'calls' specified but MaximumNumberOfCalls.Onwards absent, include all ONWARDS CALLs. |
|||
42.48. The complex type complexType[siri:StopMonitoringServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-79.2)
|
|
- |
||||
|
|
1:1 |
Default preview interval. Default is 60 minutes. |
|||
|
|
0:1 |
Whether a start time other than now can be specified for preview interval. Default is 'true'. |
|||
|
1:1 |
Whether results can be filtered by Monitoring point (LOGICAL DISPLAY). Fixed as 'true'. |
||||
|
1:1 |
Whether results can be filtered by LINE. Default is 'true' |
||||
|
0:1 |
Whether results can be filtered by DIRECTION Default is 'true'. |
||||
|
0:1 |
Whether results can be filtered by DESTINATION. Default is 'false'. |
||||
|
|
0:1 |
Whether results can be filtered by VistitType, e.g. arrivals, departures. Default True. |
|||
42.49. The complex type complexType[siri:StopMonitoringServiceCapabilitiesStructure]/RequestPolicy#complexType (typedef-79.3)
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
|
0:1 |
Whether results can return references for stops. Default is 'true'. |
|||
|
|
0:1 |
Whether results can return names for stop. |
|||
|
Inherited content is followed by own content: |
|||||
| siri:StopMonitoringVolumeGroup |
|
0:1 |
Whether Detail level filtering is supported. Default is ' false'. |
||
|
|
0:1 |
Default Detail level if non specified on request. Default Normal. |
|||
|
|
0:1 |
Whether results can be limited to a maximum number. Default is 'true'. |
|||
|
|
0:1 |
Whether results can be limited to include a minimum number per LINE. Default is 'true'. |
|||
|
|
0:1 |
Whether results can be limited to include a minimum numVIA (i.e. per JOURNEY PATTERN). (since SIRI 2.0). default is 'false'. |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of previouscalls to include can be specified. Default is 'false'. |
|||
42.50. The complex type complexType[siri:StopMonitoringServiceCapabilitiesStructure]/ResponseFeatures#complexType (typedef-79.4)
|
|
- |
||||
|
|
0:1 |
Whether result supports LINE events. Default is 'true'. |
|||
|
|
0:1 |
Whether result supports SITUATION REFERENCESs. Default is 'false'. (since SIRI 2.0) |
|||
42.51. The complex type element[siri:StopMonitoringPermissions]#complexType (typedef-79.5)
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permission for a single participant or all participants to use an aspect of the service. |
|||
42.52. The complex type complexType[siri:StopMonitoringServicePermissionStructure]/StopMonitorPermissions#complexType (typedef-79.6)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this Monitoring Point (LOGICAL DISPLAY) |
||
43. SIRI-ST Stop Timetable Service.
43.1. The toplevel element siri:StopTimetableCapabilitiesRequest
|
|
+siri:ServiceCapabilitiesRequestStructure (↔ siri:AbstractFunctionalServiceCapabilitiesRequest) |
Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. |
|||
43.2. The toplevel element siri:StopTimetableCapabilitiesResponse
|
|
+siri:StopTimetableCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. |
|||
43.3. The toplevel element siri:StopTimetableDelivery
|
|
+siri:StopTimetableDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery for Stop Timetable Service. |
|||
43.4. The toplevel element siri:StopTimetablePermissions
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permission for a single participant or all participants to use an aspect of the service. |
|||
43.5. The toplevel element siri:StopTimetableRequest
|
|
+siri:StopTimetableRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about Stop Visits, i.e. arrival and departure at a stop. |
|||
43.6. The toplevel element siri:StopTimetableServiceCapabilities
|
|
Capabilities of Stop Timetable Service. |
||||
43.7. The toplevel element siri:StopTimetableSubscriptionRequest
|
|
+siri:StopTimetableSubscriptionStructure (↔ siri:AbstractFunctionalServiceSubscriptionRequest) |
Request for a subscription to Stop TimetablesService. |
|||
43.8. The group siri:SiriStopTimetableIndexGroup
|
|
Convenience artifact to pick out main elements of the Stop Timetable Service. |
||||
| siri:SiriStopTimetableIndexGroup |
1:1 |
Request for information about Stop Visits, i.e. arrival and departure at a stop. |
|||
|
1:1 |
Request for a subscription to Stop TimetablesService. |
||||
|
1:1 |
Delivery for Stop Timetable Service. |
||||
|
1:1 |
Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. |
||||
|
1:1 |
Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. |
||||
43.9. The group siri:StopTimetablePayloadGroup
|
|
Payload part of Stop Timetable delivery. |
||||
| siri:StopTimetablePayloadGroup |
|
0:* |
A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable. |
||
|
|
0:* |
A cancellation of a previously issued TimetabledStopVisit. |
|||
43.10. The group siri:StopTimetableRequestPolicyGroup
|
|
Parameters that affect the request processing. Mostly act to reduce the number of stops returned. |
||||
| siri:StopTimetableRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
43.11. The group siri:StopTimetableSubscriptionPolicyGroup
|
|
Parameters that affect the subscription publishing and notification processing. |
||||
| siri:StopTimetableSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request. |
||
|
|
0:1 |
The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. |
|||
43.12. The group siri:StopTimetableTopicGroup
|
|
Parameters that specify the content to be returned. |
||||
| siri:StopTimetableTopicGroup |
|
0:1 |
Earliest and latest departure time. If absent, default to the data horizon of the service. |
||
|
|
1:1 |
The stop monitoring point about which data is requested. May be a STOP POINT, timing point or other display point. |
|||
|
|
0:1 |
Filter the results to include only data for journeys for the given LINE. |
|||
|
|
0:1 |
Filter the results to include only data for journeys running in a specific relative DIRECTION, for example, "inbound" or "outbound". |
|||
43.13. The complex type siri:StopTimetableCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
|
0:1 |
Capabilities of Stop Timetable Service. |
||||
|
0:1 |
Participant's permissions to use the service. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
43.14. The complex type siri:StopTimetableCapabilityRequestPolicyStructure
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether results can return references for stops. Default is 'true'. |
|||
|
|
0:1 |
Whether results can return names for stop. |
|||
43.15. The complex type siri:StopTimetableDeliveriesStructure
|
|
Type for stop timetable deliveries. Used in WSDL. |
||||
|
1:1 |
Delivery for Stop Timetable Service. |
||||
43.16. The complex type siri:StopTimetableDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:StopTimetablePayloadGroup |
|
0:* |
A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable. |
||
|
|
0:* |
A cancellation of a previously issued TimetabledStopVisit. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
43.17. The complex type siri:StopTimetableRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:StopTimetableTopicGroup |
|
0:1 |
Earliest and latest departure time. If absent, default to the data horizon of the service. |
||
|
|
1:1 |
The stop monitoring point about which data is requested. May be a STOP POINT, timing point or other display point. |
|||
|
|
0:1 |
Filter the results to include only data for journeys for the given LINE. |
|||
|
|
0:1 |
Filter the results to include only data for journeys running in a specific relative DIRECTION, for example, "inbound" or "outbound". |
|||
| siri:StopTimetableRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
43.18. The complex type siri:StopTimetableServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Available Filtering Capabilities. |
|||
|
|
0:1 |
Available request policy options. |
|||
|
|
0:1 |
Access control that can be used. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
43.19. The complex type siri:StopTimetableServicePermissionStructure
|
|
Type for Abstract Permission. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. |
||
|
b |
|
-1:1 |
Permission applies to specified participant. |
||
|
|
0:1 |
Permissions for general capabilities. |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
The OPERATOR data that the participant may access. |
||||
|
1:1 |
The LINEs that the participant may access. |
||||
|
|
1:1 |
The monitoring points that the participant may access. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
43.20. The complex type siri:StopTimetableSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for information about Stop Visits, i.e. arrival and departure at a stop. |
||||
| siri:StopTimetableSubscriptionPolicyGroup |
|
0:1 |
Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. If false each subscription response will contain the full information as specified in this request. |
||
|
|
0:1 |
The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
43.21. The complex type siri:TimetabledStopVisitCancellationStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Reference to an Activity Element of a delivery. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a stop monitoring point to which Stop Visit applies. |
|||
|
0:1 |
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. |
||||
| siri:JourneyIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a DIRECTION, typically outward or return. |
|||
|
|
0:1 |
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
|
|
0:* |
Reason for cancellation. (Unbounded since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
43.22. The complex type siri:TimetabledStopVisitStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Identifier of item. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Reference to a stop monitoring point / LOGICAL DISPLAY to which Stop Visit applies. |
|||
|
1:1 |
Timetabled VEHICLE JOURNEY. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
43.23. The complex type element[siri:LinePermissions]#complexType (typedef-21.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this LINE. |
||
43.24. The complex type element[siri:OperatorPermissions]#complexType (typedef-21.2)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this OPERATOR. |
||
43.25. The complex type complexType[siri:AbstractPermissionStructure]/GeneralCapabilities#complexType (typedef-45.1)
|
|
- |
||||
|
|
1:1 |
Participant may make direct requests for data. Default is 'true'. |
|||
|
|
1:1 |
Participant may create subscriptions. Default True. |
|||
43.26. The complex type complexType[siri:StopTimetableServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-85.1)
|
|
- |
||||
|
1:1 |
Whether results can be filtered by Monitoring point (LOGICAL DISPLAY). Fixed as 'true'. |
||||
|
1:1 |
Whether results can be filtered by LINE. Default is 'true' |
||||
|
0:1 |
Whether results can be filtered by DIRECTION Default is 'true'. |
||||
43.27. The complex type complexType[siri:StopTimetableServiceCapabilitiesStructure]/AccessControl#complexType (typedef-85.2)
|
|
Type for Common Access control capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether access control of requests is supported. Default is 'false'. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
If access control is supported, whether access control by OPERATOR is supported. Default is 'true'. |
||||
|
0:1 |
If access control is supported, whether access control by LINE is supported. Default is 'true'. |
||||
|
0:1 |
If access control is supported, whether access control by monitoring point (LOGICAL DISPLAY) is supported. Default is 'true'. |
||||
43.28. The complex type element[siri:StopTimetablePermissions]#complexType (typedef-85.3)
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permission for a single participant or all participants to use an aspect of the service. |
|||
43.29. The complex type complexType[siri:StopTimetableServicePermissionStructure]/StopMonitorPermissions#complexType (typedef-85.4)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this Monitoring Point (LOGICAL DISPLAY) |
||
44. SIRI Framewrok Location Types.
44.1. Simple type definitions
|
|
xs:float: (empty restriction) |
Type for absolute bearing. |
|
|
xs:decimal: range=[-1000,5000] |
Altitude metres from sea level. |
|
|
xs:nonNegativeInteger: (empty restriction) |
Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. ALternative units may be specifed by context. |
|
|
xs:decimal: range=[-90,90] |
Latitude from equator. |
|
|
xs:decimal: range=[-180,180] |
Longitude from Greenwich. |
|
|
xs:string: (empty restriction) |
Type for coordinate reference system. |
|
|
xs:nonNegativeInteger: (empty restriction) |
Distance (metres per second) ALternative unist may be specifed by context. |
44.2. The toplevel element siri:SrsName
|
|
GML Spatial coordinate reference system. |
||||
44.3. The group siri:WgsGroup
|
|
WGS84 Coordinates. |
||||
| siri:WgsGroup |
|
1:1 |
Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees, e.g. 2.356 |
||
|
|
1:1 |
Latitude from equator. -90 (South) to +90 (North). Decimal degrees, e.g. 56.356 |
|||
|
|
0:1 |
Altitude metres from sea level. |
|||
44.4. The complex type siri:BoundingBoxStructure
|
|
Defines a bounding box using two corner points. GML terminology. (since SIRI 2.0) |
||||
|
|
1:1 |
Upper Left corner as a geospatial point. |
|||
|
|
1:1 |
Lower right corner as a geospatial point. |
|||
44.5. The complex type siri:CircularAreaStructure
|
|
Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Identifier of POINT. |
|||
|
|
1:1 |
identifier of data reference system for geocodes if point is specified as gml compatible Coordinates. A gml value. If not specified taken from system configuration. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
| siri:WgsGroup |
a |
|
-1:1 |
Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees, e.g. 2.356 |
|
|
a |
|
-1:1 |
Latitude from equator. -90 (South) to +90 (North). Decimal degrees, e.g. 56.356 |
||
|
a |
|
-0:1 |
Altitude metres from sea level. |
||
|
b |
|
-1:1 |
Coordinates of points in a GML compatibe format, as indicated by srsName attribute. |
||
|
|
0:1 |
Precision for point measurement. In meters. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Radius around the center point in meters. |
|||
44.6. The complex type siri:CoordinatesStructure
|
|
|
- |
|||
44.7. The complex type siri:FlexibleAreaStructure
|
|
Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. (since SIRI 2.1) A flexible area is used in cases where a pre-booked service allows pick-up/drop-off anywhere in a designated area and provides a possible interchange to a higher-frequency service. |
||||
|
The element contains one of the following elements (a-c) |
|||||
|
a |
|
-1:1 |
Flexible area specified as a rectangular bounding box. |
||
|
b |
|
-1:1 |
Flexible area specified as a circular area (center coordinates and radius). |
||
|
c |
-1:1 |
A Polygon is a special surface that is defined by a single surface patch (see D.3.6). The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. The elements exterior and interior describe the surface boundary of the polygon. |
|||
44.8. The complex type siri:LineShapeStructure
|
|
Defines a line shape (since SIRI 2.0) |
||||
|
|
2:* |
A geospatial point. (since SIRI 2.0) |
|||
44.9. The complex type siri:LocationStructure
|
|
Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. |
||||
|
|
1:1 |
Identifier of POINT. |
|||
|
|
1:1 |
identifier of data reference system for geocodes if point is specified as gml compatible Coordinates. A gml value. If not specified taken from system configuration. |
|||
|
The element contains one of the following elements (b) or element sequences (a) |
|||||
| siri:WgsGroup |
a |
|
-1:1 |
Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees, e.g. 2.356 |
|
|
a |
|
-1:1 |
Latitude from equator. -90 (South) to +90 (North). Decimal degrees, e.g. 56.356 |
||
|
a |
|
-0:1 |
Altitude metres from sea level. |
||
|
b |
|
-1:1 |
Coordinates of points in a GML compatibe format, as indicated by srsName attribute. |
||
|
|
0:1 |
Precision for point measurement. In meters. |
|||
45. SIRI Framework Participant Types.
45.1. Simple type definitions
|
|
xs:NMTOKEN: (empty restriction) |
Type for Unique identifier of participant. |
45.2. The complex type siri:ParticipantRefStructure
|
|
Type for Unique identifier of participant. |
||||
46. SIRI Framework Permission Types.
46.1. The toplevel element siri:AllowAll
|
|
|
Allow access to all topics known to the service. |
|||
46.2. The complex type siri:AbstractPermissionStructure
|
|
Type for Abstract Permission. |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. |
||
|
b |
|
-1:1 |
Permission applies to specified participant. |
||
|
|
0:1 |
Permissions for general capabilities. |
|||
46.3. The complex type siri:AbstractTopicPermissionStructure
|
|
Type for Abstract Permission Topic. |
||||
|
|
1:1 |
Whether the participant may access this topic. Default is 'true'. |
|||
46.4. The complex type siri:CapabilityAccessControlStructure
|
|
Type for Common Access control capabilities. |
||||
|
|
1:1 |
Whether access control of requests is supported. Default is 'false'. |
|||
46.5. The complex type complexType[siri:AbstractPermissionStructure]/GeneralCapabilities#complexType (typedef-45.1)
|
|
- |
||||
|
|
1:1 |
Participant may make direct requests for data. Default is 'true'. |
|||
|
|
1:1 |
Participant may create subscriptions. Default True. |
|||
47. SIRI Framework Base Types.
47.1. Simple type definitions
|
|
xs:duration: (empty restriction) |
Limited version of duration that allows for precise time arithmetic. Only Month, Day, Hour, Minute Second terms should be used. Milliseconds should not be used. Year should not be used. Negative values allowed. e.g. PT1004199059S", "PT130S", "PT2M10S", "P1DT2S", "-P1DT2S". |
|
|
xs:string: (empty restriction) |
Email address type. |
|
|
xs:NMTOKEN: (empty restriction) |
Id type for document references. |
|
|
xs:decimal: (empty restriction) |
Length type for short distances. System for Units can be specified on frame. Normally (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. |
|
|
xs:nonNegativeInteger: (empty restriction) |
Number of passengers - capacity. |
|
|
xs:decimal: value>=0 |
Specifies a percentage from 0 to 100. The value range is normally 0-100, but could in some circumstances go beyond 100%, e.g. when representing the OccupancyPercentage of an over-crowded vehicle or in similar cases. |
|
|
xs:string: (empty restriction) |
International phonenumber +41675601 etc. |
|
|
xs:string: minLen=1; pattern=#[^,\[\]\{\}\?$%\^=@#;:]+# |
A name that requires at least one character of text and forbids certain reserved characters. |
|
|
xs:string: minLen=1 |
A restriction of W3C XML Schema's string that requires at least one character of text. |
|
|
xs:duration: (empty restriction) |
Limited version of duration. Must be positive. |
|
|
xs:NMTOKEN: (empty restriction) |
A string indicating the versioin of a SIRI data structure. |
|
|
xs:decimal: (empty restriction) |
Weight type for mass. System for Units can be specified on Frame. Normal default is (kilos) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. |
|
|
Union({xs:language}, {xs:string: (empty restriction)}) |
- |
47.2. The complex type siri:NaturalLanguagePlaceNameStructure
|
|
A name that requires at least one character of text and forbids certain reserved characters. |
||||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
lang (as an attribute name) denotes an attribute whose value is a language code for the natural language of the content of any element; its value is inherited. This name is reserved by virtue of its definition in the XML specification. Notes Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See BCP 47 at http://www.rfc-editor.org/rfc/bcp/bcp47.txt and the IANA language subtag registry at http://www.iana.org/assignments/language-subtag-registry for further information. The union allows for the 'un-declaration' of xml:lang with the empty string. |
|||
47.3. The complex type siri:NaturalLanguageStringStructure
|
|
A restriction of W3C XML Schema's string that requires at least one character of text. |
||||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
lang (as an attribute name) denotes an attribute whose value is a language code for the natural language of the content of any element; its value is inherited. This name is reserved by virtue of its definition in the XML specification. Notes Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See BCP 47 at http://www.rfc-editor.org/rfc/bcp/bcp47.txt and the IANA language subtag registry at http://www.iana.org/assignments/language-subtag-registry for further information. The union allows for the 'un-declaration' of xml:lang with the empty string. |
|||
48. SIRI Framework Utility Types.
48.1. Simple type definitions
|
|
xs:string: (empty restriction) |
A type with no allowed content, used when simply the presence of an element is significant. |
|
|
xs:Name: (empty restriction) |
Name of class of which TypeOfValue is an instance. Used for reflection. (since SIRI 2.1) |
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a TYPE OF VALUE. (since SIRI 2.1) |
|
|
xs:NMTOKEN: (empty restriction) |
Type for identifier of a VALUE SET. (since SIRI 2.1) |
48.2. The toplevel element siri:Extensions
|
|
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
48.3. The toplevel element siri:KeyList
|
|
A list of alternative Key values for an element. (since SIRI 2.1) |
||||
48.4. The toplevel element siri:TypeOfValue
|
|
A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. (since SIRI 2.1) |
||||
48.5. The toplevel element siri:TypesOfValue
|
|
VALUE SETs and TYPE OF VALUEs as part of the SIRI extension model. TYPES OF VALUE can be used to exchange metadata for validation or collection of data, such as the description and allowed values for codes. (since SIRI 2.1) |
||||
48.6. The toplevel element siri:ValueSet
|
|
An extensible set of code values which may be added to by user applications and is used to validate the properties of entities. Contains TYPE OF VALUEs that are an instance of the same class. (since SIRI 2.1) |
||||
48.7. The group siri:TypeOfValueGroup
|
|
Elements for TYPE OF VALUE. (since SIRI 2.1) |
||||
| siri:TypeOfValueGroup |
|
0:1 |
Name of TYPE OF VALUE. |
||
|
|
0:1 |
Short Name for TYPE OF VALUE. |
|||
|
|
0:1 |
Description of TYPE OF VALUE. |
|||
|
|
0:1 |
Default image for TYPE OF VALUE. |
|||
|
|
0:1 |
Default URL for TYPE OF VALUE. |
|||
|
|
0:1 |
Arbitrary code (usually the technical part of the identifier). |
|||
48.8. The group siri:ValueSetGroup
|
|
Elements for VALUE SET. (since SIRI 2.1) |
||||
| siri:ValueSetGroup |
|
0:1 |
Name of set. |
||
|
|
1:1 |
Values in set. |
|||
48.9. The complex type siri:ExtensionsStructure
|
|
Type for Extensions to schema. Wraps an 'any' tag to ensure decidability. |
||||
48.10. The complex type siri:KeyListStructure
|
|
Type for a Key List. (since SIRI 2.1) |
||||
|
|
1:* |
Key value pair for Entity. |
|||
48.11. The complex type siri:KeyValueStructure
|
|
Type for a Key List. (since SIRI 2.1) |
||||
|
|
1:1 |
Identifier of value e.g. System. |
|||
|
|
1:1 |
Value for alternative key. |
|||
|
|
0:1 |
Identifier of type of key. |
|||
48.12. The complex type siri:TypeOfValueRefStructure
|
|
Type for identifier of a TYPE OF VALUE. (since SIRI 2.1) |
||||
48.13. The complex type siri:TypeOfValueStructure
|
|
Type for a TYPE OF VALUE. Used to define open classifications of value types. (since SIRI 2.1) |
||||
|
|
1:1 |
Identifier of a TYPE OF VALUE. |
|||
|
|
1:1 |
Name of class of which TypeOfValue is an instance. |
|||
| siri:TypeOfValueGroup |
|
0:1 |
Name of TYPE OF VALUE. |
||
|
|
0:1 |
Short Name for TYPE OF VALUE. |
|||
|
|
0:1 |
Description of TYPE OF VALUE. |
|||
|
|
0:1 |
Default image for TYPE OF VALUE. |
|||
|
|
0:1 |
Default URL for TYPE OF VALUE. |
|||
|
|
0:1 |
Arbitrary code (usually the technical part of the identifier). |
|||
48.14. The complex type siri:TypesOfValueStructure
|
|
Type for containment of VALUE SETs and/or TYPE OF VALUEs. (since SIRI 2.1) |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
-1:1 |
An extensible set of code values which may be added to by user applications and is used to validate the properties of entities. Contains TYPE OF VALUEs that are an instance of the same class. (since SIRI 2.1) |
|||
|
b |
-1:1 |
A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. (since SIRI 2.1) |
|||
48.15. The complex type siri:ValueSetStructure
|
|
Type for a VALUE SET. Used to define open classifications of value types. (since SIRI 2.1) |
||||
|
|
1:1 |
Identifier of VALUE SET. |
|||
|
|
1:1 |
Name of Class of values in set. |
|||
| siri:ValueSetGroup |
|
0:1 |
Name of set. |
||
|
|
1:1 |
Values in set. |
|||
48.16. The complex type siri:ValuesStructure
|
|
Type for a list of TYPE OF VALUEs. (since SIRI 2.1) |
||||
|
1:* |
A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. (since SIRI 2.1) |
||||
49. SIRI-VM Vehicle Monitoring Service.
49.1. Simple type definitions
|
|
xs:NMTOKEN: (empty restriction) |
Identifier of a Vehicle Monitoring scope. |
|||||||
|
|
Detail Levels for Request. |
||||||||
|
|||||||||
49.2. The toplevel element siri:VehicleMonitoringCapabilitiesRequest
|
|
+siri:ServiceCapabilitiesRequestStructure (↔ siri:AbstractFunctionalServiceCapabilitiesRequest) |
Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
|||
49.3. The toplevel element siri:VehicleMonitoringCapabilitiesResponse
|
|
+siri:VehicleMonitoringCapabilitiesResponseStructure (↔ siri:AbstractFunctionalServiceCapabilitiesResponse) |
Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. |
|||
49.4. The toplevel element siri:VehicleMonitoringDelivery
|
|
+siri:VehicleMonitoringDeliveryStructure (↔ siri:AbstractFunctionalServiceDelivery) |
Delivery for Vehicle Monitoring Service. |
|||
49.5. The toplevel element siri:VehicleMonitoringPermissions
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permissions for use of VEHICLE MONITORING. Can be used to specify which Consumers can see which vehicles |
|||
49.6. The toplevel element siri:VehicleMonitoringRequest
|
|
+siri:VehicleMonitoringRequestStructure (↔ siri:AbstractFunctionalServiceRequest) |
Request for information about Vehicle Movements. |
|||
49.7. The toplevel element siri:VehicleMonitoringServiceCapabilities
|
|
Capabilities of Vehicle Monitoring Service. |
||||
49.8. The toplevel element siri:VehicleMonitoringSubscriptionRequest
|
|
+siri:VehicleMonitoringSubscriptionStructure (↔ siri:AbstractFunctionalServiceSubscriptionRequest) |
Request for a subscription to the Vehicle Monitoring Service. |
|||
49.9. The group siri:SiriVehicleActivityServiceIndexGroup
|
|
Convenience artifact to pick out main elements of the Vehicle Monitoring Service. |
||||
| siri:SiriVehicleActivityServiceIndexGroup |
1:1 |
Request for information about Vehicle Movements. |
|||
|
1:1 |
Request for a subscription to the Vehicle Monitoring Service. |
||||
|
1:1 |
Delivery for Vehicle Monitoring Service. |
||||
|
1:1 |
Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. |
||||
|
1:1 |
Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. |
||||
49.10. The group siri:VehicleActivityCancellationIdentityGroup
|
|
Identifiers of Vehicle Activity. |
||||
| siri:VehicleActivityCancellationIdentityGroup |
|
0:1 |
|||
|
|
0:1 |
Reference to VEHICLE JOURNEY that VEHICLE is making. |
|||
| siri:LineIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a LINE DIRECTION DIRECTION, typically outward or return. |
|||
49.11. The group siri:VehicleMonitoringPayloadGroup
|
|
Payload part of Vehicle Monitoring delivery. |
||||
| siri:VehicleMonitoringPayloadGroup |
|
0:* |
Describes the progress of a VEHICLE along its route. |
||
|
|
0:* |
Reference to an previously communicated VEHICLE activity which should now be removed from the system. |
|||
|
|
0:* |
Annotation to accompany of Vehicle Activities. |
|||
49.12. The group siri:VehicleMonitoringRequestPolicyGroup
|
|
Parameters that affect the request processing. |
||||
| siri:VehicleMonitoringRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
The maximum number of MONITORED VEHICLE JOURNEYs to include in a given delivery. The most recent n Events within the look ahead window are included. |
|||
|
|
0:1 |
Level of detail to include in response. |
|||
|
|
0:1 |
If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. (since SIRI 2.0). |
|||
|
|
0:1 |
Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) |
|||
49.13. The group siri:VehicleMonitoringSubscriptionPolicyGroup
|
|
Parameters that affect the subscription publishing and notification processing. |
||||
| siri:VehicleMonitoringSubscriptionPolicyGroup |
|
0:1 |
Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. If false or omitted, each subscription response will contain the full information as specified in this request. |
||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
The amount of change to the VEHICLE expected arrival time at next stop that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). |
||
|
b |
|
-0:1 |
Time interval in seconds in which new data is to be transmitted. If unspecified, default to system configuration. |
||
49.14. The group siri:VehicleMonitoringTopicGroup
|
|
Parameters that specify the content to be returned. |
||||
| siri:VehicleMonitoringTopicGroup |
|
0:1 |
A predefined scope for making VEHICLE requests. |
||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Reference to a specific VEHICLE about which data is requested. |
||
|
b |
|
-1:1 |
Filter the results to include only vehicles for the specific LINE. |
||
|
|
0:1 |
Filter the results to include only VEHICLEs going to this DIRECTION. |
|||
49.15. The group siri:VehicleMonitoringVolumeGroup
|
|
Elements for volume control. |
||||
| siri:VehicleMonitoringVolumeGroup |
|
0:1 |
Whether Detail level filtering is supported. Default is ' false'. |
||
|
|
0:1 |
Detail level. Default Normal. |
|||
|
|
0:1 |
Whether results can be limited to a maximum number. Default is 'true'. |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of calls to include can be specified. Default is 'false'. (since SIRI 2.0) |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. (since SIRI 2.0) |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of previous calls to include can be specified. Default is 'false'. (since SIRI 2.0) |
|||
49.16. The complex type siri:VehicleActivityCancellationStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Reference to an Activity Element of a delivery. |
|||
|
Inherited content is followed by own content: |
|||||
| siri:VehicleActivityCancellationIdentityGroup |
|
0:1 |
|||
|
|
0:1 |
Reference to VEHICLE JOURNEY that VEHICLE is making. |
|||
| siri:LineIdentityGroup |
|
1:1 |
Reference to a LINE. |
||
|
|
1:1 |
Reference to a LINE DIRECTION DIRECTION, typically outward or return. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
|
|
0:* |
Reason for cancellation. (Unbounded since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
49.17. The complex type siri:VehicleActivityStructure
|
|
Type for an Activity. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Time at which data was recorded. |
|||
|
|
0:1 |
Identifier of item. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Time until when data is valid. |
|||
|
|
0:1 |
Reference to monitored VEHICLE or GROUP OF VEHICLEs. |
|||
|
|
0:* |
Name associated with Monitoring Reference. Supports SIRI LITE servcies ((since SIRI 2.0)). |
|||
|
|
0:1 |
Provides information about the progress of the VEHICLE along its current link, that is link from previous visited top to current position. |
|||
|
|
1:1 |
Monitored VEHICLE JOURNEY that VEHICLE is following. |
|||
|
|
0:* |
Text associated with Delivery. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
49.18. The complex type siri:VehicleMonitoringCapabilitiesResponseStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ContextualisedResponseEndpointGroup |
|
0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:CapabilityStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
|
0:1 |
Capabilities of Vehicle Monitoring Service. |
||||
|
0:1 |
Participant's permissions to use the service. |
||||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
49.19. The complex type siri:VehicleMonitoringCapabilityRequestPolicyStructure
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Whether results should return references. |
|||
|
|
0:1 |
Whether results should return references. |
|||
49.20. The complex type siri:VehicleMonitoringDeliveriesStructure
|
|
Type for Deliveries for VEHICLE monitoring services Used in WSDL. |
||||
|
1:* |
Delivery for Vehicle Monitoring Service. |
||||
49.21. The complex type siri:VehicleMonitoringDeliveryStructure
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
|
The element contains one of the following elements (a) or element sequences (b) |
|||||
| siri:ContextualisedResponseEndpointGroup |
a |
|
-0:1 |
Arbitrary unique reference to the request which gave rise to this message. |
|
| siri:SubscriptionIdentifierResourcePropertyGroup |
b |
|
-0:1 |
Unique identifier of Subscriber - reference to a Participant. |
|
|
b |
|
-0:1 |
Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. |
||
|
b |
|
-1:1 |
Reference to a service subscription: unique within Service and Subscriber. |
||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:DeliveryStatusGroup |
0:1 |
Whether the request was processed successfully or not. Default is 'true'. |
|||
|
|
0:1 |
Description of any error or warning condition. |
|||
| siri:SuccessInfoGroup |
|
0:1 |
End of data horizon of the data producer. |
||
|
|
0:1 |
Minimum interval at which updates can be sent. |
|||
| siri:DeliveryDefaultGroup |
|
0:1 |
Default language for text elements. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of response. Fixed |
|||
| siri:VehicleMonitoringPayloadGroup |
|
0:* |
Describes the progress of a VEHICLE along its route. |
||
|
|
0:* |
Reference to an previously communicated VEHICLE activity which should now be removed from the system. |
|||
|
|
0:* |
Annotation to accompany of Vehicle Activities. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
49.22. The complex type siri:VehicleMonitoringRefStructure
|
|
Identifier of a Vehicle Monitoring scope. |
||||
49.23. The complex type siri:VehicleMonitoringRequestStructure
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:ContextualisedRequestEndpointGroup |
|
0:1 |
Arbitrary unique reference to this message. |
||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Version number of request. Fixed |
|||
| siri:VehicleMonitoringTopicGroup |
|
0:1 |
A predefined scope for making VEHICLE requests. |
||
|
The element contains none or one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Reference to a specific VEHICLE about which data is requested. |
||
|
b |
|
-1:1 |
Filter the results to include only vehicles for the specific LINE. |
||
|
|
0:1 |
Filter the results to include only VEHICLEs going to this DIRECTION. |
|||
| siri:VehicleMonitoringRequestPolicyGroup |
|
0:* |
Preferred languages in which to return text values. |
||
|
0:1 |
Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. Where multiple values are returned The first element returned will be used as the default value. |
||||
|
|
0:1 |
The maximum number of MONITORED VEHICLE JOURNEYs to include in a given delivery. The most recent n Events within the look ahead window are included. |
|||
|
|
0:1 |
Level of detail to include in response. |
|||
|
|
0:1 |
If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. (since SIRI 2.0). |
|||
|
|
0:1 |
Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
49.24. The complex type siri:VehicleMonitoringServiceCapabilitiesStructure
|
|
Type for Capabilities of StopMonitopring Service. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General capabilities common to all SIRI service request types. |
|||
|
|
0:1 |
Implementation properties common to all request types. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:1 |
Topic Filtering Capabilities. |
|||
|
|
0:1 |
Request Policy capabilities. |
|||
|
|
0:1 |
Subscription Policy capabilities. |
|||
|
|
0:1 |
Optional Access control capabilities. |
|||
|
|
0:1 |
Optional Response capabilities. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
49.25. The complex type siri:VehicleMonitoringServicePermissionStructure
|
|
Type for Abstract Permission. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. |
||
|
b |
|
-1:1 |
Permission applies to specified participant. |
||
|
|
0:1 |
Permissions for general capabilities. |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
The OPERATOR data that the participant may access. |
||||
|
1:1 |
The LINEs that the participant may access. |
||||
|
|
1:1 |
The Vehicle Monitors (DIUSPLAY ASSIGNMENTs) that the participant may access. |
|||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
49.26. The complex type siri:VehicleMonitoringSubscriptionStructure
|
|
Type for SIRI Service subscriptions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:SubscriptionIdentityGroup |
|
0:1 |
Participant identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. |
||
|
|
1:1 |
Identifier to be given to Subscription. |
|||
|
|
1:1 |
Requested end time for subscription. |
|||
|
|
0:1 |
By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) |
|||
|
Inherited content is followed by own content: |
|||||
|
1:1 |
Request for information about Vehicle Movements. |
||||
| siri:VehicleMonitoringSubscriptionPolicyGroup |
|
0:1 |
Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. If false or omitted, each subscription response will contain the full information as specified in this request. |
||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
The amount of change to the VEHICLE expected arrival time at next stop that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). |
||
|
b |
|
-0:1 |
Time interval in seconds in which new data is to be transmitted. If unspecified, default to system configuration. |
||
|
0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
||||
49.27. The complex type siri:VehicleMonitorPermissionStructure
|
|
Type for Abstract Permission Topic. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether the participant may access this topic. Default is 'true'. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
1:1 |
Vehicle Monitoring reference for which permission is made. |
|||
49.28. The complex type element[siri:LinePermissions]#complexType (typedef-21.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this LINE. |
||
49.29. The complex type element[siri:OperatorPermissions]#complexType (typedef-21.2)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this OPERATOR. |
||
49.30. The complex type group[siri:JourneyFormationGroup]/TrainElements#complexType (typedef-25.2)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
-1:1 |
Reference to a TRAIN ELEMENT. (since SIRI 2.1) |
|||
|
b |
-1:1 |
An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1) |
|||
49.31. The complex type group[siri:JourneyFormationGroup]/Trains#complexType (typedef-25.3)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1) |
|||
49.32. The complex type group[siri:JourneyFormationGroup]/CompoundTrains#complexType (typedef-25.4)
|
|
- |
||||
|
The element contains one or more of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
|||
|
b |
-1:1 |
Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1) TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation. |
|||
49.33. The complex type group[siri:TrainOperationalInfoGroup]/TrainNumbers#complexType (typedef-39.4)
|
|
- |
||||
|
|
1:* |
TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 |
|||
49.34. The complex type group[siri:TrainOperationalInfoGroup]/JourneyParts#complexType (typedef-39.5)
|
|
- |
||||
|
|
1:* |
Information about Parts of JOURNEY (since SIRI 2.0) |
|||
49.35. The complex type complexType[siri:AbstractPermissionStructure]/GeneralCapabilities#complexType (typedef-45.1)
|
|
- |
||||
|
|
1:1 |
Participant may make direct requests for data. Default is 'true'. |
|||
|
|
1:1 |
Participant may create subscriptions. Default True. |
|||
49.36. The complex type group[siri:VehicleMonitoringRequestPolicyGroup]/MaximumNumberOfCalls#complexType (typedef-76.1)
|
|
- |
||||
|
|
0:1 |
Maximum number of previous calls to include. Only applies if VehicleMonitoringDetailLevel of Calls specified. Zero for none. If VehicleMonitoringDetailLevel of Calls specified but MaximumNumberOfCalls.Previous absent, include all previous calls. (since SIRI 2.0). |
|||
|
|
0:1 |
Maximum number of onwards calls to include. Zero for none. Only applies if VehicleMonitoringDetailLevel of 'calls' specified. Zero for none. If VehicleMonitoringDetailLevel calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. (since SIRI 2.0). |
|||
49.37. The complex type complexType[siri:VehicleActivityStructure]/MonitoredVehicleJourney#complexType (typedef-76.2)
|
|
Type for Monitored VEHICLE JOURNEY. |
||||
|
The element content starts with items inherited from the base type: |
|||||
| siri:MonitoredJourneyIdentityGroup |
|
0:1 |
Reference to LINE of journey. |
||
|
|
0:1 |
Reference to DIRECTION of journey. |
|||
|
|
0:1 |
A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. |
|||
| siri:JourneyPatternInfoGroup |
|
0:1 |
Identifier of JOURNEY PATTERN that journey follows. |
||
|
|
0:1 |
Name of Joruney Pattern |
|||
|
|
0:* |
A means of transportation such as bus, rail, etc. |
|||
|
|
0:1 |
Identifier of ROUTE that journey follows. |
|||
|
0:* |
Name or Number by which the LINEis known to the public. |
||||
|
|
0:1 |
Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 |
|||
|
|
0:* |
Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) |
|||
|
|
0:1 |
Alternative identifier of LINE that an external system may associate with journey. |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-0:1 |
Reference to a BRANDING. (since SIRI 2.1) |
||
|
b |
|
-0:1 |
An arbitrary marketing classification. (since SIRI 2.1) |
||
| siri:BasicServiceInfoGroup |
|
0:1 |
OPERATOR of a VEHICLE JOURNEY. Note that the operator may change over the course of a journey. This shoudl show teh operator for the curent point in the journey. Use Journey Parts tp record all the operators in the whole journeyh. |
||
|
|
0:1 |
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl. |
|||
|
0:* |
Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged. |
||||
| siri:ServiceInfoGroup |
|
0:* |
Features of VEHICLE providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. |
||
| siri:JourneyEndNamesGroup |
0:1 |
Reference to the origin SCHEDULED STOP POINT of the journey. |
|||
|
|
0:* |
Name of the origin of the journey. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name. |
|||
|
|
0:* |
DIRECTION name shown for jurney at the origin. (since SIRI 2.0) |
|||
|
|
0:* |
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. |
|||
|
0:1 |
Reference to the destination SCHEDULED STOP POINT of the journey. |
||||
|
|
0:* |
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0) |
|||
|
|
0:* |
Origin name shown for jourey at the destination (since SIRI 2.0) |
|||
| siri:JourneyInfoGroup |
|
0:* |
For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0) |
||
|
0:* |
Additional descriptive text associated with journey. Inherited property. |
||||
|
|
0:1 |
Contact details for use by members of public. (since SIRI 2.0) |
|||
|
|
0:1 |
Contact details for use by operational staff. (since SIRI 2.0) |
|||
| siri:JourneyEndTimesGroup |
|
0:1 |
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'. |
||
|
|
0:1 |
Timetabled departure time from Origin. |
|||
|
|
0:1 |
Timetabled arrival time at Destination. |
|||
|
0:1 |
Whether journey is first or last journey of day. (since SIRI 2.0) |
||||
| siri:DisruptionGroup |
0:* |
Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) |
|||
|
0:* |
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. |
||||
|
0:1 |
A change to the availaibility of EQUIPMENT. Basic structure defined in the first 1.0 SIRI XSd. |
||||
|
0:* |
Reference to a SITUATION associated with the element. |
||||
| siri:JourneyProgressGroup |
|
0:1 |
Whether there is real-time information available for journey. Default is 'true'. It is recommended to specify a MonitoringError if Monitored is set to 'false'. |
||
|
|
0:1 |
If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. MonitoringError must not be used if Monitored is omitted or set to 'true'. |
|||
| siri:ProgressDataQualityGroup |
|
0:1 |
Whether the VEHICLE iis in traffic congestion. If not, present, not known. |
||
|
|
0:1 |
Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'. |
|||
|
0:1 |
Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate. If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general. |
||||
|
0:1 |
Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1) |
||||
|
|
0:1 |
System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. |
|||
|
|
0:1 |
Confidence QUALITY LEVEL of data. Default is 'reliable'. |
|||
| siri:ProgressDataGroup |
|
0:1 |
Current geospatial location of VEHICLE. Measured to front of vehicle. |
||
|
|
0:1 |
Time at which location was recorded. If not present assume that the recorded at time on the containing delivery. |
|||
|
|
0:1 |
Bearing in compass degrees in which VEHICLE is heading. |
|||
|
|
0:1 |
Rate of progress of VEHICLE. Default is 'normal' |
|||
|
|
0:1 |
Velocity of VEHICLE. EIther actual speed or average speed may be used. (since SIRI 2.0) |
|||
|
|
0:1 |
Whether the engine of the vehicle is on. Default is 'true' (since SIRI 2.0) |
|||
|
0:1 |
An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown. Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level. |
||||
|
|
0:1 |
Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. |
|||
|
|
0:* |
An arbitrary textual status description of the running of this VEHICLE JOURNEY. (Unbounded 0:* since SIRI 2.0) |
|||
|
|
0:1 |
An classification of the progress state of running of this VEHICLE JOURNEY. (since SIRI 2.0) |
|||
| siri:TrainOperationalInfoGroup |
|
0:* |
If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. |
||
| siri:OperationalBlockGroup |
|
0:1 |
BLOCK that VEHICLE is running. |
||
|
|
0:1 |
COURSE OF JOURNEY ('Run') that VEHICLE is running. |
|||
| siri:OperationalInfoGroup |
0:1 |
Reference to a VEHICLE JOURNEY. |
|||
|
0:1 |
Reference to a VEHICLE. |
||||
|
|
0:* |
Refercence to other VEHICLE Journeys ((since SIRI 2.0)) |
|||
|
|
0:1 |
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. (since SIRI 2.0) |
|||
|
|
0:1 |
The name oo the Driver or Crew (since SIRI 2.0) |
|||
| siri:TrainOperationalInfoGroup |
|
0:1 |
TRAIN NUMBERs for journey. (since SIRI 2.0) |
||
|
|
0:1 |
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. |
|||
| siri:JourneyFormationGroup |
|
0:1 |
|||
|
|
0:1 |
||||
|
|
0:1 |
||||
| siri:MonitoredCallingPatternGroup |
|
0:1 |
Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits. Should only be included if the detail level was requested. |
||
|
|
0:1 |
Monitored CALL at the current stop. For SIRI-SM this is the stop for which data is requested. For SIRI-VM this is the most recent stop visited by the VEHICLE. |
|||
|
|
0:1 |
Information on CALLs at the intermediate stops beyond the current stop, up to and including the destination, in order of visits. Should only be included if the detail level was requested. |
|||
|
|
0:1 |
Whether the above CALL sequence is complete, i.e. represents every CALL of the ROUTE and so can be used to replace a previous CALL sequence. Default is 'false'. |
|||
49.38. The complex type complexType[siri:VehicleMonitoringServiceCapabilitiesStructure]/TopicFiltering#complexType (typedef-76.3)
|
|
- |
||||
|
|
1:1 |
Default preview interval. Default is 60 minutes. |
|||
|
|
1:1 |
Whether results can be filtered by Vehicle Monitoring Fixed as 'true'. |
|||
|
0:1 |
Whether results can be filtered by VEHICLE. Default is 'false'. |
||||
|
0:1 |
Whether results can be filtered by LINE. Default is 'true' |
||||
|
0:1 |
Whether results can be filtered by DIRECTION Default is 'true'. |
||||
49.39. The complex type complexType[siri:VehicleMonitoringServiceCapabilitiesStructure]/RequestPolicy#complexType (typedef-76.4)
|
|
Type for Common Request Policy capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:* |
National languages supported by service. |
|||
|
|
0:1 |
Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) |
|||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
|
-1:1 |
Name of GML Coordinate format used for Geospatial points in responses. |
||
|
b |
|
-1:1 |
Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. |
||
|
Inherited content is followed by own content: |
|||||
| siri:VehicleMonitoringVolumeGroup |
|
0:1 |
Whether Detail level filtering is supported. Default is ' false'. |
||
|
|
0:1 |
Detail level. Default Normal. |
|||
|
|
0:1 |
Whether results can be limited to a maximum number. Default is 'true'. |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of calls to include can be specified. Default is 'false'. (since SIRI 2.0) |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. (since SIRI 2.0) |
|||
|
|
0:1 |
If system can return detailed calling pattern, whether a number of previous calls to include can be specified. Default is 'false'. (since SIRI 2.0) |
|||
49.40. The complex type complexType[siri:VehicleMonitoringServiceCapabilitiesStructure]/AccessControl#complexType (typedef-76.5)
|
|
Type for Common Access control capabilities. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
1:1 |
Whether access control of requests is supported. Default is 'false'. |
|||
|
Inherited content is followed by own content: |
|||||
|
0:1 |
If access control is supported, whether access control by OPERATOR is supported. Default is 'true'. |
||||
|
0:1 |
If access control is supported, whether access control by LINE is supported. Default is 'true'. |
||||
|
|
0:1 |
If access control is supported, whether access control by monitoring point is supported. Default is 'true'. |
|||
49.41. The complex type complexType[siri:VehicleMonitoringServiceCapabilitiesStructure]/ResponseFeatures#complexType (typedef-76.6)
|
|
- |
||||
|
|
0:1 |
Whether result has location. Default is 'true'. |
|||
|
|
0:1 |
Whether result supports SITUATION REFERENCESs. Default is 'false'. (since SIRI 2.0) |
|||
49.42. The complex type element[siri:VehicleMonitoringPermissions]#complexType (typedef-76.7)
|
|
Type for abstract permissions. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
Version of permission set. |
|||
|
Inherited content is followed by own content: |
|||||
|
|
0:* |
Permissions for use of VEHICLE MONITORING. Can be used to specify which Consumers can see which vehicles |
|||
49.43. The complex type complexType[siri:VehicleMonitoringServicePermissionStructure]/VehicleMonitoringPermissions#complexType (typedef-76.8)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Allow access to all topics known to the service. |
|||
|
b |
|
-1:* |
Participant's permission for this Vehicle Monitor (DISPLAY SSIGNMENT). |
||
50. SIRI Service Interface for Real-time Information relating to Public Transport Operations. XML Schema with loosely coupled functional services,
50.1. The toplevel element siri:Siri
|
|
- |
||||
|
|
1:1 |
||||
|
The element contains one of the following elements (a-c) |
|||||
|
The element contains one of the following elements (a-d) |
|||||
|
The element contains one of the following elements (a-c) |
|||||
| siri:ServiceRequestGroup |
aaa |
-1:1 |
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) |
||
|
aab |
-1:1 |
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. |
|||
|
aac |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
The element contains one of the following elements (a-b) |
|||||
| siri:DeliveryRequestGroup |
aba |
-1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
||
|
abb |
-1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
|||
|
The element contains one of the following elements (a-b) |
|||||
| siri:StatusRequestGroup |
aca |
-1:1 |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
||
|
acb |
-1:1 |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
|
The element contains one of the following elements (a-b) |
|||||
| siri:DiscoveryRequestGroup |
ada |
-1:1 |
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||
|
adb |
-1:1 |
Abstract Discovery request. |
|||
|
The element contains one of the following elements (a-d) |
|||||
|
The element contains one of the following elements (a-b) |
|||||
| siri:ServiceResponseGroup |
baa |
-1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
||
|
bab |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
The element contains one of the following elements (a-c) |
|||||
| siri:DeliveryResponseGroup |
bba |
-1:1 |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
||
|
bbb |
-1:1 |
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. |
|||
|
bbc |
-1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
|
The element contains one of the following elements (a) |
|||||
| siri:StatusResponseGroup |
bca |
-1:1 |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
||
|
The element contains one of the following elements (a-b) |
|||||
| siri:DiscoveryResponseGroup |
bda |
-1:1 |
Responses with the capabilities of an implementation. |
||
|
bdb |
-1:1 |
Abstract type for a discovery delivery. |
|||
|
c |
-0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
|||
50.2. The complex type group[siri:ServiceDeliveryRequestStatusGroup]/ErrorCondition#complexType (typedef-50.1)
|
|
- |
||||
|
The element contains one of the following elements (a-b) |
|||||
|
a |
-1:1 |
Error: Service does not support the requested capability. |
|||
|
b |
-1:1 |
Error: Error type other than the well defined codes. |
|||
|
|
0:1 |
Text description of error. |
|||
50.3. The complex type element[siri:SubscriptionRequest]#complexType (typedef-53.2)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
| siri:SubscriberEndpointGroup |
|
0:1 |
Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. |
||
|
|
0:1 |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. |
|||
|
|
0:1 |
General values that apply to subscription. Usually set by configuration. |
|||
|
1:* |
Subsititutable type for a SIRI Functional Service subscription request. |
||||
50.4. The complex type element[siri:Siri]#complexType (typedef-72.1)
|
|
- |
||||
|
|
1:1 |
||||
|
The element contains one of the following elements (a-c) |
|||||
|
In case of choice 'a', the element contains one of the following elements (aa-ad) |
|||||
|
In case of choice 'aa', the element contains one of the following elements (aaa-aac) |
|||||
| siri:ServiceRequestGroup |
aaa |
-1:1 |
Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) |
||
|
aab |
-1:1 |
Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. |
|||
|
aac |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'ab', the element contains one of the following elements (aba-abb) |
|||||
| siri:DeliveryRequestGroup |
aba |
-1:1 |
Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. |
||
|
abb |
-1:1 |
Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. |
|||
|
In case of choice 'ac', the element contains one of the following elements (aca-acb) |
|||||
| siri:StatusRequestGroup |
aca |
-1:1 |
Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. |
||
|
acb |
-1:1 |
Notification from Producer to Consumer to indicate that the service is running normally. |
|||
|
In case of choice 'ad', the element contains one of the following elements (ada-adb) |
|||||
| siri:DiscoveryRequestGroup |
ada |
-1:1 |
Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. |
||
|
adb |
-1:1 |
Abstract Discovery request. |
|||
|
In case of choice 'b', the element contains one of the following elements (ba-bd) |
|||||
|
In case of choice 'ba', the element contains one of the following elements (baa-bab) |
|||||
| siri:ServiceResponseGroup |
baa |
-1:1 |
Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. |
||
|
bab |
-1:1 |
Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. |
|||
|
In case of choice 'bb', the element contains one of the following elements (bba-bbc) |
|||||
| siri:DeliveryResponseGroup |
bba |
-1:1 |
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. |
||
|
bbb |
-1:1 |
Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. |
|||
|
bbc |
-1:1 |
Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. |
|||
|
In case of choice 'bc', the element contains one of the following elements (bca) |
|||||
| siri:StatusResponseGroup |
bca |
-1:1 |
Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. |
||
|
In case of choice 'bd', the element contains one of the following elements (bda-bdb) |
|||||
| siri:DiscoveryResponseGroup |
bda |
-1:1 |
Responses with the capabilities of an implementation. |
||
|
bdb |
-1:1 |
Abstract type for a discovery delivery. |
|||
|
c |
-0:1 |
Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). |
|||
50.5. The complex type element[siri:ServiceRequest]#complexType (typedef-77.2)
|
|
Type for General SIRI Request. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
|
0:1 |
General request properties - typically configured rather than repeated on request. |
|||
|
1:1 |
Timestamp on request. |
||||
| siri:AuthenticatedRequestGroup |
|
0:1 |
Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) |
||
|
|
0:1 |
Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) |
|||
| siri:RequestorEndpointGroup |
|
0:1 |
Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. |
||
|
1:1 |
Reference to a requestor - Participant Code. |
||||
|
|
0:1 |
Arbitrary unique identifier that can be used to reference this message in subsequent interactions. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
50.6. The complex type element[siri:ServiceDelivery]#complexType (typedef-77.4)
|
|
General Type for General SIRI Response. |
||||
|
The element content starts with items inherited from the base type: |
|||||
|
1:1 |
Time individual response element was created. |
||||
| siri:ProducerResponseEndpointGroup |
|
0:1 |
Unique identifier of Producer - Participant reference. |
||
|
|
0:1 |
Endpoint Address to which acknowledgements to confirm delivery are to be sent. |
|||
|
|
0:1 |
An arbitrary unique reference associated with the response which may be used to reference it. |
|||
|
|
0:1 |
Reference to an arbitrary unique identifier associated with the request which gave rise to this response. |
|||
| siri:DelegatorEndpointGroup |
|
0:1 |
Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) |
||
|
|
0:1 |
Identifier of delegating system that originated message. (since SIRI 2.0) |
|||
|
|
1:1 |
Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. |
|||
| siri:ServiceDeliveryRequestStatusGroup |
|
0:1 |
Whether the complerte request could be processed successfully or not. Default is 'true'. If any of the individual requests within the delivery failed, should be set to ' false'. |
||
|
|
0:1 |
Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. |
|||
| siri:ServiceDeliveryBodyGroup |
|
0:1 |
Whether there is a further delvery message with more current updates that follows this one. Default is 'false'. |
||
|
1:* |
Subsititutable type for a SIRI Functional Service request. |
||||