This issue was raised a long time ago, but I think it is still has not been addressed in the xsd. An overnight (train) service journey may on the morning of the second day be attached with an additional service journey working on a later operating day date. I suggest adding a ParentJourneyOperatingDayOffset element as below.
Additionally I also suggest making it possible to define the JourneyPart explicitly ,and not only by reference, as a part of a JourneyPartCouple as in the lower diagram.


-
Suggested addition in JourneyPartGroup of netex_coupledJourney_version.xsd :
<xsd:element name="ParentJourneyOperatingDayOffset" type="DayOffsetType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>OPERATING DAY date offset of parent journey relative OPERATING DAY date of main JOURNEY PART journey. Positive number indicates a later OPERATING DAY date for parent journey. Does not need to be stated if 0 or not relevant for context.</xsd:documentation>
</xsd:annotation>
</xsd:element>
-
Suggested change in JourneyPartCoupleGroup of netex_coupledJourney_version.xsd:
<xsd:element name="journeyParts" type="journeyParts_RelStructure" minOccurs="0">
<xsd:annotation>
<xsd:documentation>JOURNEY PARTs in JOURNEY PART COUPLE.</xsd:documentation>
</xsd:annotation>
</xsd:element>
This issue was raised a long time ago, but I think it is still has not been addressed in the xsd. An overnight (train) service journey may on the morning of the second day be attached with an additional service journey working on a later operating day date. I suggest adding a ParentJourneyOperatingDayOffset element as below.
Additionally I also suggest making it possible to define the JourneyPart explicitly ,and not only by reference, as a part of a JourneyPartCouple as in the lower diagram.
Suggested addition in JourneyPartGroup of netex_coupledJourney_version.xsd :
Suggested change in JourneyPartCoupleGroup of netex_coupledJourney_version.xsd: