[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes April 5, 2005 regular meeting
Posted for Paul Prescod, minute taker for the meeting:
MEETING MINUTES -- 05 Apr 2005 -- DITA TECHNICAL COMMITTEE
*** Please see Action Items and Decision Summary at the end ***
Agenda:
1. Roll call
2. Review/approve minutes from 29 March:
http://lists.oasis-open.org/archives/dita/200503/msg00117.html
3. Review of "post 1.0" requirements gathering for public review.
4. More on "OASIS Website" thread?
5. More on "Marketing/Press relations" thread?
6. AOB
MINUTES
1. Roll call
Members: Robin Cover, Stanley Doherty, Bruce Esrig, Yas Etessam, Rob
Frankland, Paul Grosso, JoAnn Hackos, Eliot Kimber, Indi Liepa, Paul
Prescod, Michael Priestley, Kevin Shaum, Dana Spradley, Sharon Veach, Chris
Wong, France Baril, Don Day (Chair)
Observers and visitors: Erik Hennum, Eric Sirois, Kirstine Nothstine
(Member at end of this meeting)
We have quorum--17/26.
2. Review/approve minutes from 29 March:
http://lists.oasis-open.org/archives/dita/200503/msg00117.html
* Items 88 and 89 are done by the chair.
* No corrections on minutes
* Minutes accepted as read: Proposed: Michael Priestley,
Seconded
Sharon Veach
3. Review of "post 1.0" requirements gathering for public review.
* URL:
http://www.oasis-open.org/apps/org/workgroup/dita/download.php/12127/DIT
A-TC-1dot1issues-1.htm
* Anyone have trouble getting to this link? No problems
reported.
* We would like to get the issues document out for public
review
today
* Triage rules are in the document
* some are done
* some are way too impactful
* some are not backwards compatible
* Bruce Esrig:
* suggest new criteria: anything that cannot wait
for
2.0 but is not backwads compatible may need to be done now
* Priestley: Design #6 is done (about otherprops syntax)
* Priestley: Is Design #13 done? (about CALS/Docbook
coordination)
* Day feels that there hasn't been enough coordination and
design consideration to be confident.
* #11 (collection-type attributes) is listed as potentially
done.
* Day et. Al. investigating: yes, it is done.
* #12 class attribute syntax
* Priestley: What does #12 class attribute syntax
mean?
* Grosso: as he recalls, issue was that class
attribute
syntax is finicky -- needs to end in space.
* Priestley: class attribute is not part of the
user's
domain. Is that good enough?
* Grosso is not happy with the usability issue but
accepts the technical reasons
* Consensus is to revisit in 2.0
* Don proposes: Issues #1 and #2 (keyword handling) are
clearly
in scope
* Proposed to make a category for nesting issues of all types
* Priestley does not understand Design #4 -- need to get more
info
* Design #5 ANSI Warning Labels-- consensus to attack issue
* Design #7 Reconcilliation of metadata -- consensus that this
is should be handled
* Design #8 trademark allowing images -- consensus to tackle
* Design #9 prototitle attribute -- consensus to tackle
* Design #10 row-level metadata -- consensus to tackle as
general consistency issue
* Design #13 (CALS liason) -- move from design section to TC
process
* Design #14 -- About referring to sets of elements. Can look
at
for 1.1
* New issue -- conref a substep into the content of the steps.
France will give more detail.
* Design #15 -- new domains
-- Day could this wait?
-- Eric: could a community do this?
-- Day: let's treat this as a TC process issue
* Design #16 -- glossary entries
-- need a complete and well-vetted requirements
` -- there is a proposal on the DeveloperWorks issue
-- Consensus is to keep for 1.1
* Design #17 -- W3C standard addressing: two issues
-- standards for addressing
-- Xinclude has a mechanism for splitting
addresses
-- wait for 2.0 because of compatibility issues
* Design #18 -- Namespace role names
-- could not implement in 1.1 if we make the
namespace
required
-- could implement it if we make it optional
-- let's discuss it more in 1.1 context
* Design #19 -- Clarify MIME versus format=
-- disconnect between DITA and W3C practice
-- proposal as a documentation issue
* Design #20 -- Issues of use context for links
-- maybe be partially implemented in 1.0
-- should be considered further in 1.1
* Design #21 -- conref improvements from deep dive
-- for example generalization on the fly
-- keep for 1.1
-- itemize for next version of link
* Design #22 -- move text attributes into elements for
translation and reuse
-- Keeper
* Design #23 -- add outputclass to linkinfo and linktext
-- consisetncy issue
-- should be considered for 1.1
* Design #24 -- move format and scope into related attributes
-- remove note about backwards incompatibility
-- basically a maintainability issue
-- 1.1 change
* Design #25 -- consider making @role (and other enumerated
atts) un-enumerated
-- related to #5 and #18
-- therefore keep
* Design #26 -- Rework of spec hierarchy
-- Priestley proposes to wait
-- Kimber concurs that it will take too long to
work it
out
-- therefore wait for 2.0
* Design #27 -- Intro of new task type
-- e.g. from Nokia
-- Handle in 1.1
* Design #28
-- Indexing
-- Indextermref
Will pick up here next week.
4. More on "OASIS Website" thread?
No time to address.
5. More on "Marketing/Press relations" thread?
No time to address.
6. AOB
None.
Decisions:
All decisions were made by consensus and are recorded in the
discussion of 1.1.
Regards,
--
Don Day <dond@us.ibm.com>
Chair, OASIS DITA Technical Committee
IBM Lead DITA Architect
11501 Burnet Rd., MS 9037D018, Austin TX 78758
Ph. 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]