Re: [docbook-tc] DocBook Technical Committee Meeting Minutes: 20April 2011

[Jirka Kosek <jirka@kosek.cz>]

Grosso, Paul wrote:

> But almost all examples in Jirka's writeup just use URIs
> anyway.  And his full proposal does allow an xpointer 
> attribute on the referencing element, but it's the same
> attribute as on xinclude, so in what way is the issue
> Larry raises above about xinclude any worse than what
> the issue would be for a DocBook transclusion feature?

The difference here is that for inline references
(http://docbook.org/docs/transclusion/#d6e20) my proposal can include
text only node without relying on xpath() XPointer scheme which has
interop problems.

Of course for external references my proposal in this aspect is very
similar to XInclude (except various ID/IDREF fixup features).

> If for whatever reason implementations don't support
> some xpointer schemes for xinclude/@xpointer, why would
> those implementations be more likely to support those
> same xpointer schemes for DocBook's @xpointer?  And
> insofar as one can write a DocBook transclusion processor
> in XSLT as Jirka has done, why couldn't the same thing
> be done for xinclude?

XIncludes are usually evaluated before XSLT transformation by XML
parser. So in environments where "native" XInclude processing can't be
disabled, XSLT can't do any magic.

				Jirka

-- 
------------------------------------------------------------------
  Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------

OpenPGP digital signature