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

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

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


Subject: sample files structure vs. module


Hi,
I'm following up on a DocBook TC action item on Larry and me to prepare sample files of the alternatives to the top-level assembly structure that we discussed at the last meeting.

To refresh your memory, I made a proposal to allow the structure element in an assembly to have a resourceref attribute like module, so that its resource could contain the root element, its attributes, and any front matter like info, acknowledgements, and dedication. We discussed alternative ways to achieve the same thing.

The attached zip file contains the sample files for your review. I added a comment to each, just before the structure, that explains each example. Below is a summary as well. I hope you can review this before the meeting.

sample1: Uses structure to define book root element, and a child module referencing
book with contentonly="true" to pull in front matter.  This one is almost legal in the
current schema (currently info is required on structure).

sample 2. Structure has single child module referencing book top-level, and structure
element does not contribute.

sample 3:  Uses structure modeled like module to reference the book module directly
(my proposal).

sample 4.  Same as 3 except renames structure to module.


Bob Stayton
Sagehill Enterprises
bobs@sagehill.net


----- Original Message ----- From: "Bob Stayton" <bobs@sagehill.net>
To: "Larry Rowland" <larry.rowland@hp.com>
Sent: Monday, November 14, 2011 1:52 PM
Subject: sample files structure vs. module


Hi Larry,
I put together a short sample showing the various approaches to the top level
structure element that we discussed.  I added a comment to each, just before the
structure, that explains each example.  Below is a summary as well.  I'd like you to
review this so we can send it out to the TC before the meeting.

sample1: Uses structure to define book root element, and a child module referencing
book with contentonly="true" to pull in front matter. This one is almost legal in the
current schema (currently info is required on structure).

sample 2. Structure has single child module referencing book top-level, and structure
element does not contribute.

sample 3:  Uses structure modeled like module to reference the book module directly
(my proposal).

sample 4.  Same as 3 except renames structure to module.

Comments?

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net


Attachment: structure-samples.zip
Description: Zip compressed data



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