docbook-tc — archive

discuss issue #156 docbookxi doesn't support XInclude 1.1

From: Scott Hudson <[email protected]>
To: [email protected]
Date: Tue, 21 Jul 2020 19:42:00 -0000

I am in favor of adding the missing @fragid. Also to allowing @href. For the XInclude on inlines, I think that s great for reuse, as long as there aren t major impacts to the stylesheet support? _____________________________________________ Scott Hudson Staff, Content Tools and Engineering docs.servicenow.com From: <[email protected]> on behalf of Bob Stayton <[email protected]> Date: Tuesday, July 21, 2020 at 1:04 PM To: Jirka Kosek <[email protected]>, DocBook Technical Committee <[email protected]>, Larry Rowland <[email protected]>, Richard Hamilton <[email protected]> Subject: [docbook-tc] discuss issue #156 docbookxi doesn't support XInclude 1.1 [External Email] https://github.com/docbook/docbook/issues/156 This issue actually has three requests in it, which are independent of each other. For reference, here are links to the two W3C documents: XInclude 1.0: https://www.w3.org/TR/xinclude/ XInclude 1.1: https://www.w3.org/TR/xinclude-11/ 1. It's missing the fragid attribute. This attribute was added in XInclude version 1.1, and should be supported. 2. The DocBook schema for XInclude also forbids href= which is a bug. Indeed, the W3C document describes the behavior of href= as equivalent to a missing href attribute, which is to be treated as a reference to the current document. 3. We thought of XInclude as structural (chapters, sections), but maybe we should allow it anywhere, including in inlines. Comments? -- Bob Stayton [email protected]