| + |
validityConditions |
mandatory |
1..1 |
unknown |
|
Used to specify a set of temporal conditions that can be associated with the ServiceJourney, for example that the corresponding journey only applies on particular days of a period (indicated by ValidDayBits, “Verkehrstagebitfeld”). |
| ++ |
AvailabilityCondition |
mandatory |
1..1 |
unknown |
|
Only a single occurence is allowed. The following elements are mandatory here, any other elements of AvailabilityCondition are not allowed or will be ignored. |
| + |
keyList |
expected |
1..1 |
unknown |
|
KEY LIST with the KEY VALUEs belonjing to the SERVICE JOURNEY. Will contain the SJYID. |
| ++ |
KeyValue |
mandatory |
1..1 |
unknown |
|
A KeyValue pair with the Key SJYID must exist. The Value contains a valid Swiss Journey ID. |
| +++ |
Key |
mandatory |
1..1 |
unknown |
|
|
| +++ |
Value |
mandatory |
1..1 |
unknown |
|
|
| + |
privateCodes |
expected |
1..1 |
unknown |
|
|
| ++ |
PrivateCode |
expected |
1..1 |
unknown |
|
|
| + |
Extensions |
optional |
1..1 |
unknown |
|
Used to indicate Facility changes. |
| ++ |
facilities |
optional |
1..1 |
unknown |
|
|
| +++ |
Facility |
optional |
1..1 |
unknown |
|
|
| ++++ |
ServiceFacilitySetRef |
mandatory |
1..1 |
unknown |
|
|
| + |
TransportMode |
optional |
1..1 |
unknown |
|
|
| + |
TypeOfProductCategoryRef |
mandatory |
1..1 |
unknown |
|
|
| + |
TypeOfServiceRef |
optional |
1..1 |
unknown |
|
|
| + |
noticeAssignments |
optional |
1..1 |
unknown |
|
The complete set of all applicable notices. Attention: Notices may be restricted to a given set of stops. |
| ++ |
NoticeAssignment |
optional |
1..1 |
unknown |
|
|
| + |
occupancies |
optional |
1..1 |
unknown |
|
|
| ++ |
OccupancyView |
optional |
1..1 |
unknown |
|
|
| + |
ServiceAlteration |
mandatory |
1..1 |
unknown |
|
Only the value planned is allowed. |
| + |
DepartureTime |
expected |
1..1 |
unknown |
|
|
| + |
DepartureDayOffset |
optional |
1..1 |
unknown |
|
|
| + |
TimeDemandTypeRef |
mandatory |
1..1 |
unknown |
|
The timing behaviour is defined here. We allow only one TimeDemandType per ServiceJourney. |
| + |
LineRef |
mandatory |
1..1 |
unknown |
|
|
| + |
DirectionType |
mandatory |
1..1 |
unknown |
|
Allowed are: inbound, outbound |
| + |
trainNumbers |
mandatory |
1..1 |
unknown |
|
|
| ++ |
TrainNumberRef |
mandatory |
1..1 |
unknown |
|
|
| + |
Destination |
expected |
1..1 |
unknown |
|
|
| + |
parts |
optional |
1..1 |
unknown |
|
For some use cases e.g. change of Facilities during ServiceJourney |
| ++ |
JourneyPartRef |
expected |
1..1 |
unknown |
|
|