[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DITA Technical Committee Meeting Minutes: 1 March 2011
DITA Technical Committee Meeting Minutes: 1 March 2011 Chaired by Don Day donday@bga.com and Kristen Eberlein <keberlein@stl.com> Minutes recorded by Bruce Nevin <bnevin@cisco.com> The DITA Technical Committee met on Tuesday, 1 March 2011 at 08:00am PT for 55 minutes. 8:00-8:05 Roll call o Regrets: JoAnn Hackos, Eliot Kimber o Quorum was established. STANDING BUSINESS: Approve minutes from previous business meeting: o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00068.html (Bruce Nevin, Tue, 22 Feb 2011 11:53:45 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00069.html (Paul Grosso, Tue, 22 Feb 2011 13:13:41 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00070.html (Bruce Nevin, Tue, 22 Feb 2011 12:23:11 -0600) Moved by Don Day, seconded by Chris Nitchie, approved by acclamation. Subcommittee/liaison reports: o OASIS DITA Enterprise Business Documentation Subcommittee Bruce summarized yesterday's meeting, which Don attended. There was a growing sense that "enterprise Business documents" no longer accurately describes the scope of issues we are grappling with, and has deterred members of other TCs from taking an interest. Three areas of work have resulted in white papers on the SC wiki: 1. Simplified topics Many elements and attributes are of interest only in tech docs, and are useless and confusing in enterprise, government, and other contexts of adoption. Most are in omissible specialization modules, but some are in <topic>. We see that "simplified DITA" is incorrect and misleading. Rather, what the TC has delivered might be said to be "(somewhat) specialized DITA". Don suggested "adoptable DITA", though clearly this is appropriate for use only amongst ourselves, and a marketing term will be called for. 2. Aggregated authoring We have explored various alternatives for presenting the user experience of a seamless document in the editing environment while managing topics and maps under the hood. Our thinking has converged on transforms between <ditabase> and topics in maps. Don presented his dita4all demo at http://learningbywrote.com/tb01/dcc/. 3. Metamodel Our investigation turned up a great diversity of document types. These fall into a number of families that are distinct in structure, semantics, and process. Rob Hanna has developed a metamodel that delineates the common structure within each family, and articulates their interrelationships of semantics and process. Initially, this was presented as an abstract layer of information types from which document types would be specialized. This should be understood not as an architectural proposal but as a way of clearly stating the problem space and presenting it to the TC for solution. Adopters are coming to DITA from divergent areas with divergent requirements. Specialization by adopters or developments by subcommittees need the metamodel as an overarching framework for proceeding in an orderly way and with mutual consistency so as to support unforeseeable future interoperability requirements. o OASIS DITA Adoption TC (deferred; has not met since last reporting here) o OASIS DITA Learning Content Subcommittee (next week) ACTION (Don): Ask John Hunt to prepare a report for next week. BUSINESS: 1. ITEM: Question about the order in which keys are resolved E-mail discussed at February 8 meeting: o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00057.html (Kris Eberlein, Fri, 21 Jan 2011 11:15:56 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00058.html (Chris Nitchie, Fri, 21 Jan 2011 12:37:08 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00059.html (Eliot Kimber, Fri, 21 Jan 2011 12:36:40 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00060.html (Paul Grosso, Fri, 21 Jan 2011 14:17:05 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00061.html (Bruce Nevin, Fri, 21 Jan 2011 13:28:03 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00062.html (Chris Nitchie, Fri, 21 Jan 2011 14:37:13 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00063.html (Bruce Nevin, Fri, 21 Jan 2011 13:45:59 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00064.html (Eliot Kimber, Fri, 21 Jan 2011 13:54:50 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00065.html (JoAnn Hackos, Sat, 22 Jan 2011 10:23:25 -0700) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00090.html (Eberlein, Fri, 28 Jan 2011 09:08:43 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00091.html (Eliot Kimber, Fri, 28 Jan 2011 08:19:52 -0600) Action (8 February): Eliot Kimber to draft a FAQ item about this issue; work completed. Action (15 February): Kris Eberlein to edit FAQ item; work completed. Action (22 February): Eliot to review FAQ item as reworked by Eberlein. See FAQ-items. PENDING Elliot's action. 2. ITEM: Key resolution for complex <topicmeta> content E-mail discussed at 15 February meeting: o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00010.html (Su-Laine Yeo, Mon, 7 Feb 2011 18:23:45 -0800) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00012.html (Eliot Kimber, Tue, 8 Feb 2011 06:21:10 -0600) E-mail discussed at 22 February meeting: o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00059.html (Robert Anderson, Mon, 21 Feb 2011 11:33:42 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00060.html (Chris Nitchie, Mon, 21 Feb 2011 13:45:41 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00063.html (Su-Laine Yeo, Mon, 21 Feb 2011 16:53:57 -0800) New e-mail: o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00071.html (Su-Laine Yeo, Tue, 22 Feb 2011 19:31:31 -0800) Action (15 February): Michael Priestley and Robert Anderson to have a call; they'll discuss this item (among others) and post to the list. Work completed. Action (22 February): Su-Laine Yeo to draft a FAQ item. Consensus achieved re discussion in 2/22 email. It probably makes sense to call this out in the spec, since we do call out comparable issues. Su-Laine will proceed with the FAQ item. 3. ITEM: Conditional processing before/after keyspace construction E-mail discussed at 15 February meeting: o http://lists.oasis-open.org/archives/dita/201102/msg00022.html (Su-Laine Yeo, Tue, 8 Feb 2011 13:11:58 -0800) o http://lists.oasis-open.org/archives/dita/201102/msg00023.html (Eliot Kimber, Tue, 8 Feb 2011 15:21:33 -0600) o http://lists.oasis-open.org/archives/dita/201102/msg00024.html (Su-Laine Yeo, Tue, 8 Feb 2011 13:29:59 -0800) o http://lists.oasis-open.org/archives/dita/201102/msg00025.html (Su-Laine Yeo, Tue, 8 Feb 2011 15:37:54 -0600) o http://lists.oasis-open.org/archives/dita/201102/msg00026.html (Kris Eberlein, Tue, 8 Feb 2011 16:56:26 -0500) o http://lists.oasis-open.org/archives/dita/201102/msg00027.html (Su-Laine Yeo, Tue, 8 Feb 2011 14:23:27 -0800) o http://lists.oasis-open.org/archives/dita/201102/msg00028.html (Robert Anderson, Tue, 8 Feb 2011 17:36:42 -0500) o http://lists.oasis-open.org/archives/dita/201102/msg00029.html (Eliot Kimber, Tue, 8 Feb 2011 16:44:03 -0600) Action (15 February): Michael Priestley and Robert Anderson to have a call; they'll discuss this item (among others) and post to the list. OPEN pending action by Michael Priestley. 4. ITEM: Conref range: Is constraint on last member of range necessary or useful? E-mail discussed at 15 February meeting: o http://lists.oasis-open.org/archives/dita/201102/msg00031.html (Eliot Kimber, Thu, 10 Feb 2011 07:03:18 -0600) o http://lists.oasis-open.org/archives/dita/201102/msg00032.html (Michael Priestley, Thu, 10 Feb 2011 08:25:31 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00033.html (Eliot Kimber, Thu, 10 Feb 2011 09:02:47 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00034.html (Michael Priestley, Thu, 10 Feb 2011 10:21:38 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00035.html (Eliot Kimber, Fri, 11 Feb 2011 05:54:38 -0600) E-mail discussed at 22 February meeting: o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00052.html (Elio Kimber, Thu, 17 Feb 2011 06:25:20 -0600) Action (15 February): Michael Priestley to write a warning. Action (22 February): Kris Eberlein to move this to the list of potential DITA 1.3 work items. Completed. Michael concurs with Eliot's formulation in email of 22 February. This is among the work items to be incorporated in the DITA 1.3 spec. CLOSED 5. ITEM: General implications of multiple uses of the same topic with different keys E-mail discussed at 15 February meeting: o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00036.html (Eliot Kimber, Sat, 12 Feb 2011 06:57:41 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00037.html (Chris Nitchie, Mon, 14 Feb 2011 17:05:47 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00038.html (Eliot Kimber, Mon, 14 Feb 2011 17:31:26 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00040.html (Chris Nitchie, Mon, 14 Feb 2011 22:04:02 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00041.html (Eliot Kimber, Mon, 14 Feb 2011 21:47:07 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00042.html (Chris Nitchie, Tue, 15 Feb 2011 08:27:22 -0500) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00043.html (Eliot Kimber, Tue, 15 Feb 2011 07:56:28 -0600) E-mail discussed at 22 February meeting: o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00053.html (Eliot Kimber, Thu, 17 Feb 2011 06:36:05 -0600) ACTION (Michael): write this up and post it to the alias. 6. ITEM: Refinements to DITAVAL for flagging E-mail discussed at 22 February meeting o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00054.html (Eliot Kimber, Fri, 18 Feb 2011 07:02:58 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00055.html (Seth Park, Fri, 18 Feb 2011 14:15:48 +0000) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00056.html (Eliot Kimber, Fri, 18 Feb 2011 09:11:37 -0600) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00057.html (Seth Park, Fri, 18 Feb 2011 15:29:19 +0000) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00058.html (Eliot Kimber, Fri, 18 Feb 2011 09:48:11 -0600) o On 22 February we decided to remove this from the agenda, but then a new e-mail hit the list. New e-mail (this may best be a new topic): o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00073.html (Jonatan Lundin, Wed, 23 Feb 2011 11:50:39 +0200) o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00083.html (Jonatan Lundin, Thu, 24 Feb 2011 17:32:40 +0200) ACTION (Kris): ask Jonathan to attend the TC call to represent his concerns in discussion, at a time when Eliot and other discussants also are present. IBM also is doing some work in this area, and should be represented. 7. ITEM: Question on keyref processing for <data> element E-mail discussed at 22 February meeting: o http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00061.html (Su-Laine Yeo, Mon, 21 Feb 2011 14:11:31 -0800) Action (22 February): Su-Laine Yepo to address this in the FAQ item about "Key resolution for complex <topicmeta> content" OPEN until FAQ written. 8. NEW ITEM: Question on keyref and duplicate element IDs in composite documents http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00072.html (Su-Laine Yeo, Tue, 22 Feb 2011 20:20:13 -0800) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00074.html (Eliot Kimber, Wed, 23 Feb 2011 06:01:49 -0600) CLOSED. Question answered. 9. NEW ITEM: Vertical industry vocabulary in DITA 1.3 http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00075.html (Eliot Kimber, Wed, 23 Feb 2011 06:34:07 -0600) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00076.html (Chris Nitchie, Wed, 23 Feb 2011 08:01:34 -0500) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00077.html (Bruce Nevin, Wed, 23 Feb 2011 08:16:00 -0600) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00078.html (Eliot Kimber, Wed, 23 Feb 2011 08:25:41 -0600) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00080.html (Bryan Schnabel, 23 Feb 2011 09:27:56 -0800) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00081.html (Su-Laine Yeo, 23 Feb 2011 10:58:02 -0800) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00082.html (Eliot Kimber, Wed, 23 Feb 2011 13:26:26 -0600) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00084.html (Bruce Nevin, Thu, 24 Feb 2011 11:29:44 -0600) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00087.html (Eliot Kimber, Thu, 24 Feb 2011 14:35:17 -0600) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00089.html (Bruce Nevin, Thu, 24 Feb 2011 17:20:07 -0600) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00090.html (Eliot Kimber, Thu, 24 Feb 2011 17:57:30 -0600) This is related to the discussion that led to a proposal to factorize into separate packages. Either develop a base spec that is part of the DITA spec, or produce a delta spec that requires its own approval process. Still very sympathetic to this, but the counter-arguments were compelling, and seem still to be effective. Kris: and the OASIS approval process is more complex now, there's even more overhead. Those who were not in that conversation were surprised at the size of the 1.2 spec. If a SC does the work, a usable work product can be created as a committee draft, and that will be adopted as a de facto standard. There shouldn't be an assumption that it will be part of the core DITA standard. If no one wants to own it, why should we do it? Learning & Training SC completed their work before any draft of the 1.2 standard was ready. Su-Laine: it was hard to get responses to questions about the many issues that came up in review. A committee draft (presenting SC work) has its own review process separate from the current spec release. This implicates the BusDocs SC metamodel. Would be good to present metamodel to TC, and make it TC work going forward. ACTION (Bruce): Ask BusDocs SC and Rob Hanna to present metamodel to TC. 10. NEW ITEM: Keyref to <mapref> element http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00094.html (Eliot Kimber, Sun, 27 Feb 2011 10:50:51 -0600) http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201102/msg00096.html (Chris Nitchie, Mon, 28 Feb 2011 09:03:19 -0500) Chris : xref to keyref where href points to a map rather than a topic : all topics, first topic, or undefined? Chris expects undefined. Su-Laine: Agree w/ Eliot that it's a lot more useful if defined. Agree it should be consistent with xref with format=ditamap. ACTION (Kris): Add to the 1.3 list of documentation changes a proposal to clarify this, with Eliot as owner. 11. NEW ITEM: Usage of <data-about> Sun, 27 Feb 2011 10:50:53 -0600 (Eliot Kimber, Sun, 27 Feb 2011 10:50:53 -0600) This was essentially a question who was using <data-about> and what for, the toolkit doesn't recognize it. Some uses under the hood mentioned. Arbortext uses it for data interchange, and IBM is using it in some ways. <data> and <data-about> are defined as something that processors should ignore. 8:55 PT Adjourn
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]