XSD invalid about ids

[JBreelKubus]

Currently we're working on an IDS implementation and we're working on the XML generation part. We wanted to validate the result against this file: https://github.com/buildingSMART/IDS/blob/master/Development/ids.xsd

Now we're getting the same errors as mentioned in the original comment when using Microsoft development tools.
src-resolve.4.2: Error resolving component 'xs:occurs'. It was detected that 'xs:occurs' is in namespace 'http://www.w3.org/2001/XMLSchema', but components from this namespace are not referenceable from schema document 'virtual://server/schema.xsd'. If this is the incorrect namespace, perhaps the prefix of 'xs:occurs' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'virtual://server/schema.xsd'.

What it seems like to us is that the syntax for XML schema's (XSD) is being used in the resulting XML files. The xs:occurs and xs:restriction are meant to be used in XSD files. The namespace of xs(http://www.w3.org/2001/XMLSchema) is thus what confuses the validation tools.

Would it be possible to look into this on your end?

[CBenghi]

See also #113.

The problem has been found both on Java and .NET implementation.
There's a concern that the initial hope that tooling would be helped by using the standard xml types does not yield the expected benefits.

Maybe it's worth specifying our on data types to resolve the issue.

[berlotti]

Wat version of XMLSpy are you using?
It works fine in mine...

[NickNisbet]

Probably my mistake, but if you download the ids.xsd locally, XMLSPY 2022 rel 2 (x64) objects to <xs:import namespace="http://www.w3.org/2001/XMLSchema" schemaLocation="https://www.w3.org/2001/XMLSchema.xsd"/> Regards, Nick. Nicholas Nisbet FRSA MA(Cantab) DipArch(UNL) From: Léon van Berlo ***@***.***> Sent: Monday, May 8, 2023 12:40 PM To: buildingSMART/IDS ***@***.***> Cc: Nicholas Nisbet ***@***.***>; Author ***@***.***> Subject: Re: [buildingSMART/IDS] XSD invalid (Issue #159) Wat version of XMLSpy are you using? It works fine in mine... — Reply to this email directly, view it on GitHub<#159 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABYIIJL3SU3HXVB7PCJFFS3XFDLQTANCNFSM6AAAAAAXZA2ENU>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[berlotti]

The IDS schema combines two namespaces.
This allows IDS to use existing well established standards like the XSD restrictions (enumerations, patterns, minInclusive, etc..) instead of mimicking them with something IDS specific.

idsXML files therefore need to make sure their tags/elements have the correct namespace.
As you will see in the examples it combines ids:whatever with xs:things.
This combination of elements with different namespaces is a somewhat advanced use of XML that not all validators can understand.

Your error on minOccurs/maxOccurs seems to say that the correct namespace was not used in the XML file.
Happy to help (and also very curious :-)). Freel free to email me the file if that is possible.

[JBreelKubus]

The issue was already with the XSD file in this repository itself. Before we were trying to validate an XML file it was already giving these errors.

It's indeed possible to use the XSD elements in an XML file itself. The XSD restrictions under my understanding are meant for validating an XML file not for adding into the XML file itself. Some tools will support this and others won't, which is the issue we're running into. The XSD tool from Microsoft (XML Schema Definition, Xsd.exe) is giving these errors just on the XSD file alone. Some online validation websites also seem to be unable to handle the XSD file.

This complicates both the implementation and validation of the XML files on our end.