OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [office] Open Office XML Format TC Meeting Minutes 3 Feb 2003


MINUTES OF THE OASIS OPEN OFFICE XML FORMAT TC MEETING
FEBRUARY, THE 3RD, 2003, 7PM GMT - 8PM GMT

Attendees
---------
Doug Alberg <doug.alberg@boeing.com>, Boeing
Phil Boutros <pboutros@stellent.com>, Stellent
Michael Brauer <michael.brauer@sun.com>, Sun Microsystems
Simon Davis <simond@naa.gov.au>, National Archive of Australia
Patrick Durusau <pdurusau@emory.edu>, Society of Biblical Literature
Gary Edwards <garyedwards@yahoo.com>
Jason Harrop <jharrop@speedlegal.com>, SpeedLegal
Paul Langille <paul.langille@corel.com>, Corel
Tom Magliery <Tom.Magliery@corel.com>, Corel
Monica Martin <mmartin@certivo.net>, Drake Certivo
Daniel Vogelheim <daniel.vogelheim@sun.com>, Sun Microsystems
Lauren Wood <lauren@textuality.com>


Acceptance of Minutes of the January, the 27th meeting
------------------------------------------------------
- The attending TC members unanimously accepted the minutes.

Action Items
------------
- Editors: Clarify technical details about editing the specification.
   - in progress
- All: Send name suggestions for "automatic-styles" element to TC's list.
   - done, no additional suggestion have been made.
- All: Send use cases for multiple "body" elements to TC's list.
   - done, no additional use cases have been found so far.
- Michael Brauer: Adjust TC's Working Plan to work package proposal.
   - in progress


Discussion of Work Package 1.2 First Level Elements
---------------------------------------------------
- After short discussion the TC unanimously agreed to not rename the 
"automatic-styles" element.
- The TC discussed whether the "body" element
a) should contain elements for paragraphs, tables, etc. directly as it 
is the case for the OpenOffice.org XML file format, or
b) should contain elements like "spreadsheet", "text" etc. that further 
classify the kind of document and can only contain the sub elements, 
that are really applicable to that kind of document.
While solution a) seems to be more open to future office application 
types, solutions b) has the advantages that validation against the 
schema is more meaningful (i.e. the schema itself rather than the 
specification text defines which elements can be contained in for 
instance a spreadsheet or a text document only) and that the schema 
itself gives much more support in manually creating documents of a 
certain kind. The advantages of b) were considered to be very strong, so 
the TC unanimously agreed to change the schema to use solution b).
- The TC further discussed whether multiple "body" elements should be 
allowed in a singe document. The TC agreed that for now only one "body" 
element should be allowed, but that the TC may reconsider this in the 
2nd phase of the TC. Michael Brauer will create and maintain a list of 
items on the TC's web page that could be reconsidered later.


New Action Items
----------------
- Michael Brauer: Create a list of items on the TC's web page that could 
be reconsidered later.


Michael Brauer

OASIS Open Office XML format TC chair



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC