…makes sense. A new snapshot is online, which only assigns the 'invalid' status when errors or fatal errors are found.

On Wed, Jun 5, 2024 at 3:18 PM ykhabins@bellsouth.net wrote:

Mr. Grun,

Thanks a lot for such a such quick turnaround.

I tested the latest BaseX 11.0 beta build 88ebdb9.

It emits the following result for the provided test case:

<report> <status>invalid</status> <message level="Warning" line="12" column="40" url="file:/C:/Users/i300179/Downloads/Warning.xsd">FacetsContradict: For simpleType definition '#AnonType_ADDR_TYPE', the enumeration value '' contradicts with value of 'length' facet.</message> </report>

There is one more outstanding issue to resolve. A logic for the final XSD validation result needs to be adjusted.

1. Messages with the attribute level="Warning" shall be NOT counted as

invalid! As end result: <status>valid</status> 2) Messages with the attribute level="Error" shall be counted as a failed validation. As end result: <status>invalid</status>

Such behavior would be consistent with the Oxygen XML IDE validation outcome.

Regards, Yitzhak Khabinsky