Up to now we have never used the XSD version of DocBook in our projects. I allways thought that there is one big advantage for the XSD version: schema-aware XSLT. Would be cool if we could use all the nice possibilities of schema-aware xslt for DocBook as input. But all the projects, where this could have been an option, are based on a *modified* DocBook grammar. Typically, we reduce DocBook 5 to the elements that we really need, and extend it at the same time with elements from a different namespace. We use the customization methods described in chapter 5 of the DocBook Guide.
The XSD version of DocBook would only be helpfull for us, it we were able to do customization as easy at it is with Relax NG. Or if we could do customization with the Relax NG version and apply the transformation to XSD Schema by ourselves. As far as i understand your mail, neither of these is likely possible in the future. In this case, it is no problem if you drop the XSD version. Sincerely, Frank Steimke -----Ursprüngliche Nachricht----- Von: Bob Stayton [mailto:b...@sagehill.net] Gesendet: Dienstag, 18. Oktober 2016 20:51 An: docbook-apps@lists.oasis-open.org; docb...@lists.oasis-open.org Betreff: [docbook] future of DocBook XML Schema (XSD)? The DocBook Technical Committee is considering dropping the XML Schema version of DocBook in a future version 6. We would like to hear from any members of the DocBook community who would be affected by this change. Let me be clear that this change is not on the horizon, but part of our long term planning. The DocBook TC takes great care in maintaining backwards compatibility on point releases because we know how much the DocBook community relies on stable sources. When DocBook rolls to a new major version number, we treat that as an opportunity to introduce changes that are not backwards compatible. The change from 4 to 5 was such. If we foresee such changes coming, we give the DocBook community very advanced notice to prepare for them. We will continue to maintain the DocBook standard in RelaxNG with Schematron rules, and will continue to generate a compatible DTD. However, the process of maintaining the XSD version of DocBook is proving burdensome because it cannot be completely generated by a conversion program, and requires manual tweaking. Because we are not sure if anyone is actually using the XSD version, we are wondering if this is worth the effort. If you are using it, or have tools that depend on XSD, please let us know. You can reply directly to me if you don't want to discuss it on the mailing list. -- Bob Stayton Sagehill Enterprises b...@sagehill.net --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
