MHonArc v2.5.0b2 -->
office message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Open Office XML Format TC Meeting Minutes 16-Aug-04
MINUTES OF THE OASIS OPEN OFFICE XML FORMAT TC MEETING
AUGUST, THE 16TH, 2004, 3PM GMT – 4:00PM GMT
Attendees
---------
Doug Alberg <doug.alberg@boeing.com>, Boeing
Michael Brauer <michael.brauer@sun.com>, Sun Microsystems
Patrick Durusau <Patrick.Durusau@sbl-site.org>,
Society of Biblical Literature
Gary Edwards <garyedwards@yahoo.com>
Tom Magliery <tom.magliery@blastradius.com>, Blast Readius
Daniel Vogelheim <daniel.vogelheim@sun.com>, Sun Microsystems
Lars Oppermann <lars.oppermann@sun.com>,
Sun Microsystems (prospective member)
Acceptance of Minutes of the August, the 16th meeting
--------------------------------------------------
- The attending TC members unanimously accepted the minutes.
Action Items
------------
- David Faure: look into aligning image filter proposal with SVG, and
rework proposal if possible
- in progress
TC membership
-------------
Lars Oppermann joined the TC as a prospective member.
File Name Extensions and MIME types
-----------------------------------
The TC continued its discussions regarding MIME types and extensions.
The TC identified the following issues:
- The registration authority is IANA and not the TC. The Open Office
specification therefor can only contain a list of MIME types that are
registered at the time the specification is published.
- How do we avoid that different vendors register multiple open office
related MIME types/extensions for the same purpose?
- How can we ensure that readers of the specification understand that
they can register their own MIME types?
- How can we ensure that the Open Office TC notices if new open office
related MIME types get registered.
While there seems to be no solution that addresses all these issues, the
TC agreed to
- add a link to the registration procedure described RFC2048 to the
specification;
- move the list of MIME types into an non normative appendix;
- state in the specification that this list of MIME types only a
snapshot of what is registered at the time the specification is
published (or contains the MIME types the TC intends to register
itself), but that the full list is available following the instructions
described in RFC2048 only.
The TC further agreed to add the non-basic MIME types/extensions
described in
http://lists.oasis-open.org/archives/office/200408/msg00004.html to the
list of MIME types it intents to register.
Margin
------
The TC unanimously agreed to add the fo:margin property to the
specification as proposed in
http://lists.oasis-open.org/archives/office/200408/msg00010.html.
Order of style elements
-----------------------
As proposed in
http://lists.oasis-open.org/archives/office/200408/msg00011.html, the TC
unanimously agreed that the various style elements may occur in any
order within the <office:styles> and <office:automatic-styles> elements.
New Action Items
----------------
none
Michael Brauer
OASIS Open Office XML format TC chair
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]