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: OpenDocument TC coordination call minutes 2007-09-24

* Rollcall
Michael Brauer, Sun Microsystems
Lars Oppermann, Sun Microsystems
Oliver-Rainer Wittmann, Sun Microsystems
Rob Weir, IBM
Patrick Durusau
David Faure, KDE

* Discussion...

Lars to track regrets (announce on mailing list)

regrets for Michael for next week
rob (maybe) too

October 8th is Columbus day - no meeting

* Action Items
no pending action items

* auto label positions
Lars to post new proposal to mailing list

* Layer-Set per page
David F. waiting for comments from openoffice.org

* Example for position and space attributes in lists
Oliver posted some to the list
should these be included in the specification

Annotations and examples are very important for implementors
We could use an independent annotations document
it could be automatically merged with the main specifications
we could use the wiki at opendocument.xml.org to maintain annotations
alternatively we may use the TC wiki
depends on how much control the TC wants for the examples/annotations
there may be the concept of "TC-approved" examples
the more open alternative may be a better starting point (at 
Michael will check how this fits with the current structure of 
opendocument.xml.org. Also talk to OASIS and adoption TC (Rob to raise 
this in adoption call)

* Version attribute in manifest entries
everyone agrees on the current proposal

Default values for formatting attributes at the schema level
Problematic because not supported by RelaxNG
Would conflict with style inheritance. Properties are inherited from 
parent styles. A default value would get in the way of inheritance.
The solution may thus be to define the fallbacks which apply when a 
property isn't defined anywhere in the hierarchy.
The question which the spec needs to answer is "what is the value for a 
certain property if it is not mentioned anywhere in the hierarchy?"
One way to do it would be to request applications to store defaults for 
Another possibility is to define defaults in the specification. 
Applications may then use the default-styles if they use a different 

Sun Microsystems                Lars Oppermann <lars.oppermann@sun.com>
Nagelsweg 55                    Software Engineer
20097 Hamburg, Germany          Phone: +49 40 23646 959
http://www.sun.com/             Fax:   +49 40 23646 550
Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1,
D-85551 Kirchheim-Heimstetten, Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering

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