[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DocBook Technical Committee Meeting Agenda: 20 February 2013
DocBook Technical Committee Meeting Agenda: 20 February 2013 ============================================================= The DocBook Technical Committee will meet on Wednesday, 20 February 2013 at 1:00pm ET for 90 minutes. Attendance at teleconferences is restricted to members (and prospective members) of the committee. This is the phone number for Wednesday's DocBook TC call: Phone: +1-719-387-5556 Code: 902213 The DocBook TC uses the #docbook 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. Agenda 1. Roll call 2. Accepting the minutes [1] of the previous meeting.3. Next meeting: 20 March 2013 4. Review of the agenda.
5. Review of open action items a. Norm to publish an XSD for 5.1 when it is finished. b. Norm to follow up on OASIS mirroring the schema directory. c. Bob to research how we decided to handle schema extensions. d. Bob to send the proposed slides schema to the TC. e. Larry to try mapping slides to assembly. f. Scott to review Norm's schema update for CALS tables to make sure it meets the requirements for accessibility. g. Bob to look at XInclude 1.1 draft to see if it meets our needs. h. Norm to clarify bridgehead entry in TDG to indicate that bridgeheads are not numbered like sections.6. OASIS website issues
7. Publisher's and eLearning subcommittee reports8. Transclusion in DocBook
9. DocBook 5.1 release 10. Review of Requests for Enhancement To browse a specific RFE, enter the URL (on one line): http://sf.net/support/tracker.php?aid=XXXXXX RFEs to revisit for 6.01907003 biblioid content model too broad
RFEs under discussion 2820947 Ability to transclude text 3035565 Allow sections at any level 3156768 <result> tag 3491860 license tag 3593209 Add see/seealso under 3599576 'info' wrapper element for processing titlepage elements This item was discussed at the last meeting, but there was no action recorded for it. Here are the minutes: "The TC felt that adding an arbitrary wrapper element to info would complicate the schema element model and stylesheet processing, without significant benefit. The capability of adding role to multiple info elements already exists, even if it is more cumbersome than a wrapper." No New RFEs ----- [1] https://lists.oasis-open.org/archives/docbook-tc/201301/msg00007.html Bob Stayton Sagehill Enterprisesbobs@sagehill.net
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]