Support for XSD in version 1.1

[jtschea]

Dear developers,

first of all thank you for this excellent VSCode extension.

I need some advanced XSD features that are only available in version 1.1. My question is, if LSP4XML supports this feature.

The XSD indicates the usage of XSD 1.1 like this:

<?xmlt version="1.0" encoding="UTF-8" standalone="no" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"  vc:minVersion="1.1" xmlns:vc="http://www.w3.org/2007/XMLSchema-versioning">
<!-- -->
</xs:schema>

I am using a "xs:group" as a child of "xs:all" which is allowed in 1.1 but I am getting an error.

Thanks in advance and best regards,
Jupp

[angelozerr]

first of all thank you for this excellent VSCode extension.

Thanks!

@jtschea we have a PR which supports XSD 1.1 in eclipse-lemminx/lemminx#515 but it has been not merged because

• it will grow up the size of the vscode-xml because it requires adds of (non standard) Xerces JAR which supports XSD 1.1
• we found a lot of problems that we fixed but we are not sure that it will cause some regression.

[A-UNDERSCORE-D]

Am also looking for XSD 1.1 support, as I have XSDs for config files that require the expanded xs:all rules (specifically allowing unbounded occurances)

[jtschea]

Hi Angelo,

thank you very much for answering.

I was finally able to try out your PR within vscode-xml but still get errors when using XSD 1.1. I cloned and built your branch xsd_1.1 and copied the resulting jar to extensions/redhat.vscode-xml-0.10.1/server. The jar was extracted to the same location as well.

Is this the correct way to experience XSD 1.1 in VSCode or am I doing something wrong?

Thanks in advance and best regards,
Jupp

[alex-bel]

Hi Everyone!
I am also looking for XSD 1.1 support, especially for xsd:assert and xsd:assertion

