duexw

The NeTEx charging model does have some functional gaps when compared to the current version of the German VDV 452 1.6 Summary: - No explicit data object for charging stations...

OK, my fault - I looked at the UMLs from Nicks proposal only. After reviewing the current TransmodelEcoSystem2024-EAv16-nk69.qea, it looks much better. Charging Processes are modelled and RechargingPointAssignment solves part...

This change would break the German Profile (VDV 462) as well. It would not be appreciated, as it would require much reworking of existing interfaces.

Both validDayBits and Daytype/DaytypeAssignment describe correctly the operating days of the journey. ValidDayBits have the advantage of minimal interpretation, you know exactly when the journey will operate. DayTypes on the...

I tried out the "mixed" Element type in Microsoft .NET 8. Basically it works, but one would have to adapt existing code. I made a simplified example. We try to...

Updated documentation of ProductValidityParametersGroup and UserProfileGroup - but TypeOfProof does not seem to be documented yet. Should I document it? And if so, then in which section

It should have been modeled this way in the first place. The change was discussed before NeTEx went live, but even then it was considered too big a change. Now...

Yet to be discussed: - Do we need RechargingBay any more - VehicleChargingEquipment: Does one use it as a type or as an instance (see example)

Fixed in my own clone duexw/NeTEx, but I currently do not have the access right to fix it in this repository. Also I observed that Altova XML Spy 2025 does...