norman.walsh.name: Comments on /2011/12/19/docbookXSD

Comment 1 on /2011/12/19/docbookXSD

2011-12-19T17:33:02Z

Did you try Trang? I had quite some success with using its products with Eclipse XML editor (for much less complicated schema).

Comment 2 on /2011/12/19/docbookXSD

2011-12-19T17:43:33Z

The DocBook schemas are way beyond the capabilities of Trang.

Comment 3 on /2011/12/19/docbookXSD

2011-12-19T18:54:02Z

Maybe, what I meant is that I am not sure how really acute the lack of XSD really is, because for many purposes even such half-solutions seems to work.

Comment 4 on /2011/12/19/docbookXSD

2011-12-20T11:07:09Z

Just did a quick test in Xopus. We don't support the processContents attribute on xs:any, so that's a step back from the previous XSD. But other than that, seems to be loading just fine...

And for an editor like Xopus a good XSD is necessary, Trang is indeed not an option in this case. So thanks for making this effort!

Comment 5 on /2011/12/19/docbookXSD

2011-12-22T11:18:08Z

Using Oxygen 13.1, validation of the 1.0 XSD file fails with lots of errors. The first one reads

docbook-ns-10.xsd Programmname: Xerces Feherlevel: error
Beschreibung: cos-nonambig: "http://docbook.org/ns/docbook":xref
and "http://docbook.org/ns/docbook":xref (or elements from their
substitution group) violate "Unique Particle Attribution". During
validation against this schema, ambiguity would be created for
those two particles. Start: 450:5 End: 450:19

It complains about source code line450, which is a refernce to the db.common.attributes group, inside the definition of the complexType named inline.type starting at line 437.

I think there are about 33 errors like this. As far as i can see always cos-nonambig:

Allthough Oxygen supports RELAX very well, we are highly interested in a good XSD for docbook. The main reason is Adobe FrameMaker, which is in fact based on DTD., but does support XSD (translates it to DTD inernally?)

We hav to customize docbook before using it in FrameMaker because some of FMs limitations. (Nested Tables are not supported, for example). Doing so in RELAX is useless, because there is no way to generate the customized DTD. My hope is, that cusomization can be don in XSD, and that would help to get the customized DTD via standard Tools (like the one builtin in Oxygen).

Cheers, Frank

Comment 6 on /2011/12/19/docbookXSD

2011-12-22T11:57:49Z

Thanks, Frank. I've discovered that Xerces reports ambiguity problems so I've got a line on fixing them. I'm just hoping it's not too painful to do so.