XML Schema "siri_journey-v2.0.xsd"
Target Namespace:
http://www.siri.org.uk/siri
Version:
2.0
Defined Components:
elements (25 global + 57 local), complexTypes (12), element groups (21)
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\Tony\eclipse_workspace\siri-20-java\xsd\siri_model\siri_journey-v2.0.xsd; see XML source
Includes Schemas (1):
siri_facility-v2.0.xsd [src]
Included in Schemas (7):
siri_datedVehicleJourney-v2.0.xsd [src], siri_discovery.xsd [src], siri_estimatedVehicleJourney-v2.0.xsd [src], siri_interchangeJourney-v2.0.xsd [src], siri_line-v2.0.xsd [src], siri_monitoredVehicleJourney-v2.0.xsd [src], siri_targetedVehicleJourney-v2.0.xsd [src]
Annotation
SIRI Common Journey Model.
All Element Summary (local elements unified by type)
ActualArrivalTime
Observed time of arrival of VEHICLE at stop.
Type:
xsd:dateTime
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
ActualDepartureTime
Observed time of departure of VEHICLE from stop.
Type:
xsd:dateTime
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
ActualHeadwayInterval
For frequency based services, observed interval between vehicles at stop.
Type:
PositiveDurationType
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
ActualQuayRef (type QuayRefStructure)
Physical QUAY actually used.
Type:
QuayRefStructure
Content:
simple
Defined:
locally within StopAssignmentStructure complexType; see XML source
AdditionalVehicleJourneyRef (type FramedVehicleJourneyRefStructure)
Refercence to other VEHICLE Journeys (+SIRI v2.0)
Type:
FramedVehicleJourneyRefStructure
Content:
complex, 2 elements
Defined:
locally within OperationalInfoGroup group; see XML source
AimedArrivalTime
Target arrival time of VEHICLE at stop according to latest working timetable.
Type:
xsd:dateTime
Content:
simple
Defined:
globally; see XML source
Used:
at 6 locations
AimedDepartureTime
Target departure time of VEHICLE from stop according to latest working timetable.
Type:
xsd:dateTime
Content:
simple
Defined:
globally; see XML source
Used:
at 4 locations
AimedHeadwayInterval
For frequency based services, target interval between vehicles at stop.
Type:
PositiveDurationType
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
AimedLatestPassengerAccessTime
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop.
Type:
xsd:dateTime
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
AimedQuayName (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
AimedQuayRef (type QuayRefStructure)
Type:
QuayRefStructure
Content:
simple
Defined:
locally at 2 locations
ArrivalBoardingActivity
Type of boarding and alighting allowed at stop.
Type:
ArrivalBoardingActivityEnumeration
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
ArrivalOperatorRefs (type OperatorRefStructure)
Type:
OperatorRefStructure
Content:
simple
Defined:
locally at 2 locations
ArrivalPlatformName
Bay or platform name.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 6 locations
ArrivalProximityText
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 1 location
ArrivalStatus
Classification of the timeliness of the visit according to a fixed list of values.
Type:
CallStatusEnumeration
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
ArrivalStopAssignment (type PlannedStopAssignmentStructure)
Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform).
Type:
PlannedStopAssignmentStructure
Content:
complex, 2 elements
Defined:
locally within AimedVehicleArrivalGroup group; see XML source
ArrivalStopAssignment (type StopAssignmentStructure)
Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform).
Type:
StopAssignmentStructure
Content:
complex, 4 elements
Defined:
locally within MonitoredStopArrivalStatusGroup group; see XML source
BlockRef (type BlockRefStructure)
Type:
BlockRefStructure
Content:
simple
Defined:
locally at 2 locations
BoardingStretch (type xsd:boolean)
Whether this is a Hail and Ride Stop.
Type:
xsd:boolean
Content:
simple
Defined:
locally within CallPropertyGroup group; see XML source
CallNote (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
CourseOfJourneyRef (type CourseOfJourneyRefStructure)
COURSE OF JOURNEY ('Run') that VEHICLE is running.
Type:
CourseOfJourneyRefStructure
Content:
simple
Defined:
locally within OperationalBlockGroup group; see XML source
DepartureBoardingActivity
Nature of boarding allowed at stop.
Type:
DepartureBoardingActivityEnumeration
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
DepartureOperatorRefs (type OperatorRefStructure)
Type:
OperatorRefStructure
Content:
simple
Defined:
locally at 2 locations
DeparturePlatformName
Departure QUAY ( Bay or platform) name.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 4 locations
DepartureProximityText
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 1 location
DepartureStatus
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values.
Type:
CallStatusEnumeration
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
DepartureStopAssignment (type PlannedStopAssignmentStructure)
Type:
PlannedStopAssignmentStructure
Content:
complex, 2 elements
Defined:
locally within AimedVehicleDepartureGroup group; see XML source
DepartureStopAssignment (type StopAssignmentStructure)
Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY.
Type:
StopAssignmentStructure
Content:
complex, 4 elements
Defined:
locally within MonitoredStopDepartureStatusGroup group; see XML source
DestinationAimedArrivalTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 2 locations
DestinationDisplay (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
DestinationDisplayAtOrigin (type NaturalLanguagePlaceNameStructure)
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
DestinationName
The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public.
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 1 location
DestinationName (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 3 locations
DestinationRef (type DestinationRefStructure)
Type:
DestinationRefStructure
Content:
simple
Defined:
locally at 3 locations
DestinationShortName (type NaturalLanguagePlaceNameStructure)
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards.
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
locally within JourneyEndNamesGroup group; see XML source
Direction
Description of a DIRECTION.
Type:
DirectionStructure
Content:
complex, 2 elements
Defined:
globally; see XML source
Used:
never
DirectionName (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
DirectionRef (type DirectionRefStructure)
Type:
DirectionRefStructure
Content:
simple
Defined:
locally at 20 locations
DistanceFromStop (type DistanceType)
Distance of VEHICLE from stop of CALL as measured along ROUTE track.
Type:
DistanceType
Content:
simple
Defined:
locally within StopProximityGroup group; see XML source
DriverName (type xsd:normalizedString)
The name oo the Driver or Crew +SIRI v2.0
Type:
xsd:normalizedString
Content:
simple
Defined:
locally within OperationalInfoGroup group; see XML source
DriverRef (type xsd:normalizedString)
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE.
Type:
xsd:normalizedString
Content:
simple
Defined:
locally within OperationalInfoGroup group; see XML source
EarliestExpectedDepartureTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 2 locations
ExpectedArrivalPredictionQuality (type PredictionQualityStructure)
Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times.
Type:
PredictionQualityStructure
Content:
complex, 4 elements
Defined:
locally within OnwardVehicleArrivalTimesGroup group; see XML source
ExpectedArrivalTime
Estimated time of arriival of VEHICLE at stop .
Type:
xsd:dateTime
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
ExpectedDeparturePredictionQuality (type PredictionQualityStructure)
Type:
PredictionQualityStructure
Content:
complex, 4 elements
Defined:
locally at 2 locations
ExpectedDepartureTime
Estimated time of departure of VEHICLE from stop.
Type:
xsd:dateTime
Content:
simple
Defined:
globally; see XML source
Used:
at 3 locations
ExpectedHeadwayInterval
For frequency based services, expected interval between vehicles at stop.
Type:
PositiveDurationType
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
ExpectedLatestPassengerAccessTime
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop.
Type:
xsd:dateTime
Content:
simple
Defined:
globally; see XML source
Used:
at 1 location
ExpectedQuayRef (type QuayRefStructure)
Physical QUAY to use accoring to the real-time prediction.
Type:
QuayRefStructure
Content:
simple
Defined:
locally within StopAssignmentStructure complexType; see XML source
FirstOrLastJourney
Whether journey is first or last journey of day.
Type:
FirstOrLastJourneyEnumeration
Content:
simple
Defined:
globally; see XML source
Used:
at 2 locations
HeadwayService (type xsd:boolean)
Type:
xsd:boolean
Content:
simple
Defined:
locally at 4 locations
HigherTimeLimit (type xsd:dateTime)
Upper bound on time of for predictios for confidence level if different from defaults +SIRI v2.0
Type:
xsd:dateTime
Content:
simple
Defined:
locally within PredictionQualityStructure complexType; see XML source
JourneyNote
Additional descriptive text associated with journey.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 1 location
LinkDistance (in ProgressBetweenStops)
The total distance in metres between the previous stop and the next stop.
Type:
xsd:decimal
Content:
simple
Defined:
locally within ProgressBetweenStopsStructure complexType; see XML source
LowerTimeLimit (type xsd:dateTime)
Lower bound on time of for prediction for confidence level if different from defaults +SIRI v2.0
Type:
xsd:dateTime
Content:
simple
Defined:
locally within PredictionQualityStructure complexType; see XML source
NumberOfStopsAway (type xsd:nonNegativeInteger)
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track.
Type:
xsd:nonNegativeInteger
Content:
simple
Defined:
locally within StopProximityGroup group; see XML source
OnwardCall (in OnwardCalls)
Type:
OnwardCallStructure
Content:
complex, 33 elements
Defined:
locally within OnwardCallsStructure complexType; see XML source
OperationsContact (type SimpleContactStructure)
Contact details for use by operational staff.
Type:
SimpleContactStructure
Content:
complex, 2 elements
Defined:
locally within JourneyInfoGroup group; see XML source
OriginAimedDepartureTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 2 locations
OriginDisplay (type NaturalLanguageStringStructure)
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
OriginDisplayAtDestination (type NaturalLanguagePlaceNameStructure)
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
locally at 2 locations
OriginName
The name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards.
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 1 location
OriginName (type NaturalLanguagePlaceNameStructure)
Name of the origin of the journey.
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
locally within JourneyEndNamesGroup group; see XML source
OriginShortName (type NaturalLanguagePlaceNameStructure)
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards.
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
locally within JourneyEndNamesGroup group; see XML source
Percentage (in ProgressBetweenStops)
Percentage along link that VEHICLE has travelled.
Type:
xsd:decimal
Content:
simple
Defined:
locally within ProgressBetweenStopsStructure complexType; see XML source
Percentile (type xsd:decimal)
Percentile associated with range as specified by lower and upper bound +SIRI v2.0
Type:
xsd:decimal
Content:
simple
Defined:
locally within PredictionQualityStructure complexType; see XML source
PhoneNumber (type PhoneType)
Type:
PhoneType
Content:
simple
Defined:
locally at 2 locations
PredictionLevel (type QualityIndexEnumeration)
An approxiimate characterisation of prediction quality as one of five values .
Type:
QualityIndexEnumeration
Content:
simple
Defined:
locally within PredictionQualityStructure complexType; see XML source
ProvisionalExpectedDepartureTime (type xsd:dateTime)
Type:
xsd:dateTime
Content:
simple
Defined:
locally at 2 locations
PublicContact (type SimpleContactStructure)
Contact details for use by members of public.
Type:
SimpleContactStructure
Content:
complex, 2 elements
Defined:
locally within JourneyInfoGroup group; see XML source
RequestStop (type xsd:boolean)
Whether Vehicle stops only if requested explicitly by passenger.
Type:
xsd:boolean
Content:
simple
Defined:
locally within CallPropertyGroup group; see XML source
Url (type xsd:anyURI)
Type:
xsd:anyURI
Content:
simple
Defined:
locally at 3 locations
VehicleJourneyName (type NaturalLanguageStringStructure)
For train services with named journeys.
Type:
NaturalLanguageStringStructure
Content:
simple, 1 attribute
Defined:
locally within JourneyInfoGroup group; see XML source
Via (type ViaNameStructure)
Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton.
Type:
ViaNameStructure
Content:
complex, 4 elements
Defined:
locally within JourneyEndNamesGroup group; see XML source
ViaName
Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton.
Type:
NaturalLanguagePlaceNameStructure
Content:
simple, 1 attribute
Defined:
globally; see XML source
Used:
at 1 location
ViaPriority (in Via)
Relative priority to give to VIA name in displays. 1=high.
Type:
xsd:nonNegativeInteger
Content:
simple
Defined:
locally within ViaNameStructure complexType; see XML source
Complex Type Summary
AbstractCallStructure
Type for Abstract CALL at stop.
Content:
complex, 4 elements
Defined:
globally; see XML source
Used:
never
AbstractMonitoredCallStructure
Type for Abstract CALL at stop.
Content:
complex, 4 elements
Defined:
globally; see XML source
Used:
at 3 locations
DestinationStructure
Type for Information about a DESTINATION.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
never
DirectionStructure
Type for DIRECTION.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 3 locations
OnwardCallsStructure
Type for CALLing pattern for JOURNEY PATTERN.
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
OnwardCallStructure
Type Onwards CALLs at stop.
Content:
complex, 33 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
PlannedStopAssignmentStructure
Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 2 locations
PredictionQualityStructure
Type for Prediction Quality quantifcation.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 2 locations
ProgressBetweenStopsStructure
Type for Progress between stops.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 1 location
SimpleContactStructure
Type for Simple Contact Details.
Content:
complex, 2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 2 locations
StopAssignmentStructure
Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 2 locations
ViaNameStructure
Type for VIA NAMes structure.
Content:
complex, 4 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
Element Group Summary
AimedCallGroup
Elements describing the the targeted CALL of a VEHICLE at a stop.
Content:
12 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 2 locations
AimedVehicleArrivalGroup
Elements describing the the arrival of a VEHICLE at a stop.
Content:
5 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
AimedVehicleDepartureGroup
Elements describing the the departure of a VEHICLE from a stop.
Content:
5 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
CallNoteGroup
Annotations of the CALL.
Content:
1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 2 locations
CallPropertyGroup
Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL.
Content:
5 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 4 locations
HeadwayIntervalGroup
Elements describing the HEADWAY INTERVALs.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 3 locations
JourneyEndNamesGroup
End names for journey.
Content:
9 elements
Defined:
globally; see XML source
Includes:
definitions of 9 elements
Used:
at 2 locations
JourneyEndTimesGroup
Call times for journey.
Content:
4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 1 location
JourneyInfoGroup
Elements describing a VEHICLE JOURNEY.
Content:
4 elements
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
at 3 locations
MonitoredStopArrivalStatusGroup
Elements describing the the arrival status of a VEHICLE at a stop.
Content:
6 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
at 2 locations
MonitoredStopDepartureStatusGroup
Elements describing the the departure status of a VEHICLE from a stop.
Content:
6 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
at 2 locations
OnwardsCallGroup
Elements describing the CALL.
Content:
26 elements
Defined:
globally; see XML source
Used:
at 2 locations
OnwardVehicleArrivalTimesGroup
Elements for Arrival in onward CALl.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
OnwardVehicleDepartureTimesGroup
Elements for departure in ONWARD CALL.
Content:
5 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 1 location
OperationalBlockGroup
Operational information about the monitored VEHICLE JOURNEY.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 3 locations
OperationalInfoGroup
Operational information about the monitored VEHICLE JOURNEY.
Content:
7 elements
Defined:
globally; see XML source
Includes:
definitions of 5 elements
Used:
at 3 locations
PassengerDepartureTimesGroup
Passenget arrivel times at STOP PLACE in order to meet VEHICLEdeparture times for CALL.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 2 locations
StopProximityGroup
Elements describing the distance from the stop of a VEHICLE.
Content:
2 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 2 locations
VehicleArrivalTimesGroup
Arrival times for CALL.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 3 locations
VehicleDepartureTimesGroup
Departure times for CALL.
Content:
3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 3 locations
VehicleJourneyInfoGroup
Common information about a VEHICLE JOURNEY.
Content:
21 elements
Defined:
globally; see XML source
Used:
at 3 locations
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2011 rel. 2 sp1 (x64) (http://www.altova.com) by Christophe Duquesne (Dryade) -->
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" id="siri_journey" targetNamespace="http://www.siri.org.uk/siri" version="2.0" xmlns="http://www.siri.org.uk/siri" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:appinfo>
<Metadata xmlns="http://www.govtalk.gov.uk/CM/gms-xs">
<Aggregation>main schema</Aggregation>
<Audience>e-service developers</Audience>
<Contributor>Cen TC278 WG3 SG7 Team</Contributor>
<Coverage>Europe</Coverage>
<Creator>
Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk
</Creator>
<Date>
<Created>2004-03-05</Created>
</Date>
<Date>
<Modified>2004-10-06</Modified>
</Date>
<Date>
<Modified>2005-05-11</Modified>
</Date>
<Date>
<Modified>2005-11-15</Modified>
</Date>
<Date>
<Modified>2007-03-29</Modified>
</Date>
<Date>
<Modified>2008-11-13</Modified>
Correct Cardinalities on SIRI DESTINATION REF Structure
</Date>
<Date>
<Modified>2011-04-18</Modified>
siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com
</Date>
<Date>
<Modified>2012-03-22</Modified>
SIRI 2.0
[VDV] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group
[VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group
[VDV] Add LatestExpectedArrivalTimeForVehicle to Departure Times Group
[VDV] Add ViaPriority to ViaNames using a new ViaNameStructure SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM
[VDV] Add Velocity to MonitoredVehicleJourney SIRI-SM and SIRI-VM
Add JOURNEY PARTs to Vehicle INFO TODO
[VDV] Add Public and Contact Details to JourneyInfo : SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM
[VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM

[MTA] Add ArrivalProximityText to Arrival Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM
[MTA] Add ArrivalProximityText to Departure Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM

[FR] Add AimedLatestPassengerAccessTime to TargetedCall : SIRI-ST
[FR] Add AimedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM
[FR] Add ExpectedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM
[FR] add ArrivalOperatorRefs and DepartureOperatorRefs to Call arrival and Departure

[Fr] Add FirstOrLastJourney to JourneyTimesGroup : SIRI-SM and SIRI-VM
[DE] Add Driver Name
</Date>
<Date>
<Modified>2012-04-27</Modified>
SIRI 2.0
[MTA] Add DistanceFromSTop and NumberOFStops away to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-ET
[NeTEx] Add Driver/Crew Ref

[DE] Add ExpectedDeparturePredictionQuality to OnwardVehicleDepartureTimes
</Date>
<Date>
<Modified>2013-01-25</Modified>
WB: elements LowerTimeLimit and UpperTimeLimit optional in prediction quality
</Date>
<Date>
<Modified>2013-02-11</Modified>
ArrivalStopAssignment and DepartureStopAssignment added to DatedCall: SIRI:PT
Correction: DestinationDisplay unbounded to allow multiple languages
</Date>
<Date>
<Modified>2014-06-20</Modified>
[ch] Add origin display wherever destination display as per Cologne meeting (siri-Journey-v2.0.xsd
* [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey-v2.0.xsd)
</Date>
<Description>
<p>
SIRI is a European CEN technical standard for the exchange of real-time information .
</p>
<p>This subschema defines common journey elements.</p>
</Description>
<Format>
<MediaType>text/xml</MediaType>
<Syntax>http://www.w3.org/2001/XMLSchema</Syntax>
<Description>XML schema, W3C Recommendation 2001</Description>
</Format>
<Identifier>
{http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_journey.xsd
</Identifier>
<Language>[ISO 639-2/B] ENG</Language>
<Publisher>Kizoom, 109-123 Clifton Street, London EC4A 4LD</Publisher>
<Relation>
<Requires>
http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd
</Requires>
</Relation>
<Rights>
Unclassified
<Copyright>CEN, VDV, RTIG 2004-2012</Copyright>
</Rights>
<Source>
<ul>
<li>
Derived from the VDV, RTIG CML and Trident standards.
</li>
</ul>
</Source>
<Status>Version 2.0 Draft</Status>
<Subject>
<Category>
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
</Category>
<Project>CEN TC278 WG3 SG7</Project>
</Subject>
<Title>
SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements
</Title>
<Type>Standard</Type>
</Metadata>
</xsd:appinfo>
<xsd:documentation>SIRI Common Journey Model.</xsd:documentation>
</xsd:annotation>
<!-- ======================================================================= -->
<xsd:include schemaLocation="siri_facility-v2.0.xsd"/>
<!-- ======================================================================= -->
<!-- ==== VEHICLEJOURNEY ================================================================== -->
<xsd:group name="JourneyInfoGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing a VEHICLE JOURNEY. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul DATED VEHICLE JOURNEYs of the timetable. Each real-time journey (e.g. ESTIMATED VEHICLE JOURNEY or MONITORED VEHICLE JORUNEY) takes its values from the DATED VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="VehicleJourneyName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
For train services with named journeys. Train name, e.g. &#8220;West Coast Express&#8221;. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="JourneyNote"/>
<xsd:element minOccurs="0" name="PublicContact" type="SimpleContactStructure">
<xsd:annotation>
<xsd:documentation>
Contact details for use by members of public. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="OperationsContact" type="SimpleContactStructure">
<xsd:annotation>
<xsd:documentation>
Contact details for use by operational staff. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="SimpleContactStructure">
<xsd:annotation>
<xsd:documentation>Type for Simple Contact Details.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="PhoneNumber" type="PhoneType">
<xsd:annotation>
<xsd:documentation>Phone number +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Url" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>Url for contact +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:group name="VehicleJourneyInfoGroup">
<xsd:annotation>
<xsd:documentation>
Common information about a VEHICLE JOURNEY. (Similar to VDV TripInfo)
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group minOccurs="0" ref="ServiceInfoGroup"/>
<xsd:group minOccurs="0" ref="JourneyEndNamesGroup"/>
<xsd:group ref="JourneyInfoGroup"/>
<xsd:group minOccurs="0" ref="JourneyEndTimesGroup"/>
</xsd:sequence>
</xsd:group>
<xsd:group name="JourneyEndNamesGroup">
<xsd:annotation>
<xsd:documentation>End names for journey.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="OriginRef"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Name of the origin of the journey. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginShortName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplayAtOrigin" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
DIRECTION name shown for jurney at the origin. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Via" type="ViaNameStructure">
<xsd:annotation>
<xsd:documentation>
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.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="DestinationRef">
<xsd:annotation>
<xsd:documentation>Reference to a DESTINATION.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationShortName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplayAtDestination" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Origin name shown for jourey at the destination +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="ViaNameStructure">
<xsd:annotation>
<xsd:documentation>Type for VIA NAMes structure.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="PlaceNameStructure">
<xsd:sequence>
<xsd:element default="2" minOccurs="0" name="ViaPriority" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
Relative priority to give to VIA name in displays. 1=high. Default is 2. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- ==== LINE ROUTE and destination elements======================================================== -->
<xsd:complexType name="DestinationStructure">
<xsd:annotation>
<xsd:documentation>Type for Information about a DESTINATION.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="DestinationRef" type="DestinationRefStructure">
<xsd:annotation>
<xsd:documentation>Identifer of Destinatioin</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" name="DestinationName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Name of Destination</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="OriginName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
The name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ViaName" type="NaturalLanguagePlaceNameStructure">
<xsd:annotation>
<xsd:documentation>
Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public. Note when used in a CALL, this is the Dynamic Destination Display: since vehicles can change their destination during a journey, the destination included here should be what the VEHICLE will display when it reaches the stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- =====Times================================================================== -->
<xsd:group name="JourneyEndTimesGroup">
<xsd:annotation>
<xsd:documentation>Call times for journey.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="false" minOccurs="0" name="HeadwayService" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="OriginAimedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Timetabled departure time from Origin.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="DestinationAimedArrivalTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Timetabled arrival time at Destination.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="FirstOrLastJourney"/>
</xsd:sequence>
</xsd:group>
<xsd:element default="unspecified" name="FirstOrLastJourney" type="FirstOrLastJourneyEnumeration">
<xsd:annotation>
<xsd:documentation>
Whether journey is first or last journey of day. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="JourneyNote" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Additional descriptive text associated with journey. Inherited property.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Direction" type="DirectionStructure">
<xsd:annotation>
<xsd:documentation>Description of a DIRECTION.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="DirectionStructure">
<xsd:annotation>
<xsd:documentation>Type for DIRECTION.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>Identifer of DIRECTION,</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DirectionName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Description of DIRECTION. (Unbounded since SIRI 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:group name="OperationalInfoGroup">
<xsd:annotation>
<xsd:documentation>
Operational information about the monitored VEHICLE JOURNEY.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="OperationalBlockGroup"/>
<xsd:element minOccurs="0" ref="VehicleJourneyRef"/>
<xsd:element minOccurs="0" ref="VehicleRef"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="AdditionalVehicleJourneyRef" type="FramedVehicleJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>Refercence to other VEHICLE Journeys (+SIRI v2.0)</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="DriverRef" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>
A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="DriverName" type="xsd:normalizedString">
<xsd:annotation>
<xsd:documentation>The name oo the Driver or Crew +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="OperationalBlockGroup">
<xsd:annotation>
<xsd:documentation>
Operational information about the monitored VEHICLE JOURNEY.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="BlockRef" type="BlockRefStructure">
<xsd:annotation>
<xsd:documentation>BLOCK that VEHICLE is running.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="CourseOfJourneyRef" type="CourseOfJourneyRefStructure">
<xsd:annotation>
<xsd:documentation>
COURSE OF JOURNEY ('Run') that VEHICLE is running.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="ProgressBetweenStopsStructure">
<xsd:annotation>
<xsd:documentation>Type for Progress between stops.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="LinkDistance" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation>
The total distance in metres between the previous stop and the next stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Percentage" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation>Percentage along link that VEHICLE has travelled.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<!-- ===== CALL =============================================================== -->
<xsd:complexType name="AbstractCallStructure">
<xsd:annotation>
<xsd:documentation>Type for Abstract CALL at stop.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="StopPointInSequenceGroup"/>
</xsd:sequence>
</xsd:complexType>
<!-- =====Aimed Call====================================================== -->
<xsd:group name="AimedCallGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the the targeted CALL of a VEHICLE at a stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="AimedVehicleArrivalGroup"/>
<xsd:group ref="AimedVehicleDepartureGroup"/>
<xsd:element minOccurs="0" ref="AimedLatestPassengerAccessTime"/>
<xsd:element minOccurs="0" ref="AimedHeadwayInterval"/>
</xsd:sequence>
</xsd:group>
<xsd:group name="AimedVehicleArrivalGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the the arrival of a VEHICLE at a stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="AimedArrivalTime"/>
<xsd:element minOccurs="0" ref="ArrivalPlatformName"/>
<xsd:element minOccurs="0" ref="ArrivalBoardingActivity"/>
<xsd:element minOccurs="0" name="ArrivalStopAssignment" type="PlannedStopAssignmentStructure">
<xsd:annotation>
<xsd:documentation>
Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ArrivalOperatorRefs" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="AimedVehicleDepartureGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the the departure of a VEHICLE from a stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="AimedDepartureTime"/>
<xsd:element minOccurs="0" ref="DeparturePlatformName"/>
<xsd:element minOccurs="0" ref="DepartureBoardingActivity"/>
<xsd:element minOccurs="0" name="DepartureStopAssignment" type="PlannedStopAssignmentStructure"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DepartureOperatorRefs" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- =====MONITORED JOURNEY CALL============================================================ -->
<xsd:complexType name="AbstractMonitoredCallStructure">
<xsd:annotation>
<xsd:documentation>Type for Abstract CALL at stop.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="ContextualisedStopPointInSequenceGroup"/>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Elements describing the the arrival status of a VEHICLE at a stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="ArrivalStatus"/>
<xsd:element minOccurs="0" ref="ArrivalProximityText"/>
<xsd:element minOccurs="0" ref="ArrivalPlatformName">
<xsd:annotation>
<xsd:documentation>
Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel to arrive at.Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is
(i) any arrival platform on any related dated timetable element,
(ii) any departure platform name on this estimated element;
(iii) any departure platform name on any related dated timetable CALL.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="ArrivalBoardingActivity">
<xsd:annotation>
<xsd:documentation>
Nature of boarding and alighting allowed at stop. Default is 'Alighting'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ArrivalStopAssignment" type="StopAssignmentStructure">
<xsd:annotation>
<xsd:documentation>
Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="ArrivalOperatorRefs" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>
Elements describing the the departure status of a VEHICLE from a stop.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="DepartureStatus"/>
<xsd:element minOccurs="0" ref="DepartureProximityText"/>
<xsd:element minOccurs="0" ref="DeparturePlatformName">
<xsd:annotation>
<xsd:documentation>
Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable..
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="DepartureBoardingActivity"/>
<xsd:element minOccurs="0" name="DepartureStopAssignment" type="StopAssignmentStructure">
<xsd:annotation>
<xsd:documentation>
Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DepartureOperatorRefs" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- ======MONITORED CALL================================================= -->
<xsd:group name="CallPropertyGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="TimingPoint"/>
<xsd:element default="false" minOccurs="0" name="BoardingStretch" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether this is a Hail and Ride Stop. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="false" minOccurs="0" name="RequestStop" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="OriginDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (+Siri 2.0)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="DestinationDisplay" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="CallNoteGroup">
<xsd:annotation>
<xsd:documentation>Annotations of the CALL.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="CallNote" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Text annotation that applies to this CALL.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- =====ONWARDS CALL==================================================== -->
<xsd:complexType name="OnwardCallsStructure">
<xsd:annotation>
<xsd:documentation>Type for CALLing pattern for JOURNEY PATTERN.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="OnwardCall" type="OnwardCallStructure"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="OnwardCallStructure">
<xsd:annotation>
<xsd:documentation>Type Onwards CALLs at stop.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="AbstractMonitoredCallStructure">
<xsd:sequence>
<xsd:sequence>
<xsd:element minOccurs="0" ref="VehicleAtStop"/>
<xsd:element minOccurs="0" ref="TimingPoint"/>
</xsd:sequence>
<xsd:group ref="OnwardsCallGroup"/>
<xsd:element minOccurs="0" ref="Extensions"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:group name="OnwardsCallGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the CALL. Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="OnwardVehicleArrivalTimesGroup"/>
<xsd:group ref="PassengerDepartureTimesGroup"/>
<xsd:group ref="HeadwayIntervalGroup"/>
<xsd:group ref="StopProximityGroup"/>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>Elements for Arrival in onward CALl.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="AimedArrivalTime"/>
<xsd:element minOccurs="0" ref="ExpectedArrivalTime"/>
<xsd:element minOccurs="0" name="ExpectedArrivalPredictionQuality" type="PredictionQualityStructure">
<xsd:annotation>
<xsd:documentation>
Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:annotation>
<xsd:documentation>Elements for departure in ONWARD CALL.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="AimedDepartureTime">
<xsd:annotation>
<xsd:documentation>
Target departure time of VEHICLE according to latest working timetable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="ExpectedDepartureTime">
<xsd:annotation>
<xsd:documentation>
Estimated time of departure of VEHICLE, most likely taking into account all control actions such as waiting.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ProvisionalExpectedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="EarliestExpectedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ExpectedDeparturePredictionQuality" type="PredictionQualityStructure">
<xsd:annotation>
<xsd:documentation>
Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:group name="HeadwayIntervalGroup">
<xsd:annotation>
<xsd:documentation>Elements describing the HEADWAY INTERVALs.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="AimedHeadwayInterval"/>
<xsd:element minOccurs="0" ref="ExpectedHeadwayInterval"/>
</xsd:sequence>
</xsd:group>
<xsd:group name="StopProximityGroup">
<xsd:annotation>
<xsd:documentation>
Elements describing the distance from the stop of a VEHICLE. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="DistanceFromStop" type="DistanceType">
<xsd:annotation>
<xsd:documentation>
Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="NumberOfStopsAway" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="PredictionQualityStructure">
<xsd:annotation>
<xsd:documentation>Type for Prediction Quality quantifcation.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="PredictionLevel" type="QualityIndexEnumeration">
<xsd:annotation>
<xsd:documentation>
An approxiimate characterisation of prediction quality as one of five values . +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:sequence minOccurs="0">
<xsd:element default="0.9" minOccurs="0" name="Percentile" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation>
Percentile associated with range as specified by lower and upper bound +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="LowerTimeLimit" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Lower bound on time of for prediction for confidence level if different from defaults +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="HigherTimeLimit" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Upper bound on time of for predictios for confidence level if different from defaults +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:complexType name="StopAssignmentStructure">
<xsd:annotation>
<xsd:documentation>
Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="AimedQuayRef" type="QuayRefStructure">
<xsd:annotation>
<xsd:documentation>
Physical QUAY to use according to the planned timetable. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="AimedQuayName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>
Scheduled Platform name. Can be used to indicate platfrom change. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ExpectedQuayRef" type="QuayRefStructure">
<xsd:annotation>
<xsd:documentation>
Physical QUAY to use accoring to the real-time prediction. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="ActualQuayRef" type="QuayRefStructure">
<xsd:annotation>
<xsd:documentation>Physical QUAY actually used. +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ======================================================================= -->
<xsd:complexType name="PlannedStopAssignmentStructure">
<xsd:annotation>
<xsd:documentation>
Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" name="AimedQuayRef" type="QuayRefStructure">
<xsd:annotation>
<xsd:documentation>
Physical QUAY to use according to the planned timetable. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="AimedQuayName" type="NaturalLanguageStringStructure">
<xsd:annotation>
<xsd:documentation>Scheduled Platform name. +SIRI v2.0</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- =====Arrival================================================================== -->
<xsd:element name="AimedArrivalTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Target arrival time of VEHICLE at stop according to latest working timetable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ActualArrivalTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Observed time of arrival of VEHICLE at stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ExpectedArrivalTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Estimated time of arriival of VEHICLE at stop .</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ArrivalStatus" type="CallStatusEnumeration">
<xsd:annotation>
<xsd:documentation>
Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, &#8220;Enroute&#8221;, &#8220;5 Km&#8221;, &#8220;Approaching&#8221;. May depend on the policy of the OPERATOR, for example show &#8220;Approaching&#8221; if less than 200metres away from stop. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Bay or platform name. Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is (i) any arrival platform on any related dated timetable element, (ii) any departure platform name on this estimated element; (iii) any departure platform name on any related dated timetable CALL.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="alighting" name="ArrivalBoardingActivity" type="ArrivalBoardingActivityEnumeration">
<xsd:annotation>
<xsd:documentation>
Type of boarding and alighting allowed at stop. Default is 'Alighting'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group name="VehicleArrivalTimesGroup">
<xsd:annotation>
<xsd:documentation>Arrival times for CALL.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="AimedArrivalTime">
<xsd:annotation>
<xsd:documentation>
Target arrival time of VEHICLE according to latest working timetable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:element minOccurs="0" ref="ActualArrivalTime">
<xsd:annotation>
<xsd:documentation>Observed time of arrival of VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="ExpectedArrivalTime">
<xsd:annotation>
<xsd:documentation>Estimated time of arriival of VEHICLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:group>
<!-- =====Departure================================================================== -->
<xsd:element name="AimedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Target departure time of VEHICLE from stop according to latest working timetable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ActualDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Observed time of departure of VEHICLE from stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ExpectedDepartureTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>Estimated time of departure of VEHICLE from stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="AimedLatestPassengerAccessTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ExpectedLatestPassengerAccessTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI 2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="DepartureStatus" type="CallStatusEnumeration">
<xsd:annotation>
<xsd:documentation>
Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, &#8220;Boarding&#8221;, &#8220;GatesClosed&#8221;. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>
Departure QUAY ( Bay or platform) name. Inheritable property.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element default="boarding" name="DepartureBoardingActivity" type="DepartureBoardingActivityEnumeration">
<xsd:annotation>
<xsd:documentation>
Nature of boarding allowed at stop. Default is 'Boarding'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group name="VehicleDepartureTimesGroup">
<xsd:annotation>
<xsd:documentation>Departure times for CALL.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="AimedDepartureTime">
<xsd:annotation>
<xsd:documentation>
Target departure time of VEHICLE according to latest working timetable.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice>
<xsd:element minOccurs="0" ref="ActualDepartureTime">
<xsd:annotation>
<xsd:documentation>Observed time of departure of VEHICLE from stop.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="ExpectedDepartureTime">
<xsd:annotation>
<xsd:documentation>
Estimated time of departure of VEHICLE from stop. May include waiting time. For people on a VEHICLE this is the time that would normally be shown.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:group>
<xsd:group name="PassengerDepartureTimesGroup">
<xsd:annotation>
<xsd:documentation>
Passenget arrivel times at STOP PLACE in order to meet VEHICLEdeparture times for CALL.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="AimedLatestPassengerAccessTime">
<xsd:annotation>
<xsd:documentation>
Target Latest time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times as itmay include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="ExpectedLatestPassengerAccessTime">
<xsd:annotation>
<xsd:documentation>
Expected Latest time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times as it may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data) If absent assume to be the same as Earliest expected departure time, +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<!-- =====Interval================================================================= -->
<xsd:element name="AimedHeadwayInterval" type="PositiveDurationType">
<xsd:annotation>
<xsd:documentation>
For frequency based services, target interval between vehicles at stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ExpectedHeadwayInterval" type="PositiveDurationType">
<xsd:annotation>
<xsd:documentation>
For frequency based services, expected interval between vehicles at stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ActualHeadwayInterval" type="PositiveDurationType">
<xsd:annotation>
<xsd:documentation>
For frequency based services, observed interval between vehicles at stop.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!-- ====================================================================== -->
</xsd:schema>
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:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
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/