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] | [List Home]

Subject: Open Office XML Format TC Meeting Minutes 28-Apr-03

APRIL, THE 28TH, 2003, 3PM GMT - 4:00PM GMT

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>
David Faure <faure@kde.org>
Paul Grosso <pgrosso@arbortext.com>, Arbortext
Tom Magliery <Tom.Magliery@corel.com>, Corel
Uche Ogbuji <uche.ogbuji@fourthought.com>
Daniel Vogelheim <daniel.vogelheim@sun.com>, Sun Microsystems

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

Action Items
- Daniel Vogelheim: Clarify whether the various index mark elements 
could be combined into one.
   - in progress
- Michael Brauer: Collect information how many attributes used in the 
Open Office XML format specification could be taken from the xhtml 
   - done
- Michael Brauer: Post examples for typical tables
   - done

Discussion of Work Package 4.3 Table Change Tracking
The TC clarified that the specification of table change tracking is 
designed for tracking changes within spreadsheets documents rather than 
for tables within text documents. This means that it focuses on changes 
to the table structure up to the granularity of cells, but not on 
changes within cells. Changes within cells are tracked as changes to the 
cell itself. In contrast to this, change tracking for text focuses on 
changes to text, but not on changes to table structures. Phil Boutros 
will create a proposal for unifying these two concepts and post it on 
the TC's list.

Discussion of Work Package 4.4 Other Table Elements
The TC clarified that these elements describe features that in current 
office applications are implemented for spreadsheet applications only. 
The TC unanimously agreed to the elements and attributes described in 
this work package.

General Discussion About Features that
may, should or must be supported
The TC discussed whether the Open Office XML format specification should 
specify whether conforming applications may, should or must support 
certain elements or attributes, for instance, whether a conforming 
spreadsheet application has to support the table change tracking 
elements. For applications that write Open Office XML files, this would 
have the advantage that it is known which features are processed by all 
conforming applications, and which features might get lost. The 
disadvantage would be that an application that does not support certain 
features might not be called Open Office XML file format compliant, even 
if these feature are meaningless for the application.
An example are applications that display documents only and therefor do 
not have to support all editing related elements to render documents 
correctly. Another example might be a rich text editor that does not 
support tables, but might want to use the Open Office XML file format. 
Since specifying all kinds of applications and the features they have to 
be supported seems to be impossible, at least in a reasonable time 
frame, the TC unanimously agreed to
- state normatively in the specification that a complying application 
either has to read all files that are valid against the Open Office XML 
schema, or have to write files that are valid against these schema.
- add a non normative appendix to the specification that states for some 
typical application classes what feature may, should or must be supported.

Discussion of Work Package 6 Graphical Content
The TC decided to change the agenda for the meeting to discuss graphical 
content before discussing styles.

The TC started to discuss graphical content, especially whether the 
specification supports text boxes that are continued on the next page if 
the text flow of a text box does not fit into a text box on a single 
page. Since this is not the case so far, David Faure will create a 
proposal for this feature.

The TC also discussed whether the specification supports graphical 
content that is displayed within a text document on a sequence of  pages 
rather than on a single one. Michael Brauer will clarify whether this is 
supported by the already existing master page concept.

New Action Items
- Phil Boutros: create proposal for unifying change tracking in text and 
table documents
- David Faure: create proposal for text boxes that are continued on the 
following page
- Michael Brauer: clarify whether the master page concept can be used 
within text documents.

Michael Brauer

OASIS Open Office XML format TC chair

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