Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
main schemae-service developersCEN TC278 WG3 SG7 TeamWerner Kohl MDVEuropeDrafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:[email protected]2003-02-102004-10-312005-02-142005-02-202005-05-112007-04-17
Name Space changes
2008-03-26
Add wrapper tag for Line DIRECTION to help binding to Axis
2008-11-17
Revise to support substitution groups
2011-04-18
- siri_productionTimetable_service.xsd Type on request ValidiyPeriod start and end should be datetime not time ..
- Change to ClosedTimestampRange instead of ClosedTimeRange.
Fix Subscription request to be an element and have extensions .
2011-01-19
SIRI 1.3 Drop use of As Flat Groups for DatedCalls.
2012-03-23
Factor out fropm ProductionTimetable package
(since SIRI 2.0) Add ServiceJourneyInterchange (i.e. Monitored Connection)
[VDV] Add additional times to TargetedServiceInterchange MinimumTransferTime, MaximimTransferTime, StandardTransferTime, MaximumAUtomaticWaitTime, StandardWaitTime.
[VDV] Add Public and Contact Details to JourneyInfo
[VDV] Add AimedLatestPassengerAccessTime to TargetedCall
2013-02-11
SIRI v2.0 Modified ServiceJourneyInterchange SIRI:PT
SIRI is a European CEN standard for the exchange of Public Transport real-time information.
This sub-schema describes the Production Timetable Service.
Derived from the VDV, RTIG XML and Trident standards.
Version 2.1Arts, recreation and travel, Tourism, Travel (tourism), Transport,
Air transport, Airports,
Ports and maritime transport, Ferries (marine),
Public transport, Bus services, Coach services, Bus stops and stations,
Rail transport, Railway stations and track, Train services, Underground trains,
Business and industry, Transport, Air transport, Ports and maritime transport, Public transport,
Rail transport, Roads and road transport
CEN TC278 WG3 SG7SIRI_PT XML schema. Service Interface for Real-time Information. Production Timetable Service.StandardSIRI-Model Dated Vehicle Joruney.A planned VEHICLE JOURNEY taking place on a particular date.Type for Planned VEHICLE JOURNEY (Production Timetable Service).Identifier for a VEHICLE JOURNEY.Complete sequence of stops along the route path, in calling order.Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc.Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. (since SIRI 2.1)A reference to the DATED VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer.Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops.TRAIN NUMBERs for journey.TRAIN NUMBER assigned to VEHICLE JOURNEY.General info elements that apply to all journeys of timetable version unless overriden.Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (since SIRI 2.0)Description of the destination stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (Unbounded since SIRI 2.0)Additional Text associated with LINE. (Unbounded since SIRI 2.0)Whether journey is first or last jouurney of day. (since SIRI 2.0)If the journey is an alteration to a timetable, indicates the original journey, and the nature of the difference.Use of simple reference is deprecated Refecence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 Whether this journey is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition.Whether this journey is a cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled.Additional descriptive properties of service.Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable.Whether VEHICLE JOURNEYs of LINE are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable.A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0)A planned SERVICE JOURNEY INTERCHANGE from a journey. (since SIRI 2.0)A planned SERVICE JOURNEY INTERCHANGE to a journey. (since SIRI 2.0)A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0)Type for a previously planned SERVICE JOURNEY INTERCHANGE that a data producer wants to silently remove from the plan (because it is erroneous data). Careful: Removal is different from Cancellation. (since SIRI 2.1)Time Elements for SERVICE JOURNEY INTERCHANGE.Elements for INTERCHANGE WAIT TIME.Elements for INTERCHANGE TRANSFER duration.Standard transfer duration for INTERCHANGE. SIRI v2,0Minimum transfer duration for INTERCHANGE. SIRI v2,0Maximum transfer duration for INTERCHANGE. SIRI v2,0Elements for INTERCHANGE WAIT TIME.Standard wait time for INTERCHANGE. SIRI v2,0Maximum time that Distributor will wait for Feeder for INTERCHANGE. SIRI v1.0Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0)Complete sequence of stops along the route path, in calling order.Type for Planned VEHICLE JOURNEY Stop (Production Timetable Service).Whether this DATED CALL is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition.Whether this DATED CALL is a cancellation of a previously announced call (or planned according to the long-term timetable). Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled.Text annotation that applies to this call.Information on any planned distributor connections (deprecated from SIRI V2.0 ... see 2 next attributes)Information on any planned feeder connections. SIRI 2.0Information on any planned distributor connections. SIRI 2.0Planned Connection between two VEHICLE JOURNEYs.Reference to a (dated) distributor VEHICLE JOURNEY.Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place.Link to Interchange stop from which the distributor journey departs. If omitted: the distributor journey stop is the same as the feeder journey stop, i.e. that of theh dated call.For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation.Connection between two stops within a connection area. Used within the context of one or other end.Identifier of CONNECTION LINk.Times for making SERVICE JOURNEY INTERCHANGE.Default time (Duration) needeed to traverse SERVICE JOURNEY INTERCHANGE from feeder to distributor.Time needeed by a traveller whis is familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration.Time needeed by a traveller whis is not familiar with SERVICE JOURNEY INTERCHANGE to traverse it. If absent, use DefaultDuration and a standard weighting.Time needeed by a traveller wos is mobility impaired to traverse SERVICE JOURNEY INTERCHANGE. If absent, use DefaultDuration and a standard impaired travel speed.Properties of SERVICE JOURNEY INTERCHANGE.Whether the passenger can remain in VEHICLE (i.e. BLOCKlinking). Default is 'false': the passenger must change vehicles for this connection.Whether the SERVICE JOURNEY INTERCHANGE is guaranteed. Default is 'false'; SERVICE JOURNEY INTERCHANGE is not guaranteed.Whether the SERVICE JOURNEY INTERCHANGE is advertised as a connection. Default is 'false'.Nature of Interchange management.Interchange is considered a possible connection between journeys.Interchange is advertised to public as a possible connection between journeys.Interchange is actively managed as a possible connection between journeys and passengers are informed of real-time alterations.Interchange is actively managed as a possible connection between journeys and distributor may be delayed in order to make a transfer possible.Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0)Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. (since SIRI 2.1)Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable.
Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. (since SIRI 2.1)The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. (since SIRI 2.1)Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0)SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0)Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN.For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead.
ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1)Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1)Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0)SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0)Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN.For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead.
ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1)Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1)
