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
From: <docbook-tc@lists.oasis-open.org> on behalf of Bob Stayton <bobs@sagehill.net>
Date: Tuesday, July 21, 2020 at 1:04 PM
To: Jirka Kosek <jirka@kosek.cz>, DocBook Technical Committee <docbook-tc@lists.oasis-open.org>, Larry Rowland <lrrhome@aol.com>, Richard Hamilton <dick@rlhamilton.net>
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
bobs@sagehill.net