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.
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-PT DATED JOURNEY Model view.Convenience artefact to pick out main elements of the Production Timetable Service.Request for daily production timetables.Type for Functional Service Request for Production Timetables.Version number of request. Fixed.Parameters that specify the content to be returned.Communicate only differences to the timetable specified by this VERSION of the TIMETABLe.Filter the results to include journeys for only the specified OPERATORs.Filter the results to include only vehicles along the given LINEs.Iinclude only vehicles along the given LINE.Filter the results to include only journeys of the specified VEHICLE MODE. (since SIRI 2.1)Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. (since SIRI 2.1)Filter the results to include only journeys with a CALL at the specified STOP POINT. (since SIRI 2.1)Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged.Preferred languages in which to return text values.Whether to return the whole timetable, or just differences from the inidicated version. Default is 'false'.Request for a subscription to the Production Timetable Service.Subscription Request for Production Timetable Service.Parameters that affect the subscription content.Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions.
If false each subscription response will contain the full information as specified in this request.Delivery for Production Timetable Service.Payload part of Production Timetable delivery.A TIMETABLE to run on a specified date.Delivery for Production Timetable Service type.Version number of response. fixed.A TIMETABLE FRAME to run on a specified date.Type for Production Timetable of a LINE.Timetable Version.Minimum interval at which updates for this DATED TIMETABLE VERSION FRAME can be sent. (since SIRI 2.1)Complete list of all planned VEHICLE JOURNEYs for this LINE and DIRECTION.List of all removed VEHICLE JOURNEYs for this LINE and DIRECTION.
A data producer may silently remove a journey from the plan if it was previously provided in error. Careful: Removal is different from Cancellation.
Minimal information, or no information at all, of a RemovedDatedVehicleJourney or the removal itself must be communicated to the passengers, i.e., it is "silently" removed. A Cancellation, on the other hand, is possibly the most important information to provide to the passengers.
It is strongly advised to only use this feature in cases where a journey was sent in error and it can be assumed that as few passengers as possible have seen the erroneous information to avoid confusion. (since SIRI 2.1)Connection paramters for a SERVICE JOURNEY INTERCHANGE between a feeder and distributor journey. SIRI 2.0List of all removed SERVICE JOURNEY INTERCHANGEs.
A data producer may silently remove an interchange from the plan if it was previously provided in error. Careful: Removal is different from Cancellation.
Minimal information, or no information at all, of a RemovedServiceJourneyInterchange or the removal itself must be communicated to the passengers, i.e., it is "silently" removed. A Cancellation, on the other hand, is possibly the most important information to provide to the passengers.
It is strongly advised to only use this feature in cases where an interchange was sent in error and it can be assumed that as few passengers as possible have seen the erroneous information to avoid confusion. (since SIRI 2.1)Start and end of timetable validity (time window) of journeys for which schedules are to be returned by the data producer.
The ValidityPeriod of the timetable must not exceed the ValidityPeriod requested by the subscriber.
If omitted, then the full - by the subscriber requested - ValidityPeriod or configured data horizon applies.
Since the end of an OPERATING DAY of one ITCS does not usually coincide with the end of another ITCS, it may happen that data cannot be provided for the complete time frame requested by a subscriber.
In order for the data consumer to be aware of this situation, the data producer should confirm - in each returned timetable - for which part of the requested ValidityPeriod he can actually deliver journey schedules.
If the requested period is so far in the past that the data producer does no longer have any data, he should reject the subscription with "Status=false" and a BeyondDataHorizon ErrorCondition.
If the requested period is so far in the future that the data producer does not yet have any data, he will deliver data as soon as it is available.
A timetable falls inside the ValidityPeriod if all of its journeys fall inside it.
A journey falls inside the ValidityPeriod if the AimedDepartureTime or AimedArrivalTime at any CALL lies between the Start- and EndTime of the ValidityPeriod (regardless of whether the aimed times at a previous or subsequent CALL fall ouside of the ValidityPeriod).
Careful: Journeys which themselves fall outside the ValidityPeriod, but which are linked to a journey within the ValidityPeriod by a JOURNEY RELATION, are also regarded as falling inside the ValidityPeriod. Examples are journeys where the vehicle is split or joins with or is replaced by another vehicle.
Type for deliveries of production timetable service. Used in WSDL.Request for information about ProductionTimetable Service Capabilities. Answered with a ProductionTimetableCapabilitiesResponse.Capabilities for ProductionTimetable Service. Answers a Answered with a ProductionTimetableCapabilitiesRequest.Type for Delivery for ProductionTimetable Capability.Version number of response. fixed.Type for Estimated ProductionCapability Request Policy.Whether results returns foreign journeys only. Capabilities of ProductionTimetableService.Type for ProductionTimetable Capabilities.Filtering Capabilities.Whether results can be filtered by TIMETABLE VERSION Default is 'true'.Request Policiy capabilities.Subscription Policy capabilities.Whether incremental updates can be specified for updates Default is ' true'.Optional Access control capabilities.Participant's permissions to use the service.
