- Roll call
- Scott Hudson
- Dick Hamiltion
- Nic Gibson
- Next meeting: 9 May 2012
- Review of the agenda.
- Create Specification Draft
- Use "5.0-variant publishers-1.0" per discussion/decision from docbook-tc list. Need to ensure this is documented in specification. Next version will likely be 1.1 and based on DocBook v5.1, so would be identified by "5.1-variant publishers-1.1"
- ACTION: Nic to create the draft.
- ACTION: Scott to send the location of the spec source to Nic.
- time schedule? when should we close the period for review? Call for RFEs went out yesterday. Wait for 1 month for additional RFEs, if no new RFEs, plan to release the draft spec by 15 July 2012.
- Modify Schema
- Norm has already posted a 1.1b1 to http://www.docbook.org/schemas/5x-custom.html#pub5x. Need to add accepted RFE changes.
- Propose:
## A short inscription at the beginning of a document or component
element epigraph {
db.epigraph.attlist,
db.epigraph.info,
db.attribution?,
(db.para.blocks | db.literallayout | db.publishers.blocks)+
}
db.publishers.blocks = db.dialogue | db.poetry | db.drama
db.extension.blocks = db.publishers.blocks
This construct should be backwards compatible and prevent accidental expansion of content models if anyone overrides db.extension.blocks.
6. ACTION: Need everyone to test publishers samples on sourceforge with the stylesheets contributed by Nic Gibson.
ACTION: Scott to forward stylesheets to the list.
7. Review of Requests for Enhancement
- 3519024 Add admonitions to Publishers - working with textbook publishers and identified a need for caution, warning and notes. Want to take advantage of existing XSLT. Small set of elements that would be re-introduced (caution, important, note, tip, warning). Unanimously APPROVED.
- 3292583 Include HTML table model by default – general question for DocBook TC: should CALS be updated to be more compatible with accessibility? CALS hasn’t seen an update since 1999! http://www.oasis-open.org/specs/tm9901.html Preference is to extend existing CALS model rather than allowing the complexity of multiple table models. Also missing some of the presentational (shading/color) that HTML has. Might be able to use role attribute to fit into the HTML class attribute on output (for CSS styling).
- ACTION: Scott to bring this issue to TC and post comment on sourceforge RFE.
- Nic planning to put in a new RFE for restriction of the poetry model. (what about cantas, stanza, verses?) May not be possible due to backwards compatibility rules.
db.poetry =
## A container for poetry.
element poetry {
db.poetry.attlist,
db.all.blocks*,
db.poetry.info?,
(db.mediaobject | db.linegroup | db.line)+
}
}
|
DocBook Publishers SC (Conference Call)