Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -88,3 +88,4 @@ fabric.properties
# Editor-based Rest Client
.idea/httpRequests

/.idea
Original file line number Diff line number Diff line change
Expand Up @@ -420,6 +420,10 @@ The Calendar is shown coded as
<Advertised>true</Advertised>
</NoticeAssignment>
</noticeAssignments>
<!-- check for CheckConstraint. V2.1 -->
<CheckConstraint id="mybus:cc:1" version="any">
<Congestion>noWaiting</Congestion>
</CheckConstraint>
</StopPointInJourneyPattern>
<StopPointInJourneyPattern version="any" order="2" id="hde:spijp_24o_02">
<ScheduledStopPointRef version="any" ref="mybus:SSP_002"/>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,13 @@
<!-- ======================================================================= -->
<xsd:include schemaLocation="netex_servicePattern_support.xsd"/>
<xsd:include schemaLocation="../part1_tacticalPlanning/netex_fareZone_support.xsd"/>
<xsd:include schemaLocation="../../netex_part_1/part1_ifopt/netex_ifopt_checkConstraint_version.xsd"/>
<xsd:include schemaLocation="netex_journeyPattern_version.xsd"/>
<xsd:include schemaLocation="netex_timingPattern_version.xsd"/>
<xsd:include schemaLocation="netex_siteConnection_version.xsd"/>
<xsd:include schemaLocation="../part1_networkDescription/netex_flexibleNetwork_version.xsd"/>
<xsd:include schemaLocation="../../netex_part_2/part2_occupancy/netex_oc_occupancy_version.xsd"/>
<xsd:include schemaLocation="../../netex_part_2/part2_journeyTimes/netex_vehicleJourneyStopAssignment_version.xsd"/>
<!-- ======================================================================= -->
<xsd:annotation>
<xsd:appinfo>
Expand Down Expand Up @@ -63,8 +65,7 @@
<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>
<Copyright>CEN, Crown Copyright 2009-2023</Copyright></Rights>
<Source>
<ul>
<li>Derived from the Transmodel, VDV, TransXChange, NEPTUNE, BISON and Trident standards.</li>
Expand Down Expand Up @@ -901,6 +902,9 @@ Rail transport, Roads and Road transport
<xsd:documentation>Nature of use of stop, e.g. access, interchange only, or pass through. Default is Access.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="QuayAssignmentGroup"/>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you place it in the middle to align it with Call?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried. But different place would also be ok. We had in OJP some cases where we switched the order of some elements in service and this caused problems. So to do it as harmonised as possible seems a good idea to me.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You understand that the way you are now doing it explicitly would break parsing and validation? So if it was deliberate to put them here, was this because in the other structures they are already at this point?

<xsd:element ref="AccessibilityAssessment" minOccurs="0"/>
<xsd:element ref="CheckConstraint" minOccurs="0"/>
<xsd:choice>
<xsd:element name="bookingArrangements" type="bookingArrangements_RelStructure" minOccurs="0">
<xsd:annotation>
Expand Down
Loading