VDV examples

[skinkie]

So someone "broke" or at least "was able to spot issues" in the VDV examples.

https://github.com/NeTEx-CEN/NeTEx/actions/runs/15869257615/job/44741970679#step:6:215

[Aurige]

The error is coming from the a set of <RegistrationNumber/>
They have to either contain a value, either just be removed
There is now a _VehicleUnique_RegistrationNumber_constraint that does not allow this kind of empty RegistrationNumber

[Aurige]

But he corresponding #837 is quite old

[Aurige]

it looks that master is broken for 4 month (since #837 ) when no error was triggered !
The merge of #925 (comment update) to master, triggered a new validation that caught the error...
Does this makes sense ?

[Aurige]

If that's the case, I'm not willing to correct examples in master, so the solution would be to revert #837 and migrate it to next.

[skinkie]

So you are not willing to do it. Because?

[Aurige]

Sure I can do it, but wanted first to make sure that this option was OK for the group

[Aurige]

@duexw to fix the VDV example with help if @Aurige if needed

[duexw]

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 not find the validation error unless you change the unique constraint to include the namespace of the element, e.g <xsd:field xpath="RegistrationNumber"/> to <xsd:field xpath="netex:RegistrationNumber"/>

[skinkie]

@duexw According to the settings you must be able to create a branch, and push that branch for a pull request.