Open codingpoets opened 3 months ago
The reason at the time was simply that we wanted to enforce schemas so that tool developers would actually create and provide them. However, over the last few years it has turned out that nobody provides schemas anyway, apart from a few CPACS ultras. That's why I had also already considered no longer enforcing the schema. So thanks for the issue. Let me put this up for discussion in the developer group before we take this step.
In the
toolType
definition, is there a reason not to change the<xsd:any>
to<xsd:any processContents="lax">
? https://github.com/DLR-SL/CPACS/blob/dca8d9d5fc0a52b94a5e0cd06e04da5ac2ea2088/schema/cpacs_schema.xsd#L35020-L35026When validating a CPACS file you would otherwise always need all toolspecific schema definitions. Setting the
processContents="lax"
avoids this.