Adding different types of restrictions between Services especially for DRT #959
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ue71603 marked this conversation as resolved.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Contributor
There was a problem hiding this comment. Adding "RoutingConstraintInFrameGroup" is like shooting sparrows with cannons. It adds huge complexity to the model where we originally only wanted to state "do not compete with regular PT operating within +-15 minutes".
Contributor
Author
There was a problem hiding this comment. but it works with cannons... Ok. I had this first but the restriction group works. You propose we do a simple element with a xs:duration then. I can live with that.
Contributor
There was a problem hiding this comment. I don't know if I want to switch to something simple, if we can facilitate all variants with a "more difficult" proposal.
Contributor
Author
There was a problem hiding this comment. It is now possible to do the simple way again as RoutingConstraintInFrameGroup is optional
Contributor
Author
There was a problem hiding this comment. reduce to max, we can do in the profile |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,206 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <xsd:schema xmlns="http://www.netex.org.uk/netex" xmlns:netex="http://www.netex.org.uk/netex" xmlns:siri="http://www.siri.org.uk/siri" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.netex.org.uk/netex" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.0" id="netex_serviceRestrictions_version"> | ||
| <xsd:include schemaLocation="../../netex_framework/netex_responsibility/netex_typeOfValue_version.xsd"/> | ||
| <xsd:include schemaLocation="../../netex_framework/netex_genericFramework/netex_organisation_support.xsd"/> | ||
| <xsd:include schemaLocation="../../netex_framework/netex_reusableComponents/netex_serviceRestrictions_support.xsd"/> | ||
| <xsd:include schemaLocation="../../netex_framework/netex_reusableComponents/netex_serviceRestrictions_version.xsd"/> | ||
| <xsd:include schemaLocation="../../netex_part_1/part1_networkDescription/netex_line_support.xsd"/> | ||
| <xsd:include schemaLocation="../../netex_part_1/part1_tacticalPlanning/netex_routingConstraint_version.xsd"/> | ||
| <xsd:include schemaLocation="netex_usageParameterEligibility_version.xsd"/> | ||
| <!-- ======================================================================= --> | ||
| <xsd:annotation> | ||
| <xsd:appinfo> | ||
| <Metadata xmlns="http://www.govtalk.gov.uk/CM/gms-xs"> | ||
| <Aggregation>main schema</Aggregation> | ||
| <Audience>e-service developers</Audience> | ||
| <Contributor>V1.0 Matthias Günter</Contributor> | ||
| <Contributor>Nicholas Knowles</Contributor> | ||
| <Coverage>Europe</Coverage> | ||
| <Creator>First drafted for NeTEx version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles.</Creator> | ||
| <Date> | ||
| <Created>2010-09-04</Created> | ||
| </Date> | ||
| <Date><Modified>2025-09-24</Modified> Created and put in the things needed from part 1 and part 3 | ||
| </Date> | ||
| <Description> | ||
| <p>NeTEx is a European CEN standard for the exchange of Public Transport data including timetables.</p> | ||
| <p>This sub-schema describes the Common Service Restriction Types.</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.netex.org.uk/schemas/1.0/xsd/netex_framework/netex_reusableComponents}netex_serviceRestrictions_version.xsd</Identifier> | ||
| <Language>[ISO 639-2/B] ENG</Language> | ||
| <Publisher>Kizoom Software Ltd, 16 High Holborn, London WC1V 6BX </Publisher> | ||
| <Relation> | ||
| <Requires>http://www.netex.org.uk/schemas/1.0/PATH/netex_prereqfile.xsd</Requires> | ||
| </Relation> | ||
| <Rights>Unclassified | ||
| <Copyright>CEN, Crown Copyright 2009-2023</Copyright> | ||
| </Rights> | ||
| <Source> | ||
| <ul> | ||
| <li>Derived from the Transmodel, VDV, TransXChange, NEPTUNE, BISON and Trident standards.</li> | ||
| </ul> | ||
| </Source> | ||
| <Status>Version 1.0</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 SG9.</Project> | ||
| </Subject> | ||
| <Title>NeTEx Travel Right Value Types.</Title> | ||
| <Type>Standard</Type> | ||
| </Metadata> | ||
| </xsd:appinfo> | ||
| <xsd:documentation>NeTEx Service Restrictions.</xsd:documentation> | ||
| </xsd:annotation> | ||
| <!-- ===== SERVICE COMPETITIVE CONDITION ===================================== --> | ||
| <xsd:element name="ServiceCompetitiveCondition" substitutionGroup="BookingArrangement_Dummy"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Type for a SERVICE COMPETITIVE CONDITION.</xsd:documentation> | ||
| </xsd:annotation> | ||
| <xsd:complexType> | ||
| <xsd:complexContent> | ||
| <xsd:restriction base="ServiceCompetitiveCondition_VersionStructure"> | ||
| <xsd:sequence> | ||
| <xsd:sequence> | ||
| <xsd:group ref="EntityInVersionGroup" minOccurs="0"/> | ||
| </xsd:sequence> | ||
| <xsd:sequence> | ||
| <xsd:group ref="DataManagedObjectGroup"/> | ||
| </xsd:sequence> | ||
| <xsd:sequence> | ||
| <xsd:group ref="ServiceCompetitiveConditionGroup"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Details for ServiceCompetitiveCondition.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:group> | ||
| </xsd:sequence> | ||
| </xsd:sequence> | ||
| <xsd:attribute name="id" type="BookingArrangementIdType" use="required"/> | ||
| </xsd:restriction> | ||
| </xsd:complexContent> | ||
| </xsd:complexType> | ||
| </xsd:element> | ||
| <xsd:complexType name="ServiceCompetitiveCondition_VersionStructure"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Version of a SERVICE COMPETITIVE CONDITION.</xsd:documentation> | ||
| </xsd:annotation> | ||
| <xsd:complexContent> | ||
| <xsd:extension base="BookingArrangement_VersionStructure"> | ||
| <xsd:sequence> | ||
| <xsd:group ref="ServiceCompetitiveConditionGroup"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Details for ServiceCompetitiveCondition.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:group> | ||
| </xsd:sequence> | ||
| </xsd:extension> | ||
| </xsd:complexContent> | ||
| </xsd:complexType> | ||
| <xsd:group name="ServiceCompetitiveConditionGroup"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Elements for SERVICE COMPETITIVE CONDITION.</xsd:documentation> | ||
| </xsd:annotation> | ||
| <xsd:sequence> | ||
| <xsd:choice> | ||
| <xsd:sequence> | ||
| <xsd:group ref="RoutingConstraintInFrameGroup"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Restrictions in what the SERVICE is allowed to do in conncetion with other SERVICES.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:group> | ||
| <xsd:element name="TemporalDistance" type="xsd:duration" minOccurs="0"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Temporal distance to the SERVICE / transfer in the RoutingConstraint.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:element> | ||
| <xsd:element name="Distance" type="xsd:integer" minOccurs="0"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Distance in metres to the line/service.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:element> | ||
| </xsd:sequence> | ||
| <xsd:sequence> | ||
| <xsd:element name="InterchangeBetweenFlexibleServicesAllowed" type="xsd:boolean" default="false" minOccurs="0"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Interchange between different flexible services is allowed.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:element> | ||
| <xsd:element name="InterchangeWithConventionalServicesAllowed" type="xsd:boolean" default="false" minOccurs="0"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Interchange between the flexible service and conventional services is allowed.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:element> | ||
| </xsd:sequence> | ||
| </xsd:choice> | ||
| </xsd:sequence> | ||
| </xsd:group> | ||
| <!-- ===== SERVICE COMPETITIVE CONDITION ===================================== --> | ||
| <xsd:element name="ServiceEligibilityCondition" substitutionGroup="BookingArrangement_Dummy"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Type for a SERVICE ELIGIBLITY CONDITION.</xsd:documentation> | ||
| </xsd:annotation> | ||
| <xsd:complexType> | ||
| <xsd:complexContent> | ||
| <xsd:restriction base="ServiceEligiblityCondition_VersionStructure"> | ||
| <xsd:sequence> | ||
| <xsd:sequence> | ||
| <xsd:group ref="EntityInVersionGroup" minOccurs="0"/> | ||
| </xsd:sequence> | ||
| <xsd:sequence> | ||
| <xsd:group ref="DataManagedObjectGroup"/> | ||
| </xsd:sequence> | ||
| <xsd:sequence> | ||
| <xsd:group ref="ServiceEligibilityConditionGroup"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Details for ServiceEligbilityCondition</xsd:documentation> | ||
|
ue71603 marked this conversation as resolved.
Outdated
|
||
| </xsd:annotation> | ||
| </xsd:group> | ||
| </xsd:sequence> | ||
| </xsd:sequence> | ||
| <xsd:attribute name="id" type="BookingArrangementIdType" use="required"/> | ||
| </xsd:restriction> | ||
| </xsd:complexContent> | ||
| </xsd:complexType> | ||
| </xsd:element> | ||
| <xsd:complexType name="ServiceEligiblityCondition_VersionStructure"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Version of a SERVICE ELIGIBILITY CONDITION.</xsd:documentation> | ||
| </xsd:annotation> | ||
| <xsd:complexContent> | ||
| <xsd:extension base="BookingArrangement_VersionStructure"> | ||
| <xsd:sequence> | ||
| <xsd:group ref="ServiceEligibilityConditionGroup"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Details for ServiceEligibilityCondition.</xsd:documentation> | ||
| </xsd:annotation> | ||
| </xsd:group> | ||
| </xsd:sequence> | ||
| </xsd:extension> | ||
| </xsd:complexContent> | ||
| </xsd:complexType> | ||
| <xsd:group name="ServiceEligibilityConditionGroup"> | ||
| <xsd:annotation> | ||
| <xsd:documentation>Elements for SERVICE ELIGIBILITY CONDITION.</xsd:documentation> | ||
| </xsd:annotation> | ||
| <xsd:sequence> | ||
| <xsd:choice> | ||
| <xsd:element ref="UserProfile"/> | ||
| <xsd:element ref="CommercialProfile"/> | ||
| <xsd:element ref="ResidentialQualification"/> | ||
| <xsd:element ref="CompanionProfile"/> | ||
| </xsd:choice> | ||
| </xsd:sequence> | ||
| </xsd:group> | ||
| <!-- ======================================================================= --> | ||
| </xsd:schema> | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think it is a good idea that as a data producer you have to enumerate all regular services ("LINE") to state the competition rules. The data producer will not have these in their system, unless they are a data integration system. Even if they do have all LINEs, the process for determining the competing LINEs is not straight forward. Taxi-like DRT will usually be determined by a geographical area and by operating days and times. So the system would need to determine the stops in the area, then determine the LINEs serving the stops, and then find out if there are any journeys during the operating time of the DRT. I suggest that it is not necessary to state the competing regular LINEs, the journey planner can work that out at run time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@duexw counter-proposal? how would you state them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is now optional. Also I added some more points.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that is what I had in mind - If you do not state any LINEs, it means that the competitive rule applies to all LINEs.