I was able to build the xsd_1.1 branch (https://github.com/angelozerr/lsp4xml/tree/xsd_1.1), but unfortunately assertions do not work properly there. The reason is wrong version of 'org.eclipse.wst.xml.xpath2.processor' lib in the pom.xml. Xerces is built against version 1.2.0 of this lib, however in pom.xml 2.1.100 is used. Version 1.2.0 is not published to maven repo (at least I was not able to find it).
I thought it will be a good idea to make an uberjar of xercesImpl.jar, including xpath processor and icu4j bundled with xerces distribution binary.
I already did this locally and so far it works well. Use of bundled icu4j (which has only 'normalizer' module) also solves the size problem of lsp4xml uberjar. I will publish everything I have soon.

@jtschea Try adding this into your settings.json:
"xml.validation.schemaVersion": "1.1"
This turns on 'XML Schema 1.1' mode for the validator.

[angelozerr]

Hi @alex-bel thank a lot for your feedback!

You mean https://github.com/angelozerr/lsp4xml/blob/xsd_1.1/org.eclipse.lsp4xml/pom.xml#L103 is not enough? Please create a PR to fix it.

I thought it will be a good idea to make an uberjar of xercesImpl.jar, including xpath processor and icu4j bundled with xerces distribution binary.

We create an uberjar for LSP4XML which includes xerces, is it not working?

@jtschea Try adding this into your settings.json:
"xml.validation.schemaVersion": "1.1"

Indeed, @jtschea please add this settings.

@alex-bel is there any chance that you create a PR from my branch https://github.com/angelozerr/lsp4xml/tree/xsd_1.1

Please note LSP4XML should be move too soon to Eclipse.org. There will have some packages rename.

[alex-bel]

Hi @angelozerr

I will try to give more detailed explanation.

Let's say you want to use Xerces4j with XML Schema 1.1 support. First problem you face immediately is that you cannot find official (published by developers) artifact in public maven repositories.
However, you have official binary distributions (available here: https://archive.apache.org/dist/xerces/j/binaries/ ). If you download Xerces-J-bin.2.12.1-xml-schema-1.1.zip and unpack it you'll see that it contains not only Xerces itself (XercesImpl.jar), but also all its dependencies, including transitive ones.

Some folks already uploaded xercesImpl into Maven central (https://search.maven.org/search?q=xerces ). Some of them ( https://search.maven.org/artifact/com.rackspace.apache/xerces2-xsd11/2.11.2/jar ) added reference to version 2.1.100 of org.eclipse.wst.xml.xpath2.processor:xpath2, which breaks xsd:assert support. Other guys added reference to correct version 1.2.0 (https://search.maven.org/artifact/org.exist-db.thirdparty.xerces/xercesImpl/2.12.1/jar), but the artifact itself is not available in the maven central.

Long story short, you cannot assemble working version of Xerces with fully operational Schema 1.1 support from what you can find in Maven central right now.
Therefore, you have to make and upload your own artifact(s). You have 2 approaches: either upload XercesImpl and its dependencies separately, or create and upload an uberjar (that consists of xercesImpl.jar, org.eclipse.wst.xml.xpath2.processor_1.2.0.jar and optionally icu4j.jar).

I took the second way. There is ( https://github.com/alex-bel/xerces4j-with-deps) a simple gradle project that downloads official Xerces distribution, creates uberjar and uploads it there: https://dl.bintray.com/alex-bel/alexbel-repo/xerces4j-with-deps/xerces-schema-1_1-icu/2.12.1.1/

There is my version of xsd_1.1 branch (https://github.com/alex-bel/lsp4xml/tree/xsd_1.1) that uses xerces-schema-1_1-icu:2.12.1.1 artifact. I have also rebased it onto master to fetch recent changes. You probably don't want to merge these changes into your repo since pom.xml contains reference to my maven repo in bintray.

My suggestion is that you make and publish your version of Xerces under your groupId into maven central, since you already have access to it. If you choose to publish uberjar, you can use my publisher. If you decide to publish xercesImpl and its dependencies as separate artifacts, I also can assist you with making of gradle script.

With that's being said, I can answer your questions

You mean https://github.com/angelozerr/lsp4xml/blob/xsd_1.1/org.eclipse.lsp4xml/pom.xml#L103 is not enough? Please create a PR to fix it.

Reference to xercesImpl is OK. Version of org.eclipse.wst.xml.xpath2.processor:xpath2 is the main problem (https://github.com/angelozerr/lsp4xml/blob/xsd_1.1/org.eclipse.lsp4xml/pom.xml#L112). I cannot make a PR since version 1.2.0 of org.eclipse.wst.xml.xpath2.processor:xpath2 is not uploaded into maven central.

We create an uberjar for LSP4XML which includes xerces, is it not working?

I was referencing to "xerces-with-dependencies" uberjar, which consists of xercesImpl.jar, org.eclipse.wst.xml.xpath2.processor_1.2.0.jar and lightweight version of icu4j.jar

[angelozerr]

Thank a lot for your great feedback @alex-bel !

We plan to move lsp4xml to Eclipse.org and we will see how we could manage this xerces 1.1. @fbricon what do you think about that?

[xballiet]

Hello,
Can you tell me if the support of XSD 1.1 will be implemented sooner or later?
I need that especially for xs:assert... :)
Thanks for your useful tool!

[angelozerr]

Can you tell me if the support of XSD 1.1 will be implemented sooner or later?

For the moment it's not in our priority and it requires to use a non official Xerces distribution. I find it's annoying.

@fbricon have you some idea about that?

[angelozerr]

Thanks for your useful tool!

Glad vscode-xml please you. Thanks!

[gotlibsh]

For what it's worth, I'm also looking for VSCode extension support for XSD 1.1, especially to be able to add xs:assert elements.

Anyway, thanks for the great tool and I hope you guys will find the time to support it :).

[git-n-pissed]

Would also like to see XSD 1.1 support in VS Code for the xs:alternative element.

[bthdimension]

Hello everyone. Is this feature still planned? Love the extension but since I'm working with XSD 1.1, the validations won't work for me. Thanks!

[angelozerr]

While Xerces will not provide an official support with XSD 1.1, we cannot provide this support.

[bthdimension]

Ok, thanks for the update!