[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Meeting Minutes 7/13/04 -- DITA Technical Committee
Meeting Minutes 7/13/2004 -- DITA Technical Committee
*** Please see Action Items and Decision Summary at the end ***
** Agenda **
------------
1. Roll call
2. Review/approve minutes from 29 June
http://lists.oasis-open.org/archives/dita/200406/msg00070.html
and 06 July
http://lists.oasis-open.org/archives/dita/200407/msg00004.html
3. Progress on issues currently in discussion.
New:
- Clarification of OASIS policy about Observer contributions
- What is the business value of DITA?
- Data element proposal by Erik Hennum:
http://lists.oasis-open.org/archives/dita/200407/msg00008.html
http://lists.oasis-open.org/archives/dita-comment/200407/msg00006.html
- "link target rendition context ambiguity" (discuss whether
to defer):
http://lists.oasis-open.org/archives/dita-comment/200407/msg00005.html
Ongoing:
- Conref and XInclude? (new info from Michael and Erik?)
http://lists.oasis-open.org/archives/dita-comment/200407/msg00003.html
- Namespace for DITA? How many are needed?
- Which version of CALS table model?
- Are the current domains adequate?
4. Continue working on outlines for the initial specifications.
Templates issue:
- OASIS template input from Jerry Smith:
http://lists.oasis-open.org/archives/dita/200407/msg00015.html
- Report from Eliot on substructure conventions? Specs we
should emulate?
Content:
- Guidance from Michael and JoAnne. Latest outline:
http://lists.oasis-open.org/archives/dita/200407/msg00013.html
- DITA Map/task map for the spec documents?
5. AOB?
** Minutes **
-------------
1. Roll call
- Members: Jerry Smith, Stanley Doherty, Robin Cover, Mike
Wethington, Seraphim Larsen, Bruce Sesnovich, Indie Liepa,
Sharon Veach, Shawn Jordan, Mary McRae, Rob Frankland,
Paul Grosso, Michael Priestley, France Baril, Bruce Esrig,
Don Day
- Prospective: Yas Etessam and Wendy Hambleton (fulfil thier
membership this meeting)
- Observers: David Brainard, Christopher Kreiler, Eric
Sirois, Nancy Harrison, Tyde Richards
- We have quorum.
2. Review/approve minutes
- 29 June
-
http://lists.oasis-open.org/archives/dita/200406/msg00070.html
- Approved.
- 06 July
-
http://lists.oasis-open.org/archives/dita/200407/msg00004.html
- Forgot to include Wendy Hambleton in the roll call.
- Approved with this one amendment.
3. Progress on issues currently in discussion.
- New:
- Clarification of OASIS policy about Observer
contributions
- Decision:
- It is permissible for observers to contribute
to the discussion on the main mailing list.
- Observers may also contribute to the
discussion at TC meetings.
- What is the business value of DITA?
- Michael Priestley started this discussion on the
list. Indi and France made some contributions
too.
- Don asks, Why was this topic opened on the list?
- To make explicit some of the reasons why IBM
is making DITA public -- what are IBM's
motives?
- To gather some of the rationales of some of
the other members of the TC -- why are they
adopting DITA? Indi's note falls into this
category.
- Why are some of the users adopting DITA? Why is
it valuable to them?
- BMC's XML system is in development, can offer
more information later.
- We can continue this discussion later.
- Data element proposal by Erik Hennum:
-
http://lists.oasis-open.org/archives/dita/200407/msg00008.html
-
http://lists.oasis-open.org/archives/dita-comment/200407/msg00006.html
- Erik not on the call
- This is something Erik wanted to see incorporated
into the 1.0 spec.
- Discussion --
- Shawn Jordan -- What kinds of things MUST go
into the 1.0 spec, because they would be
difficult/impossible to incorporate later?
This element proposal seems like it would be
*easy* to add later.
- Decision: Deferred to post-1.0.
- "link target rendition context ambiguity" (discuss
whether to defer):
-
http://lists.oasis-open.org/archives/dita-comment/200407/msg00005.html
- Is this a crucial item? Or defer to post-1.0?
- Decision: Deferred to post-1.0.
- Ongoing:
- Conref and XInclude? (new info from Michael and Erik?)
-
http://lists.oasis-open.org/archives/dita-comment/200407/msg00003.html
- Decision: Leave this open for discussion. We
need to check with Eliot and see if he thinks we
can defer to post-1.0.
- Action Required: Don to ask Eliot about this.
- Namespace for DITA? How many are needed?
- Is this an issue for the 1.0 spec?
- Decision: Answers must be provided for 1.0. Let's
continue the discussion with the intention of
including in 1.0
- Which version of CALS table model?
- Yas Etessam from XMetaL: Is it possible to allow
flexibility here? Forcing users to use
a particular version of CALS will discourage users
who are already standardized on a different
version.
- No, the XSLT can only handle one.
- If you use a different version, you'll need
a different XSLT.
- It's important to have a single standard, so
that all DITA users retain interoperability.
- Additional discussion ensued.
- Action Required: Paul Grosso to start
discussion on this on the TC list.
- Are the current domains adequate?
- Don: This may be superfluous for the 1.0 spec.
- Decision: Defer to post-1.0.
4. Continue working on outlines for the initial specifications.
- Templates issue:
- OASIS template input from Jerry Smith:
-
http://lists.oasis-open.org/archives/dita/200407/msg00015.html
- Report from Eliot on substructure conventions? Specs
we should emulate?
- Content:
- Guidance from Michael and JoAnne. Latest outline:
-
http://lists.oasis-open.org/archives/dita/200407/msg00013.html
- DITA Map/task map for the spec documents?
- Not covered -- ran out of time.
5. AOB?
- Dave Brainard from BMC Software: Observed content model
issues with the current DTDs. Don has made some
updates -- David to contact Don for testing these.
** Summary of Decisions **
--------------------------
- Observer participation:
- Observers may contribute to the discussion on the main
mailing list.
- Observers may also contribute to the discussion at TC
meetings.
- The following issues to be deferred till after the 1.0 spec --
(not necessary to resolve for the 1.0 spec):
- Data element proposal by Erik Hennum
- "link target rendition context ambiguity"
- Are the current domains adequate?
- We will leave the conref and xinclude discussion open; Don to
ask Eliot if this must be included in 1.0.
- We must make decisions about namespaces for the 1.0 spec.
Discussion to be continued on TC list.
** Action Required **
---------------------
017 Shawn Jordan -- Post to the TC list his ideas about general
extensibility and the creation of new elements not
necessarily descended from the Topic element. Still open
(not an immediate deliverable -- probably for 1.1 or 1.2
spec.).
021 JoAnn Hackos, Michael Priestley -- Summarize the discussion
of substitution and post to the TC list. Still pending as
of 6/29/04.
022 Don, Michael -- Put together a "self-study" tutorial/demo,
as per JoAnn's comments regarding the DITA sessions. Still
pending as of 6/29/04.
023 Jerry -- Post to the list regarding his group's usage of the
OASIS OpenOffice template. Still pending as of 6/29/04.
024 Eliot -- Find out exactly how to entitle the subsections
within the two specifications (as "sub specification", or as
"Part 1, part 2, etc.", or in some other way).
- Eliot sent email to specification support person, but
no response back yet. (6/29/04)
- Also Eliot should ask if OASIS can provide any
examples of well-written specs (in regard to content,
not format)
025 Michael, JoAnn -- Work together to drill down into the
details of the TOC of the specification and report this back
to the TC for reaction/comment. Still pending as of
6/29/04.
026 Michael -- See how Conref and XInclude contrast with SGML.
027 Erik Hennum -- Wrap up his thoughts about Conref and
XInclude and put them on the list.
028 All -- Use the mailing list to drive progress on open
issues, especially the namespace issue.
029 Eliot -- Wrap up the "set of namespaces" as a proposal for
the TC to approve next week.
030 All -- Contribute to Michael Priestley's posted question on
"What is the business value of DITA?"
031 Don -- Ask Eliot whether the conref/xinclude issues must be
resolved for 1.0 or can be deferred.
032 Paul Grosso -- Start discussion on table models on the TC
list -- is it possible to allow flexibility? Why/why not?
How to handle this?
** Issues to be Resolved **
---------------------------
001 Bruce Esrig -- How does specialization interact with maps?
002 Bruce Sesnovich -- How do we resolve name conflicts? (E.g.
two people create two different specializations off the same
parent topic, but give them the same name).
003 Don Day -- Let's explore tools that can make the
specialization process easier (that is, help automate it --
it is simple but tedious). Maybe there are vendors who
would be interested in working with us on this.
004 Bruce -- We need to go beyond naming conventions, and have
a formal syntax that captures the specialization structure.
<END>
___________________________________________________________
Seraphim Larsen ICG Technical Publications
Sr. Technical Writer Intel Corporation
(480) 552-6504 Chandler, AZ
The content of this message is my personal opinion only.
Although I am an employee of Intel, the statements I make
here in no way represent Intel's position on the issue, nor
am I authorized to speak on behalf of Intel on this matter.
___________________________________________________________
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]