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 09-Feb-03


MINUTES OF THE OASIS OPEN OFFICE XML FORMAT TC MEETING
FEBRUARY, THE 9TH, 2004, 3PM GMT – 4:00PM GMT

Attendees
---------
Doug Alberg <doug.alberg@boeing.com>, Boeing
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


Acceptance of Minutes of the February, the 2nd meeting
------------------------------------------------------
- The attending TC members unanimously accepted the minutes.


Action Items
------------
Daniel Vogelheim: Clarify on the Relax-NG mailing list whether an 
automatic conversion to DTDs exists.
   - in progress
Michael Brauer: Get in contact with DCMI regarding a liaison relationship.
   - in progress


Specification document Clarifications
-------------------------------------
The TC discussed some details of the specification document that need a 
clarification by the TC (see also 
http://lists.oasis-open.org/archives/office/200402/msg00006.html):

The TC discussed the content model of the "genre" elements like <text> 
or <spreadsheet>. The TC unanimously agreed that the genre elements 
should permit all content that might be usable within a certain kind of 
application. Restrictions should be made only where necessary. The TC 
editors shall adapt the content models this way, so that the TC can vote 
about this together with the specification document itself.

The TC further agreed that content restrictions for other elements might 
be reasonable, but that they will be done only if a TC members requests 
them for a certain element.

The TC discussed the usage of ID/IDREF attribute types instead of 
strings in cases where the attribute values represent unique names. The 
TC unanimously agreed that ID/IDREF attribute values should be used 
where the names are usually generated by the applications during 
loading/saving documents, but that ID/IDREF should not be used where the 
the unique names might be chosen be the applications users.

The TC further agreed that the value of the table:algorithm attribute of 
<table:sort> should be a namespaced name.

The TC also agreed that the meta information contained in 
<office:change-info> and <office:annotation> should be represented by 
<meta:*> elements. For both elements, the <meta:*> shall be direct child 
elements, and in both cases, only the meta elements that represent the 
meta information that exists already are allowed, but not arbitrary ones.


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]