docbook-apps

I'm curious why v5 has separate schemas for the xinclude version?



regards

--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Dave Pawson wrote:

> I'm curious why v5 has separate schemas for the xinclude version?

Normally, you should validate final document after XIncludes are
resolved. DocBook+XInclude schema is there mainly for editors which are
able to guide through editing. Such editors are usually unable to
resolver XIncludes on-the-fly and thus with DocBook+XInclude schema you
will not get errors messages about unknown xi:include element.

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
------------------------------------------------------------------
Want to speak at XML Prague 2007 => http://xmlprague.cz/cfp.html

Jirka Kosek wrote:
> Dave Pawson wrote:
>
>> I'm curious why v5 has separate schemas for the xinclude version?
>
> Normally, you should validate final document after XIncludes are
> resolved. DocBook+XInclude schema is there mainly for editors which are
> able to guide through editing. Such editors are usually unable to
> resolver XIncludes on-the-fly and thus with DocBook+XInclude schema you
> will not get errors messages about unknown xi:include element.

Ah!
So the xi version *includes* xinclude... whereas the 'normal' docbook
excludes it. Subtle. very subtle!

I'm guessing you guys are ahead of me, and the stylesheets expand
xinludes prior to styling? Or do I need to tell the parser to expand
xincludes?
(At least entities were simple :-)



regards

--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

Jirka Kosek wrote:
> Dave Pawson wrote:
>
>> I'm curious why v5 has separate schemas for the xinclude version?
>
> Normally, you should validate final document after XIncludes are
> resolved. DocBook+XInclude schema is there mainly for editors which are
> able to guide through editing. Such editors are usually unable to
> resolver XIncludes on-the-fly and thus with DocBook+XInclude schema you
> will not get errors messages about unknown xi:include element.

Thanks Bob.
All is explained.

http://www.sagehill.net/docbookxsl/Xinclude.html#JavaXIncludes


regards

--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk