< Return to Calendar

* DocBook Publishers SC meeting (Conference Call)
Name * DocBook Publishers SC meeting (Conference Call)
Time Wednesday, 09 May 2012, 12:30pm to 01:30pm PDT
(Wednesday, 09 May 2012, 07:30pm to 08:30pm UTC)
Description

 

The DocBook SC for Publishers will meet on Wednesday, 9 May 2012 at:
Denver (U.S.A. - Colorado)    Wednesday, 
9 May 2012 at 1:30:00 PM    MST    UTC-7 hours
San Diego (U.S.A. - California)    Wednesday, 
9 May 2012 at 12:30:00 Noon    PST    UTC-8 hours
Corresponding UTC (GMT)    Wednesday, 
9 May 2012 at 20:30:00

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

-------------------------------------------------------

Meeting information

-------------------------------------------------------

Topic: OASIS DocBook Publishers SC

Date: Wednesday, May 9, 2012

Time: 1:30 pm, Mountain Daylight Time (Denver, GMT-06:00)

Meeting Number: 923 973 472

Meeting Password: DocBook1

-------------------------------------------------------

To start or join the online meeting

-------------------------------------------------------

Go to https://pelco.webex.com/pelco/j.php?ED=194016947&UID=497832417&PW=NNDRjNGE4NjZk&RT=MiM2

-------------------------------------------------------

Teleconference information

-------------------------------------------------------

Provide your phone number when you join the meeting to receive a call back. Alternatively, you can call:

Call-in toll-free number (Verizon): 1-866-917-7712  (US)

Call-in number (Verizon): 1-210-795-2663  (US)

Show global numbers: https://wbbc.verizonbusiness.com/wbbcClick2Join/servlet/WBBCClick2Join?TollNumCC=1&TollNum=210-795-2663&TollFreeNumCC=1&TollFreeNum=866-917-7712&ParticipantCode=75215950&customHeader=mymeetings&dialInNumbers=true

Attendee access code: 752 159 50


The DocBook SC for Publishers uses the #dbpub IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.
Minutes

 

  1. Roll call
    1. Scott Hudson
    2. Dick Hamilton
    3. Nic Gibson
  2. Next meeting:  6 Jun 2012
  3. Review of the agenda.
  4. Review of ACTION items:
    1. ​Scott to send spec source to Nic: COMPLETE
    2. Nic to create the draft spec: CONTINUE
    3. Need everyone to test publishers samples on sourceforge with the stylesheets contributed by Nic Gibson: CONTINUE. Nic tested and would like to tweak output. Everyone to provide additional feedback to Nic. Need to add processing of Dublin Core still.
    4. Scott to forward stylesheets to the list: COMPLETE
    5. Scott to bring HTML table issue to TC and post comment on sourceforge RFE: COMPLETE. Awaiting discussion in next TC meeting.
  5. Specification Draft status
    • 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"
    • time schedule? when should we close the period for review? (June meeting). Call for RFEs went out a month ago. Wait for 1 additional month for additional RFEs, if no new RFEs, plan to release the draft spec by 15 July 2012
    • Nic has some additions from Penguin UK that could be considered: canto, stanza, stage direction, multiple characters speaking simultaneously (Pygmalion example). ACTION: Nic to contact Penguin to see if the source could be made available for markup example.
  6. Modify Schema
    1. Norm has already posted a 1.1b1 to http://www.docbook.org/schemas/5x-custom.html#pub5x. Need to add accepted RFE changes.
    2. 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.


7. Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):
  • 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. Need to add to spec and schema. ACTION: Scott to provide RNC include markup.
     
  • 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.htmlPreference 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).
  • 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. ACTION: All to review standard.rnc from Nic and propose any backward-compatible changes to the model. These should be entered in the sourceforge tracker.

 db.poetry =
   
    ## A container for poetry.
   element poetry {
     db.poetry.attlist,
      
db.all.blocks*,
      db.poetry.info?,
     (db.mediaobject | db.linegroup | db.line)+
   }

8. Nathalie brought up the Editeur initiative, where DocBook could be increasingly used. Please review. 

http://www.editeur.org/109/Enabling-Technologies-Framework/



Agenda

 

  1. Roll call
    1.  
  2. Next meeting:  
  3. Review of the agenda.
  4. Review of ACTION items:
    1. ​Scott to send spec source to Nic: COMPLETE
    2. Nic to create the draft spec
    3. Need everyone to test publishers samples on sourceforge with the stylesheets contributed by Nic Gibson.
    4. Scott to forward stylesheets to the list: COMPLETE
    5. Scott to bring HTML table issue to TC and post comment on sourceforge RFE: COMPLETE. Awaiting discussion in next TC meeting.
  5. Specification Draft status
    • 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"
    • 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.
  6. Modify Schema
    1. Norm has already posted a 1.1b1 to http://www.docbook.org/schemas/5x-custom.html#pub5x. Need to add accepted RFE changes.
    2. 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.


7. Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):
  • 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. Need to add to spec and schema.
     
  • 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.htmlPreference 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).
    •  
  • 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)+
   }
}



Submitter Mr. Scott Hudson
GroupDocBook Publishers SC
Access This event is visible to DocBook Publishers SC and shared with
  • OASIS Open (General Membership)
  • General Public
  • OASIS DocBook TC