[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Meeting Minutes 6/22/2004 -- DITA Technical Committee
Meeting Minutes 6/22/2004 -- DITA Technical Committee
*** Please see Action Items and Decision Summary at the end ***
** Agenda **
------------
1. Roll call
2. Review/approve minutes from 15 June
http://lists.oasis-open.org/archives/dita/200406/msg00022.html
3. Review yesterday's DITA Briefing 5 (conditional processing
and reuse).
- The remaining sessions are: June 28 -- Lifecycle
4. Continue working on outlines for the initial specifications
Initial outline:
- http://lists.oasis-open.org/archives/dita/200406/msg00019.html
- "Updated strawman proposal for DITA specification chunks"
from last week's discussion:
http://lists.oasis-open.org/archives/dita/200406/msg00035.html
- OASIS formal template for specifications:
http://www.oasis-open.org/spectools/index.php (just
a pointer to OpenOffice.org)
5. AOB?
** Minutes **
-------------
1. Roll call
- Voting Members present: Eliot, Jerry S, Stanley D., Mary
Mcrae, Dave Schell, Paul Grosso, Michael Priestley, France
Baril, JoAnn Hackos, Seraphim, Bruce Sesnovich, Sharon
Veach, Shawn Jordan, Indi Liepa, Don Day
- Prospective: Mike Wethington
- Observers: Nancy Harrison, Eric Sirois
2. Review/approve minutes from 15 June
http://lists.oasis-open.org/archives/dita/200406/msg00022.html
- One comment on the DITA briefings ("Good detail, but not
enough higher-level overview to understand where he was
going with the detail.") was attributed to "Bruce", but
neither Bruce Esrig nor Bruce Sesnovich claimed the
comment. Not sure to whom to attribute the comment.
- Minutes approved as amended.
3. Review yesterday's DITA Briefing 5 (conditional processing
and reuse).
- The remaining sessions are:
- June 28 -- Lifecycle
- Would it be worthwhile to compare/contrast DITA's
profiling mechanism to DocBook's profiling mechanism?
- Nancy Harrison (IBM), who is also on the DocBook TC,
gave a summary of DocBook's profiling capabilities.
- JoAnn commented on another method of achieving
conditional processing, by using a list of substitions
instead of messing with the metadata of elements.
Easier to use and maintain.
- Michael commented that JoAnn's idea is similar to the
substitution idea in DITA.
- There was some more discussion I didn't catch.
- Don: It would be good to publish this scenario to the
list. JoAnn will write something up, send it to
Michael to elaborate, and Michael will post to the
list.
- Next week is the last scheduled session -- Do we need to
schedule any additional sessions, or do any repeats?
- JoAnn: Would it be possible to have a demo session on
WebEx: Start a topic, write a topic, do some
processing, showing how it works practically with the
tools.
- Don: Would this merit another session, or perhaps
a "self-study" tutorial/demo that you can do on
your own?
- Don will work on this with Michael.
4. Continue working on outlines for the initial specifications
Initial outline:
- http://lists.oasis-open.org/archives/dita/200406/msg00019.html
- "Updated strawman proposal for DITA specification chunks"
from last week's discussion:
http://lists.oasis-open.org/archives/dita/200406/msg00035.html
- Michael: The major changes include:
- Added an overview and introduction
- Moved DITA topic, map, and metadata specs into
a new "DITA Markup" spec.
- Moved DITA content, design, and processing specs
into "DITA Specialization" spec.
- Michael: How should we entitle the sections within
each spec? As sub-specs, or as "part 1, part 2, part
3"?
- No one has a firm opinion about this.
- Eliot will take the action item to find out
exactly how we should do this.
- Don: How will we document the DTD vs. the schema?
- Didn't catch all this discussion...
- Don: How will we handle the language reference?
- Michael: Leave it in markup and reference it.
- Don: What will be the content for the metadata
specification?
- Michael: The content would be the actual DTD and
schema modules, plus descriptions of the markup,
and a reference to the language reference for
metadata elements.
- Don: Where do we document "known issues"?
- Eliot: Internally with the TC -- not in the spec.
- Don: What will go into part 3, "DITA Specialization"?
- Michael: We'll take existing documentation and
repackage it to fit the outline.
- Don: Do the editors have any comments? Is this good
enough to start from?
- Michael: Will get with JoAnn and drill down into
it (offline).
- Don: This seems to make the TC into
a review/update group and not an authoring group.
Is that accurate? Is that OK?
- No objections.
- Shawn: Some things appear to be non-standard XML,
such as the conref feature. How do we handle
things like this?
- Michael: xinclude doesn't do the things we
need it to do, so we invented conref instead.
But it can be processed by XSTL so it's not
really nonstandard XML.
- Shawn: So, is it an issue or not?
- Paul Grosso: He's talked with Eliot about
this. He thinks we should consider using
xinclude in a future release, because it's
been widely adopted already.
- Eliot: Processing semantics associated with
conref are partly semantic and partly
processing rules. Need to separate them out.
- Discussion ensued...
- Don: We're running out of time, let's take
this discussion to the list.
- OASIS formal template for specifications:
http://www.oasis-open.org/spectools/index.php (just
a pointer to OpenOffice.org)
- Don: Has anyone started working with these templates
yet?
- Jerry: Yes, a little. He will talk with his person
who is working with this, and post something to the
list about it.
5. AOB?
- Not covered (ran out of time)
** Summary of Decisions **
--------------------------
- No decisions made.
** Action Required **
---------------------
014 Don Day -- Don will send out a list of all the remaining
briefings subjects, with a specific request for people to
submit questions ahead of time. Completed as of 6/22/04.
015 Don Day -- Don to post a URL to the list, pertinent to the
discussion of naming conflicts and namespaces. (cf. Issue
#002). Completed as of 6/22/04.
016 Don Day -- Slides for the briefings must be made available
well in advance, just in case people aren't able to connect
to SameTime or WebEx. Completed as of 6/22/04.
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.
018 Michael Priestley -- Post a new draft of the initial
specification outline to the TC list, incorporating the
ideas from the discussion on 6/15/04. Completed as of
6/22/04.
019 All -- Discuss with Michael Priestley if you are interested
in helping with any sections of the DITA specification.
Ongoing -- let's remove this from the list.
020 All -- If you have a "case study" on a complete DITA system
-- from system design through to implementation and actual
delivery of documents to end users -- please let Michael
know so this can be presented at one of the briefing
sessions. Still open.
021 JoAnn Hackos, Michael Priestley -- Summarize the discussion
of substitution and post to the TC list.
022 Don, Michael -- Put together a "self-study" tutorial/demo,
as per JoAnn's comments regarding the DITA sessions.
023 Jerry -- Post to the list regarding his group's usage of the
OASIS OpenOffice template.
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).
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.
026 Michael -- Start thread on list to continue conref/xinclude
discussion. -- Completed by Eliot Kimber.
** 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]