All Downloads are FREE. Search and download functionalities are using the official Maven repository.

siri-2.0.xsd.siri_model.siri_reference-v2.0.xsd Maven / Gradle / Ivy

The newest version!




	
		
			
				main schema
				e-service developers
				CEN TC278 WG3 SG7 Team
				Europe
				Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:[email protected]
				
					2004-09-29
				
				
					2004-10-01
				
				
					2005-02-14
				
				
					2005-02-20
				
				
					2005-03-20
				
				
					2005-05-11
				
				
					2007-03-29
				
				
					2012-03-22
				 SIRI 2.0 
					 Refactor Monitoring code 
					 Add QUAY Ref
				
				
					2012-06-22
				SIRI 2.0  
					Add Group of Lines to JourneyPatternInfoGroup
					[CH] Set explicit  default value for VehicleAtStop to be false  
					[DE] Add Driver Ref
				
				
					2013-02-11
					Correction: PlaceName unbounded to allow multiple languages
				
				
					

SIRI is a European CEN standard for the exchange of real-time information .

This package defines common basic domain model identifier elements that are used in one or more SIRI fucntional service.

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schema/2.0/xsd/siri/utility/}siri_reference-v2.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd Unclassified CEN, VDV, RTIG 2004-2012
  • Derived from the VDV, RTIG CML and Trident standards.
Version 2.0 Draft Arts, 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 SG7 SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Common DomainModel elements. Standard
Version Identifier. Type for identifier of a Version. Type for reference Timetable Version. Type for identifier of a SCHEDULED STOP POINT. Reference to a SCHEDULED STOP POINT. Sequence of visit to SCHEDULED STOP POINT.within VEHICLE JOURNEY. Increases monotonically, but not necessarily sequentially. 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. Elements for a SCHEDULED STOP POINT. Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) Reference to a SCHEDULED STOP POINT. Reference to a STOP POINT. Name of SCHEDULED STOP POINT. Elements identifying an ordered visit to a SCHEDULED STOP POINT within a SERVICE PATTERN. Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) Elements identifying Ordered visit to a stop within calling sequence of a SERVICE PATTERN. Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) Type for Stop Visit. Identifier of a Stop for Direct Cleardown. Suitable for radio transmission over a constrained bandwidth channel. This may be a separate code from the full stop identifier. Reference Cleardown identifier of a stop. Type for identifier of a STOP AREA. Reference to a STOP AREA. Type for identifier of a QUAY (Platform, Bay, etc). Type for reference to a QUAY. Identifier of a monitoring point. May correspond to a SCHEDULED STOP POINT or represent a group of Stops other Timing Points (i.e. LOGICAL DISPLAY) Type for reference to a monitoring point (LOGICAL DISPLAY). Whether the stop is a TIMING POINT. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is 'true'. Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) Type for identifier of a CONNECTION link Reference to a CONNECTION link Type for reference to a CONNECTION link MODEs of transport applicable to timetabled public transport. MODEs of transport applicable to private and non-timetabled transport. Union of VEHICLE and continuous MODEs. Type for Transport MODEs. A method of transportation such as bus, rail, etc. if true, listed modes to be excluded from list. Type for identifier of a JOURNEY PATTERN. Type for refrence to a JOURNEY PATTERN. Reference to a JOURNEY PATTERN. Elements describing the ROUTE and JOURNEY PATTERN Identfiers associated with a journey. Elements describing the LINE, ROUTE and DIRECTION of a VEHICLE JOURNEYwhich are derived from the JOURNEY PATTERN associated with the journey. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each monitored journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. Identifier of JOURNEY PATTERN that journey follows. Name of Joruney Pattern A means of transportation such as bus, rail, etc. Identifier of ROUTE that journey follows. Name or Number by which the LINE is known to the public. (Unbounded since SIRI 2.0) Reference to a GROUP OF LINEs to which journey belongs. SIRI 2.0 Description of the DIRECTION. May correspond to a DESTINATION DISPLAY. (Unbounded since SIRI 2.0) Alternative identifier of LINE that an external system may associate with journey. Elements for identifying a LINE and DIRECTION. Reference to a LINE. Reference to a LINE DIRECTION DIRECTION, typically outward or return. Type for LINEand DIRECTION. Elements for a LINE and DIRECTION. Line Reference. Direction Reference. Type for identifier of a LINE Reference to a LINE. Type for reference to a LINE. Elements describing the LINEand DESTINATION of a journey. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated VEHICLE JOURNEYs of the timetable. Each real-time journey takes its values from the dated VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity. Description of the destination stop (vehicle signage), if different from the that in timetable - the DESTINATION DISPLAY. Can be overwritten section by section by the entry in an individual CALL. Name or Number by which the LINEis known to the public. Identifier of a GROUP OF LINEs Reference to a GROUP OF LINEs Type for identifier of a Route. Description of route by which it can be recogniozed. Reference to a Route (Transmodel) Identifier of a DIRECTION. Reference to a DIRECTION. Identifier of a ROUTE LINk. Reference to a ROUTE LINk. Type for identifier of a DESTINATION. Reference to a PLACE visited by a VEHICLE JOURNEY. Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested. Reference to a TOPOGRAPHIC PLACE. Names of place used to help identify the LINE. Short name of TOPOGRAPHIC PLACE. Should only be included if the detail level was requested. Identifier of a VEHICLE. Reference to a VEHICLE. Reference to a VEHICLE. Passenger load status of a VEHICLE. Identifier of a DRIVER Reference to a DRIVER. DataType for a NOTICe. Text annotation that applies to an element. Type for identifier of an Info Channel. Type for reference to an Info Channel.




© 2015 - 2025 Weber Informatics LLC | Privacy Policy