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] Proposal for "cover"


On Thu, 2006-02-16 at 14:10 -0500, Norman Walsh wrote:
> In response to RFE 1416903[1], the TC agreed to add a "cover" element
> to "info". The purpose of "cover" is to contain the front and back
> cover copy of a book. The element is designed to be general enough to
> support any possible combination of front, inside-front, inside-back,
> back, dust jacket, dust jacket foldovers, spine, etc.
> 
> Accordingly, the processing expectations of "cover" will be fairly
> loose.

Loose as in 'configurable', as per the main cover?

> 
> I propose the following content model for cover:
<snip/>
> 
> That's intended to be db.all.blocks+ (i.e., the content model of
> sidebar[2]) except for db.admonition.blocks, db.formal.blocks, and
> db.indexterm. None of which belong on a cover, IMHO.

Sounds good to me.
The 'cover' I was thinking of was the 4th page (for an O'Reilly)
which has the bibliographers/librarians 'stuff'
I.e. the formal title, revision, Print history etc.
I think Norm's list covers that pretty well.

Also, it's possible that default processing would
render it as seen in many books.
+1 Norm.

regards DaveP





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