Support XSD schema

[Rolf-Smit]

Currently the schema's provided for USX 3.0 are in the Relax NG format, to me it makes a lot of sense to also make these available in the common XSD schema format.

I would not really mind how this is done, but it would make sense to make the Relax NG schema's so that when converting them with tools like Trang you would end up with a valid and workable XSD schema.

Currently when you try to convert the Relax NG schema using Trang you don't get a workable XSD schema.

[jonbitgood]

Here's an xsd schema for usx3 that I've been using for testing.

[Rolf-Smit]

@jonbitgood thanks for sharing!

But how do you, when generating code from the xsd, avoid errors such as:

org.xml.sax.SAXParseException: cos-element-consistent: Error for type '#AnonType_periph'. Multiple elements with name 'para', with different types, appear in the model group.

Or

org.xml.sax.SAXParseException: cos-nonambig: para and para (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.

[jonbitgood]

Hmmm... I've not worked with SAX but for these two you might be able to create a custom error handler that just returns without an error code. Alternatively, you could petition the good folks at UBS to split up para so that a different element name is used whenever the allowed attributes changes.

[Rolf-Smit]

It would indeed be nice if elements could have different names if they have different requirements. The current situation makes it really hard to write an XSD for. It can be done but it will be very loosely and non-strict (since you will have to combine requirements for elements with the same name).

If anyone could point me towards a Relax NG codegenerator that spits out Java POJO's that would be nice. But it seems within the Java community there doesn't seem to be a Relax NG codegen that is not from 20 years ago ;)

[Rolf-Smit]

@jonbitgood I created my own XSD file for now:

https://github.com/Rolf-Smit/BibleMultiConverter/blob/feature/usx-3.0/biblemulticonverter-schemas/src/main/resources/usx3.xsd

But it is by far not as strict as the Relax NG file due to the limitations of using the same element names for many different things. It works for unmarshalling and marshalling, but is no where near perfect when it comes to very strict verification of contents. In the end XSD is more suited for structure validation it seems, not really for verifying content/values.

I would love to see a bit more element tags being used in the next version of USX, to make it easier to write tooling for this format.

[gjgigol]

@jonbitgood, it's been a few years, is your XSD schema still valid?

I guess I'm asking whethere there are any updates I should be looking for. :‑)
Greg

[jonbitgood]

Should be! It's only 6 years old and the changelog hasn't been updated in 8. Though, I've not tested it in a bit since these days I parse mainly from usfm without the usx intermediate step.

[gjgigol]

@jonbitgood, I'm working with USX files provided by a third party.

So I'm trying to validate them with Notepad++ and I'm getting an “Ivalid schema or missing namespace” error.

To be frank, I'm not a developer, so I might be doing something stupid here.
When validating, Notepad++ asks for the schema and the namespace. I provided the schema, but as for the namespace, I didn't know what to say, so I left the field blank. :‑/

Can you help, please?
(Again, I'm not a developer, so if it's too much trouble, just ignore this. :‑)