Christophe Duquesne
Christophe Duquesne
I just did a few check (like TrainDimensionsGroup that was replaces by a more general VehicleDimensionsGroup ...). I think that we can get rid of most of them.
For now **VersionIdType** is said to be "_A revision identifier (e.g. a number) that should be updated (e.g. increased) each time the unit that is refers to is modified._" and...
At minimum, refine annotations
Don't change the type, but make recommendations for monotonically increasing use (what about dates). There is also difference between the global Frame versioning and the per object versioning. Guidelines to...
> @Aurige @TuThoThai can any of your make an example so we can validate the feature? it requires a complex example (with multiple SJ and Train Composition changes). I will...
Postponed due to lack of agreement (in Transmodel group)
That would be Ok for me. Could be named "deprecatedFrom" and have the corresponding fixed NeTEx version value.
Just having the JourneyPatternRef (or view) mandatory in the ServiceJourney may be sufficient. And if we do it at TimetabledPassingTime level, we also need to do it at Call level.
Document update done in https://github.com/NeTEx-CEN/NeTEx/pull/859
in addition to this discussion, @Robbendebiene pointed (in another discussion) that you an Equipment can ba assigned an a VEHICLE TYPE via the **ActualVehicleEquipment**, for example : ``` ``` Which...