Schema Validation - Problem about schema-dev HOT 2 CLOSED

Dan @dponti was having this problem too. Here is what he had emailed me and Nick.

Hi Peter - I figured out that the schema validation errors occur because of multiple import and include statements in the various schema files. These are there in order for each schema file to individually validate. and Oxygen ignores multiple imports, as is allowable in the standard.This works fine when pointing to files on a local directory on on the GitHub site, but not when pointing to the files on diggsml.org/schemas/2.5.a. I have no idea why this is the case. However, I found a workaround by pointing to Kernel.xsd instead of Complete.xsd - this appears to avoid the multiple import issue and file validation works fine. I'll post info to GitHub on this so that folks point to the correct location.

Still would be nice to know what is different about the diggsml.org site that causes this...

I wondered if it could be that there are multiple schemas available on diggsml.org/schemas ?
In other words, maybe Oxygen is pulling multiple schema files from the diggsml.org website?

from schema-dev.

Until we figure out the issues on the diggsml.org site, Diggs v 2.5.a instance documents should point to Kernel.xsd for validation instead of Complete.xsd as follows:

xsi:schemaLocation="http://diggsml.org/schemas/2.5.a https://diggsml.org/schemas/2.5.a/Kernel.xsd"

from schema-dev.