[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DITA TC meeting minutes, Oct 24, 2006 (list copy)
Clear text list copy of contents of http://lists.oasis-open.org/archives/dita/200610/msg00072.html DITA Technical Committee Meeting Minutes: 24 October 2006 Recorded by Bruce Esrig (esrig-ia@esrig.com) The DITA Technical Committee met on Tuesday, 24 October 2006 at 08:00am PT for 60 minutes. 1. Roll call We have quorum. DITA TC Wiki: http://wiki.oasis-open.org/dita/FrontPage Request a scribe for today's minutes: Bruce Esrig 8:00-8:05 Roll call. We have quorum. Approve minutes from previous business meeting: * http://lists.oasis-open.org/archives/dita/200610/msg00057.html (17 Oct) Moved, seconded, and approved by acclamation. Announcements (at end of meeting): Chris Kravogel: Machine SC met today. It will meet next week and then every two weeks. JoAnn Hackos: Deadline for speaker submissions for next CMS conference in March is next week. Business: Items 1 and 2 were resolved. Item 8 was previously resolved. The remaining items will remain on the agenda. 1. ITEM: Proposal: Update foreign topic to include processing info for generalization/specialization use case o http://lists.oasis-open.org/archives/dita/200610/msg00062.html Robert Anderson, speaking on behalf of a group, proposes to externalize the foreign content and refer to the foreign content using an <object> element. Robert Anderson moves, Michael Priestly seconds. Approved by acclamation. 2. New item: content model of reltable for bookmap o http://lists.oasis-open.org/archives/dita/200610/msg00065.html (Grosso) (Background information, Michael Priestly:) The chapter element in bookmap (i.e. at the map level) points to an ordinary topic. (Robert Anderson:) To use reltable as currently defined, you need to express chapter as an ordinary topicref. (E. Hennum:) Is it important to indicate relationships between chapters? We are using the bookmap to do the organizing. (JoAnn Hackos:) Views links to other chapters as a poor practice, but others consider relationships possible, and have seen them. (Paul Grosso, acknowledging question by Don Day:) How to support copy and paste? (Erik Hennum:) This would copy the whole chapter. (Michael P.:) Copy and paste is already problematic for structural elements. Could treat copy of chapter specially (to improve usability of implementations). The special treatment would be only to copy the top level and convert it to a topicref. (Robert A.:) To allow chapter in reltable, we’d have to specialize reltable to bookmapreltable, so we wouldn’t be able to copy reltables from elsewhere into bookmap. Result of the discussion is to keep the status quo, which would leave it up to user interfaces to conveniently support references to chapters in reltables. Moved by Grosso, seconded by Anderson, accepted by acclamation. 3. ITEM: inherited attribute values in a DITA relationship table o http://lists.oasis-open.org/archives/dita/200610/msg00070.html (MP) o http://lists.oasis-open.org/archives/dita/200610/msg00029.html (Grosso) Discussion: (Michael Priestly) Table, row, cell has a clear hierarchy. If column attributes are specified, they are defining the behavior for all rows, whereas the row behavior does not define the behavior of all columns. Rows define relationships. Columns define patterns. The patterns take priority. Held over to next meeting to allow review. 4. ITEM: Status of Nested Sections Issue o http://lists.oasis-open.org/archives/dita/200610/msg00060.html (MP latest) Feedback from Chris Kravogel: Agrees with Michael’s answer to the given example. There are deeper examples. Proposes a separate block-like element above and below section. Pure topic-based authoring becomes a serious obstacle against adoption, weighing against favorable view due to specialization. Response from Michael Priestly: What is the reason that using nested topics is an obstacle? CK: Context-based authoring. Context in one body with the content. MP: Would blocks help with that? How do blocks help? CK: Think of body with … <body>text <section>…</section> further text</body>. MP: Wouldn’t “further text” need a title? The output on the page won’t reflect the end of the <section>. Suggests policy: trailing content is included in previous heading, or gets its own heading. This preserves the output. Not hypothetical. It worked for our users. JoAnn Hackos: Eliot Kimber’s message about this was to discuss deeply-nested headings. Users don’t understand deeply-nested material (beyond two or three levels of heading). CK and MP plan to have a separate call with the CK customer. Don Day: Seek best practices for migrators and for consultants creating specializations. How should someone approach nested sections when converting to DITA? Michael referenced “compound documents” which allow nesting topics of different types. Bruce Esrig: Sounds as though the <section> mentioned by CK is an inserted element in a larger flow. CK: Will try to get a better example from the customer. Action CK: organize call. No action in the TC pending separate conference call. Discussion to continue. 5. ITEM: Use of standardized prefixes when incorporating foreign vocabularies o http://lists.oasis-open.org/archives/dita/200610/msg00021.html 6. ITEM: Versioning of DITA public identifiers o http://lists.oasis-open.org/archives/dita/200610/msg00025.html 7. ITEM: metadata behaviour in maps o http://lists.oasis-open.org/archives/dita/200610/msg00012.html 8. ITEM: treating index-see as index-see-also o http://lists.oasis-open.org/archives/dita/200610/msg00014.html (Paul Grosso) Resolved last week. 9. ITEM: Ongoing review of 1.1 drafts: o Architectural Spec (Michael Priestley) * http://lists.oasis-open.org/archives/dita/200609/msg00030.html (Arch Spec) o Language Spec (Don Day) * http://lists.oasis-open.org/archives/dita/200609/msg00027.html (Lang Spec) o http://lists.oasis-open.org/archives/dita/200609/msg00005.html (1.1 XSDs) o http://lists.oasis-open.org/archives/dita/200609/msg00004.html (1.1 DTDs) Regards, -- Don Day Chair, OASIS DITA Technical Committee IBM Lead DITA Architect Email: dond@us.ibm.com 11501 Burnet Rd. MS9033E015, Austin TX 78758 Phone: +1 512-838-8550 T/L: 678-8550 "Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" --T.S. Eliot
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]