Christophe Duquesne
Christophe Duquesne
Most probably, but only for consistency reasons ... this NX.xsd is just for information (not for use), so provided that you have either XXX either XXXs, the information is there,...
Yes you are fully right
Only NeTEx_publication.xsd and NeTEx_siri.xsd are referenced in the documentation as possible entry point NX.xsd is never mentionned and is just provided for information (not for use, as explained in its...
The id is really mandatory only when it is a stand-alone object that can be referenced ... when used embedded in another object, you don't really care
Agreed on my side... needs to be approved by the group
Start in v2 (on any possibly first class object.. any object having an "inFrame" possibility) but postpone breaking changes in v3
Just to clearly understand your expectation, for example we have ` ` but also ``` ... ``` So the _InfrastructureLinkRef_ is both inheriting from _LinkRefStructure_ and is in the _LinkRef_...
in that case, they do since you also have: ``` ... ``` So the inheritance chain is _InfrastructureLinkRefStructure_ -> _LinkRefStructure_ -> _VersionOfObjectRefStructure_
that's for strong typing, and avoid mixing refs of totally unrelated types of objects. However, I agree that all Refs should end on a _VersionOfObjectRefStructure_ at hte end of their...
@skinkie to check with some of above examples ... and generalise if OK @nick-knowles to work on it too