[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Re: [docbook] future of DocBook XML Schema (XSD)?
I manage a large schema that uses DocBook 5. The normative schema is RelaxNG. This schema is automatically translated to XSD using Trang, but the resulting XSD files have to be post-processed in order to fix them before they are useable by consumers.
DocBook 6 in pure RelaxNG+Schematron would be fine with me.
> On 19 Oct 2016, at 5:51 AM, Bob Stayton <firstname.lastname@example.org> wrote:
> 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
> To unsubscribe, e-mail: docbook-unsubscribe@lists.
> For additional commands, e-mail: email@example.com.