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: Re: [office] Open Office XML Format TC Meeting Agenda 9Feb 2004

Dear TC members,

below is a summary of the open TODOs in the specification document:

1. We have decided to add "genre" elements like <text>, <spreadsheet>, 
etc. within <office:body>. Do we want to make restrictions for the 
content in of these elements, or do we want to move these restrictions 
to the appendix about typical document types only?

2. There are some places where unique names (or ids) are used within the 
specification, for instance within change tracking. Currently, these 
unique names are strings only, because using an ID/IDREF pair would add 
some restriction regarding the names that can be used as ids. Shall we 
keep these names as strings?

3. The original spec did not allow footnotes/endnotes in other 
footnotes/endnotes; the DTD contained an appriopriate comment. Do we 
wish to maintain this restriction for <text:notes> elements?

4. The <table:sort> element contains a table:algorithm attribute that 
specifies a sort algorithm. Such algorithms usually are provided by I18N 
frameworks, and it seems to be outside the scope of this TC to define 
unique names for them. The attribute currently is a string only, but we 
might want to turn it into a namespaced name just like we did in some 
other situations.

5. The <office:annotation> element contains attributes for the author 
and a date. Shall we use the <meta:*> elements instead as we agreed for 
the information contained in the <office:change-info> element. If we do 
so, we would have to add a meta element that allows specifying a date as 
an arbitrary formatted string.

6. Since we agreed to specify meta information in the 
<office:change-info> element using the <meta:*> elements, the 
<office:change-info> element becomes a container for the <meta:*> 
elements only, so we might want to replace it with <office:meta>. 
Whether we want to do so depends on whether we want to allow arbitrary 
meta data within change tracking information or not.

Best regards


Michael Brauer wrote:
> Open Office XML Format TC
> Agenda Phone Conference 9 February 2003
> =======================================
> The Open Office XML Format Technical Committee will have its next
> meeting on Monday, February the 9th, at 8am PT (4pm GMT).
> Please notify the TC mailing list if you are not able to attent to the
> con call, so that the con call can be moved if necessary.
> The teleconference phone number can be found at the TC's web page at
> http://www.oasis-open.org/committees/event.php?event_id=3919&wg_abbrev=office 
> Attendance to the conference is restricted to members and prospective
> members of the committee.
> Agenda
> ------
> Approx.
> Time (PDT)      Topic
> ----------      -----
> 8:00-8:05       Roll Call
> 8:05-8:10       Approval of last meeting's minutes, action item review
> 8:05-8:55       Specification review/Discussion about topics for phase 2
> 8:55-9:00       New Action-Item-Review
> In case you have certain issues regarding above topics that you would
> like to discuss in the meeting, please announce
> them on the TC's mailing list.
> Best regards
> Michael
> To unsubscribe from this mailing list (and be removed from the roster of 
> the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/office/members/leave_workgroup.php. 

Michael Brauer                                Phone:  +49 40 23646 500
Technical Architect Software Engineering      Fax:    +49 40 23646 550
StarOffice Applications
Star Office Software Entwicklungs GmbH
Sachsenfeld 4
D-20097 Hamburg, Germany                e-mail: michael.brauer@sun.com

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