Re: [docbook] Is Docbook Assembly easier to process than standard Docbook?

[Thomas Schraitle <tom_schr@web.de>]

Hi Lech,

Am Dienstag, 3. Juli 2012, 16:12:21 schrieb Lech Rzedzicki:
> I'm sure there's good reasons for DB Assembly to be the way it is right
> now, but I need to understand those reasons.

I'm also investigating assemblies and I would like to offer some of my 
thoughts.

 
> If I need to read or modify, let's say the first para of a topic, I have to
> parse the <structure>, fetch the id from the the module, then parse the
> resources to fetch the URI of the actual file and finally fetch and parse
> the topic and grab the first para.
> Had this been one big file, it'd simply be current-topic/para[1].

This is true to some extend, but I wouldn't consider that as a problem.

A complex document is usually split up in several pieces (parts, chapters, 
maybe even sections). This makes it a LOT easier to edit than the complete 
document. This is a very reasonable approach especially if you work in a team.

However, an assembly can be used to define your deliverable. For example, it 
can hold a user guide, a reference guide, and maybe some quick start. Let's 
assume, we have your "topic" which is used inside the quick start and also in 
our user guide, but it is not needed in the reference guide. 

How will you be able to get your first para of your respective topic if you 
don't process the assembly? You don't know. You can only be sure, if you 
process your assembly file, create the "big file" and see, if it's inside your 
deliverable.

Hope you get the idea. :) Well, at least, that's my understanding. Maybe I'm 
completely wrong as assemblies are a new topic. ;)


> [...]


-- 
Gruß/Regards
  Thomas Schraitle