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


In DocBook 4.5, ackno has inline-level content and can
only appear at the end of article. I have seen a need
for an acknowlegements element in books, as a sibling to
chapters.

The proposal for DocBook v5.0 is to remove the ackno element,
add an acknowlegements element, and give it a content
model like that of dedication.  Also allow that element
in article.

A straw poll on the TC showed 6 in favor and 1 opposed (Norm thinks it 
is a bad idea).

Some of the front matter materials have very specific semantics 
(dedication for example), so I would not advise overloading that element 
and using a role attribute (e.g., <dedication role="acknowledgements">). 
The same situation occurs with preface. What if you need a preface, 
foreword and introduction? Do you overload preface?

Another consideration was a more general element that
could use a class attribute to distinguish between them. For example, 
class="dedication" and class="acknowledgements" and perhaps others.

In this way, we could potentially consolidate some of these existing 
front and back matter elements, while providing a generic structure to 
meet future needs without having to adopt new elements.

What would you call such a structure?

Thanks and best regards,

--Scott
begin:vcard
fn:Scott Hudson
n:Hudson;Scott
org:Flatirons Solutions
adr:Suite 200;;4747 Table Mesa Drive ;Boulder;CO;80305;USA
email;internet:scott.hudson@flatironssolutions.com
title:Consultant
tel;work:303-542-2146
tel;fax:303-544-0522
tel;cell:303-332-1883
url:http://www.flatironssolutions.com
version:2.1
end:vcard



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