DITA Technical Committee Meeting Minutes: 16 October 2007 (Recorded by Alan Houser ) The DITA Technical Committee met on Tuesday, 16 October 2007 at 11:00am EDT for 60 minutes. 1. Roll call We have quorum. 2. Approve minutes from previous business meeting: http://lists.oasis-open.org/archives/dita/200710/msg00024.html (9 October 2007) Approved by acclamation. Business Items Business: 1. ITEM: Reviewing prepared proposals 1. Proposal #12020: Generic "text" element * http://www.oasis-open.org/committees/download.php/25723/IssueNumber12020.html Stan Doherty -- Proposal adds to 5 elements and to another four. Allows small reuse of text and make extensible. Michael Priestley -- Tech requirements call out which content models are changing. Even though small number of CMs are changing, has effect on large number of specializations. Effect on specializations is not spelled out. Should be in proposal. For example, all specializations get , even though some are specializations of keyword. For each specialization -- proposal needs to specify whether each specialization will get: text, keyword, or ph. Also issue with text of proposal regarding lack of semantics. Action: Will request that Deborah Pickett update proposal. If DP agrees with MP’s comments, will be up for vote. 1. ITEM: Review prepared proposals: 1. ITEM: #12013 Referencing a range of elements (Etassam) * http://www.oasis-open.org/committees/download.php/25611/dita_1.3_conrefrange_v3.html Michael Gannon -- current conref mechanism only supports a single element. Proposal supports referencing a range of nodes by addressing the first and last node in the range. Intermediate nodes need not have an id attribute. Existing conref attr marks start of range. New conrefend marks end of range. Existance of conrefend indicates range. Beginning and end must be of same type. Must be same as or generalizerable back to same type as referencing element. Parent must be generalizable to same type. Eliot Kimber -- Why this constraint? Michael Priestley -- Current proposal preserves promise of conref validity. Also checks container element for validity of conref’ed range. Proposal supports conref of a range of steps -- a popular use case. MP proposes to stage for formal vote, Michael Gannon seconds. Staged for vote next week. 1. ITEM: MUST, SHOULD, MAY rollup * http://lists.oasis-open.org/archives/dita/200710/msg00013.html (Priestley) Jeff Ogden -- not controversial We just need to agree which one to use where, and be consistent. 1. How much flexibility do specializers have to make exceptions to behaviors that are outlined in the DITA standard? This is a spin off from issue 12055, but it is also related to item #3 above. I’ll send out another message later today or tomorrow to outline the issue. http://lists.oasis-open.org/archives/dita/200710/msg00025.html Move to email discussion on TC list. ---- 2. What does it mean when we say that an implementation supports the DITA standard? Is the entire standard required or are some parts optional? MP -- dependent on item 1. 1. Is the approach outlined in the proposed DITA 1.2 documentation TOC a good approach? The proposed TOC is available here: http://wiki.oasis-open.org/dita/Draft_1.2_TOC MP -- Jeff or I will kick off discussion after 1 and 2 are resolved. 1. Is the scope of DITA 1.2 as it is shaping up too large? Is the DITA specification becoming too complex? MP -- These are larger issues with cascading effects. Not comfortable staging for discussion next week. JO -- suggestion -- include at end of TC regular business agendas, for discussion over several weeks. JO -- Encourage all to contribute. Even if you have no opinion, say so on the list. ---- Action: MP has keyref proposal ready. Contact MP if you would like to participate in reviewing proposal. ---- New ITEM: URI Scheme for TC Subcommittees (Sirois) http://lists.oasis-open.org/archives/dita/200710/msg00000.html Eric Sirois -- as subcommittees are preparing to deliver DTDs and schemas, 1.1 introduces uri scheme to uniquely identify components of schemas. Proposal is to extend uri scheme to subcommittees. Main difference from dita 1.1, add two pieces of information: - SC for subcommittee - Subcommittee name Would allow unambiguous referencing of DTDs/schema in catalogs and documentation. Discussion deferred until next week. Please comment on-list. Adjourned at noon EDT.