Open skinkie opened 1 year ago
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 we already have implementations using AlternativeText (e.g. South Tyrolia where everything needs to be bilingual), and a breaking change would be expensive.
@duexw shouldn't stop us to make breaking changes in future major versions which improve the standard. The "Name" element by itself is ambigious too. What is a Name element? If it is actually a description, how does it differ to Description, for example in the case of DestinationName.
I think those are related: https://github.com/NeTEx-CEN/NeTEx/issues/567 The group should tell what we do. When it is 2.0 we can do bigger changes.
complicated and breaking change: wait for 3.0 (if really needed)
At this moment Alternative Text is used for translated Name elements. I would like to see it part of the Name-element, having multiple lang-attributes.