NeTEx
NeTEx copied to clipboard
ServiceJourneyInterchange points to ServiceJourney via VehicleJourneyRefStructure
I think it would again be in hour best interest that VehicleJourneyRefStructure and the consequence that it is basically unknown from which type the Journey originates from is avoided. I understand that from_something and to_something in its short hand form cannot specify a type, but I would then rather see that we have <To>
and <From>
which receive an abstract substitution group that expilictly use a ServiceJourneyRef, etc.
@Aurige what to do?