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] Please respond: adding generic sibling to high-level book components


Camille B«±gnis <camille@neodoc.biz>, 2007-02-22 08:50 +0100:

> Keith Fahlgren a «±crit :
> > On 2/21/07, Scott Hudson <scott.hudson@flatironssolutions.com> wrote:
> >> In absence of any further responses, I think I will recommend an element
> >> called "bookunit" for this purpose. Now the question should be asked:
> > 
> > I don't particularly like the name, but I certainly don't have a
> > better one and hate fighting about names...
> 
> I guess the difficulty to find an appropriate name reflects the fact the
> element is a bit clumsy anyway.

Exactly.

> What about something like <extramatter>.

I don't think it's much of an improvement over bookunit.

> >> What content model should this follow? The same model as
> >> Chapter/Appendix/Preface or Dedication?
> > 
> > Non-restrictive, so dedication is out. Chapter looks fine to me.
> 
> If it's to follow the chapter content model it should be called a ...
> chapter

Along with elements called Appendix, Preface, Dedication,
Acknowledgements.

> to which a class attribute would be added.

So that would result in <chapter class="appendix"> ?

  --Mike


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