@@ -87,9 +86,9 @@ Rail transport, Roads and Road transport
Reference to a CLASS OF USE.
-
+
-
+
@@ -697,9 +696,9 @@ Rail transport, Roads and Road transport
Reference to a TYPE OF PAYMENT METHOD.
-
+
-
+
@@ -1056,4 +1055,102 @@ See ERA B.4 7037 Characteristic description code.
+
+
+ Type for identifier of a TYPE OF Booking SERVICE.
+
+
+
+
+
+ Allowed Booking Services. +V2.1
+
+
+
+
+ tOMP.
+
+
+
+
+ OSDM.
+
+
+
+
+ BOB.
+
+
+
+
+ TRIAS, VDV 431.
+
+
+
+
+ OJP service (only availability and price).
+
+
+
+
+ Other means of payment .
+
+
+
+
+
+
+
+ supported booking process steps. +V2.1
+
+
+
+
+ Trip Planning
+
+
+
+
+ Getting price information
+
+
+
+
+ simple availability request
+
+
+
+
+ booking
+
+
+
+
+ Reservation.
+
+
+
+
+ Fullfillment.
+
+
+
+
+ The full process including fullfillment.
+
+
+
+
+ Other means of payment .
+
+
+
+
+
+
+ List of supported booking process steps.
+
+
+
+
diff --git a/xsd/netex_framework/netex_reusableComponents/netex_serviceRestrictions_version.xsd b/xsd/netex_framework/netex_reusableComponents/netex_serviceRestrictions_version.xsd
index b5e69e60f..1fc0ddd07 100644
--- a/xsd/netex_framework/netex_reusableComponents/netex_serviceRestrictions_version.xsd
+++ b/xsd/netex_framework/netex_reusableComponents/netex_serviceRestrictions_version.xsd
@@ -1,6 +1,7 @@
+
@@ -57,8 +58,7 @@
http://www.netex.org.uk/schemas/1.0/PATH/netex_prereqfile.xsdUnclassified
- CEN, Crown Copyright 2009-2023
-
+ CEN, Crown Copyright 2009-2023
Derived from the Transmodel, VDV, TransXChange, NEPTUNE, BISON and Trident standards.
@@ -181,7 +181,12 @@ Rail transport, Roads and Road transport
-
+
+
+ Dummy Supertype for BookingArrangement elements.
+
+
+ Details of the booking arrangements for a given LINE, STOP, SERVICE etc.
@@ -271,7 +276,12 @@ Rail transport, Roads and Road transport
- URL for booking. +V1.1
+ Static URL for booking. -V2.1 depreciated
+
+
+
+
+ new structure to defines how this can be booked.
@@ -347,7 +357,146 @@ Rail transport, Roads and Road transport
-
+
+
+
+ Defines an open classification of what services are supported in this booking service. + v2.1
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Identifier of TYPE OF BOOKING SERVICE.
+
+
+
+
+
+
+
+
+ Type for a TYPE OF BOOKING SERVICE.
+
+
+
+
+
+
+
+
+
+
+
+ Elements for TYPE OF BOOKING SERVICE.
+
+
+
+
+ Booking service value.
+
+
+
+
+
+
+ Type for containment in frame of SERVICE BOOKING URLs
+
+
+
+
+
+
+
+ Static URL for booking. It might also be a parameterised URL as long as it is still a valid URL. Better however to use BookingDeepUrl or BookingService. +V1.1
+
+
+
+
+ Dynamic URL for booking. +V2.0
+
+
+
+
+ Service definition for booking. +V2.0
+
+
+
+
+
+
+
+
+
+ A booking link structure. +V2.1
+
+
+
+
+ The endpoint that is used for the deep link.
+
+
+
+
+ The parameters and their meaning for the end point. The list of allowed parameters should be taken from an approved list in the standard.
+
+
+
+
+
+
+ A booking service structure. +V2.1
+
+
+
+
+ The definition of the BOOKING SERVICE. +V2.1
+
+
+
+
+
+
+ The information that is needed for the booking service. +V2.1
+
+
+
+
+ The endpoint that is used for the deep link.
+
+
+
+
+ the version.
+
+
+
+
+ Service protocol.
+
+
+
+
+ Service protocol.
+
+
+
+
+
Type for containment in frame of SERVICE BOOKING ARRANGEMENTs
@@ -355,7 +504,7 @@ Rail transport, Roads and Road transport
-
+ Information on booking rules and additional data allowing the user to take the decision to book a service and to undertake the booking of a LOCAL SERVICE.
@@ -371,13 +520,13 @@ Rail transport, Roads and Road transport
-
-
+
+
-
+ Type for a SERVICE BOOKING ARRANGEMENT.
@@ -392,21 +541,17 @@ Rail transport, Roads and Road transport
-
-
- Details for a BookingArrangement
-
-
+
- Details for BookingArrangement
+ Details for ServiceBookingArrangement
-
+
diff --git a/xsd/netex_part_1/part1_networkDescription/netex_flexibleNetwork_version.xsd b/xsd/netex_part_1/part1_networkDescription/netex_flexibleNetwork_version.xsd
index 0dc1ece32..8ce383137 100644
--- a/xsd/netex_part_1/part1_networkDescription/netex_flexibleNetwork_version.xsd
+++ b/xsd/netex_part_1/part1_networkDescription/netex_flexibleNetwork_version.xsd
@@ -46,7 +46,7 @@ Rail transport, Roads and Road transport
- A group of FLEXIBLE ROUTEs of which is generally known to the public by a similar name or number and which have common booking arrangements. DEPRECATED: please use LINE instead. +v2.0
+ A group of FLEXIBLE ROUTEs of which is generally known to the public by a similar name or number and which have common booking arrangements. DEPRECATED: please use LINE instead. -v2.1
@@ -103,7 +103,7 @@ Rail transport, Roads and Road transport
- Specialisation of ROUTE for flexible service. May include both point and zonal areas and ordered and unordered sections.
+ Specialisation of ROUTE for flexible service. May include both point and zonal areas and ordered and unordered sections. Deprecated. Use Route instead -v2.1
diff --git a/xsd/netex_part_1/part1_networkDescription/netex_line_support.xsd b/xsd/netex_part_1/part1_networkDescription/netex_line_support.xsd
index 8e8696ee6..4b1498615 100644
--- a/xsd/netex_part_1/part1_networkDescription/netex_line_support.xsd
+++ b/xsd/netex_part_1/part1_networkDescription/netex_line_support.xsd
@@ -186,17 +186,55 @@ Rail transport, Roads and Road transport
-
-
+
+
+ This case is very similar to fixed line operation: journey patterns are defined as usual, but stops are served only if there is a passenger booking for it. Several vehicles may be allocated to the same journey when high level of demand occurs. Virtual line can be operated with fixed or dynamic passing times.
+
+
+
+
+ A minimal list and order of stops are defined determining a “main and minimal” journey pattern. Possible additional stops are defined but will be served only in case of passenger reservation.
+A range of journey patterns is determined through a stop list and order defined dynamically according to the passenger reservations and "around" the “main and minimal” journey pattern. N.B.This may mess with the timebehaviour, so we suggest to avoid corridorService as a pattern.
+
+
-
-
-
-
+
+
+ The line covers up to N areas, while the service will cover part of these N areas based on demand. Pickup and dropoff can be booked for any given location within the defined area, at any time within the given operating times. The actual route that is operated is based on the bookings.
+
+
+
+
+ Following a defined route, the service can pick up or drop off passengers in certain sections based on demand. A fixed route with fixed stops, but where boarding and alighting is allowed at certain sections between stops. Operation can be requested by signalling to the driver. The route is defined, but the Journey Pattern only has a start and an end. Boarding or alighting is obtained by signalling the driver that one wishes to board/alight and can occur anywhere along the Route. It also sometimes happens that boarding occurs on fixed stop, and only alighting can occur on demand anywhere along the Route.
+
+
+
+
+ The service is scheduled based on passenger demand; all pick-up and drop-off must be done at existing stops. The service is scheduled based on passenger demand; all pick-up and drop-off must be done at existing stops.
+
+
+
+
+ The service is defined by one or several zones (in sequence). Each zone is defined by a set of possible stops. Stops served and stop order are defined for each vehicle journey according to the reservations. Passing times (entry and exit time) are usually defined for each zone. They may also be defined for each stop.
+
+
-
-
-
+
+
+ A line operates both a fixed service (fixed stops, fixed schedule) and a specific flexible service
+. The possible stops of the journey pattern are known, and the possible stop sequences are also defined, and the real stop list and order are defined dynamically according to the passenger reservations without any reference to a main pattern.
+
+
+
+
+ Standard line with official steps and a linear route.
+
+
+
+
+ This value should only be used, when none of the others apply.
+
+
diff --git a/xsd/netex_part_1/part1_networkDescription/netex_line_version.xsd b/xsd/netex_part_1/part1_networkDescription/netex_line_version.xsd
index 40f5462c8..66a0297ea 100644
--- a/xsd/netex_part_1/part1_networkDescription/netex_line_version.xsd
+++ b/xsd/netex_part_1/part1_networkDescription/netex_line_version.xsd
@@ -79,8 +79,7 @@
http://www.netex.org.uk/schemas/1.0/PATH/netex_prereqfile.xsdUnclassified
- CEN, Crown Copyright 2009-2023
-
+ CEN, Crown Copyright 2009-2023
Derived from the Transmodel, VDV, TransXChange, NEPTUNE, BISON and Trident standards.
@@ -466,9 +465,9 @@ Rail transport, Roads and Road transport
Timetable documents associated with the LINE, e.g pdf files
-
+
- Set of possible Booking Arrangements for this LINE. +v2.0
+ Set of possible Booking Arrangements for this LINE. Using ServiceBookingArrangement for DRT. +v2.0
diff --git a/xsd/netex_part_2/part2_journeyTimes/netex_interchange_version.xsd b/xsd/netex_part_2/part2_journeyTimes/netex_interchange_version.xsd
index e3607ea9d..4c514c1c7 100644
--- a/xsd/netex_part_2/part2_journeyTimes/netex_interchange_version.xsd
+++ b/xsd/netex_part_2/part2_journeyTimes/netex_interchange_version.xsd
@@ -45,8 +45,7 @@
http://www.netex.org.uk/schemas/1.0/PATH/netex_prereqfile.xsdUnclassified
- CEN, Crown Copyright 2009-2019
-
+ CEN, Crown Copyright 2009-2019
Derived from the Transmodel, VDV, TransXChange, NEPTUNE, BISON and Trident standards.
diff --git a/xsd/netex_part_3/part3_fares/netex_all_objects_part3_fares.xsd b/xsd/netex_part_3/part3_fares/netex_all_objects_part3_fares.xsd
index 802155a7a..f40ae069a 100644
--- a/xsd/netex_part_3/part3_fares/netex_all_objects_part3_fares.xsd
+++ b/xsd/netex_part_3/part3_fares/netex_all_objects_part3_fares.xsd
@@ -5,4 +5,5 @@
+
diff --git a/xsd/netex_part_3/part3_fares/netex_extendedBookingArrangements_version.xsd b/xsd/netex_part_3/part3_fares/netex_extendedBookingArrangements_version.xsd
new file mode 100644
index 000000000..9ec964bfa
--- /dev/null
+++ b/xsd/netex_part_3/part3_fares/netex_extendedBookingArrangements_version.xsd
@@ -0,0 +1,221 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ main schema
+ e-service developers
+ V1.0 Matthias Günter
+ Nicholas Knowles
+ Europe
+ First drafted for NeTEx version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles.
+
+ 2010-09-04
+
+ 2025-09-24 Created and put in the things needed from part 1 and part 3
+
+
+
NeTEx is a European CEN standard for the exchange of Public Transport data including timetables.
+
This sub-schema describes the Common Service Restriction Types.
Derived from the Transmodel, VDV, TransXChange, NEPTUNE, BISON and Trident standards.
+
+
+ Version 1.0
+
+ 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 SG9.
+
+ NeTEx Travel Right Value Types.
+ Standard
+
+
+ NeTEx Service Restrictions.
+
+
+
+
+ Type for a SERVICE COMPETITIVE CONDITION.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Details for ServiceCompetitiveCondition.
+
+
+
+
+
+
+
+
+
+
+
+ Version of a SERVICE COMPETITIVE CONDITION.
+
+
+
+
+
+
+ Details for ServiceCompetitiveCondition.
+
+
+
+
+
+
+
+
+ Elements for SERVICE COMPETITIVE CONDITION.
+
+
+
+
+
+
+ Restrictions in what the SERVICE is allowed to do in connection with other SERVICES. If not set, then the rules apply in general.
+
+
+
+
+ Distance in metres to the line/service or classical public transport in general. Builds geometric exclusion zones.
+
+
+
+
+ Temporal distance to the SERVICE / transfer in the RoutingConstraint or classical public transport in general.
+
+
+
+
+ Factor to multiply the classical public drive time with for the calculation of the dominance of the demand responsive traffic.
+
+
+
+
+ Factor to multiply the classical public transfer times with for the calculation of the dominance of the demand responsive traffic.
+
+
+
+
+ Factor to multiply walk time for the classical public transport to calculate if the classical public transport still should dominate the demand responsive traffic.
+
+
+
+
+
+
+ Interchange between different flexible services is allowed.
+
+
+
+
+ Interchange between the flexible service and conventional services is allowed.
+
+
+
+
+
+
+
+
+
+ Type for a SERVICE ELIGIBLITY CONDITION.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Details for ServiceEligbilityCondition.
+
+
+
+
+
+
+
+
+
+
+
+ Version of a SERVICE ELIGIBILITY CONDITION.
+
+
+
+
+
+
+ Details for ServiceEligibilityCondition.
+
+
+
+
+
+
+
+
+ Elements for SERVICE ELIGIBILITY CONDITION.
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/xsd/netex_part_3/part3_fares/netex_usageParameterEligibility_version.xsd b/xsd/netex_part_3/part3_fares/netex_usageParameterEligibility_version.xsd
index 2ba327cfe..7fd523b08 100644
--- a/xsd/netex_part_3/part3_fares/netex_usageParameterEligibility_version.xsd
+++ b/xsd/netex_part_3/part3_fares/netex_usageParameterEligibility_version.xsd
@@ -692,7 +692,7 @@ Rail transport, Roads and Road transport
- The policy to apply if ta user's eligibility as a USER PROFILE changes.
+ The policy to apply if a user's eligibility as a USER PROFILE changes.