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


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

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

Subject: RE: [docbook-apps] Re-use in DocBook

Thanks Bob. I guess I will need some time to understand the procedure
and adapt this to my case. I'm curious to read about this in your
(excellent) book.

> -----Original Message-----
> From: Bob Stayton [mailto:bobs@sagehill.net] 
> Sent: Dienstag, 3. Juli 2007 18:39
> To: Thomas, Ludger; docbook-apps@lists.oasis-open.org
> Subject: Re: [docbook-apps] Re-use in DocBook
> Hi Thomas,
> I know of a couple of solutions.  One is to use XIncludes and 
> use the object.id template to alter the id values, as 
> described in this email
> thread:
> http://lists.oasis-open.org/archives/docbook-apps/200701/msg00134.html
> If you need something more active, a preprocessing "transclusion" 
> stylesheet could be used.  You would use XIncludes as the 
> first step, then process the result to modify ids before 
> further processing with a formatting stylesheet.
> If you don't want to use XInclude, you could insert some 
> empty elements with attributes that indicate that it is a 
> transclusion element and where to find its content.  I'm not 
> sure what attributes would be appropriate, but there are 
> several common attributes.  Then those could be used by a 
> transclusion stylesheet to prepare the content for further processing.
> Bob Stayton
> Sagehill Enterprises
> DocBook Consulting
> bobs@sagehill.net
> ----- Original Message -----
> From: <Ludger.Thomas@iese.fraunhofer.de>
> To: <docbook-apps@lists.oasis-open.org>
> Sent: Friday, June 29, 2007 2:17 AM
> Subject: [docbook-apps] Re-use in DocBook
> Dear all,
> I have a question regarding multiple re-use of elements in DB. Hope I
> manage to express what I mean.
> Currently we are heavily working with entities + very modular 
> XML files
> which we aggregate to books, articles etc. using xi:include. 
> This works
> fine but nodes may only be included once (due to unique ID).
> I wonder which ways exist to realize multiple usage of modular
> information chunks in DB. I read about using the DITA maps, conref
> method etc. but I'm not quite sure how and if this works. How would
> xref, indexterm etc. be handled in case of multiple occurrences in DB?
> What I had in mind for my document was to realize a model which might
> look like this (abstract non-DB example, idea picked up from IMS
> Manifest structure):
> <root>
> <organization> My Structure A
> <item resourceRef="res1"/>
> <item resourceRef="res2">
> <item resourceRef="res1"/>
> </item>
> </organization>
> <organization> My Structure B
> <item resourceRef="res2"/>
> </organization>
> <resources>
> <resource id="res1" .../>
> <resource id="res2" .../>
> </resources>
> <root>
> I'd be curious to hear your comments if and how such multiple 
> re-use of
> resources could be realized in DB. My current alternative is 
> to put all
> resources in an appendix and make some references if they are 
> used. But
> I'd prefer to have the information in place and not only as a 
> reference.
> So I'd need some kind of transclusion.
> Any ideas or comments? Has anybody realized such a document in DB? How
> do you manage re-use in DB?
> Best wishes.
> Ludger Thomas
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: 
> docbook-apps-help@lists.oasis-open.org

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