Schema Summary |
||
|
SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (2):
|
||
|
Target Namespace:
Version:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (11):
Included in Schemas (2):
|
||
|
SIRI Common Request Fra,mework
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (1):
|
||
|
SIRI Framework - Common Requests.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (2):
|
||
|
SIRI subschema with view of SCHEDULED CONNECTION LINKS for use in Connection Link Discovery service
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (2):
Included in Schemas (1):
|
||
|
SIRI-CM Connection Monitoring Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
|
||
|
SIRI-CM Connection Monitoring Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (1):
|
||
|
SIRI-CT Connection Timetable Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (2):
|
||
|
SIRI-CT Connection Timetable Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (1):
|
||
|
SIRI-Model Dated Vehicle Joruney.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (1):
|
||
|
SIRI DIscovery Services for SCHEDULED STOP POINTs, LINEs,OPERATORs, FACILITies and feature TYPE OF VALUE codes.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (7):
Included in Schemas (1):
|
||
|
SIRI-ET Estimated Timetable Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (1):
|
||
|
SIRI-ET Estimated Timetable Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (1):
|
||
|
SIRi Facilities
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Included in Schemas (1):
|
||
|
SIRi Facility model elemenys
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imports Schemas (2):
Includes Schemas (3):
Included in Schemas (2):
|
||
|
SIRI-FM Facility Monitoring Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imports Schemas (5):
Includes Schemas (3):
Included in Schemas (1):
|
||
|
SIRI subschema with view of classifiers for use in Discovery service
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (2):
Included in Schemas (3):
|
||
|
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imported by Schemas (1):
Included in Schemas (1):
|
||
|
SIRI-GM General Message Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (1):
|
||
|
SIRI subschema with view of Info channel for use in Discovery service
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (1):
|
||
|
SIRI-CT Interchange journey Connection Timetable Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (2):
|
||
|
SIRI Common Journey Model.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (7):
|
||
|
SIRI Journey Model Identifiers.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (1):
|
||
|
SIRI subschema with view of LINE for use in Discovery service
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imports Schemas (1):
Includes Schemas (2):
Included in Schemas (1):
|
||
|
SIRI Framewrok Location Types.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imported by Schemas (2):
Included in Schemas (1):
|
||
|
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (2):
Included in Schemas (10):
|
||
|
SIRI TRANSPORT MODEs
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imported by Schemas (1):
Included in Schemas (1):
|
||
|
SIRI MONITORED VEHICLE JOURNEY Model.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (3):
|
||
|
OPERATOR types for SIRi.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Included in Schemas (1):
|
||
|
SIRI Framework Participant Types.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Included in Schemas (3):
|
||
|
SIRI Framework Permission Types.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (1):
|
||
|
SIRI-PT DATED JOURNEY Model view.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (1):
|
||
|
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (4):
Included in Schemas (6):
|
||
|
SIRI Framework Error COnditions.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (2):
Included in Schemas (1):
|
||
|
SIRI Common Framework basic identifier types.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (1):
|
||
|
SIRI Common Request Framework.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (12):
|
||
|
SIRI-SX Situation Model.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imports Schemas (3):
Includes Schemas (5):
Included in Schemas (1):
|
||
|
SIRI-SX Situation Actions.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (1):
|
||
|
SIRI-SX Situation Scope.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imports Schemas (10):
Includes Schemas (4):
Included in Schemas (1):
|
||
|
SIRI-SX Situation Classifiers.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Included in Schemas (1):
|
||
|
SIRI-SX Situation Exchange Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imports Schemas (4):
Includes Schemas (3):
Included in Schemas (1):
|
||
|
SIRI-SX Situation IDentifiers.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imports Schemas (2):
Includes Schemas (2):
Included in Schemas (2):
|
||
|
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Included in Schemas (1):
|
||
|
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Included in Schemas (2):
|
||
|
SIRI-SM Stop Monitoring Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (1):
|
||
|
SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (2):
Included in Schemas (2):
|
||
|
SIRI-ST Stop Timetable Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (1):
|
||
|
SIRI-ST TargetedVehicleJourney for Stop Timetable Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (1):
Included in Schemas (1):
|
||
|
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Included in Schemas (1):
|
||
|
SIRI Framework Base Types.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Imports Schemas (1):
Imported by Schemas (4):
Included in Schemas (5):
|
||
|
SIRI Framework Utility Types.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Included in Schemas (4):
|
||
|
SIRI-VM Vehicle Monitoring Service.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (3):
Included in Schemas (1):
|
||
|
SIRI Service Interface for Real-time Information relating to Public Transport Operations.
Target Namespace:
Version:
Defined Components:
Default Namespace-Qualified Form:
Schema Location:
Includes Schemas (2):
|
||
All Element Summary (local elements unified by type) |
||||||||||||||
|
Abstract type for a discovery delivery.
|
||||||||||||||
|
Abstract Discovery request.
|
||||||||||||||
|
Subsititutable type for a SIRI Functional Service Capabiloitiesequest.
|
||||||||||||||
|
Subsititutable type for a SIRI Functional Service Capabiloitiesequest.
|
||||||||||||||
|
Subsititutable type for a SIRI Functional Service request.
|
||||||||||||||
|
Subsititutable type for a SIRI Functional Service request.
|
||||||||||||||
|
Subsititutable type for a SIRI Functional Service subscription request.
|
||||||||||||||
|
Subsititutable type for a timestamped SIRI request.
|
||||||||||||||
|
Subsititutable type for a SIRI response.
|
||||||||||||||
|
Substitutable type for a SIRI Functional Service request.
|
||||||||||||||
|
Subsititutable type for a SIRI request with requestor dteials tracked.
|
||||||||||||||
|
Optional Access control capabilities.
|
||||||||||||||
|
Optional Access control capabilities.
|
||||||||||||||
|
Optional Access control capabilities.
|
||||||||||||||
|
Available Optional Access control capabilities.
|
||||||||||||||
|
Access control that can be used.
|
||||||||||||||
|
Optional Access control capabilities.
|
||||||||||||||
|
||||||||||||||
|
Classification of Access Facility.
|
||||||||||||||
|
Classification of Access Facility.
|
||||||||||||||
|
Type of AccessFeature (+SIRI.20)
|
||||||||||||||
|
||||||||||||||
|
Nature of CONNECTION link.
|
||||||||||||||
|
Parameters to filter Situation Exchange Service requests, based on specific needs .
|
||||||||||||||
|
Filter only for facility changes that affect the following accessibility needs.
|
||||||||||||||
|
||||||||||||||
|
Error: Requestor is not authorised to the service or data requested.
|
||||||||||||||
|
Classification of Accomodation Facility type - Tpeg pti23.
|
||||||||||||||
AccountId (type xsd:NMTOKEN) |
Account Identifier.
|
|||||||||||||
AccountKey (type xsd:normalizedString) |
Authentication key for request.
|
|||||||||||||
|
Data associated with action.
|
||||||||||||||
|
Actions that apply to all SITUATIONs unless overridden.
|
||||||||||||||
|
Processing Status of action at time of SITUATION publication.
|
||||||||||||||
|
Observed time of arrival of VEHICLE at stop.
|
||||||||||||||
|
Observed time of departure of VEHICLE from stop.
|
||||||||||||||
|
For frequency based services, observed interval between vehicles at stop.
|
||||||||||||||
|
Physical QUAY actually used.
|
||||||||||||||
|
Refercence to other VEHICLE Journeys (+SIRI v2.0)
|
||||||||||||||
|
||||||||||||||
Advertised (type xsd:boolean) |
Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection.
|
|||||||||||||
|
Advice to passengers.
|
||||||||||||||
|
Further advice to passengers.
|
||||||||||||||
|
Reference to a standardis advisory NOTICE to be given to passengers if a particular condition arises .
|
||||||||||||||
|
Quay affected by SITUATION.
|
||||||||||||||
|
Quays affected by SITUATION.
|
||||||||||||||
|
CONNECTION LINKs from stop that are affected by the SITUATION.
|
||||||||||||||
|
Facilities available for component (+SIRI 2.0)
|
||||||||||||||
|
Facilities available for VEHICLE JOURNEY (+SIRI 2.0)
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Information about the indvidual LINEs in the network that are affected.
|
||||||||||||||
|
Modes within station/stop affected by the SITUATION.
|
||||||||||||||
|
PathLinks affected by SITUATION.
|
||||||||||||||
|
Nrtworks and Route(s) affected by SITUATION.
|
||||||||||||||
|
Indicates whether the list of STOP POINTS contains all STOP POINTS of ROUTE or only affected by SITUATION.
|
||||||||||||||
|
||||||||||||||
|
PATH LINKs affected by a SITUATION.
|
||||||||||||||
|
Stop affected by SITUATION.
|
||||||||||||||
|
Description of affected road.
|
||||||||||||||
|
Route affected by Situation.
|
||||||||||||||
|
||||||||||||||
|
Stop affected by SITUATION.
|
||||||||||||||
|
||||||||||||||
|
Vehicles affected by the SITUATION.
|
||||||||||||||
|
Journeys affected by the SITUATION.
|
||||||||||||||
|
||||||||||||||
|
Reference to an Agent, i.e.
|
||||||||||||||
|
Target arrival time of VEHICLE at stop according to latest working timetable.
|
||||||||||||||
AimedArrivalTime (type xsd:dateTime) |
|
|||||||||||||
|
Target departure time of VEHICLE from stop according to latest working timetable.
|
||||||||||||||
AimedDepartureTime (type xsd:dateTime) |
|
|||||||||||||
|
For frequency based services, target interval between vehicles at stop.
|
||||||||||||||
|
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
TPEG pti08 Air submodes.
|
||||||||||||||
|
Terminate all subscriptions for the requestor.
|
||||||||||||||
|
Whether to return all data, or just new updates since the last delivery.
|
||||||||||||||
|
||||||||||||||
|
All known modes for stop.
|
||||||||||||||
|
All OPERATORs.
|
||||||||||||||
Allow (type xsd:boolean) |
Whether the participant may access this topic.
|
|||||||||||||
|
Allow access to all topics known to the service.
|
||||||||||||||
|
Who may make a prediction.
|
||||||||||||||
|
Error: Valid request was made but request would exceed the permitted resource usage of the client.
|
||||||||||||||
|
Parmissions apply by default to All particpants.
|
||||||||||||||
|
Altitude.
|
||||||||||||||
|
SCHEDULED CONNECTION LINK definition.
|
||||||||||||||
|
Facility Definition.
|
||||||||||||||
|
Information about LINEs covered by server.
|
||||||||||||||
|
SCHEDULED STOP POINT definition.
|
||||||||||||||
|
In case of a delayed cancellation this time tells from when the cancellation applies.
|
||||||||||||||
|
Affected overall Geographic scope.
|
||||||||||||||
|
Type of boarding and alighting allowed at stop.
|
||||||||||||||
|
Type of boarding and alighting allowed at stop.
|
||||||||||||||
|
||||||||||||||
|
Bay or platform name.
|
||||||||||||||
|
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”.
|
||||||||||||||
|
Classification of the timeliness of the visit according to a fixed list of values.
|
||||||||||||||
|
Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform).
|
||||||||||||||
|
Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform).
|
||||||||||||||
|
||||||||||||||
|
Classification of Assistance Facility.
|
||||||||||||||
|
Intended audience of SITUATION.
|
||||||||||||||
|
Subsititutable type for an authenticated request Authenticated.
|
||||||||||||||
|
Bearing in compass degrees in which VEHICLE is heading.
|
||||||||||||||
|
Whether reminders should be sent.
|
||||||||||||||
|
Error: Data period or subscription period is outside of period covered by service.
|
||||||||||||||
|
How Disruption should be handled in Info systems.
|
||||||||||||||
|
||||||||||||||
|
Change to normal boarding activity allowed at stop.
|
||||||||||||||
BoardingStretch (type xsd:boolean) |
Whether this is a Hail and Ride Stop.
|
|||||||||||||
|
Booking Status - Tpeg Report Type pti24.
|
||||||||||||||
|
||||||||||||||
|
TPEG pti05 Bus submodes.
|
||||||||||||||
|
Send as email alert.
|
||||||||||||||
|
Send as mobile alert by SMS or WAP push.
|
||||||||||||||
|
Whether a start time other than now can be specified for preview interval.
|
||||||||||||||
|
||||||||||||||
|
Status of CALL TPEG 13_6
|
||||||||||||||
|
||||||||||||||
|
CALLs making up VEHICLE JOURNEY [equivalent to TPEG pti15 3 stop, 15_5 not-stopping, 15-6 temporary stop route_description_type]
|
||||||||||||||
Cancellation (type xsd:boolean) |
|
|||||||||||||
|
Requests a the current capabilities of the server.
|
||||||||||||||
|
Requests a the current capabilities of the server.
|
||||||||||||||
|
Responses with the capabilities of an implementation.
|
||||||||||||||
|
Responses with the capabilities of an implementation.
|
||||||||||||||
|
Error: Service does not support the requested capability.
|
||||||||||||||
|
Id of capabiliuty that is noit supported.
|
||||||||||||||
|
Information on casualties.
|
||||||||||||||
|
Impact of Road SITUATION as specified by Datex2 model.
|
||||||||||||||
|
Publish to Teltext.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
If access control is supported, whether access control by CONNECTION link is supported.
|
||||||||||||||
|
If access control is supported, whether access control by LINE is supported.
|
||||||||||||||
|
If access control is supported, whether access control by LINE is supported.
|
||||||||||||||
|
If access control is supported, whether access control by monitoring point (LOGICAL DISPLAY) is supported.
|
||||||||||||||
|
If access control is supported, whether access control by OPERATOR is supported.
|
||||||||||||||
|
Address to which CheckStatus requests are to be sent.
|
||||||||||||||
|
Request from Consumer to Producer to check whether services is working.
|
||||||||||||||
|
Response from Producer to Consumer to inform whether services is working.
|
||||||||||||||
|
If access control is supported, whether access control by monitoring point is supported.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
ClearNotice (type xsd:boolean) |
Whether a clearing notice should be displayed.
|
|||||||||||||
|
TPEG pti03 Coach submodes.
|
||||||||||||||
|
Communications Transport method used to exchange messages.
|
||||||||||||||
|
Name of component.
|
||||||||||||||
|
Reference to a Stop Place.
|
||||||||||||||
|
Type of Component.
|
||||||||||||||
|
Compression method used to compress messages for transmission.
|
||||||||||||||
|
Classification of effect on service.
|
||||||||||||||
|
Confidence QUALITY LEVEL of data.
|
||||||||||||||
|
Whether Consumers should issue an acknowledgement on successful receipt of a delivery.
|
||||||||||||||
|
||||||||||||||
|
Name of other connecting STOP POINT of a CONNECTION link.
|
||||||||||||||
|
Reference to other connecting STOP POINT of a CONNECTION link.
|
||||||||||||||
|
||||||||||||||
|
Reference to connecting VEHICLE JOURNEY affected by a SITUATION.
|
||||||||||||||
|
Zone in which connecting stop lies.
|
||||||||||||||
|
Direction of SERVICE JOURNEY INTERCHANGE.
|
||||||||||||||
|
Reference to a CONNECTION Link affected by a SITUATION.
|
||||||||||||||
|
Identifier of CONNECTION LINk.
|
||||||||||||||
|
Name of SCHEDULED CONNECTION LINK.
|
||||||||||||||
|
Participant's permission for this CONNECTION link.
|
||||||||||||||
|
The CONNECTION links that the participant may access.
|
||||||||||||||
|
Reference to a CONNECTION link
|
||||||||||||||
|
CONNECTION links from stop.
|
||||||||||||||
|
Returns the CONNECTION LINKs covered by a web service.
|
||||||||||||||
|
Level of detail to include in response.
|
||||||||||||||
|
Requests a list of the CONNECTION LINKs covered by a Producer.
|
||||||||||||||
|
Whether connection monitoring is active or not for this connection +SIRI v2.0
|
||||||||||||||
|
Request for information about Connection Monitoring Service Capabilities.
|
||||||||||||||
|
Request for information about Connection Monitoring Service Capabilities.
|
||||||||||||||
|
Capabilities for Connection Monitoring Service.
|
||||||||||||||
|
Capabilities for Connection Monitoring Service.
|
||||||||||||||
|
||||||||||||||
|
Distributor Delivery for Connection Monitoring Service.
|
||||||||||||||
|
Distributor Delivery for Connection Monitoring Service.
|
||||||||||||||
|
Feeder Delivery for Connection Monitoring Service.
|
||||||||||||||
|
Feeder Delivery for Connection Monitoring Service.
|
||||||||||||||
|
||||||||||||||
|
Participants permissions to use the service.
|
||||||||||||||
|
Participants permissions to use the service.
|
||||||||||||||
|
Request for information about changes to connections at a stop for Connection Monitoring service.
|
||||||||||||||
|
Request for information about changes to connections at a stop for Connection Monitoring service.
|
||||||||||||||
|
Capabilities of Connection Monitoring Service.
|
||||||||||||||
|
Capabilities of Connection Monitoring Service.
|
||||||||||||||
|
Request for a subscription to Connection Monitoring Service.
|
||||||||||||||
|
Request for a subscription to Connection Monitoring Service.
|
||||||||||||||
|
Name of CONNECTION link affected by a SITUATION.
|
||||||||||||||
|
Request for information about Connection Timetable Service Capabilities.
|
||||||||||||||
|
Request for information about Connection Timetable Service Capabilities.
|
||||||||||||||
|
Capabilities for Connection Timetable Service.
|
||||||||||||||
|
Capabilities for Connection Timetable Service.
|
||||||||||||||
|
Delivery for Connection Timetable Service.
|
||||||||||||||
|
Delivery for Connection Timetable Service.
|
||||||||||||||
|
||||||||||||||
|
Participant's permissions to use the service, Only returned if requested.
|
||||||||||||||
|
Participant's permissions to use the service, Only returned if requested.
|
||||||||||||||
|
Request for information about timetabled connections at a stop.
|
||||||||||||||
|
Request for information about timetabled connections at a stop.
|
||||||||||||||
|
Capabilities of Connection Timetable Service.
|
||||||||||||||
|
Capabilities of Connection Timetable Service.
|
||||||||||||||
|
Subscription Request for information about Timetabled connections at a stop.
|
||||||||||||||
|
Subscription Request for information about Timetabled connections at a stop.
|
||||||||||||||
|
Nature of the effect to disrupt (or restore) service, and further details.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Variant text.
|
||||||||||||||
|
Message Content.
|
||||||||||||||
|
Coordinates of points in a GML compatibe format, as indicated by srsName attribute.
|
||||||||||||||
|
Country of origin of source element.
|
||||||||||||||
|
||||||||||||||
|
COURSE OF JOURNEY ('Run') that VEHICLE is running.
|
||||||||||||||
CreationTime (type xsd:dateTime) |
|
|||||||||||||
|
Current Location of the VEHICLE
|
||||||||||||||
|
identifier of data frame within particpant service.
|
||||||||||||||
|
Maximum data horizon for requests.
|
||||||||||||||
|
Default names pace used to scope data identifiers.
|
||||||||||||||
DataReady (type xsd:boolean) |
Whether data delivery is ready to be fetched SIRI v 2.0
|
|||||||||||||
|
Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received.
|
||||||||||||||
|
Request from Producer to Consumer to notify that data update is ready to fetch.
|
||||||||||||||
|
Response from Consumer to Producer to acknowledge that data hase been received.
|
||||||||||||||
DataSource (type xsd:string) |
System originating real-time data.
|
|||||||||||||
|
Request from Consumer to Producer to fetch update previously notified by a Data ready message.
|
||||||||||||||
|
Complete sequence of stops along the route path, in calling order.
|
||||||||||||||
|
Complete sequence of stops along the route path, in calling order.
|
||||||||||||||
|
A TIMETABLE FRAME to run on a specified date.
|
||||||||||||||
|
A planned VEHICLE JOURNEY taking place on a particular date.
|
||||||||||||||
|
Complete list of all planned VEHICLE JOURNEYs for this LINE and DIRECTION.
|
||||||||||||||
|
Identifier for a VEHICLE JOURNEY.
|
||||||||||||||
|
If no VEHICLE JOURNEY reference is available, identify it by origin and destination and the scheduled times at these stops.
|
||||||||||||||
|
Reference to a DATED VEHICLE JOURNEY.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Refereences to road network locations affected by the SITUATION.
|
||||||||||||||
|
Tpeg DAY TYPE pti_table 34
|
||||||||||||||
|
Days type for monitoring availability.
|
||||||||||||||
|
Default Detail level if non specified on request.
|
||||||||||||||
|
Detail level.
|
||||||||||||||
|
Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor.
|
||||||||||||||
DefaultLanguage (type xsd:language) |
|
|||||||||||||
|
Additional journey time needed to overcome disruption.
|
||||||||||||||
|
Delay of VEHICLE against schedule, to a precision in seconds.
|
||||||||||||||
|
Time band into which delay will fall.
|
||||||||||||||
|
||||||||||||||
|
Category of delay.
|
||||||||||||||
|
Address of original Consumer, i.e. requesting system to which delegating response is to be returned.
|
||||||||||||||
|
Identifier of delegating system that originated message.
|
||||||||||||||
|
Delivery capabilities.
|
||||||||||||||
|
Whether Delivery is fetched or retrieved.
|
||||||||||||||
|
Variant of a notice for use in a particular media channel.
|
||||||||||||||
|
Nature of boarding allowed at stop.
|
||||||||||||||
|
Type of alighting allowed at stop.
|
||||||||||||||
|
||||||||||||||
|
Departure QUAY ( Bay or platform) name.
|
||||||||||||||
|
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”.
|
||||||||||||||
|
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values.
|
||||||||||||||
|
||||||||||||||
|
Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY.
|
||||||||||||||
|
Earliest and latest departure time.
|
||||||||||||||
|
Description of SITUATION.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Description of a DESTINATION.
|
||||||||||||||
|
Destination of VEHICLE JOURNEY.
|
||||||||||||||
DestinationAimedArrivalTime (type xsd:dateTime) |
|
|||||||||||||
|
||||||||||||||
|
||||||||||||||
|
The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public.
|
||||||||||||||
|
||||||||||||||
|
Reference to the destination SCHEDULED STOP POINT of the journey.
|
||||||||||||||
|
The destination is used to help identify the VEHICLE JOURNEY.
|
||||||||||||||
|
||||||||||||||
|
DESTINATIONs to which the LINE runs.
|
||||||||||||||
|
||||||||||||||
|
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards.
|
||||||||||||||
|
Additional descriptive details about the SITUATION (Unbounded since SIRI 2.0).
|
||||||||||||||
|
Further Textual advice to passengers.
|
||||||||||||||
|
Whether the service supports Direct delivery.
|
||||||||||||||
|
Description of a DIRECTION.
|
||||||||||||||
|
Directions of Route
|
||||||||||||||
|
||||||||||||||
|
The DIRECTION at the reference point in terms of general destination DIRECTION.
|
||||||||||||||
|
||||||||||||||
|
DIRECTIONs and Stops for the LINE.
|
||||||||||||||
|
Distance in metres from end of link at which SITUATION is to be shown.
|
||||||||||||||
|
Distance in metres from start of link at which SITUATION is to be shown.
|
||||||||||||||
|
Distance of VEHICLE from stop of CALL as measured along ROUTE track.
|
||||||||||||||
|
Units for Distance Type.
|
||||||||||||||
|
Link to Interchange stop from which the distributor journey departs.
|
||||||||||||||
|
Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Reference to a connecting distributor VEHICLE JOURNEY.
|
||||||||||||||
DistributorOrder (type xsd:positiveInteger) |
|
|||||||||||||
|
||||||||||||||
|
Name of the distributor's stop.
|
||||||||||||||
|
Identifer of the distributor's stop.
|
||||||||||||||
|
Reference to a (dated) distributor VEHICLE JOURNEY.
|
||||||||||||||
|
||||||||||||||
|
Whether an acknowledgement has been received that the driver will wait.
|
||||||||||||||
DriverName (type xsd:normalizedString) |
The name oo the Driver or Crew +SIRI v2.0
|
|||||||||||||
DriverRef (type xsd:normalizedString) |
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE.
|
|||||||||||||
|
||||||||||||||
EarliestExpectedDepartureTime (type xsd:dateTime) |
|
|||||||||||||
|
Description of fare exceptions allowed because of disruption.
|
||||||||||||||
|
Refernce to a fare exceptions code that is allowed because of the disruption.
|
||||||||||||||
|
Description of fare exceptions allowed because of disruption.
|
||||||||||||||
|
Email address to which notice should be sent.
|
||||||||||||||
|
Email of Supplier of information.
|
||||||||||||||
|
||||||||||||||
|
Error:Endpoint to which a message is to be distributed did not allow access by the cloient.
|
||||||||||||||
|
Error:Recipient of a message to be distributed is not available.
|
||||||||||||||
|
Identifier of stop point at which availability last applies.
|
||||||||||||||
|
||||||||||||||
EndTime (type xsd:dateTime) |
|
|||||||||||||
|
||||||||||||||
|
If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation.
|
||||||||||||||
EngineOn (type xsd:boolean) |
Whether the engine of the vehicle is on.
|
|||||||||||||
|
TPEG Pti18_4/TPEG Pti_22 environment event reason.
|
||||||||||||||
|
Additional refinements TPEG Environmentevent reason.
|
||||||||||||||
|
Availability change for Equipment item.
|
||||||||||||||
|
Service Features associated with equipment.
|
||||||||||||||
|
TPEG Pti18_3/TPEG Pti_21 equipment event reason.
|
||||||||||||||
|
Reference to an EQUIPMENT found at location.
|
||||||||||||||
|
Reference to an EQUIPMENT.
|
||||||||||||||
|
Availability status of the EQUIPMENT.
|
||||||||||||||
|
Additional refinements TPEG Equipment event reason.
|
||||||||||||||
|
Reference to a TYPE OF EQUIPMENT.r.
|
||||||||||||||
|
Subsititutable type for a SIRI Error code.
|
||||||||||||||
|
Description of error or warning condition associated with response.
|
||||||||||||||
|
Description of any error or warning condition that applies to the status check.
|
||||||||||||||
|
Description of any error or warning conditions that appluy to the overall request.
|
||||||||||||||
|
Description of any error or warning condition as to why Consumer cannot fetch data.
|
||||||||||||||
|
Description of any error or warning condition.
|
||||||||||||||
|
Description of any error or warning condition.
|
||||||||||||||
|
||||||||||||||
|
Element fror an erroc condition (for use in WSDL.)
|
||||||||||||||
ErrorText (type xsd:string) |
Addtional Description of error.
|
|||||||||||||
|
Text description providing additional information about the reason for the subscription termination.
|
||||||||||||||
|
Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered.
|
||||||||||||||
|
Estimated call tmes for journey
|
||||||||||||||
|
Estimated Journeys of a common TIMETABLE VERSION FRAME, grouped by timetable version.
|
||||||||||||||
|
A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs.
|
||||||||||||||
|
Request for information about Estimated Timetable Service Capabilities.
|
||||||||||||||
|
Capabilities for Estimated Timetable Service.
|
||||||||||||||
|
Delivery for Estimated Timetable Service.
|
||||||||||||||
|
Level of detail to include in response.
|
||||||||||||||
|
Permission for a single participant or all participants to use an aspect of the service.
|
||||||||||||||
|
Participant's permissions to use the service.
|
||||||||||||||
|
Request for information about the estimated timetable.
|
||||||||||||||
|
Capabilities of Estimated TimetableService.
|
||||||||||||||
|
Request for a subscription to the Estimated Timetable Service.
|
||||||||||||||
|
A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs.
|
||||||||||||||
|
If this is the first message about an extra unplanned VEHICLE JOURNEY, a new and unique code must be given for it.
|
||||||||||||||
|
Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times.
|
||||||||||||||
|
Estimated time of arriival of VEHICLE at stop .
|
||||||||||||||
ExpectedArrivalTime (type xsd:dateTime) |
|
|||||||||||||
|
||||||||||||||
|
Estimated time of departure of VEHICLE from stop.
|
||||||||||||||
|
||||||||||||||
|
Time at which distributor VEHICLE is expected to depart.
|
||||||||||||||
|
For frequency based services, expected interval between vehicles at stop.
|
||||||||||||||
|
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop.
|
||||||||||||||
|
Physical QUAY to use accoring to the real-time prediction.
|
||||||||||||||
|
Expected time fro reavailability of servcie.
|
||||||||||||||
|
Name of the unknown encountered extensions.
|
||||||||||||||
|
Extensions to schema.
|
||||||||||||||
|
Extension point.
|
||||||||||||||
|
External system reference to SITUATION.
|
||||||||||||||
|
Alternative identifier of LINE that an external system may associate with journey.
|
||||||||||||||
|
A single string that identifiers the referenced SITUATION.
|
||||||||||||||
ExtraCall (type xsd:boolean) |
|
|||||||||||||
ExtraJourney (type xsd:boolean) |
|
|||||||||||||
|
Facilities available for VEHICLE JOURNEY (+SIRI 2.0)
|
||||||||||||||
|
||||||||||||||
|
A change to the availaibility of EQUIPMENT.
|
||||||||||||||
|
Type of facility (several types may be associated to a single facility)
|
||||||||||||||
|
Identfier of Facility.
|
||||||||||||||
|
Condition of a Facility that is being monitored.
|
||||||||||||||
|
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management.
|
||||||||||||||
|
Returns the Facilities covered by a service.
|
||||||||||||||
|
Level of detail to include in response.
|
||||||||||||||
|
Describes where the facility is located.
|
||||||||||||||
|
Request for information about Vehicle Monitoring Service Capabilities.
|
||||||||||||||
|
Capabilities for Vehicle Monitoring Service.
|
||||||||||||||
|
Delivery for Vehicle Monitoring Service.
|
||||||||||||||
|
||||||||||||||
|
Participant's permissions to use the service.
|
||||||||||||||
|
Request for information about Facilities status.
|
||||||||||||||
|
Capabilities of Vehicle Monitoring Service.
|
||||||||||||||
|
Request for a subscription to the Vehicle Monitoring Service.
|
||||||||||||||
|
Name of FACILITY.
|
||||||||||||||
|
Reference to a Facility.
|
||||||||||||||
|
Requests a list of the Facilities covered by a Producer.
|
||||||||||||||
|
Status of Facility
|
||||||||||||||
|
Status of Facility.
|
||||||||||||||
|
Classification of FareClass Facility type - Tpeg pti23.
|
||||||||||||||
|
Fax number of Supplier of information.
|
||||||||||||||
|
Description of the feauture of the facility.
|
||||||||||||||
|
Classification of facilities into arbitrary Facility categories.
|
||||||||||||||
|
Service or Stop features associated with equipment.
|
||||||||||||||
|
Service features of stop.
|
||||||||||||||
|
Features of service.
|
||||||||||||||
|
||||||||||||||
|
Fedder/Fetcher SERVICE JOURNEY INTERCHANGE Activity.
|
||||||||||||||
|
Fedder/Fetcher SERVICE JOURNEY INTERCHANGE Activity.
|
||||||||||||||
|
||||||||||||||
|
Reference to a connecting distributor VEHICLE JOURNEY.
|
||||||||||||||
|
||||||||||||||
|
Name of the feeder's stop.
|
||||||||||||||
|
Identifer of the feeder's stop.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Whether the service supports Fetched delivery (VDV Style)
|
||||||||||||||
|
Whether results can be filtered by CONNECTION LINK.
|
||||||||||||||
|
Whether results can be filtered by DESTINATION.
|
||||||||||||||
|
Whether results can be filtered by DIRECTION Default is 'true'.
|
||||||||||||||
|
Whether results can be filtered by Facility (EQUIPMENT).
|
||||||||||||||
|
Whether results can be filtered by InfoChannel, departures.
|
||||||||||||||
|
Whether results can be filtered by SERVICE JOURNEY INTERCHANGE.
|
||||||||||||||
FilterByJourney (type xsd:boolean) |
|
|||||||||||||
|
Whether results can be filtered by Keywords.
|
||||||||||||||
|
Whether results can be filtered by LINE.
|
||||||||||||||
FilterByLocationRef (type xsd:boolean) |
|
|||||||||||||
|
Whether results can be filtered by MODE.
|
||||||||||||||
|
Whether results can be filtered by Monitoring point (LOGICAL DISPLAY).
|
||||||||||||||
|
Whether results can be filtered by NETWORKs.
|
||||||||||||||
|
Whether results can be filtered by OPERATOR.
|
||||||||||||||
FilterBySpecificNeed (type xsd:boolean) |
|
|||||||||||||
|
Whether results can be filtered by STOP PLACE identifvier.
|
||||||||||||||
|
Whether results can be filtered by SCHEDULED STOP POINT.
|
||||||||||||||
FilterByTime (type xsd:boolean) |
|
|||||||||||||
|
Whether results can be filtered by VALIDITY PERIOD.
|
||||||||||||||
|
Whether results can be filtered by VEHICLE JOURNEY.
|
||||||||||||||
|
Whether results can be filtered by Vehicle Monitoring Fixed as 'true'.
|
||||||||||||||
|
Whether results can be filtered by VEHICLE.
|
||||||||||||||
FilterByVersionRef (type xsd:boolean) |
|
|||||||||||||
|
Whether results can be filtered by VistitType, e.g. arrivals, departures.
|
||||||||||||||
|
Whether journey is first or last journey of day.
|
||||||||||||||
|
Whether journey is first or last jouurney of day.
|
||||||||||||||
ForeignJourneysOnly (type xsd:boolean) |
|
|||||||||||||
|
||||||||||||||
|
Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it.
|
||||||||||||||
|
Information on any planned feeder connections.
|
||||||||||||||
|
TPEG pti10 Funicular submodes.
|
||||||||||||||
|
Permissions for general capabilities.
|
||||||||||||||
|
General capabilities common to all SIRI service request types.
|
||||||||||||||
|
An informative message.
|
||||||||||||||
|
A revocation of a previous message.
|
||||||||||||||
|
Request for information about General Message Service Capabilities.
|
||||||||||||||
|
Capabilities for General Message Service.
|
||||||||||||||
|
Delivery for General Message Service.
|
||||||||||||||
|
Permission or a single particpant or all participants.
|
||||||||||||||
|
Participant's permissions to use the service.
|
||||||||||||||
|
Request for information about general information messages affecting stops, vehicles or services.
|
||||||||||||||
|
Capabilities of General Message Service.
|
||||||||||||||
|
Request for a subscription to General Message Service.
|
||||||||||||||
|
Datex 2 comments for public use.
|
||||||||||||||
|
Address to which requests are to return data.
|
||||||||||||||
|
||||||||||||||
|
Reference to a GROUP OF LINEs to which journey belongs.
|
||||||||||||||
|
Datex 2 model of where event ois taking place on the road.
|
||||||||||||||
Guaranteed (type xsd:boolean) |
Whether the SERVICE JOURNEY INTERCHANGE is guaranteed.
|
|||||||||||||
|
Whether change threshold can be specified for updates.
|
||||||||||||||
|
Whether the service supports Delivery confirm.
|
||||||||||||||
HasDetailLevel (type xsd:boolean) |
|
|||||||||||||
|
Whether result supports facility location information.
|
||||||||||||||
|
Whether the service has a heartbeat message.
|
||||||||||||||
HasIncrementalUpdates (type xsd:boolean) |
|
|||||||||||||
|
Whether result supports LINE events.
|
||||||||||||||
|
Whether result has location.
|
||||||||||||||
|
Whether a maximum number of Facility Status to include can be specified.
|
||||||||||||||
|
If system can return detailed calling pattern, whether a number of calls to include can be specified.
|
||||||||||||||
|
Whether a maximum number ofSITUATIONS to include can be specified.
|
||||||||||||||
|
Whether results can be limited to a maximum number.
|
||||||||||||||
|
Whether results can be limited to a maximum number.
|
||||||||||||||
|
Whether results can be limited to include a minimum number per LINE.
|
||||||||||||||
|
Whether results can be limited to include a minimum numVIA (i.e. per JOURNEY PATTERN).
|
||||||||||||||
HasNames (type xsd:boolean) |
Whether results should return references.
|
|||||||||||||
HasNumberOfOnwardsCalls (type xsd:boolean) |
|
|||||||||||||
HasNumberOfPreviousCalls (type xsd:boolean) |
|
|||||||||||||
HasReferences (type xsd:boolean) |
Whether results should return references.
|
|||||||||||||
|
Whether result supports remedy information.
|
||||||||||||||
HasSituations (type xsd:boolean) |
|
|||||||||||||
HeadwayService (type xsd:boolean) |
|
|||||||||||||
|
Interval for heartbeat.
|
||||||||||||||
|
Notification from Producer to Consumer to indicate that the service is running normally.
|
||||||||||||||
HigherTimeLimit (type xsd:dateTime) |
Upper bound on time of for predictios for confidence level if different from defaults +SIRI v2.0
|
|||||||||||||
|
Classification of Hire Facility.
|
||||||||||||||
|
Holiday type for monitoring availability.
|
||||||||||||||
HomePage (type xsd:boolean) |
|
|||||||||||||
Icon (type xsd:anyURI) |
|
|||||||||||||
|
Image description.
|
||||||||||||||
|
Image to use when presenting hyperlink.
|
||||||||||||||
ImageBinary (type xsd:base64Binary) |
Embedded image.
|
|||||||||||||
|
Categorisation of image content.
|
||||||||||||||
ImageRef (type xsd:anyURI) |
Reference to an image.
|
|||||||||||||
|
Any images associated with SITUATION.
|
||||||||||||||
|
Impact of Road SITUATION as specified by Datex2.
|
||||||||||||||
|
Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE.
|
||||||||||||||
Incidents (type xsd:boolean) |
|
|||||||||||||
|
Only incidents that are currently within their publication window shouldbe included.
|
||||||||||||||
IncludeSituations (type xsd:boolean) |
|
|||||||||||||
|
Whether additional translations of text names are to be included in elements.
|
||||||||||||||
|
||||||||||||||
IncrementalUpdates (type xsd:boolean) |
|
|||||||||||||
|
Info Channel supported by Producer service.
|
||||||||||||||
|
Identifier of classification.
|
||||||||||||||
|
Returns the Info Channels covered by a service.
|
||||||||||||||
|
Participant's permission for this InfoChannel.
|
||||||||||||||
|
The monitoring points that the participant may access.
|
||||||||||||||
|
||||||||||||||
|
Requests a list of the Info Channels covered by a Producer.
|
||||||||||||||
|
Hyperlink description.
|
||||||||||||||
|
Hyperlinks to other resources associated with SITUATION.
|
||||||||||||||
|
||||||||||||||
|
Optional version number of update to previosu message.
|
||||||||||||||
InitialTerminationTime (type xsd:dateTime) |
Requested end time for subscription.
|
|||||||||||||
|
||||||||||||||
|
Interaction capabilities.
|
||||||||||||||
|
||||||||||||||
|
Reference to a SERVCIE JOURNEY INTERCHANGE.
|
||||||||||||||
|
||||||||||||||
|
Status of a SERVICE JOURNEY INTERCHANGE Status TPEG cross reference pti31.
|
||||||||||||||
|
Name of other Connecting STOP POINT of a connection.
|
||||||||||||||
|
Identifier of STOP POINT of a stop at which VEHICLE JOURNEY meets for interchange If blank, same stop as destination.
|
||||||||||||||
|
Further advice to passengers.
|
||||||||||||||
|
Intervals before validity start date to send reminders.
|
||||||||||||||
|
Error: Request contains references to identifiers that are not known.
|
||||||||||||||
|
Invalid reference values encoountered.
|
||||||||||||||
|
Internet protocol address of the VEHICLE in form 000.000.000.000
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
enum Status of service for this Vehicle Journey - TPEG value.
|
||||||||||||||
|
Name of journey affected by a SITUATION.
|
||||||||||||||
|
Additional descriptive text associated with journey.
|
||||||||||||||
|
||||||||||||||
|
Refrence to a JOURNEY part.
|
||||||||||||||
|
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.
|
||||||||||||||
|
JOURNEY PARTs making up JOURNEY +SIRIv2.0 e.
|
||||||||||||||
|
JourneyPattern.
|
||||||||||||||
|
Name of Joruney Pattern
|
||||||||||||||
|
Reference to a JOURNEY PATTERN.
|
||||||||||||||
|
Identifier of JOURNEY PATTERN that journey follows.
|
||||||||||||||
|
JourneyPatterns in Direction of route (+SIRI 2.0)
|
||||||||||||||
|
Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs.
|
||||||||||||||
|
User key.
|
||||||||||||||
Keywords (type xsd:NMTOKENS) |
|
|||||||||||||
|
Label for Link.
|
||||||||||||||
Language (type xsd:boolean) |
Preferred language in which to return text values.
|
|||||||||||||
Language (type xsd:language) |
||||||||||||||
Language (type xsd:NMTOKEN) |
Default language.
|
|||||||||||||
|
||||||||||||||
|
Latest time at which a VEHICLE will arrive at stop.
|
||||||||||||||
|
||||||||||||||
|
Likellihoo of a future sutuation happening.
|
||||||||||||||
|
Limitation of facility.
|
||||||||||||||
|
||||||||||||||
|
Reference to line for which details are to be returned (v2.0)
|
||||||||||||||
|
Name of LINE.
|
||||||||||||||
|
Name space for LINE names and DIRECTIONss.
|
||||||||||||||
|
Additional Text associated with LINE.
|
||||||||||||||
|
Special text associated with LINE.
|
||||||||||||||
|
Participant's permission for this LINE.
|
||||||||||||||
|
The LINEs that the participant may access.
|
||||||||||||||
|
Reference to a LINE.
|
||||||||||||||
|
LINEs that use stop.
|
||||||||||||||
|
Filter the results to include only VEHICLEs along the given LINEs.
|
||||||||||||||
|
Filter the results to include only vehicles along the given LINEs.
|
||||||||||||||
|
Filter the results to include only situations along the given LINEs.
|
||||||||||||||
|
Returns the LINEs covered by a web service.
|
||||||||||||||
|
Level of detail to include in response.
|
||||||||||||||
|
Requests a list of the LINEs covered by a Producer.
|
||||||||||||||
|
Categorisation of link content.
|
||||||||||||||
|
Description of a DIRECTION of CONNECTION link.
|
||||||||||||||
|
The total distance in metres between the previous stop and the next stop.
|
||||||||||||||
|
Description of Link.
|
||||||||||||||
|
GIs projection of Section.
|
||||||||||||||
|
||||||||||||||
|
Identifier of CONNECTION link.
|
||||||||||||||
|
||||||||||||||
LocationRecordedAtTime (type xsd:dateTime) |
Time at which location was recorded.
|
|||||||||||||
|
||||||||||||||
|
A geospatial point.
|
||||||||||||||
LowerTimeLimit (type xsd:dateTime) |
Lower bound on time of for prediction for confidence level if different from defaults +SIRI v2.0
|
|||||||||||||
|
Classification of Luggage Facility type - Tpeg pti23.
|
||||||||||||||
|
||||||||||||||
|
Address to which subscription requests are to be sent.
|
||||||||||||||
|
Action: Publish SITUATION Manually. i.e. a procedure must be carried out.
|
||||||||||||||
|
Maximum Number of subscriptions that can be sustained by the subscriber.
|
||||||||||||||
MaximumAutomaticWaitTime (type xsd:duration) |
Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE.
|
|||||||||||||
|
If calls are to be returned, maximum number of calls to include in response.
|
||||||||||||||
|
If calls are to be returned, maximum number of calls to include in response.
|
||||||||||||||
|
The maximum number of facility status in a given delivery.
|
||||||||||||||
|
The maximum number of SITUATION elements to return in a given delivery.
|
||||||||||||||
MaximumStopVisits (type xsd:nonNegativeInteger) |
The maximum number of Stop Visits to include in a given delivery.
|
|||||||||||||
MaximumTextLength (type xsd:positiveInteger) |
Maximum length of text to return for text elements.
|
|||||||||||||
MaximumTransferTime (type xsd:duration) |
Maximum transfer duration for INTERCHANGE.
|
|||||||||||||
|
The maximum number of MONITORED VEHICLE JOURNEYs to include in a given delivery.
|
||||||||||||||
MaximumWaitTime (type xsd:duration) |
Maximum time that Distributor will wait for Feeder for INTERCHANGE.
|
|||||||||||||
|
||||||||||||||
|
Reference to an arbitrary unique reference associated with the request which gave rise to this response.
|
||||||||||||||
|
TPEG pti04 Metro submodes.
|
||||||||||||||
MinimumStopVisitsPerLine (type xsd:nonNegativeInteger) |
The minimum number of Stop Visits for a given LINE to include in a given delivery.
|
|||||||||||||
MinimumStopVisitsPerLineVia (type xsd:nonNegativeInteger) |
The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery.
|
|||||||||||||
MinimumTransferTime (type xsd:duration) |
Minimum transfer duration for INTERCHANGE.
|
|||||||||||||
|
TPEG Pti18_1/TPEG Pti_19 miscellaneous event reason.
|
||||||||||||||
|
Additional refinements TPEG miscellaneous event reason.
|
||||||||||||||
|
Effect of change on impaired access users.
|
||||||||||||||
|
Classification of Mobility Facility type - Tpeg pti23.
|
||||||||||||||
|
Whether stop or service is accessible to mobility impaired users.
|
||||||||||||||
|
Mode affected by SITUATION.
|
||||||||||||||
|
A method of transportation such as bus, rail, etc.
|
||||||||||||||
Monitored (type xsd:boolean) |
|
|||||||||||||
|
Monitored CALL at the current stop.
|
||||||||||||||
|
A feeder arrival at the connection point.
|
||||||||||||||
|
A feeder arrival at the connection point.
|
||||||||||||||
|
Cancellation of a feeder arrival at a connection point.
|
||||||||||||||
|
Cancellation of a feeder arrival at a connection point.
|
||||||||||||||
|
A visit to a stop by a VEHICLE as an arrival and /or departure.
|
||||||||||||||
|
Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop.
|
||||||||||||||
|
Provides real-time information about the VEHICLE JOURNEY along which a VEHICLE is running.
|
||||||||||||||
|
Monitored VEHICLE JOURNEY that VEHICLE is following.
|
||||||||||||||
MonitoringError (type xsd:NMTOKENS) |
Condition indicating nature of real-time fault.
|
|||||||||||||
|
Description of the mechanism used to monitor the change of the facility status.
|
||||||||||||||
|
Mean time interval between two measurements.
|
||||||||||||||
|
||||||||||||||
|
When the monitoring is in effect.
|
||||||||||||||
|
||||||||||||||
|
How monitoring is automatic, manual, etc..
|
||||||||||||||
MoreData (type xsd:boolean) |
|
|||||||||||||
MultipartDespatch (type xsd:boolean) |
|
|||||||||||||
|
Whether the service supports multiple Subscriber Filters.
|
||||||||||||||
|
Name of action data Element.
|
||||||||||||||
|
||||||||||||||
NationalLanguage (type xsd:language) |
National languages supported by service.
|
|||||||||||||
|
||||||||||||||
|
Default Network of affected LINEs.
|
||||||||||||||
|
Default context for common properties of Public Transport SITUATIONs.
|
||||||||||||||
|
||||||||||||||
|
Network of affected LINE.
|
||||||||||||||
|
||||||||||||||
|
Networks affected by SITUATION.
|
||||||||||||||
|
||||||||||||||
|
Error: Valid request was made but service does not hold any data for the requested topic. expression.
|
||||||||||||||
|
Ccomments not for public use.
|
||||||||||||||
|
||||||||||||||
|
Text explanation of service exception.
|
||||||||||||||
|
Reference to a specific notification message for which data is to be fetched.
|
||||||||||||||
|
Address to which notifcations requests are to be sent.
|
||||||||||||||
|
Action: Publish SITUATION to a named workgroup or individual by email.
|
||||||||||||||
|
Action: Publish SITUATION To pager.
|
||||||||||||||
|
Action: Publish SITUATION to an individual by SMS.
|
||||||||||||||
|
Action: Publish SITUATION To User.
|
||||||||||||||
|
Classification of Nuisance Facility type - Tpeg pti23.
|
||||||||||||||
|
Total number of BLOCK parts making up the train of which this is part.
|
||||||||||||||
|
Number of fatalities.
|
||||||||||||||
|
Number of injured presons.
|
||||||||||||||
NumberOfStopsAway (type xsd:nonNegativeInteger) |
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track.
|
|||||||||||||
NumberOfTransferPassengers (type xsd:nonNegativeInteger) |
|
|||||||||||||
|
Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Include onboard displays.
|
||||||||||||||
|
Include in SITUATION lists on station displays.
|
||||||||||||||
|
||||||||||||||
|
Information on CALLs at the intermediate stops beyond the current stop, up to and including the destination, in order of visits.
|
||||||||||||||
|
Plot of points from this stop to next Stop.
|
||||||||||||||
Onwards (type xsd:nonNegativeInteger) |
|
|||||||||||||
|
OPERATIONAL UNIT responsible for managing services.
|
||||||||||||||
|
OPERATIONAL UNIT responsible for managing services.
|
||||||||||||||
|
Contact details for use by operational staff.
|
||||||||||||||
|
OPERATOR of LINE affected by SITUATION.
|
||||||||||||||
|
Default OPERATOR for SITUATIONs.
|
||||||||||||||
|
Public Name of OPERATOR.
|
||||||||||||||
|
Participant's permission for this OPERATOR.
|
||||||||||||||
|
The OPERATOR data that the participant may access.
|
||||||||||||||
|
Affected OPERATORs, If absent, taken from context.
|
||||||||||||||
|
Short Name for OPERATOR.
|
||||||||||||||
|
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.
|
||||||||||||||
Order (type xsd:positiveInteger) |
|
|||||||||||||
|
Origin of the VEHICLE JOURNEY.
|
||||||||||||||
OriginAimedDepartureTime (type xsd:dateTime) |
|
|||||||||||||
|
||||||||||||||
|
||||||||||||||
|
The name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards.
|
||||||||||||||
|
Name of the origin of the journey.
|
||||||||||||||
|
Reference to the origin SCHEDULED STOP POINT of the journey.
|
||||||||||||||
|
The origin is used to help identify the VEHICLE JOURNEY.
|
||||||||||||||
|
Origin SCHEDULED STOP POINTs from which the LINE runs.
|
||||||||||||||
|
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards.
|
||||||||||||||
|
Other information about source.
|
||||||||||||||
|
Error: Error type other than the well defined codes.
|
||||||||||||||
|
Textual description of the owner of the facility.
|
||||||||||||||
|
Refererence to identifier of owner of facility.
|
||||||||||||||
|
Pager number of pager to be notfied.
|
||||||||||||||
|
Reference to a pager group to be notfied.
|
||||||||||||||
|
Name of the unsupported parameter.
|
||||||||||||||
|
Error: Request contained parameters that were not supported by the producer.
|
||||||||||||||
|
Classification of Access Facility.
|
||||||||||||||
ParticipantPermissions (type xsd:boolean) |
Whether to include the requestors permissions in the response.
|
|||||||||||||
|
||||||||||||||
|
Classification of PassengerComms Facility type - Tpeg pti23.
|
||||||||||||||
|
Classification of PassengerInfo Facility type - Tpeg pti23.
|
||||||||||||||
|
Percentage along link that VEHICLE has travelled.
|
||||||||||||||
Percentile (type xsd:decimal) |
Percentile associated with range as specified by lower and upper bound +SIRI v2.0
|
|||||||||||||
|
||||||||||||||
|
Version of permission set.
|
||||||||||||||
|
TPEG Pti18_2/TPEG Pti_20 personnel event reason.
|
||||||||||||||
|
Additional refinements TPEG Personnelevent reason.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Category of TOPGRAPHIC PLACE or SITE.
|
||||||||||||||
|
Names of place used to help identify the LINE.
|
||||||||||||||
|
||||||||||||||
|
Reference to a TOPOGRAPHIC PLACE.
|
||||||||||||||
PlaceRef (type xsd:NMTOKEN) |
|
|||||||||||||
PlaceRef (type xsd:normalizedString) |
|
|||||||||||||
|
Refernce to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code).
|
||||||||||||||
|
Places other than STOP POINTs affected by SITUATION.
|
||||||||||||||
|
Short name of TOPOGRAPHIC PLACE.
|
||||||||||||||
Planned (type xsd:boolean) |
Whether the SITUATION was planned (eg engineering works) or unplanned (eg service alteration).
|
|||||||||||||
|
For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform.
|
||||||||||||||
|
A geospatial point.
|
||||||||||||||
|
Description of position of Train BLOCK Part within Train to guide passengers where to find it.
|
||||||||||||||
|
Precision for point measurement.
|
||||||||||||||
|
Classification of Predictability status.
|
||||||||||||||
|
Whether just planned, unplanned or both SITUATIONs will be returned.
|
||||||||||||||
|
Name of prediction method used.
|
||||||||||||||
PredictionInaccurate (type xsd:boolean) |
|
|||||||||||||
|
An approxiimate characterisation of prediction quality as one of five values .
|
||||||||||||||
|
Whether content is flagged as subject to premium charge.
|
||||||||||||||
|
Relative priority for incliding via in displays. 1 Is high 3 is low.
|
||||||||||||||
|
||||||||||||||
Previous (type xsd:nonNegativeInteger) |
|
|||||||||||||
|
||||||||||||||
|
Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits.
|
||||||||||||||
Priority (type xsd:nonNegativeInteger) |
Arbitrary rating of priority 1-High.
|
|||||||||||||
|
Alternative identifier of SITE or TOPOGRAPHIC PLACE
|
||||||||||||||
PrivateRef (type xsd:string) |
Alternative private code of stop.
|
|||||||||||||
|
An assessment of the degree of likelihood that the reported event will occur.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Returns the Product Categories covered by a service.
|
||||||||||||||
|
Requests a list of the Product Categories covered by a Producer.
|
||||||||||||||
|
Category for classification of a journey as a Product
|
||||||||||||||
|
Identifier of TYPE OF PRODUCT CATEGORY classification.
|
||||||||||||||
|
Name space for Product Categories.
|
||||||||||||||
|
Product Classification of VEHICLE JOURNEY- subdivides a transport mode. e.g. express, loacl.
|
||||||||||||||
|
Request for information about ProductionTimetable Service Capabilities.
|
||||||||||||||
|
Capabilities for ProductionTimetable Service.
|
||||||||||||||
|
Delivery for Production Timetable Service.
|
||||||||||||||
|
Permission for a single participant or all participants to use an aspect of the service.
|
||||||||||||||
|
Participant's permissions to use the service.
|
||||||||||||||
|
Request for daily production timetables.
|
||||||||||||||
|
Capabilities of ProductionTimetableService.
|
||||||||||||||
|
Request for a subscription to the Production Timetable Service.
|
||||||||||||||
|
Workflow Progress Status.
|
||||||||||||||
|
ProgressStatus.
|
||||||||||||||
|
Provides information about the progress of the VEHICLE along its current link, that is link from previous visited top to current position.
|
||||||||||||||
|
Rate of progress of VEHICLE.
|
||||||||||||||
|
An arbitrary textual status description of the running of this VEHICLE JOURNEY.
|
||||||||||||||
|
Display prompt for presenting action to user.
|
||||||||||||||
ProvisionalExpectedDepartureTime (type xsd:dateTime) |
|
|||||||||||||
|
Default context for common properties of SITUATIONs, Values specified apply to all SITUATIONs unless overridden.
|
||||||||||||||
|
Type for individual IPT ncident.
|
||||||||||||||
|
Description of a SITUATION.
|
||||||||||||||
|
Publishing status one of a specified set of substates to which a SITUATION can be assigned.
|
||||||||||||||
|
Publication Window for SITUATION if different from validity period.
|
||||||||||||||
|
Contact details for use by members of public.
|
||||||||||||||
|
Classifier of Pub;ic Event.
|
||||||||||||||
|
Name or Number by which the LINEis known to the public.
|
||||||||||||||
|
Name or Number by which the LINE is known to the public.
|
||||||||||||||
|
||||||||||||||
PublishSubscribe (type xsd:boolean) |
|
|||||||||||||
|
Action: Publish SITUATION To Alert Service.
|
||||||||||||||
|
Action: Publish SITUATION To Displays.
|
||||||||||||||
|
Action: Publish SITUATION To WAP and PDA.
|
||||||||||||||
|
Action: Publish SITUATION To TvService.
|
||||||||||||||
|
Action: Publish SITUATION To Web.
|
||||||||||||||
|
Assessement of likely correctness of data.
|
||||||||||||||
|
Radio address of the VEHICLE
|
||||||||||||||
|
TPEG pti02 Rail submodes loc13.
|
||||||||||||||
|
Whether SITUATION is real or a test.
|
||||||||||||||
|
Whether SITUATION is real or a test.
|
||||||||||||||
|
Whether information about parts of the network identified by Affects should be blocked from real-time departureinfo systems.
|
||||||||||||||
|
Reason.
|
||||||||||||||
|
||||||||||||||
|
Text explanation of SITUATION reason.
|
||||||||||||||
RecordedAtTime (type xsd:dateTime) |
|
|||||||||||||
|
Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered.
|
||||||||||||||
|
Observed call tmes for that art of teh journey that has already been completed. (+ SIRI 2..0)
|
||||||||||||||
|
Road reference POINT identifier, unique on the specified road.
|
||||||||||||||
|
Associations with other SITUATIONs.
|
||||||||||||||
|
Classification of Refreshment Facility type - Tpeg pti23.
|
||||||||||||||
|
Relationship of refercence to the referncing SITUATION e.
|
||||||||||||||
|
A reference to another SITUATION with an indication of the nature of the association, e.g. a cause, a result, an update.
|
||||||||||||||
|
Setup action to remedy the change of the facility status (if partialy or totaly anavailable)
|
||||||||||||||
|
Type of the remedy (repair/replacement/remove)
|
||||||||||||||
|
situation applies only on the repeated day types within the overall validity period(s).
|
||||||||||||||
|
Scope of incident - Tpeg Report Type pti27.
|
||||||||||||||
RequestChecking (type xsd:boolean) |
Whether access control of requests is supported.
|
|||||||||||||
|
||||||||||||||
|
||||||||||||||
|
Reference to a requestor - Participant Code.
|
||||||||||||||
|
Request Policy capabilities.
|
||||||||||||||
|
Request Policy capabilities.
|
||||||||||||||
|
Request Policy capabilities.
|
||||||||||||||
|
Request Policy capabilities.
|
||||||||||||||
|
Request Policy capabilities.
|
||||||||||||||
|
Request Policy capabilities.
|
||||||||||||||
|
Request Policiy capabilities.
|
||||||||||||||
|
Request Policiy capabilities.
|
||||||||||||||
|
Request Policy capabilities.
|
||||||||||||||
|
Available Request Policy capabilities.
|
||||||||||||||
|
Available request policy options.
|
||||||||||||||
|
Request Policy capabilities.
|
||||||||||||||
RequestResponse (type xsd:boolean) |
|
|||||||||||||
RequestStop (type xsd:boolean) |
Whether Vehicle stops only if requested explicitly by passenger.
|
|||||||||||||
|
Timeout for requests.
|
||||||||||||||
|
Timestamp on request.
|
||||||||||||||
|
Classification of Reserved Space Facility.
|
||||||||||||||
|
Participant reference that identifies responder.
|
||||||||||||||
|
Optional Response capabilities.
|
||||||||||||||
|
Optional Response capabilities.
|
||||||||||||||
|
Available Optional Response capabilities.
|
||||||||||||||
|
Optional Response capabilities.
|
||||||||||||||
|
An arbitrary unique reference associated with the response which may be used to reference it.
|
||||||||||||||
|
Contains infromation about the processing of a an individual service subscription - either success info or an error condition.
|
||||||||||||||
|
Time individual response element was created.
|
||||||||||||||
|
Classification of Retail Facility.
|
||||||||||||||
|
Whether VEHICLE will reverse at stop.
|
||||||||||||||
|
AFfected Road as described by a Date2x location.
|
||||||||||||||
|
||||||||||||||
|
Identifier or number of the road on which the reference POINT is located.
|
||||||||||||||
|
Roads affected by.
|
||||||||||||||
|
Type for individual IPT ncident.
|
||||||||||||||
|
ROUTE affected by the SITUATION.
|
||||||||||||||
|
||||||||||||||
|
ROUTE LINKs affected by SITUATION.
|
||||||||||||||
|
Description of route by which it can be recogniozed.
|
||||||||||||||
|
Route point type Tpeg Report Type pti15.
|
||||||||||||||
|
||||||||||||||
|
ROUTEs affected if LINE has multiple ROUTEs.
|
||||||||||||||
|
Textual description of overall routes affected.
|
||||||||||||||
|
Classification of Sanitary Facility type - Tpeg pti23.
|
||||||||||||||
|
Types of SITUATION to include.
|
||||||||||||||
|
Nature of scope, e.g. general, network.
|
||||||||||||||
|
additioanl reasons.
|
||||||||||||||
|
Reference to a section of ROUTE affected by a SITUATION.
|
||||||||||||||
|
Sections of ROUTE affected by SITUATION.
|
||||||||||||||
|
Sections of LINE affected.
|
||||||||||||||
|
Only some ROUTEs are affected, LINE level information not available.
|
||||||||||||||
|
TPEG pti12 SelfDrive submodes.
|
||||||||||||||
|
Confidentiality of SITUATION.
|
||||||||||||||
|
Response from Producer to Consumer to deliver payload data.
|
||||||||||||||
|
Response from Producer to Consumer to deliver payload data.
|
||||||||||||||
|
Element fror an erroc condition for use in WSDL.
|
||||||||||||||
|
Exceptions to service availability for all or some services SIRI 2.0
|
||||||||||||||
|
Service Feature description.
|
||||||||||||||
|
Description of Service features of stop.
|
||||||||||||||
|
Identifier of classification.
|
||||||||||||||
|
Name space for service features.
|
||||||||||||||
|
Classification of service into arbitrary Service categories, e.g. school bus.
|
||||||||||||||
|
Returns the SERVICE FEATUREs covered by a service.
|
||||||||||||||
|
Requests a list of the Service Features covered by a Producer.
|
||||||||||||||
|
Connection paramters for a SERVICE JOURNEY INTERCHANGE between a feeder and distributor journey.
|
||||||||||||||
|
Error: Functional service is not available to use (but it is still capable of giving this response).
|
||||||||||||||
|
Request from Consumer to Producer for immediate delivery of data.
|
||||||||||||||
|
Request from Consumer to Producer for immediate delivery of data.
|
||||||||||||||
|
General request properties - typically configured rather than repeated on request.
|
||||||||||||||
ServiceStartedTime (type xsd:dateTime) |
|
|||||||||||||
|
Status of service, Service not yet started, Service ended for day, no service today, etc.
|
||||||||||||||
|
Severity of Incident.
|
||||||||||||||
|
Severity of disruption if different from that of SITUATION.
|
||||||||||||||
|
Severity filter value to apply: only SITUATIONs with a severity greater than or equal to the specified value will be returned.
|
||||||||||||||
|
Minimum interval at which updates can be sent.
|
||||||||||||||
|
Status of signal clearance for TRAIN.
|
||||||||||||||
|
SIRI Service Interface for Real-time Operation.
|
||||||||||||||
|
Service Interface for Real-time Operation.
|
||||||||||||||
|
Request for information about Situation Exchange Service Capabilities.
|
||||||||||||||
|
Capabilities for Situation Exchange Service.
|
||||||||||||||
|
Delivery for Situation Exchange Service.
|
||||||||||||||
|
||||||||||||||
|
Participant's permissions to use the service.
|
||||||||||||||
|
Request for information about Facilities status.
|
||||||||||||||
|
Capabilities of Situation Exchange Service.
|
||||||||||||||
|
Request for a subscription to the Situation Exchange Service.
|
||||||||||||||
|
Reference to a SITUATION.
|
||||||||||||||
|
Identifier of SITUATION within a Participant.
|
||||||||||||||
|
Datex2 SITUATION Record.
|
||||||||||||||
|
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.
|
||||||||||||||
|
The date/time that the SITUATIONRecord object (the first version of the record) was created by the original supplier.
|
||||||||||||||
|
||||||||||||||
|
The date/time that the current version of the SITUATION Record was written into the database of the original supplier in the supply chain.
|
||||||||||||||
|
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.
|
||||||||||||||
|
Each record within a SITUATION may iterate through a series of versions during its life time.
|
||||||||||||||
|
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.
|
||||||||||||||
|
Reference to a SITUATION associated with the element.
|
||||||||||||||
|
Reference to a SITUATION providing further information about exception
|
||||||||||||||
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Road.
|
||||||||||||||
|
SITUATIONs in Delivery.
|
||||||||||||||
|
Reference to a SITUATION associated with the element.
|
||||||||||||||
|
Include in social NETWORK indicated by this name.
|
||||||||||||||
|
||||||||||||||
|
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.
|
||||||||||||||
|
Electronic file / attachment containing information about SITUATION.
|
||||||||||||||
|
Nature of method used to get Source.
|
||||||||||||||
|
Job title of Source.
|
||||||||||||||
|
Nature of Source.
|
||||||||||||||
|
GML Spatial coordinate reference system.
|
||||||||||||||
StandardTransferTime (type xsd:duration) |
Standard transfer duration for INTERCHANGE.
|
|||||||||||||
StandardWaitTime (type xsd:duration) |
Standard wait time for INTERCHANGE.
|
|||||||||||||
|
Identifier of stop point at which availability first applies.
|
||||||||||||||
|
||||||||||||||
StartTime (type xsd:dateTime) |
|
|||||||||||||
|
Whether the request was processed successfully or not.
|
||||||||||||||
|
Status of the facility.
|
||||||||||||||
Status (type xsd:boolean) |
Whether the complerte request could be processed successfully or not.
|
|||||||||||||
|
Address to which CheckStatus responses and heartbeats are to be sent.
|
||||||||||||||
StaySeated (type xsd:boolean) |
Whether the passenger can remain in VEHICLE (i.e.
|
|||||||||||||
|
Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs.
|
||||||||||||||
|
Status of STOP
|
||||||||||||||
|
Facility associated with stop visit
|
||||||||||||||
|
LINE notice for stop.
|
||||||||||||||
|
Reference to an previously communicated LINE notice which should now be removed from the arrival/departure board for the stop.
|
||||||||||||||
|
Request for information about Stop Monitoring Service Capabilities.
|
||||||||||||||
|
Capabilities for Stop Monitoring Service.
|
||||||||||||||
|
Delivery for Stop Monitoring Service.
|
||||||||||||||
|
Level of detail to include in response.
|
||||||||||||||
|
Request particulars for an individual stop as part of a list of multiple= requests.
|
||||||||||||||
|
Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop.
|
||||||||||||||
|
Permission for a single participant or all participants to use an aspect of the service.
|
||||||||||||||
|
Participants permissions to use the service, Only returned if requested.
|
||||||||||||||
|
Request for information about Stop Visits, i.e. arrivals and departures at a stop.
|
||||||||||||||
|
Capabilities of StopMonitoring Service.
|
||||||||||||||
|
Request for a subscription to Stop Monitoring Service.
|
||||||||||||||
|
||||||||||||||
|
The monitoring points that the participant may access.
|
||||||||||||||
|
The monitoring points that the participant may access.
|
||||||||||||||
|
Name of SCHEDULED STOP POINT.
|
||||||||||||||
|
Text associated with Stop Notice ed since SIRI 2.0)
|
||||||||||||||
|
Notice for stop.
|
||||||||||||||
|
Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop.
|
||||||||||||||
|
||||||||||||||
|
System identifier of Stop Place component.
|
||||||||||||||
|
Reference to a stop place component.
|
||||||||||||||
|
Reference to part of a STOP PLACE.
|
||||||||||||||
|
||||||||||||||
|
Places other than STOP POINTs affected by SITUATION.
|
||||||||||||||
|
Type of Stop Place.
|
||||||||||||||
|
Stop within Route of LINE.
|
||||||||||||||
|
Name of SCHEDULED STOP POINT.
|
||||||||||||||
|
||||||||||||||
|
Name space for STOP POINTs.
|
||||||||||||||
|
Reference to a SCHEDULED STOP POINT.
|
||||||||||||||
|
||||||||||||||
|
Stop Poins of the ROUTE.
|
||||||||||||||
|
STOP POINTs affected by SITUATION.
|
||||||||||||||
|
Returns basic details about the STOP POINTs/places covered by a service.
|
||||||||||||||
|
Level of detail to include in response.
|
||||||||||||||
|
Requests a list of the STOP POINTs and places covered by a Producer.
|
||||||||||||||
|
STOP POINT type Tpeg Report Type pti17.
|
||||||||||||||
|
Type of stop type.
|
||||||||||||||
|
Ordered collection of STOP POINTs the LINE and direction .
|
||||||||||||||
|
Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse.
|
||||||||||||||
|
Delivery for Stop Timetable Service.
|
||||||||||||||
|
Delivery for Stop Timetable Service.
|
||||||||||||||
|
Permission for a single participant or all participants to use an aspect of the service.
|
||||||||||||||
|
Participant's permissions to use the service.
|
||||||||||||||
|
Request for information about Stop Visits, i.e. arrival and departure at a stop.
|
||||||||||||||
|
Capabilities of Stop Timetable Service.
|
||||||||||||||
|
Request for a subscription to Stop TimetablesService.
|
||||||||||||||
|
Text associated with Stop Visit.
|
||||||||||||||
|
Whether to include arrival Visits, departure Visits, or all.
|
||||||||||||||
|
Address to which subscription requests are to be sent.
|
||||||||||||||
|
Address to which subscription responses are to be sent.
|
||||||||||||||
|
||||||||||||||
|
Ubscription code that could not be found. + SIRI v2.0
|
||||||||||||||
|
General values that apply to subscription.
|
||||||||||||||
SubscriptionFilterIdentifier (type xsd:NMTOKEN) |
Reference to a Subscription Filter with which this subscription is to be aggregated for purposes of notification and delivery.
|
|||||||||||||
|
Unique identifier of Subscription filter to which this subscription is assigned.
|
||||||||||||||
|
Identifier to be given to Subscription.
|
||||||||||||||
|
||||||||||||||
|
Subscription Policy capabilities.
|
||||||||||||||
|
||||||||||||||
|
Request from Subscriber to Producer for a subscription.
|
||||||||||||||
|
Request from Subscriber to Producer for a subscription.
|
||||||||||||||
|
Response from Producer to Consumer to inform whether subscriptions have been created.
|
||||||||||||||
|
Notification from Subscriber to Subscription Manager to terminate a subscription.
|
||||||||||||||
SuggestedWaitDecisionTime (type xsd:dateTime) |
|
|||||||||||||
|
Effect on different passenger needs.
|
||||||||||||||
|
Suitabilities of facility for specific passenger needs.
|
||||||||||||||
|
||||||||||||||
|
Summary of SITUATION.
|
||||||||||||||
|
Information about the call at the stop.
|
||||||||||||||
|
Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes)
|
||||||||||||||
|
Timetabled VEHICLE JOURNEY.
|
||||||||||||||
|
TPEG pti11 Taxi submodes.
|
||||||||||||||
|
TPEG pti09 Telecabin submodes.
|
||||||||||||||
|
Publish to Ceefax.
|
||||||||||||||
|
Request from Subscriber to Subscription Manager to terminate a subscription.
|
||||||||||||||
|
Request from Subscriber to Subscription Manager to terminate a subscription.
|
||||||||||||||
|
Status of each subscription termnination response.
|
||||||||||||||
|
Include in moving ticker band.
|
||||||||||||||
|
Classification of Ticketing Facility type - Tpeg pti23.
|
||||||||||||||
|
Ticket restriction conditiosn in effect.
|
||||||||||||||
|
Ticket restrictions - Tpeg Report Type pti25.
|
||||||||||||||
|
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.).
|
||||||||||||||
|
Time of communication of message, if different from creation time.
|
||||||||||||||
|
||||||||||||||
|
A feeder arrival at the arrival SCHEDUELD STOP POINT of the CONNECTION link .
|
||||||||||||||
|
A feeder arrival at the arrival SCHEDUELD STOP POINT of the CONNECTION link .
|
||||||||||||||
|
Cancellation of a previously issued Feeder Arrival.
|
||||||||||||||
|
Cancellation of a previously issued Feeder Arrival.
|
||||||||||||||
|
A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable.
|
||||||||||||||
|
A cancellation of a previously issued TimetabledStopVisit.
|
||||||||||||||
|
Timetable type - Tpeg pti33.
|
||||||||||||||
|
||||||||||||||
|
Whether the stop is a TIMING POINT.
|
||||||||||||||
|
Filtering Capabilities.
|
||||||||||||||
|
Filtering Capabilities.
|
||||||||||||||
|
Filtering Capabilities.
|
||||||||||||||
|
Filtering Capabilities.
|
||||||||||||||
|
Filtering Capabilities.
|
||||||||||||||
|
Filtering Capabilities.
|
||||||||||||||
|
Filtering Capabilities.
|
||||||||||||||
|
Filtering Capabilities.
|
||||||||||||||
|
Filtering Capabilities.
|
||||||||||||||
|
Available Filtering Capabilities.
|
||||||||||||||
|
Available Filtering Capabilities.
|
||||||||||||||
|
Topic Filtering Capabilities.
|
||||||||||||||
|
Name of locality in which SITUATIONs apply.
|
||||||||||||||
|
Refrence to a TOPOGRAPHIC PLACE (locality).
|
||||||||||||||
|
Information on any planned distributor connections.
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
TRAIN NUMBERs for journey.
|
||||||||||||||
|
TRAIN NUMBERs for journey.
|
||||||||||||||
|
Reference to a train BLOCK part.
|
||||||||||||||
|
TPEG pti06 Tram submodes.
|
||||||||||||||
Translations (type xsd:boolean) |
Whether producer can provide multiple translations of NL text elements +SIRI 2.0
|
|||||||||||||
|
Implementation properties common to all request types.
|
||||||||||||||
|
Data type of action data.
|
||||||||||||||
|
Error:Recipient of a message to be distributed is not available.
|
||||||||||||||
|
TPEG Pti18_255/TPEG Pti_22 undefined event reason.
|
||||||||||||||
|
Error: Recipient for a message to be distributed is unknown.
|
||||||||||||||
|
Error: Request contained extensions that were not supported by the producer.
|
||||||||||||||
|
Error: Recipient for a message to be distributed is unknown.
|
||||||||||||||
|
TPEG Pti18_0/TPEG unknown event reason.
|
||||||||||||||
|
Error: Subscriber not found.
|
||||||||||||||
|
Error: Subscription not found.
|
||||||||||||||
|
Unique identifier of a Country of a Participant who created Update SITUATION element.
|
||||||||||||||
|
Time interval in seconds in which new data is to be transmitted.
|
||||||||||||||
|
Unique identifier of a Participant.
|
||||||||||||||
|
A geospatial point.
|
||||||||||||||
|
URI for link.
|
||||||||||||||
Url (type xsd:anyURI) |
|
|||||||||||||
UseNames (type xsd:boolean) |
|
|||||||||||||
UseReferences (type xsd:boolean) |
|
|||||||||||||
|
Name of user to be notified.
|
||||||||||||||
|
User need to be monitored.
|
||||||||||||||
|
Reference to a user to be notified.
|
||||||||||||||
|
||||||||||||||
|
When Facility is normally avaialble.
|
||||||||||||||
|
Start and end of timetable validity (time window) of journeys for which schedules are to be returned.
|
||||||||||||||
|
Temporal scope of Situations be included in response.
|
||||||||||||||
|
||||||||||||||
ValidUntil (type xsd:dateTime) |
End of data horizon of the data producer.
|
|||||||||||||
ValidUntilTime (type xsd:dateTime) |
|
|||||||||||||
|
Value for action.
|
||||||||||||||
|
Classification of DELIVERY VARIANT +SIRI v2.0.
|
||||||||||||||
|
Describes the progress of a VEHICLE along its route.
|
||||||||||||||
|
Reference to an previously communicated VEHICLE activity which should now be removed from the system.
|
||||||||||||||
|
||||||||||||||
|
Whether VEHICLE is currently at stop.
|
||||||||||||||
|
Vehicle Feature description.
|
||||||||||||||
|
Identifier of feature of VEHICLE.
|
||||||||||||||
|
Name space for VEHICLE features.
|
||||||||||||||
|
Features of VEHICLE providing journey.
|
||||||||||||||
|
Returns the Vehicle Features covered by a service.
|
||||||||||||||
|
Requests a list of the Vehicle Features covered by a Producer.
|
||||||||||||||
|
For train services with named journeys.
|
||||||||||||||
|
Reference to a VEHICLE JOURNEY.
|
||||||||||||||
|
Reference to a service VEHICLE JOURNEY affected by a SITUATION.
|
||||||||||||||
|
||||||||||||||
|
Specific journeys affected by SITUATION.
|
||||||||||||||
|
Current geospatial location of VEHICLE.
|
||||||||||||||
|
Exact location that VEHICLE will take up / or has taken at STOP POINT.
|
||||||||||||||
|
Vehicle mode- Tpeg ModeType pti1.
|
||||||||||||||
|
A means of transportation such as bus, rail, etc.
|
||||||||||||||
|
Request for information about Vehicle Monitoring Service Capabilities.
|
||||||||||||||
|
Capabilities for Vehicle Monitoring Service.
|
||||||||||||||
|
Delivery for Vehicle Monitoring Service.
|
||||||||||||||
|
Level of detail to include in response.
|
||||||||||||||
|
Permissions for use of VEHICLE MONITORING.
|
||||||||||||||
|
Participant's permissions to use the service.
|
||||||||||||||
|
The Vehicle Monitors (DIUSPLAY ASSIGNMENTs) that the participant may access.
|
||||||||||||||
|
||||||||||||||
|
Request for information about Vehicle Movements.
|
||||||||||||||
|
Capabilities of Vehicle Monitoring Service.
|
||||||||||||||
|
Request for a subscription to the Vehicle Monitoring Service.
|
||||||||||||||
|
Participant's permission for this Vehicle Monitor (DISPLAY SSIGNMENT).
|
||||||||||||||
|
Reference to a VEHICLE.
|
||||||||||||||
|
||||||||||||||
|
Registration plate of VEHICLE
|
||||||||||||||
|
Specific vehicles affected by SITUATION.
|
||||||||||||||
|
An classification of the progress state of running of this VEHICLE JOURNEY.
|
||||||||||||||
|
Velocity of VEHICLE.
|
||||||||||||||
|
Units for Distance Type.
|
||||||||||||||
|
Whether the SITUATION has been verified.
|
||||||||||||||
|
Whether incident has been verified or not If not specified return all.
|
||||||||||||||
|
Classification of verification status TPEG Pti13 Service Condition values.
|
||||||||||||||
|
Unique identifier of update version within a SITUATION Number Omit if reference to the base SITUATION.
|
||||||||||||||
|
Unique identifier of a Country of a Participant who created Update SITUATION element.
|
||||||||||||||
VersionedAtTime (type xsd:dateTime) |
Time at which SITUATION element was versioned.
|
|||||||||||||
|
Version Identifier.
|
||||||||||||||
|
Timetable Version.
|
||||||||||||||
|
VIA points for VEHICLE JOURNEY
|
||||||||||||||
|
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton.
|
||||||||||||||
|
Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton.
|
||||||||||||||
|
Relative priority to give to VIA name in displays. 1=high.
|
||||||||||||||
|
Reference to a SCHEDULED STOP POINT that is a VIA point on the journey.
|
||||||||||||||
|
Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY.
|
||||||||||||||
|
Whether VisitNumber can be used as a strict order number within JOURNEY PATTERN.
|
||||||||||||||
|
||||||||||||||
|
Time up until which the distributor will wait.
|
||||||||||||||
|
TPEG pti07 Water submodes.
|
||||||||||||||
|
Information was obtained from a web site URL of site and/or page.
|
||||||||||||||
|
||||||||||||||
|
Distributor will not wait (i.e. connection broken) SIRI w.0
|
||||||||||||||
|
Nature of wait that distributer will make.
|
||||||||||||||
|
Workgroup of user to be notified.
|
||||||||||||||
Complex Type Summary |
||||||||||||
|
Type for Abstract CALL at stop.
|
||||||||||||
|
Type for Capabilities of StopMonitopring Service.
|
||||||||||||
|
Abstract supertype fro discovery responses.
|
||||||||||||
|
Requests for stop reference data for use in service requests.
|
||||||||||||
|
Type for an SERVICE JOURNEY INTERCHANGE Activity.
|
||||||||||||
|
Type for an SERVICE JOURNEY INTERCHANGE Activity.
|
||||||||||||
|
Type for an SERVICE JOURNEY INTERCHANGE feeder Activity.
|
||||||||||||
|
Type for an SERVICE JOURNEY INTERCHANGE feeder Activity.
|
||||||||||||
|
Abstract Service Request for SIRI Service request.
|
||||||||||||
|
Type for an Activity that can be referenced.
|
||||||||||||
|
Type for an Activity.
|
||||||||||||
|
Type for Abstract CALL at stop.
|
||||||||||||
|
Type for Notification Request.
|
||||||||||||
|
Type for Abstract Permission.
|
||||||||||||
|
Type for an Activity that references a previous Activity.
|
||||||||||||
|
Type for General SIRI Request.
|
||||||||||||
|
Type for an Activity that can be referenced.
|
||||||||||||
|
Type for an Activity that references a previous Activity.
|
||||||||||||
|
Type for capabilities response.
|
||||||||||||
|
Type for Common elementd for a SIRI service delivery of the Form xxxDelivery.
|
||||||||||||
|
A planned SERVICE JOURNEY INTERCHANGE between two journeys.
|
||||||||||||
|
Abstract Service Request for SIRI Service request.
|
||||||||||||
|
Type for abstract EntryAbstract type.
|
||||||||||||
|
Type for COmmon Subscription Request.
|
||||||||||||
|
Type for SIRI Service subscriptions.
|
||||||||||||
|
Type for Abstract Permission Topic.
|
||||||||||||
|
Type for information about Accessibility Facilities status.
|
||||||||||||
|
Type forError:Access Not Allowed.
|
||||||||||||
|
Type for list of SITUATIONs.
|
||||||||||||
|
Type for list of actions.
|
||||||||||||
|
Type for reference to predefined advisory NOTICE.
|
||||||||||||
|
Type for information about a CALL affected by an SITUATION.
|
||||||||||||
|
Type for a reference Information about a CONNECTION link from a given stop that is affected by a SITUATION.
|
||||||||||||
|
Type for information about a FACILITY affected by an SITUATION.
|
||||||||||||
|
Information about a SERVICE JOURNEY INTERCHANGE at CONNECTION link from a given SCHEDULED STOP POINT.
|
||||||||||||
|
Type for information about the LINEs affected by a SITUATION.
|
||||||||||||
|
Type for TRANSPORT MODEs affecetd by a SITUATION.
|
||||||||||||
|
Type for information about the parts of the network affected by an incident.
|
||||||||||||
|
Type for Annotated reference to an OPERATOR affected by a SITUATION.
|
||||||||||||
|
Information about a CONNECTION link from a given stop affected by a SITUATION.
|
||||||||||||
|
Type for annotated references to a TOPOGRAPHIC PLACE.
|
||||||||||||
|
Type for Location model for scope of SITUATION or effect.
|
||||||||||||
|
Type for Raod scope for scope of SITUATION or effect.
|
||||||||||||
|
Type for information about the routes affected by a SITUATION.
|
||||||||||||
|
Type for information about the sectons affected by a SITUATION.
|
||||||||||||
|
Type for information about the quays affected by an SITUATION.
|
||||||||||||
|
Type for information about the quays affected by an SITUATION.
|
||||||||||||
|
Type for information about the Stop Places affected by an SITUATION.
|
||||||||||||
|
Type for an SCHEDUELD STOP POINT affected by a SITUATION.
|
||||||||||||
|
Type for information about a VEHICLE JOURNEY affected by a SITUATION.
|
||||||||||||
|
Type for information about a VEHICLE affected by an SITUATION.
|
||||||||||||
|
Type for Location model for scope of SITUATION or effect.
|
||||||||||||
|
Description of the features of any of the available facilities.
|
||||||||||||
|
Type for error.
|
||||||||||||
|
View of a SCHEDULED CONNECTION LINK description.
|
||||||||||||
|
Type for DESTINATION and place name.
|
||||||||||||
|
Summary information about Facility.
|
||||||||||||
|
Summary information about a LINE type.
|
||||||||||||
|
View of a SCHEDULED STOP POINT description.
|
||||||||||||
|
Type for Authticated SIRI Request.
|
||||||||||||
|
Type for error.
|
||||||||||||
|
Type for blocking.
|
||||||||||||
|
Type for reference to a BLOCK.
|
||||||||||||
|
Type for boarding restrictions.
|
||||||||||||
|
Defines a bounding box using two corner points.
|
||||||||||||
|
Type for Requests for capabilities of the current system.
|
||||||||||||
|
Type for Requests for capabilities of the current system.
|
||||||||||||
|
Type for the capabilities of an implementation.
|
||||||||||||
|
Type for the capabilities of an implementation.
|
||||||||||||
|
Type for Common Access control capabilities.
|
||||||||||||
|
Type for Common Request Policy capabilities.
|
||||||||||||
|
Type for Error: Service does not support requested capability.
|
||||||||||||
|
Type for capability ref.
|
||||||||||||
|
Type for Common Request Policy capabilities.
|
||||||||||||
|
Type for Common Subscription capabilities.
|
||||||||||||
|
Type for Information on casualties.
|
||||||||||||
|
Type for check status request.
|
||||||||||||
|
Type for Body of Service Status Check Response.
|
||||||||||||
|
Type for Service Status Check Response.
|
||||||||||||
|
Reference Cleardown identifier of a stop.
|
||||||||||||
|
Type for a range of times.
|
||||||||||||
|
Type for a range of date and times.
|
||||||||||||
|
Type for filter for connecting journeys.
|
||||||||||||
|
Type for filter for connecting journeys.
|
||||||||||||
|
Type for a reference to a connecting journey.
|
||||||||||||
|
Type for time filter for connecting journeys.
|
||||||||||||
|
Type for time filter for connecting journeys.
|
||||||||||||
|
Abstract type for capability access control.
|
||||||||||||
|
Type for CONNECTION link Permission.
|
||||||||||||
|
Type for reference to a CONNECTION link
|
||||||||||||
|
Response with CONNECTION LINKs available to make requests.
|
||||||||||||
|
Requests for CONNECTION LINK data for use in service requests.
|
||||||||||||
|
Type for Delivery for Connection Monitoring Capability.
|
||||||||||||
|
Type for Delivery for Connection Monitoring Capability.
|
||||||||||||
|
Type for Connection Monitoring Capability Request Policy.
|
||||||||||||
|
Type for Connection Monitoring Capability Request Policy.
|
||||||||||||
|
Type for Deliveries for Connection Monitoring Service.
|
||||||||||||
|
Type for Deliveries for Connection Monitoring Service.
|
||||||||||||
|
Type for Distributor Delivery for Connection Monitoring Service.
|
||||||||||||
|
Type for Distributor Delivery for Connection Monitoring Service.
|
||||||||||||
|
Type for Delivery for Connection Monitoring.
|
||||||||||||
|
Type for Delivery for Connection Monitoring.
|
||||||||||||
|
Type for Request Connection Monitoring Service.
|
||||||||||||
|
Type for Request Connection Monitoring Service.
|
||||||||||||
|
Type for Connection Monitoring Capabilities.
|
||||||||||||
|
Type for Connection Monitoring Capabilities.
|
||||||||||||
|
Subscription Request for Connection Monitoring.
|
||||||||||||
|
Subscription Request for Connection Monitoring.
|
||||||||||||
|
Type for Monitoring Service Permission.
|
||||||||||||
|
Type for Delivery for Connection TimetableService.
|
||||||||||||
|
Type for Delivery for Connection TimetableService.
|
||||||||||||
|
Type for capability request.
|
||||||||||||
|
Type for capability request.
|
||||||||||||
|
Type for Deliveries for Connection Timetable Service.
|
||||||||||||
|
Type for Deliveries for Connection Timetable Service.
|
||||||||||||
|
Type for Delivery for Connection Protection.
|
||||||||||||
|
Type for Delivery for Connection Protection.
|
||||||||||||
|
Type for Request for Connection Timetable Service.
|
||||||||||||
|
Type for Request for Connection Timetable Service.
|
||||||||||||
|
Type for Connection Timetable Capabilities.
|
||||||||||||
|
Type for Connection Timetable Capabilities.
|
||||||||||||
|
Type for Subscription Request for Connection Protection.
|
||||||||||||
|
Type for Subscription Request for Connection Protection.
|
||||||||||||
|
Type for Unique reference to this request, created by Consumer.
|
||||||||||||
|
Type for Unique reference to this response created by Consumer.
|
||||||||||||
|
Common parameters for all SITUATIONs.
|
||||||||||||
|
Connection between two stops within a connection area.
|
||||||||||||
|
Type for General SIRI Request.
|
||||||||||||
|
Type for GM Coordinates.
|
||||||||||||
|
Type for reference to a COURSE OF JOURNEY (Run).
|
||||||||||||
|
Type for identifier of a data VERSION FRAME.
|
||||||||||||
|
Name spaces.
|
||||||||||||
|
Type for Request from Producer to Consumer to notify that data update is ready to fetch.
|
||||||||||||
|
Type for Data ready Acknowledgement Response.
|
||||||||||||
|
Type for Data received Acknowledgement Response.
|
||||||||||||
|
Type for Body of Data Supply Request.
|
||||||||||||
|
Type for Data supply Request.
|
||||||||||||
|
Type for Planned VEHICLE JOURNEY Stop (Production Timetable Service).
|
||||||||||||
|
Type for Production Timetable of a LINE.
|
||||||||||||
|
Type for Origin and Destination stop of a VEHICLE JOURNEY.
|
||||||||||||
|
Type for reference to a Dated VEHICLE JOURNEY.
|
||||||||||||
|
Type for Planned VEHICLE JOURNEY (Production Timetable Service).
|
||||||||||||
|
Type for a text that may be overridden.
|
||||||||||||
|
Type for easement info.
|
||||||||||||
|
Type for Delviery Variant +SIRI v2.0
|
||||||||||||
|
Type for reference to a DESTINATION.
|
||||||||||||
|
Type for Information about a DESTINATION.
|
||||||||||||
|
Reference to a DIRECTION.
|
||||||||||||
|
Type for DIRECTION.
|
||||||||||||
|
Type for Cancellation of a Distributor VEHICLE JOURNEY from a connection.
|
||||||||||||
|
Type for Cancellation of a Distributor VEHICLE JOURNEY from a connection.
|
||||||||||||
|
Reference to a DRIVER.
|
||||||||||||
|
Type for easement info.
|
||||||||||||
|
Type for Error: EndpointDeniedAccess +SIRI v2.0
|
||||||||||||
|
Type for Error: EndpointNotAvailable +SIRI v2.0
|
||||||||||||
|
Type for a referenceUnique identifier of a SITUATION within participant.
|
||||||||||||
|
Type for Availaibility Change of EQUIPMENT.
|
||||||||||||
|
Type for Error Code.
|
||||||||||||
|
Type for Standard ErrorConditions for Service request.
|
||||||||||||
|
Type for RequestErrorCondition.
|
||||||||||||
|
Type for Description of an error.
|
||||||||||||
|
Type for Rea-ltime info about a VEHICLE JOURNEY Stop.
|
||||||||||||
|
Type for Estimated SERVICE JOURNEY INTERCHANGE.
|
||||||||||||
|
Type for Delivery for Estimated Timetable Capability.
|
||||||||||||
|
Type for Estimated Timetable Capability Request Policy.
|
||||||||||||
|
Type for Deliveries for Real-time Timetable Service.
|
||||||||||||
|
Type for Delivery for Real-time Timetable Service.
|
||||||||||||
|
Type for Type for Functional Service Request for Estimated Timetable.
|
||||||||||||
|
Type for Estimated Timetable Capabilities.
|
||||||||||||
|
Subscription Request for the Estimated Timetable Service.
|
||||||||||||
|
Type for Real-time info about a VEHICLE JOURNEY.
|
||||||||||||
|
Type for version frame structure.
|
||||||||||||
|
Type for Extensions to schema.
|
||||||||||||
|
Type for change to equipment availability.
|
||||||||||||
|
Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Faclities Management.
|
||||||||||||
|
Response with Facilities available to make requests.
|
||||||||||||
|
Location of the MONITORED FACILITY.
|
||||||||||||
|
Type for Delivery for Vehicle Monitoring Service.
|
||||||||||||
|
Type for Deliveries for VEHICLE monitoring services Used in WSDL.
|
||||||||||||
|
Type for Delivery for Vehicle Monitoring Service.
|
||||||||||||
|
Type for Functional Service Request for Facility Monitoring Service.
|
||||||||||||
|
Type for Vehicle Monitoring Capabilities.
|
||||||||||||
|
Type for Facility Monitoring Service Permissions.
|
||||||||||||
|
Type for Subscription Request for Vehicle Monitoring Service.
|
||||||||||||
|
Type for reference to a Faclility.
|
||||||||||||
|
Requests for info channels for use in service requests.
|
||||||||||||
|
Descriprion of the status of a MONITORED FACILITY.
|
||||||||||||
|
Type for sescription the MONITORED FACILITY itself.
|
||||||||||||
|
Type for reference to a Feature Code.
|
||||||||||||
|
Type for identifer of a VEHICLE JOURNEY within data Horizon of a service.
|
||||||||||||
|
A planned SERVICE JOURNEY INTERCHANGE from a journey.
|
||||||||||||
|
Type for Delivery for General MessageService.
|
||||||||||||
|
Type for access control.
|
||||||||||||
|
Type for Deliveries.
|
||||||||||||
|
Delivery for General Message.
|
||||||||||||
|
Service Request for General Messages.
|
||||||||||||
|
Type for General Message Capabilities.
|
||||||||||||
|
Type for General MessageService Permission.
|
||||||||||||
|
Subscription for General Message Service.
|
||||||||||||
|
Reference to a GROUP OF LINEs
|
||||||||||||
|
Type for a range of times.
|
||||||||||||
|
Type for a range of date times.
|
||||||||||||
|
Type for a range of date times.
|
||||||||||||
|
Type for Service Heartbeat Notification.
|
||||||||||||
|
Type for image.
|
||||||||||||
|
Type for Response with Info channels categories available to make requests.
|
||||||||||||
|
Requests for info channels for use in service requests.
|
||||||||||||
|
Type for Info Channel Permission.
|
||||||||||||
|
Type for reference to an Info Channel.
|
||||||||||||
|
Type for Info Channels description.
|
||||||||||||
|
Type for a general hyperlink.
|
||||||||||||
|
Type for Revocation of a previous message.
|
||||||||||||
|
Type for reference to an Info Message.
|
||||||||||||
|
Type for an Info Message.
|
||||||||||||
|
Type for feeder or Distributor Journey info about a VEHICLE JOURNEY.
|
||||||||||||
|
Type for reference to a SERVCIE JOURNEY INTERCHANGE.
|
||||||||||||
|
Type for InvalidDataReferencesError:.
|
||||||||||||
|
Type for reference to an Item.
|
||||||||||||
|
Type for a refernces to JOURNEY PARTs.
|
||||||||||||
|
Type for reference to a JOURNEY PART
|
||||||||||||
|
Type for refrence to a JOURNEY PATTERN.
|
||||||||||||
|
Reference to a PLACE visited by a VEHICLE JOURNEY.
|
||||||||||||
|
Type for LINEand DIRECTION.
|
||||||||||||
|
Type for Line Permission.
|
||||||||||||
|
Type for reference to a LINE.
|
||||||||||||
|
Response with LINEs available to make requests.
|
||||||||||||
|
Requests for LINE data for use in service requests.
|
||||||||||||
|
Defines a line shape +SIRI v2.0
|
||||||||||||
|
Type for gepspatial Position of a point.
|
||||||||||||
|
Type for Action Publish SITUATION Manual process.
|
||||||||||||
|
Unique identifier of a message within SIRI functional service type and participant.
|
||||||||||||
|
Type for message ref.
|
||||||||||||
|
Type for effect of EQUIPMENT availability change on impaired access users.
|
||||||||||||
|
Type for Transport MODEs.
|
||||||||||||
|
Type for Current CALL at stop.
|
||||||||||||
|
Type for Deletion of a feeder connection.
|
||||||||||||
|
Type for Deletion of a feeder connection.
|
||||||||||||
|
Type for Real time connection at a stop.
|
||||||||||||
|
Type for Real time connection at a stop.
|
||||||||||||
|
Type for Cancellation of an earlier Stop Visit.
|
||||||||||||
|
Type for Visit of a VEHICLE to a stop monitoring point.
|
||||||||||||
|
Type for Monitored VEHICLE JOURNEY.
|
||||||||||||
|
Type for Monitoring Service Capability access control.
|
||||||||||||
|
Allowed values for the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check.
|
||||||||||||
|
Type for reference to a monitoring point (LOGICAL DISPLAY).
|
||||||||||||
|
Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check.
|
||||||||||||
|
Type for shared context.
|
||||||||||||
|
Type for reference to an OPERATOR.
|
||||||||||||
|
Type for Annotated reference to a NETWORK affected by a SITUATION.
|
||||||||||||
|
Type for Error: No Info for Topic
|
||||||||||||
|
DataType for a NOTICe.
|
||||||||||||
|
Type for Notify user by Email.
|
||||||||||||
|
Type for Notify user by Pager.
|
||||||||||||
|
Type for Notify user by SMS.
|
||||||||||||
|
Type for Notify user by other means.
|
||||||||||||
|
Type for information about the LINEs affected by a SITUATION.
|
||||||||||||
|
Type for CALLing pattern for JOURNEY PATTERN.
|
||||||||||||
|
Type Onwards CALLs at stop.
|
||||||||||||
|
Type for reference to an Operatorational Unit Code.
|
||||||||||||
|
Type for OPERATOR Permission.
|
||||||||||||
|
Reference to an OPERATOR.
|
||||||||||||
|
An event which is not planned by the traffic OPERATOR, which is affecting, or has the potential to affect traffic flow.
|
||||||||||||
|
Reference to an Organisation.
|
||||||||||||
|
Type for error.
|
||||||||||||
|
Type for parameterised, i.e. user definable, actions.
|
||||||||||||
|
Type for Parameters Ignored Error:.
|
||||||||||||
|
Reference to Unique identifier of participant.
|
||||||||||||
|
Type for abstract permissions.
|
||||||||||||
|
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton.
|
||||||||||||
|
Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0.
|
||||||||||||
|
Type for Prediction Quality quantifcation.
|
||||||||||||
|
Type for Ordered list of CALLs at previous stop.
|
||||||||||||
|
Type for CALL at previous stop.
|
||||||||||||
|
Type for Unique reference to request to the producer.
|
||||||||||||
|
Type for Unique reference to reponse from producer.
|
||||||||||||
|
Type for General SIRI Producer Response.
|
||||||||||||
|
Type for Response with Product Categories available to make requests.
|
||||||||||||
|
Requests for TYPE OF PRODUCT CATEGORY reference data for use in service requests.
|
||||||||||||
|
Type for reference to a TYPE OF PRODUCT CATEGORY.
|
||||||||||||
|
Type for TYPE OF PRODUCT CATEGORY description.
|
||||||||||||
|
Type for Delivery for ProductionTimetable Capability.
|
||||||||||||
|
Type for Estimated ProductionCapability Request Policy.
|
||||||||||||
|
Type for deliveries of production timetable service.
|
||||||||||||
|
Delivery for Production Timetable Service type.
|
||||||||||||
|
Type for Functional Service Request for Production Timetables.
|
||||||||||||
|
Type for ProductionTimetable Capabilities.
|
||||||||||||
|
Subscription Request for Production Timetable Service.
|
||||||||||||
|
Type for Progress between stops.
|
||||||||||||
|
Type for advice.
|
||||||||||||
|
Type for list of effects.
|
||||||||||||
|
Type for disruption.
|
||||||||||||
|
Type for individual PT SITUATION.
|
||||||||||||
|
Type for Action Publish SITUATION To Alert Service.
|
||||||||||||
|
Type for Action Publish SITUATION To Web.
|
||||||||||||
|
Type for Action Publish SITUATION To Displays.
|
||||||||||||
|
Type for Notify SITUATION to Tv.
|
||||||||||||
|
Type for Action Publish SITUATION To Web.
|
||||||||||||
|
Type for publication action.
|
||||||||||||
|
Type for reference to a QUAY.
|
||||||||||||
|
Type for recroded Real-time info about a VEHICLE JOURNEY Stop.
|
||||||||||||
|
Type for references.
|
||||||||||||
|
Type for a reference.
|
||||||||||||
|
Description of the remedy to the change of a facility status (mainly when it becomes partially or totally anavailable)
|
||||||||||||
|
Type for General SIRI Request.
|
||||||||||||
|
Type for Unique reference to reponse.
|
||||||||||||
|
General Type for General SIRI Response.
|
||||||||||||
|
Type for Parameters to filter Situation Exchange Service requests, based on the SITUATION Road, Logically ANDed with other values.
|
||||||||||||
|
Type for individual PT SITUATION.
|
||||||||||||
|
Summary information about a Direction of a Line
|
||||||||||||
|
Reference to a ROUTE LINk.
|
||||||||||||
|
Reference to a Route (Transmodel)
|
||||||||||||
|
Type for reference to a Section.
|
||||||||||||
|
Type for ServcieCapabilities request.
|
||||||||||||
|
Type for SIRI Service Delivery Body..
|
||||||||||||
|
Type for SIRI Service Delivery type.
|
||||||||||||
|
Type for Standard ErrorConditiosn for Service request.
|
||||||||||||
|
Type for SIRI Service Delivery.
|
||||||||||||
|
Type for SIRI Service Delivery.
|
||||||||||||
|
Type for whether service is unavailable for all or some services SIRI 2.0
|
||||||||||||
|
Type for reference to a ServiceCategory.
|
||||||||||||
|
Type for Response with SERVICE FEATUREs available to make requests.
|
||||||||||||
|
Type for equests for TYPE OF PRODUCT CATEGORY reference data for use in service requests.
|
||||||||||||
|
Type for Service Feature description.
|
||||||||||||
|
A planned SERVICE JOURNEY INTERCHANGE between two journeys.
|
||||||||||||
|
Type for Service Not Available error.
|
||||||||||||
|
Configurable context for requests.
|
||||||||||||
|
SIRI Service Request.
|
||||||||||||
|
SIRI Service Request.
|
||||||||||||
|
Type for list of SITUATIONs.
|
||||||||||||
|
Type for Simple Contact Details.
|
||||||||||||
|
@lang.
|
||||||||||||
|
Tyoe for a string in a specified language.
|
||||||||||||
|
||||||||||||
|
Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL.
|
||||||||||||
|
Type for SIRI Functional Service Subscription types.
|
||||||||||||
|
Type for loggable Entry.
|
||||||||||||
|
Type for Delivery for Situation Exchange Service.
|
||||||||||||
|
Type for Deliveries for Situation Exchange Service.
|
||||||||||||
|
Type for Delivery for Situation Exchange Service.
|
||||||||||||
|
Type for Functional Service Request for Situation Exchange Service.
|
||||||||||||
|
Type for SItuation Exchange Service Capabilities.
|
||||||||||||
|
Type for Situation Exchange Service Permissions.
|
||||||||||||
|
Type for Subscription Request for Situation Exchange Service.
|
||||||||||||
|
Type for reference to a SITUATION.
|
||||||||||||
|
Type for reference to a SITUATION.
|
||||||||||||
|
Type for reference to a SITUATION or an update to a SITUATION.
|
||||||||||||
|
Type for reference to a SITUATION.
|
||||||||||||
|
Type for a source, i.e. provider of information.
|
||||||||||||
|
Type for SITUATION version number if entry is update to a previous version.
|
||||||||||||
|
Type for Response Status.
|
||||||||||||
|
Reference to a STOP AREA.
|
||||||||||||
|
Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0.
|
||||||||||||
|
Type for Cancellation of an earlier Stop Line Notice.
|
||||||||||||
|
Type for a Stop Line Notice.
|
||||||||||||
|
Type for Delivery for Stop Monitoring Service.
|
||||||||||||
|
Type for Monitoring Service Capability Request Policy.
|
||||||||||||
|
Type for Deliveries for Stop Monitoring Service.
|
||||||||||||
|
Type for Delivery for Stop Monitoring Service.
|
||||||||||||
|
Type for an individual Stop Monitoring a Multiple Request.
|
||||||||||||
|
Type for Functional Service Request for Stop Monitoring Service on multiple stops.
|
||||||||||||
|
Type for Functional Service Request for Stop Monitoring Service.
|
||||||||||||
|
Type for Stop Monitoring Capabilities.
|
||||||||||||
|
Type for Monitoring Service Permission.
|
||||||||||||
|
Type for Subscription Request for Stop Monitoring Service.
|
||||||||||||
|
Type for Monitoring Point (LOGICAL DISPLAY) Permission.
|
||||||||||||
|
Type for Cancellation of an earlier Stop Notice.
|
||||||||||||
|
Type for Notice for stop
|
||||||||||||
|
Type for Change to a Distributor stop position.
|
||||||||||||
|
Type for Change to a Distributor stop position.
|
||||||||||||
|
Summary information about a stop within line
|
||||||||||||
|
Reference to a SCHEDULED STOP POINT.
|
||||||||||||
|
Response with STOP POINTs available to make requests.
|
||||||||||||
|
Requests for stop reference data for use in service requests.
|
||||||||||||
|
Type for Delivery for Stop Timetable Service.
|
||||||||||||
|
Type for Monitoring Service Capability Request Policy.
|
||||||||||||
|
Type for stop timetable deliveries.
|
||||||||||||
|
Data type Delivery for Stop Timetable Service.
|
||||||||||||
|
Type for Functional Service Request for Stop Timetables.
|
||||||||||||
|
Type for Capabilities of Stop Timetable Service.
|
||||||||||||
|
Type for Monitoring Service Permission.
|
||||||||||||
|
Subscription Request for Stop Timetables.
|
||||||||||||
|
Type for Subscription context - Configuration parameters which may be evrriden.
|
||||||||||||
|
Type Unique identifier of Subscription Filter within Participant.
|
||||||||||||
|
Type Unique identifier of Subscription Filter within Participant.
|
||||||||||||
|
Type Unique identifier of Subscription within Participant.
|
||||||||||||
|
Type for SIRI Subscription Request.
|
||||||||||||
|
Type for SIRI Subscription Request.
|
||||||||||||
|
Type for Body of Subscription Response.
|
||||||||||||
|
Type for Subscription Response.
|
||||||||||||
|
Type for Notification to terminate a subscription or subscriptions.
|
||||||||||||
|
Type for a targeted call.
|
||||||||||||
|
Planned Connection between two VEHICLE JOURNEYs.
|
||||||||||||
|
Type for a targeted VEHICLE JOURNEY.
|
||||||||||||
|
Type for Body of Terminate Subscription Request content.
|
||||||||||||
|
Type for request to terminate a subscription or subscriptions.
|
||||||||||||
|
Type for Response to a request to terminate a subscription or subscriptions.
|
||||||||||||
|
Type for Status of termination response.
|
||||||||||||
|
Type for Timetabled Deletion of a feeder connection.
|
||||||||||||
|
Type for Timetabled Deletion of a feeder connection.
|
||||||||||||
|
Type for incoming visit by feeder journey to SERVICE JOURNEY NTERCHANGE
|
||||||||||||
|
Type for incoming visit by feeder journey to SERVICE JOURNEY NTERCHANGE
|
||||||||||||
|
Type for Cancellation of Timetabled Visit of a VEHICLE to a stop.
|
||||||||||||
|
Type for Timetabled Visit of a VEHICLE to a stop.
|
||||||||||||
|
A planned SERVICE JOURNEY INTERCHANGE to a journey.
|
||||||||||||
|
Type for BLOCK part elements of VEHICLE JOURNEY.
|
||||||||||||
|
Type for reference to a TRAIN NUMBER
|
||||||||||||
|
Type for reference to a Train Part.
|
||||||||||||
|
Type for implementation structure.
|
||||||||||||
|
Type for Error: UnapprovedKey +SIRI v2.0
|
||||||||||||
|
Type for Error: Unknown Endpoint +SIRI v2.0
|
||||||||||||
|
Type for Unknown Extensions Error:.
|
||||||||||||
|
Type for Error: Unknown Participant.
|
||||||||||||
|
Type for Error: Subscriber not found.
|
||||||||||||
|
Type for Error: Subscription not found.
|
||||||||||||
|
Type for cancellation of an earlier Vehicle Activity.
|
||||||||||||
|
Type for a Vehicle Activity.
|
||||||||||||
|
Type for reference to a Vehicle Feature Code.
|
||||||||||||
|
Type for Response with Vehicle Features available to make requests.
|
||||||||||||
|
Requests for VEHICLE feature data for use in service requests.
|
||||||||||||
|
Type for description of feature of VEHICLE.
|
||||||||||||
|
Type for reference to a VEHICLE JOURNEY.
|
||||||||||||
|
Type for Delivery for Vehicle Monitoring Service.
|
||||||||||||
|
Type for capability request policy.
|
||||||||||||
|
Type for Deliveries for VEHICLE monitoring services Used in WSDL.
|
||||||||||||
|
Type for Delivery for Vehicle Monitoring Service.
|
||||||||||||
|
Type for reference to a Vehicle Monitoring scope
|
||||||||||||
|
Type for Functional Service Request for Vehicle Monitoring Service.
|
||||||||||||
|
Type for Vehicle Monitoring Capabilities.
|
||||||||||||
|
Type for Monitoring Service Permissions.
|
||||||||||||
|
Type for Subscription Request for Vehicle Monitoring Service.
|
||||||||||||
|
Type for MonitoringPoint Permission.
|
||||||||||||
|
Reference to a VEHICLE.
|
||||||||||||
|
Type for reference Timetable Version.
|
||||||||||||
|
Type for VIA NAMes structure.
|
||||||||||||
|
Type for Distributor prolonged wait action.
|
||||||||||||
|
Type for Distributor prolonged wait action.
|
||||||||||||
|
Type for Will Wait details
|
||||||||||||
|
Type for a reference to a ZONE or locality.
|
||||||||||||
Simple Type Summary |
||||||
|
Type for absolute bearing.
|
||||||
|
Values for Access Facility.
|
||||||
|
Values for Accomodation Facility: TPEG pti_table 23.
|
||||||
|
Values for Progress Status.
|
||||||
|
Type for identifier of an advisory NOTICE
|
||||||
|
Values for Air ModesOfTransport: TPEG pti_table_08.
|
||||||
|
Union of VEHICLE and continuous MODEs.
|
||||||
|
Altitude metres from sea level.
|
||||||
|
Values for Area Of Interest.
|
||||||
|
Allowed types activity for Alighting.
|
||||||
|
Values for Assistance Facility.
|
||||||
|
Values for Audience.
|
||||||
|
Type for identifier of an BLOCK.
|
||||||
|
Allowed types activity for Boarding and Alighting.
|
||||||
|
Values for TBookingStatus TPEG pti_table 24.
|
||||||
|
Values for Bus ModesOfTransport: TPEG pti_table_05, loc_table_10.
|
||||||
|
Classification of the timeliness of the CALL, according to a fixed list of values.
|
||||||
|
Type for capability code.
|
||||||
|
Identifier of a Stop for Direct Cleardown.
|
||||||
|
Values for Coach ModesOfTransport: TPEG pti_table_03.
|
||||||
|
Enumeration of communications transport method usage.
|
||||||
|
Enumeration of compression usage.
|
||||||
|
Values for DIRECTION of CONNECTION link or SERVCIE JOURNEY INTERCHANGE.
|
||||||
|
Type for identifier of a CONNECTION link
|
||||||
|
Detail Levels for CONNECTION LINKs Discovery Request.
|
||||||
|
Detail Levels for Connection Monitoring Request.
|
||||||
|
Detail Levels for Connection Monitoring Request.
|
||||||
|
MODEs of transport applicable to private and non-timetabled transport.
|
||||||
|
Type for identifier of a COURSE OF JOURNEY (Run).
|
||||||
|
Type for identifier of a data VERSION FRAME.
|
||||||
|
Type for identifier of a Dated VEHICLE JOURNEY.
|
||||||
|
Values for Day Type TPEG pti_table 34
|
||||||
|
Values for Day Type TPEG pti_table 34
|
||||||
|
Type for allwoed values of Dela band.
|
||||||
|
Delivery Method: Fetched or Direct Delivery.
|
||||||
|
Allowed types activity for Boarding.
|
||||||
|
Type for identifier of a DESTINATION.
|
||||||
|
Identifier of a DIRECTION.
|
||||||
|
Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres.
|
||||||
|
Identifier of a DRIVER
|
||||||
|
A type with no allowed content, used when simply the presence of an element is significant.
|
||||||
|
Type for a endpoint.
|
||||||
|
Allowed values for EndTime Precision
|
||||||
|
Allowed values for EndTime Status.
|
||||||
|
Values for Environment incident reason types TPEG Pti18_4/TPEG Pti_22.
|
||||||
|
Values for Environment incident subreason types.
|
||||||
|
Values for Equipment incident reason types TPEG Pti18_3/TPEG Pti_21.
|
||||||
|
Values for Equipment incident sub reason types.
|
||||||
|
Detail Levels for Estimated Timetable Request.
|
||||||
|
Type for identifier of a Realtime VEHICLE JOURNEY.
|
||||||
|
Generic catégory of a facility.
|
||||||
|
Type for identifier of a Faclility.
|
||||||
|
Detail Levels for Facility Points Request.
|
||||||
|
Allowed values for changes to the status of a facility.
|
||||||
|
Allowed values for the status of a MONITORED FACILITY.
|
||||||
|
Values for FareClass Facility: TPEG pti_table 23.
|
||||||
|
Type for identifier of a StopFeature.
|
||||||
|
Allowed types activity for FirstOrLastJourney.
|
||||||
|
Values for Funicular ModesOfTransport: TPEG pti_table_10.
|
||||||
|
Identifier of a GROUP OF LINEs
|
||||||
|
Values for Hire Facility.
|
||||||
|
Values for Day Type TPEG pti_table 34
|
||||||
|
Values for image content.
|
||||||
|
Type for identifier of an Info Channel.
|
||||||
|
Type for identifier of an Info Message.
|
||||||
|
Type for identifer of a SERVCIE JOURNEY INTERCHANGE.
|
||||||
|
Nature of Interchange management.
|
||||||
|
Values for Interchange Status TPEG cross reference pti_table 31.
|
||||||
|
Type for identifier of an Item.
|
||||||
|
Type for identifier of an JOURNEY PART
|
||||||
|
Type for identifier of a JOURNEY PATTERN.
|
||||||
|
Latitude from equator.
|
||||||
|
Type for identifier of a LINE
|
||||||
|
Detail Levels for Lines Discovery Request.
|
||||||
|
Values for image content.
|
||||||
|
Longitude from Greenwich.
|
||||||
|
Values for Luggage Facility: TPEG pti_table 23.
|
||||||
|
Values for Metro ModesOfTransport: TPEG pti_table_04.
|
||||||
|
Values for Miscellaneous incident reason types TPEG Pti18_1/TPEG Pti_19.
|
||||||
|
Values for Miscellaneous incident sub reason types.
|
||||||
|
Values for Mobility Facility: TPEG pti_table 23.
|
||||||
|
Identifier of a monitoring point.
|
||||||
|
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.
|
||||||
|
Type for Quality of data indication.
|
||||||
|
Type for identifier of an OPERATOR Code.
|
||||||
|
Values for Nuisance Facility: TPEG pti_table 23.
|
||||||
|
Passenger load status of a VEHICLE.
|
||||||
|
Type for identifier of an OPERATOR Code.
|
||||||
|
Type for identifier of an OPERATOR Code.
|
||||||
|
Type for identifier of an OrganisationCode.
|
||||||
|
Values for Access Facility.
|
||||||
|
Type for Unique identifier of participant.
|
||||||
|
Values for PassengerComms Facility: TPEG pti_table 23.
|
||||||
|
Values for Passenger Information Facility.
|
||||||
|
Values for Personnel incident reason types TPEG Pti18_2/TPEG Pti_20.
|
||||||
|
Values for Personnel incident sub reason types.
|
||||||
|
Values for Predictability Status.
|
||||||
|
Allowed values for predictors.
|
||||||
|
Type for identifier of a TYPE OF PRODUCT CATEGORY.
|
||||||
|
Classification of the rate of progress of VEHICLE according a fixed list of values.
|
||||||
|
Type for Publication status.
|
||||||
|
Type for Quality of data indication.
|
||||||
|
Classification of the quality of the prediction of the CALL, according to a fixed list of values.
|
||||||
|
Type for identifier of a QUAY (Platform, Bay, etc).
|
||||||
|
Values for Rail ModesOfTransport: TPEG pti_table_02, train link loc_table_13.
|
||||||
|
Values for Refreshment Facility: TPEG pti_table 23.
|
||||||
|
Values for Type of Source.
|
||||||
|
Allowed values for actions to remedy a faclity change.
|
||||||
|
Values for Report Type TPEG pti_table 27.
|
||||||
|
Values for Reserved Space Facility.
|
||||||
|
Values for Retail Facility.
|
||||||
|
Type for identifier of a Route.
|
||||||
|
Identifier of a ROUTE LINk.
|
||||||
|
route_point_type TPEG pti_table15.
|
||||||
|
Values for Sanitary Facility: TPEG pti_table 23.
|
||||||
|
Values for ScopeType.
|
||||||
|
Type for ideifier of a Route section.
|
||||||
|
Values for SelfDrive ModesOfTransport: TPEG pti_table_12.
|
||||||
|
Values for Sensitivity.
|
||||||
|
Values for Service Condition.
|
||||||
|
Classification of the service exception
|
||||||
|
Type for identifier of a ServiceCategory.
|
||||||
|
Values for Severity.
|
||||||
|
Limited version of duration that allows for precise time arithmetic.
|
||||||
|
Email address type.
|
||||||
|
Id type for document references.
|
||||||
|
International phonenumber +41675601 etc.
|
||||||
|
A name that requires at least one character of text and forbids certain reserved characters.
|
||||||
|
A restriction of W3C XML Schema's string that requires at least one character of text.
|
||||||
|
Limited version of duration.
|
||||||
|
A string indicating the versioin of a SIRI data structure.
|
||||||
|
Type for identifier of a SITUATION.
|
||||||
|
Values for Type of Source.
|
||||||
|
Type for coordinate reference system.
|
||||||
|
Type for identifier of a STOP AREA.
|
||||||
|
Detail Levels for Stop Monitoring Request.
|
||||||
|
Type for identifier of a SCHEDULED STOP POINT.
|
||||||
|
Detail Levels for Stop Points Discovery Request.
|
||||||
|
Values for TBookingStatus TPEG pti_table17.
|
||||||
|
Visit Types to Return.
|
||||||
|
Values for Taxi ModesOfTransport: TPEG pti_table_11.
|
||||||
|
Values for Telecabin ModesOfTransport: TPEG pti_table_09, loc_table_14.
|
||||||
|
Values for Ticketing Facility.
|
||||||
|
Values for TicketRestrictionTypeTPEG pti_table 25.
|
||||||
|
Values for timetable type TPEG pti_table 33.
|
||||||
|
Type for identifier of an TRAIN NUMBER
|
||||||
|
Type for identifier of Train Part.
|
||||||
|
Values for Tram ModesOfTransport: TPEG pti_table_06, loc_table_12.
|
||||||
|
Identifier of a VEHICLE.
|
||||||
|
Type for identifier of a Vehicle Feature.
|
||||||
|
Type for identifier of a VEHICLE JOURNEY.
|
||||||
|
MODEs of transport applicable to timetabled public transport.
|
||||||
|
Values for ModesOfTransport : TPEG pti_table 01.
|
||||||
|
Identifier of a Vehicle Monitoring scope.
|
||||||
|
Detail Levels for Request.
|
||||||
|
Classification of the State of the VEHICLE JORUNEY according to a fixed list of values.
|
||||||
|
Distance (metres per second) ALternative unist may be specifed by context.
|
||||||
|
Values for Verification Status Corresponds to TPEG pti_table 32.
|
||||||
|
Type for identifier of a Version.
|
||||||
|
Type for Stop Visit.
|
||||||
|
Values for Water ModesOfTransport: TPEG pti_table_07.
|
||||||
|
Values for Entry Status.
|
||||||
|
Type for identifier of a ZONe.
|
||||||
Element Group Summary |
||||||||||
|
Allowed actions to perform to distribute SITUATION.
|
||||||||||
|
Mode Submode and OPERATOR.
|
||||||||||
|
Elements describing the the arrival of a VEHICLE at a SCHEDULED STOP POINT.
|
||||||||||
|
Elements describing the the departure of a VEHICLE from a SCHEDULED STOP POINT.
|
||||||||||
|
Elements describing the the targeted CALL of a VEHICLE at a stop.
|
||||||||||
|
Elements describing the the arrival of a VEHICLE at a stop.
|
||||||||||
|
Elements describing the the departure of a VEHICLE from a stop.
|
||||||||||
|
Facilities that apply to stops.
|
||||||||||
|
Errors that may arise in the execution of a request.
|
||||||||||
|
Elemenst for authecticiation.
|
||||||||||
|
Information that classifies journey.
|
||||||||||
|
Annotations of the CALL.
|
||||||||||
|
Parameters that affect the subscription publishing and notification processing.
|
||||||||||
|
Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL.
|
||||||||||
|
Elements describing theProperties specific to a rail CALLs.
|
||||||||||
|
Elements describing the Real-time CALL properties.
|
||||||||||
|
Information relating to real-time properties of call.
|
||||||||||
|
Status Information for individual request.
|
||||||||||
|
Data received AcknowledgementService Status Check Request content.
|
||||||||||
|
Structured Classification Elements.
|
||||||||||
|
Address elements for SIRI messages to the Subscriber/Consumer client.
|
||||||||||
|
tructured Classification Elements.
|
||||||||||
|
Times for making SERVICE JOURNEY INTERCHANGE.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that specify the CONNECTION LINKs to be returned.
|
||||||||||
|
Distributor (fetcher) payload content.
|
||||||||||
|
Distributor (fetcher) payload content.
|
||||||||||
|
Feeder delivery payload content.
|
||||||||||
|
Feeder delivery payload content.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the subscription processing.
|
||||||||||
|
Parameters that affect the subscription processing.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Feeder delivery payload content.
|
||||||||||
|
Feeder delivery payload content.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the subscription processing.
|
||||||||||
|
Parameters that affect the subscription processing.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Unique reference to this request, created by Consumer.
|
||||||||||
|
Unique reference to this response message from Consumer.
|
||||||||||
|
Unique reference to request: participant and SIRI service type are given by context.
|
||||||||||
|
Endpoint reference proprerties for response message: participant and SIRI service type are given by context.
|
||||||||||
|
Elements identifying Ordered visit to a stop within calling sequence of a SERVICE PATTERN.
|
||||||||||
|
Data received Acknowledgement content.
|
||||||||||
|
Groups the data supply messages.
|
||||||||||
|
Specifies content to be included in data supply.
|
||||||||||
|
General info elements that apply to all journeys of timetable version unless overriden.
|
||||||||||
|
Datex2 SITUATION management elements.
|
||||||||||
|
Datex2 Tarffic element.
|
||||||||||
|
Datex2 Trrffic element road.
|
||||||||||
|
Datex2 SITUATION common elements.
|
||||||||||
|
If request has been proxied by an intermediate aggregating system , tracking informattion relating to the original requestor.
|
||||||||||
|
Delivery options.
|
||||||||||
|
Common defaults.
|
||||||||||
|
Elements identifying data Consumer, i.e. requestor, if synchronous delivery or subscriber if asynchronous.
|
||||||||||
|
General requests for fetched data delivery.
|
||||||||||
|
Responses that deliver payload content.
|
||||||||||
|
Responses that deliver payload content.
|
||||||||||
|
Status Information for individual request.
|
||||||||||
|
Text description of SITUATION.
|
||||||||||
|
Requests for reference data for use in service requests.
|
||||||||||
|
Responses with reference data for use in service requests.
|
||||||||||
|
Elements describing nature of disruption.
|
||||||||||
|
Errors that may arise in the execution of a delegated distribution request.
|
||||||||||
|
General properties of the journey.
|
||||||||||
|
Real-time properties of the journey.
|
||||||||||
|
If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference.
|
||||||||||
|
Payload part of Estimated Timetable Delivery.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the subscription publishing and notification processing.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Group of Facility accessibility elements.
|
||||||||||
|
Parameters to filter Facility Monitoring requests, based on the facility location .
|
||||||||||
|
Payload part of Vehicle Monitoring delivery.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the subscription publishing and notification processing.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Elements for volume control.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that specify the Facilities to be returned.
|
||||||||||
|
Group of Facility accessibility elements.
|
||||||||||
|
Group of Facility accessibility elements.
|
||||||||||
|
General Message payload content.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Elements describing the HEADWAY INTERVALs.
|
||||||||||
|
Extra information provided on general message notifcation that can be used to filter messages.
|
||||||||||
|
Identifiers of Interchange Distributor Stop.
|
||||||||||
|
Identifiers of Interchange Distributor Stop.
|
||||||||||
|
Elements identifying CALL at CONNECTION link of SERVICE JORUNEY INTERCHANGE of Feeder Journey .
|
||||||||||
|
Elements identifying CALL at CONNECTION link of SERVICE JORUNEY INTERCHANGE of Feeder Journey .
|
||||||||||
|
Properties of SERVICE JOURNEY INTERCHANGE.
|
||||||||||
|
Time Elements for SERVICE JOURNEY INTERCHANGE.
|
||||||||||
|
Elements for INTERCHANGE TRANSFER duration.
|
||||||||||
|
Elements for INTERCHANGE WAIT TIME.
|
||||||||||
|
End names for journey.
|
||||||||||
|
Call times for journey.
|
||||||||||
|
Elements identifying VEHICLE JOURNEY.
|
||||||||||
|
Elements describing a VEHICLE JOURNEY.
|
||||||||||
|
Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the journey.
|
||||||||||
|
Elements describing the ROUTE and JOURNEY PATTERN Identfiers associated with a journey.
|
||||||||||
|
Elements describing the real-time progress of a monitored VEHICLE JOURNEY.
|
||||||||||
|
Elements for a LINE and DIRECTION.
|
||||||||||
|
Line to which link connects.
|
||||||||||
|
Elements for identifying a LINE and DIRECTION.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that specify the LINEs to be returned.
|
||||||||||
|
Transport Sub Modes.
|
||||||||||
|
Arrival times for CALL.
|
||||||||||
|
Departure times for CALL.
|
||||||||||
|
Elements for a monitored CALL.
|
||||||||||
|
The service pattern of a monitored VEHICLE JOURNEY.
|
||||||||||
|
Elements identifying a VEHICLE JOURNEY.
|
||||||||||
|
Elements describing the the arrival status of a VEHICLE at a stop.
|
||||||||||
|
Elements describing the the departure status of a VEHICLE from a stop.
|
||||||||||
|
Elements describing the CALL.
|
||||||||||
|
Elements for Arrival in onward CALl.
|
||||||||||
|
Elements for departure in ONWARD CALL.
|
||||||||||
|
Operational information about the monitored VEHICLE JOURNEY.
|
||||||||||
|
Operational information about the monitored VEHICLE JOURNEY.
|
||||||||||
|
Unique reference to subscription May be used to reference subscription in subsequent interactions.
|
||||||||||
|
Passenget arrivel times at STOP PLACE in order to meet VEHICLEdeparture times for CALL.
|
||||||||||
|
Prediction options.
|
||||||||||
|
Non PT Road Submodes.
|
||||||||||
|
Unique reference to request from producer.
|
||||||||||
|
Unique reference to reponse from producer.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Payload part of Production Timetable delivery.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the subscription content.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Elements describing the real-time progress of a journey.
|
||||||||||
|
Elements describing the qua;ity of real-time progress data of a journey.
|
||||||||||
|
||||||||||
|
Body of SITUATION.
|
||||||||||
|
PT Transport Sub Modes.
|
||||||||||
|
Submode of mode.
|
||||||||||
|
Body of SITUATION.
|
||||||||||
|
Elements describing the LINEand DESTINATION of a journey.
|
||||||||||
|
StructuredReason Elements.
|
||||||||||
|
Information relating to recorded real-time properties of call.
|
||||||||||
|
Namespace related elements in Request Context.
|
||||||||||
|
SIRI All Requests.
|
||||||||||
|
SIRI Requests.
|
||||||||||
|
Elements relating to system that sent request.
|
||||||||||
|
Resources related elements in Request Context.
|
||||||||||
|
Unique reference to response May be used to reference response in subsequent interactions.
|
||||||||||
|
SIRI Service Responses.
|
||||||||||
|
SIRI Service Responses.
|
||||||||||
|
Datex 2 SITUATION.
|
||||||||||
|
Body of SITUATION.
|
||||||||||
|
Elements for SIRI Service Delivery.
|
||||||||||
|
Elements for SIRI Service Delivery type.
|
||||||||||
|
Status Information for overall request.
|
||||||||||
|
Address elements for SIRI messages to the Producer server.
|
||||||||||
|
Facilities that apply to services.
|
||||||||||
|
Elements classifying the Service or journey.
|
||||||||||
|
Elements describing the main places bewteen which a VEHICLE JOURNEY runs.
|
||||||||||
|
Errors that may arise in the execution of a request.
|
||||||||||
|
Requests for service provision.
|
||||||||||
|
Requests for service provision.
|
||||||||||
|
Responses to requests other than deliveries and status information.
|
||||||||||
|
Responses to requests other than deliveries and status information.
|
||||||||||
|
Convenience artefact to pick out main elements of the common requests.
|
||||||||||
|
Convenience artifact to pick out main elements of the Connection Monitoring Service.
|
||||||||||
|
Convenience artifact to pick out main elements of the Connection Monitoring Service.
|
||||||||||
|
Convenience artifact to pick out main elements of the Connection Services.
|
||||||||||
|
Convenience artifact to pick out main elements of the Connection Services.
|
||||||||||
|
Convenience artifact to pick out main elements of the Connection Timetable Service.
|
||||||||||
|
Convenience artifact to pick out main elements of the Connection Timetable Service.
|
||||||||||
|
Convenience artifact to pick out main elements of the Estimated Timetable Service.
|
||||||||||
|
Responses with reference data for use in service requests.
|
||||||||||
|
Requests for reference data for use in SIRI Functional Service requests.
|
||||||||||
|
Responses with reference data for use in SIRI Functional Service requests.
|
||||||||||
|
Convenience artifact to pick out main elements of the Estimated Timetable Service.
|
||||||||||
|
Convenience artifact to pick out main elements of the Facility Monitoring Service.
|
||||||||||
|
Convenience artefact to pick out main elements of the General Message Service.
|
||||||||||
|
Convenience artefact to pick out main elements of the Production Timetable Service.
|
||||||||||
|
Requests for reference data for use in service requests.
|
||||||||||
|
Defines the capabilities of an individual SIRI service request functions.
|
||||||||||
|
Defines the capabilities of an individual SIRI service response functions.
|
||||||||||
|
SIRI Functional Service Delivery types.
|
||||||||||
|
SIRI Functional Service Concrete Requests.
|
||||||||||
|
Convenience artifact to pick out main elements of the Situation Exchange Service.
|
||||||||||
|
Convenience artifact to pick out main elements of the Stop Monitoring Service.
|
||||||||||
|
Convenience artifact to pick out main elements of the Stop Timetable Service.
|
||||||||||
|
SIRI Functional Service Subscription types.
|
||||||||||
|
Convenience artifact to pick out main elements of the Vehicle Monitoring Service.
|
||||||||||
|
Type for reference to a SITUATION or an update to a SITUATION.
|
||||||||||
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Classifiers.
|
||||||||||
|
Payload part of Situation Exchange Service delivery.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the subscription publishing and notification processing.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Elements for volume control.
|
||||||||||
|
Type for reference to a SITUATION or an update to a SITUATION.
|
||||||||||
|
situation Informatiion.
|
||||||||||
|
Parameters to filter Situation Exchange Service requests, based on the VEHICLE JOURNEYs affected by the SITUATION.
|
||||||||||
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Network.
|
||||||||||
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Place.
|
||||||||||
|
References to a SITUATION.
|
||||||||||
|
Elements Reference to a SITUATION or an update to a SITUATION.
|
||||||||||
|
Group of source details.
|
||||||||||
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Status.
|
||||||||||
|
Parameters to filter Situation Exchange Service requests, based on the STOP PLACEs affected SITUATIONs.
|
||||||||||
|
Type for reference to a SITUATION or an update to a SITUATION.
|
||||||||||
|
Status elements.
|
||||||||||
|
Requests about system status.
|
||||||||||
|
Responses that infrom about the service status.
|
||||||||||
|
Elements describing the the arrival of a VEHICLE at a stop.
|
||||||||||
|
Elements describing the the departure of a VEHICLE from a stop.
|
||||||||||
|
Facilities that apply to stops.
|
||||||||||
|
Payload part of Stop Monitoring Service delivery.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the subscription publishing and notification processing.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Elements for volume control.
|
||||||||||
|
Elements for a SCHEDULED STOP POINT.
|
||||||||||
|
Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that specify the STOP POINTs to be returned.
|
||||||||||
|
Elements describing the distance from the stop of a VEHICLE.
|
||||||||||
|
Payload part of Stop Timetable delivery.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the subscription publishing and notification processing.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
External identifiers of Cancelled Stop Visit.
|
||||||||||
|
External identifiers of Stop Visit.
|
||||||||||
|
Unique reference to request.
|
||||||||||
|
Unique reference to subscription May be used to reference subscription in subsequent interactions.
|
||||||||||
|
Type for unique identifier of a subscription.
|
||||||||||
|
groups the subscription request.
|
||||||||||
|
Subscription Response content.
|
||||||||||
|
Additional information provided if request is successful.
|
||||||||||
|
Elements for a targeted call.
|
||||||||||
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Status.
|
||||||||||
|
Timing related elements in Request Context:
|
||||||||||
|
Elements affecting temporal scope of SITUATION.
|
||||||||||
|
Parameters to filter Situation Exchange Service requests, based on the SITUATION Status.
|
||||||||||
|
Parameters that specify the content to be processed.
|
||||||||||
|
Status Info.
|
||||||||||
|
If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference.
|
||||||||||
|
Additional descriptive properties of service.
|
||||||||||
|
Structured Classification Elements.
|
||||||||||
|
Structured Classification Elements.
|
||||||||||
|
Operational information about the monitored VEHICLE JOURNEY.
|
||||||||||
|
Identifiers of Vehicle Activity.
|
||||||||||
|
Arrival times for CALL.
|
||||||||||
|
Departure times for CALL.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Common information about a VEHICLE JOURNEY.
|
||||||||||
|
Payload part of Vehicle Monitoring delivery.
|
||||||||||
|
Parameters that affect the request processing.
|
||||||||||
|
Parameters that affect the subscription publishing and notification processing.
|
||||||||||
|
Parameters that specify the content to be returned.
|
||||||||||
|
Elements for volume control.
|
||||||||||
|
WGS84 Coordinates.
|
||||||||||
|
This XML schema documentation has been generated with DocFlex/XML 1.9.5 using DocFlex/XML XSDDoc 2.8.1 template set.
DocFlex/XML is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from
any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually
using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML,
single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only.
And, of course, you could develop any template applications by your own!
Please note that by purchasing a license for this software, you not only acquire a useful tool,
you will also make an important investment in its future development, the results of which you could enjoy later by yourself.
Every single your purchase matters and makes a difference for us!
To purchase a license, please follow this link: http://www.filigris.com/shop/
|