MHonArc v2.5.0b2 -->
dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: MEETING MINUTES -- 24 AUG 2004 -- DITA TECHNICAL COMMITTEE
MEETING MINUTES -- 24 AUG 2004 -- DITA TECHNICAL COMMITTEE
*** Please see Action Items and Decision Summary at the end ***
** Agenda **
------------
1. Roll call
2. Review/approve minutes from 17 August
- http://lists.oasis-open.org/archives/dita/200408/msg00051.html
3. Review/revalidate our managing authoring/review process:
(based on email from Seraphim Larsen)
- Solicit editorial comments from the group during
a specific time period -- either email directly to Michael
and JoAnn, or post to the TC list
- Michael and JoAnn compile the comments, using their
discretion on whether to incorporate something or not
- If there are conflicts, we should summarize them at the
committee meeting, take them to the TC list, and try to
resolve them there. If resolution is not possible on the
list, then let's bring them to the meeting.
4. Timed discussion on current issues.
- Namespace for DITA?
- Which version of CALS table model?
- Conref and XInclude? (no recent discussion--is this "in"
or "out"?)
5. New discussions/issues:
- S1000D (general separation of class architecture from
implementation vocabularies)
- Terminology
-
http://lists.oasis-open.org/archives/dita/200408/msg00064.html
5. New tasks--discuss DTD cleanup for specification, for
example:
- Edit and normalize formatting, comments, copyrights,
licenses, etc..
- Test the DTDs and Schemas
- Test suites for conformance testing? methodologies for
testing?
- Implementation/interoperability tips for users, vendors
6. AOB?
** Minutes **
-------------
1. Roll call
- Members: Paul Grosso, France Baril, Eliot Kimber, Seraphim
Larsen, Bruce Esrig, Robin Cover, Rob Frankland, Sharon
Veach, Stanley Doherty, Debbie Lapeyre, Don Day
- Observers and visitors: Zachary Taylor, Eric Sirois, Erik
Hennum, John Hunt, Tyde Richards
- We do have a quorum (11/22).
2. Review/approve minutes from 17 August
- http://lists.oasis-open.org/archives/dita/200408/msg00051.html
- Minutes approved.
3. Review/revalidate our managing authoring/review process:
(based on email from Seraphim Larsen)
- Solicit editorial comments from the group during
a specific time period -- either email directly to Michael
and JoAnn, or post to the TC list
- Michael and JoAnn compile the comments, using their
discretion on whether to incorporate something or not
- If there are conflicts, we should summarize them at the
committee meeting, take them to the TC list, and try to
resolve them there. If resolution is not possible on the
list, then let's bring them to the meeting.
- Discussion --
- Why? So we can spend the meeting time dealing with
more substantive issues, instead of line-by-line
editing.
- Have a specific agenda item to cover any open issues
-- for example, someone has already submitted an issue
to JoAnn/Michael, but it hasn't been addressed in the
spec yet.
- Perhaps the written current version of the spec could
include a list of issues that still need to be
resolved.
- Paul Grosso -- Yes, carry the issues along with each
rev of the spec. When you are ready to release 1.0,
you shouldn't have any issues left.
- No objections -- Approved by acclamation.
4. Timed discussion on current issues.
- Namespace for DITA?
- Which version of CALS table model?
- Conref and XInclude? (no recent discussion--is this "in"
or "out"?)
- OK to defer till Michael gets back, so we don't need to
discuss these things twice?
- No objections, approved by acclamation.
5. New discussions/issues:
- S1000D (general separation of class architecture from
implementation vocabularies)
- Eliot -- DITA's mechanisms fill a real need, so the
specialization architecture will "sell itself".
- Bruce Esrig -- Maybe it makes sense to separate out
the architectural issues -- and highlight them so
others can use them?
- Erik Hennum -- It seems like we're seeing a trend
towards TWO specifications -- and this is something he
likes. If we make a clean separation, we'll have
a better specification overall.
- John Hunt -- Didn't catch his comments.
- Don -- Do we need to make this decision today?
Probably not -- let's take it to the list for
discussion.
- Erik Hennum -- He'll take the action item to bring
this discussion to the list.
- Terminology
-
http://lists.oasis-open.org/archives/dita/200408/msg00064.html
- Erik Hennum took a few minutes to summarize.
- What is a "module"? >>> A useful collection of
elements.
- Erik Hennum and Bruce Esrig are recognized for the
excellent work that has gone into this!
- We will leave this discussion to the list.
5. New tasks--discuss DTD cleanup for specification, for
example:
- Edit and normalize formatting, comments, copyrights,
licenses, etc..
- Eliot and Debbie -- Take action item to lead this
discussion on the list, since they both have strong
opinions about how DTDs should be formatted.
- Test the DTDs and Schemas
- Test suites for conformance testing? methodologies for
testing?
- Don -- How do we test the DTDs and Schemas?
- For example, we want to make sure the content
models are complete.
- For schemas, how do we ensure that inheritance has
been properly indicated?
- Robin Cover -- There isn't really anything in
place at OASIS for testing -- no real standards or
methods. But some issues have appeared with other
specs in the past; for example, DTDs that wouldn't
parse.
- Has anyone seen anything else?
- Do we want to "guarantee" that our DTDs have been
checked with certain tools? Do we want to offer
a "test suite", so that vendors have something to
test against (so vendors can say they are "DITA
compliant")?
- Don will take the action to post something on this
to the TC list for further discussion.
- Implementation/interoperability tips for users, vendors
- Use the DITA Users Group (on Yahoo) as a repository
for guidelines, tips, case studies, and so on.
- Need to discuss further in future meetings.
6. AOB?
- No time -- this item not covered.
** Summary of Decisions **
--------------------------
- Decided to carry a list of open issues along with each
revision of the 1.0 spec. When we get to the 1.0 release,
hopefully all the issues will have been resolved.
- Decided to defer discussion on the following issues till
Michael gets back, so we don't need to discuss them twice --
- Namespace for DITA?
- Which version of CALS table model?
- Conref and XInclude? (no recent discussion--is this "in"
or "out"?)
** 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 -- for post-1.0).
021 JoAnn Hackos, Michael Priestley -- Summarize the discussion
of substitution and post to the TC list. Still pending as of
7/20/04.
022 Don, Michael -- Put together a "self-study" tutorial/demo,
as per JoAnn's comments regarding the DITA sessions. Still
pending as of 7/20/04.
026 Michael -- See how Conref and XInclude contrast with SGML.
Still pending as of 7/20/04.
027 Erik Hennum -- Wrap up his thoughts about Conref and
XInclude and put them on the list. >>> Done as of 8/24/04.
036 Shawn Jordan -- Investigate where to point the DITA
namespace -- where does the URL point? Maybe an OASIS page
that describes what DITA does, etc. Still pending 8/17/04.
040 Don -- Cull the past minutes and discussion list to create
an inventory of all the things we need to close on in order
to create the 1.0 spec. Create a list of these items and
post it in the Documents area of the website. >>> This will
be ongoing.
042 All -- Consider need for and practicality of 2-3 day
face-to-face meeting in late October in order to resolve
final technical issues in advance of final editorial work.
>>> Let's make this an agenda item for next week (for 8/31).
043 Michael Priestley -- Add a straw-man audience statement to
the introduction.
044 All -- Review the .chm file sent out by Michael Priestley
located at
http://www.oasis-open.org/apps/org/workgroup/dita/download.php/8636/dita
spec-intro-08102004.chm
and post comments to the TC list. Closed 8/24/04.
045 Erik Hennum -- Start discussion on the TC list about the use
of the phrase "document type" in the specification. Closed
8/24/04.
046 Don? -- Incorporate review comments from today's discussion
into the 1.0 draft (8/17/04).
047 Erik Hennum -- Start discussion on the TC list about
separating the spec into two specs -- one for the
architecture and one for the implementation vocabulary.
048 Eliot and Deborah -- Start discussion on the TC list about
the formatting of the DTD/schemas.
049 Don Day -- Start discussion on the TC list about testing the
DTD/schemas and developing a "test suite".
** Issues to be Resolved **
---------------------------
005 All -- What should the scope and length of the conceptual
introduction be? >>> We'll get this from JoAnn.
006 All -- Should DITA specialization mechanism be documented in
a separate specification in order to make it easier to use
in other XML applications that otherwise have no
relationship to topic-based writing? >>> Ongoing.
007 All -- Decide which version of the CALS table model to use
-- either the full CALS model, or the CALS Exchange model.
<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]