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 2004-11-25

OCTOBER, THE 25TH, 2004, 3PM GMT – 4:00PM GMT

Doug Alberg <doug.alberg@boeing.com> (The Boeing Company)
Patrick <Durusau Patrick.Durusau@sbl-site.org> (SBL)
Simon Davis <simond@naa.gov.au> (National Archives of Australia)
Tom Magliery <tom.magliery@blastradius.com> (Blast Radius Inc.)
Gary Edwards <garyedwards@yahoo.com> (Individual)
Lars Oppermann <lars.oppermann@sun.com> (Sun Microsystems)
David Faure <faure@kde.org> (Individual)
Michael Brauer <michael.brauer@sun.com> (Sun Microsystems)

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

Action Items
- Lars Oppermann: Preparation of MIME type registration.
   - done, template, formula types must be added
- Michael Brauer: Prepare TC charter clarification
   - done, vote on charter at next meeting

Lars will be enlisted as "Committee" secretary and post the meeting 
minutes from now on.

List Styles in Graphic Styles
The issue and it's implications have been discussed on the Mailing list. 
The TC has agreed on the following:
- graphic styles should be allowed to contain list styles.
- names of such list-styles should not be shown by the UI, though they
   still be referenced like any other style.

Proposal: Form Content
The attending TC members unanimously accepted the proposal

Proposal: Formatting Properties
The attending TC members unanimously accepted the proposal

Copyright Notice and Disclaimer in Published Schema Files
Michael clarified with Karl Best, that the published schema files are 
not required to include the full copyright disclaimer.

Issues from Comments List
Mostly enhancements for upcoming versions, except:
a) the wording concerning whitespace differs from what is said in the 
W3C XML specification. Since a W3C compliant behavior is intended, the 
wording should change in the TC draft.
b) a statement about implementation security was requested. the TC 
agreed, that such a statement would be non-normative and is not 
necessary at this point, since no non-normative information is currently 
provided in the TC draft.
A statement about security aspects of applications implementing the file 
format was also deemed to be somewhat out-of-scope by TC members.

New Action Items

Oct-29. 2004
Lars Oppermann

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