OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook] DocBook 5 Assemblies and XML Fragments

Hi Thomas,
A resource href with fragment identifier works in assembly, but not href with xpointer. The DocBook Technical Committee discussed going further with XInclude features like xpointer, but wanted to avoid reinventing XInclude in DocBook. So the TC is also pursuing improvements to the XInclude standard.

However, you can currently create a hybrid assembly/XInclude that defines a resource that points to a file that contains just an XInclude. Then you process the assembly with an XInclude-enabled processor to get the same effect. I tried that with xsltproc and it worked.

BTW, the current assembly/assemble.xsl stylesheet still expects @fileref instead of @href in resource elements. That attribute name was changed in the spec and the schema last year, but the change did not make it into the latest 1.78 stylesheet update. 8^(
I'll fix it so either will work in the snapshot builds.

Bob Stayton
Sagehill Enterprises

From: "Thomas Schraitle" <tom_schr@web.de>
Sent: Monday, April 15, 2013 12:13 AM
To: <docbook@lists.oasis-open.org>
Subject: [docbook] DocBook 5 Assemblies and XML Fragments


DocBook 5 contains the new element "assembly" as definied in the TDG:


According to the TDG5, the resource contains a href attribute which is
definied as an anyURI datatype.

Does that mean, an ID fragment is allowed too? Something like:

 <resource href="foo.xml#intro"/>

Would that be supported? How it is supposed to work with other "XML
fragments"? Let's say, a user wants to refer to the first section
inside a file, but this section doesn't contain an xml:id attribute?
Should that be an XPointer expression? Or something else?

It seems, the current level of modularization with assemblies just
covers files and only files. However, sometimes the current situation
dictates a specific structure. As such using a more granular approach
would be very helpful.

This question originated from the docbook-apps mailinglist[1].



   Thomas Schraitle

To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]