You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TimetabledPassingTime is directly linked to a StopPointInJourneyPattern (or more generally PointInJourneyPattern ) and therefore benefit directly from its order (therefore addind an order would mainly be a source of unconsistency)
The TimetabledPassingTime is directly linked to a StopPointInJourneyPattern (or more generally PointInJourneyPattern ) and therefore benefit directly from its order (therefore addind an order would mainly be a source of unconsistency)
While it benefits from a foreign order, only after it has been related, I noticed something cool happening on StopPointInJourneyPattern, being that it can take the same id of the ServiceJourneyPattern, and the order makes the StopPointInJourneyPattern (and others) unique. I think having passingTimings with the id of the parent, and the order to make the passing time unique, could certainly bring some elegance.
StopPointInJourneyPattern is an embedded object which is ordered. What is the reason that TimetabledPassingTime wasn't made ordered?
The text was updated successfully, but these errors were encountered: