Austria wants to use ServiceSections in parallel.
E.g. a person wants to go from Bern to Kerzers. This is part of coupled journey. So if commerical TrainNumbers are used then there might exist two Service Sections in parallel.
Should we update the description.
Also as the two parallel ServiceSections have different destinations (one going Bern - Neuenburg, the other Bern - Murten), the Origin and Destination should be moved to ServiceSection.
In those cases also Cancellations are on one ServiceSection only.
Perhaps Section should be merged.
For possible JSON implementation having groups around everything that can exist n times would be great. Currently ServiceSection is just 1:n
Austria wants to use ServiceSections in parallel. E.g. a person wants to go from Bern to Kerzers. This is part of coupled journey. So if commerical TrainNumbers are used then there might exist two Service Sections in parallel.
Should we update the description.
Also as the two parallel ServiceSections have different destinations (one going Bern - Neuenburg, the other Bern - Murten), the Origin and Destination should be moved to ServiceSection.
In those cases also Cancellations are on one ServiceSection only.
Perhaps Section should be merged.
For possible JSON implementation having groups around everything that can exist n times would be great. Currently ServiceSection is just 1:n