-------------------------------------------------------
OASIS DITA Technical Committee Minutes
Tuesday, 23 June 2009
-------------------------------------------------------
Minutes recorded by Kristen James Eberlein.
1. ROLL CALL
Present: Robert Anderson, Stan Doherty, Jim Earley, Paul Grosso, Chris
Kravogel, Bruce Nevin, Seth Park, Su-Laine Yeo, Kristen Eberlein, JoAnn
Hackos, Gershon Joseph, Michael Priestley, Don Day, Craig Keyes, Steve
Studer, John Hunt, Nancy Harrison, Darryl Tewes, Anne Rockley
Regrets: Rob Frankland, Elliot Kimber
Quorum is present.
2. APPROVE MINUTES FROM PREVIOUS MEETING
* http://lists.oasis-open.org/archives/dita/200906/msg00118.html (Seth
Park, 16 June 2009)
Motion made to approve minutes; seconded by Kristen Eberlein; motion
carried by acclamation.
3. SUBCOMMITTEE REPORTS
* OASIS DITA Translation Subcommittee is reviewing a best practices article
about glossaries.
* OASIS DITA Learning Content Subcommittee is scheduled to report on 30
June 2009.
Two new subcommittee have been proposed: OASIS DITA Mashup Subcommittee and
OASIS DITA Technical Communication Subcommittee. The Mashup SC has a
planning call scheduled on 30 June; contact Seth Park for more information.
Gershon Joseph drafted a charter for the Tech Comm SC and asked for
comments and potential members. Darryl Tewes, Chris Kravogel, and Bruce
Nevin expressed interest
DITA Mashup SC planning call: *
http://tech.groups.yahoo.com/group/dita-users/message/14618 (Seth Park)
DITA Technical Communication SC proposed charter:
http://lists.oasis-open.org/archives/dita/200906/msg00144.html (Gershon
Joseph)
Action (23 June 2009):
----------------------
Gershon Joseph to refresh the charter proposal package for the OASIS DITA
Technical Communication Subcommittee in accordance with the OASIS policies
and procedures section on subcommittee resolution votes.
4. ADMINISTRIVIA
Don Day will not be present on 7 July 2009; Gershon Joseph will chair the
call.
5. REVIEW MASTER TOPIC LIST
Kris Eberlein uploaded a draft of the architectural spec in both CHM and
TOCjs format:
* http://www.oasis-open.org/committees/download.php/32957/archspec.chm (16
June 2009)
*
http://www.oasis-open.org/committees/download.php/32968/archspec_tocjs.zip
(17 June 2009)
Gershon thanked authors for meeting the first deadline, as well as Stan
Doherty for completing his work on the review. He encouraged other TC
members to participate in the review, which is scheduled to end 30 June
2009, and to add their comments to the Wiki page. You can access the Wiki
pages for the review from http://wiki.oasis-open.org/dita/TechReview1.
Don Day reminded Gershon and Kris to update the review section of the DITA
Wiki before each week's TC call.
Chris Kravogel asked whether the Language Specification was frozen; Robert
Anderson replied that comments should be sent to him. Nancy Harrison
commented that she had included material from the Language Spec in the
Architectural Spec and needed to communicate with Robert about that. Kris
Eberlein commented that she had added draft comments to sections of the
Architectural Spec where she saw overlap between the two documents, and
that she thought that duplicate material should be single-sourced between
the Language Spec and the Architectural Spec. Robert Anderson commented
that the TC had previously discussed combining the two specs into single
document packages: base, tech comm, and learning and training. He had given
up on working on this, since it didn't seem fruitful until there was a
draft of the Architectural Spec. Robert further added that this strategy
was heavily discussed by the TC previously; the only concern raised was
whether it would make the document more difficult to use. They decided that
there was no way to know without prototyping and that could not be done
until there was content for the Architectural Spec.
Don Day raised the point that someone has offered to publish the DITA 1.2
specification as a book. Gershon commented that the XLIFF specification has
architectural information first, followed by language reference material.
John Hunt raised the point that the Learning and Training Subcommittee
needs to be included in such discussions; Don commented that *all*
subcommittees needs to be involved. Robert Anderson pointed out that the
Language Spec already is delivered in several version, in preparation for
the specification reorganization. Robert Anderson reiterated again that the
TC should review the previous discussion of a year or more ago (which
should be documented in a e-mail thread) before rehashing the discussion.
Robert Anderson to compile a list of the previous e-mail exchanges and post
it to the list, if possible.
Action (23 June 2009)
---------------------
Gershon Joseph or Kris Eberlein to add discussion of how to deliver the
DITA 1.2 specifications (Separate Language and Architectural
Specifications? Combined Language and Architectural Specification?) to the
specifications subagenda.
5. ITEM: MEANINGFUL VALUES FOR TYPE= ON XREF AND TOPICREF
* http://lists.oasis-open.org/archives/dita/200905/msg00033.html
Action (26 May 2009): Eliot to do a write-up.
Left open for next week.
6. ITEM: REFERENCING A BOOKMAP FROM A MAP
* http://lists.oasis-open.org/archives/dita/200906/msg00020.html (Grosso)
* http://lists.oasis-open.org/archives/dita/200906/msg00145.html (Call
scheduled for after today's TC meeting)
Resume TC discussion on 30 June 2009.
7. ITEM: CLARIFICATION OF THE MEANING OF SCOPE=PEER
* http://lists.oasis-open.org/archives/dita/200906/msg00048.html (Kimber)
Robert Anderson commented that Elliot Kimber had accepted comments made
during the 16 June 2009 TC meeting, and that this item should be noted as
being closed.
8. NEW ITEM: CLI BRIDGE FOR THE SOFTWARE AND PROGRAMMING DOMAINS
* http://lists.oasis-open.org/archives/dita/200906/msg00086.html (Nevin)
* http://lists.oasis-open.org/archives/dita/200906/msg00110.html
(Nevin--rollup for today's discussion)
Bruce Nevin summarized that some elements are available only in software
domain and other elements are available only in the programming domain. A
CLI product bridges those two domains. If someone is documenting keywords
for a CLI using the programming domain, they must use the