XInclude 1.1 attempts to address a couple of new use cases.

When I first wrote about the efforts of the DocBook TC to address some transclusion problems, Elliotte was the first to point out that we were doing it wrong.

There was subsequent discussion and finally some experimentation. The practical upshot of which is this: with a couple of small amendments, XInclude could be used to address DocBook's transclusion problems.

Last week, the XML Core WG posted a note describing XInclude 1.1 Requirements and Use Cases outlining how this might be achieved.

Comments most welcome, as always.

There are no comments on this essay.
Add a comment or subscribe to (existing and future) comments on this essay.
Name:
Email*:
 *Please provide your real email address; it will not be displayed as part of the comment.
Homepage:
Comment**:
 **The following markup may be used in the body of the comment: a, abbr, b, br, code, em, i, p, pre, strong, and var. You can also use character entities. Any other markup will be discarded, including all attributes (except href on a). Your tag soup will be sanitized...