OASIS Open Document Format for Office Applications (OpenDocument) TC

  • 1.  OpenDocument TC coordination call minutes 2007-09-24

    Posted 09-25-2007 09:47
    * 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 
    opendocument.xml.org)
    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 
    everything.
    Another possibility is to define defaults in the specification. 
    Applications may then use the default-styles if they use a different 
    behavior.
    
    -- 
    Sun Microsystems                Lars Oppermann 


  • 2.  Defaults

    Posted 09-27-2007 21:23
    > 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.
    
    Rather than specifying the defaults using RelaxNG - which would interfere with style inheritance implemented by OpenDocument - why not define the OpenDocument defaults using the _OpenDocument_ format itself?
    
    You could claim that all styles inherit from some RootStyle (need a better name), and then include a definition of RootStyle (for the values you cared about) using the OpenDocument spec itself.
    
    Or am I missing something?
    
    --- David A. Wheeler
    


  • 3.  Re: [office] Defaults

    Posted 09-28-2007 07:07
    Hi David,
    
    David A. Wheeler wrote:
    >> 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.
    > 
    > Rather than specifying the defaults using RelaxNG - which would interfere with style inheritance implemented by OpenDocument - why not define the OpenDocument defaults using the _OpenDocument_ format itself?
    
    Yes, that's one option, and I think not a bad one. It's compact, and 
    provides the chance to use them directly in implementations.
    
    The other option I can think of are tables that list the defaults. Such 
    tables could be generated from default styles in ODF, and vice versa. 
    So, the effort to provide the information seems to be the same for both 
    option, and it is more a question of style.
    
    Best regards
    
    Michael
    
    > 
    > You could claim that all styles inherit from some RootStyle (need a better name), and then include a definition of RootStyle (for the values you cared about) using the OpenDocument spec itself.
    > 
    > Or am I missing something?
    > 
    > --- David A. Wheeler
    
    
    -- 
    Michael Brauer, Technical Architect Software Engineering
    StarOffice/OpenOffice.org
    Sun Microsystems GmbH             Nagelsweg 55
    D-20097 Hamburg, Germany          michael.brauer@sun.com
    http://sun.com/staroffice         +49 40 23646 500
    http://blogs.sun.com/GullFOSS
    
    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
    


  • 4.  Re: [office] OpenDocument TC coordination call minutes 2007-09-24

    Posted 10-15-2007 09:38
    On Tuesday 25 September 2007, Lars Oppermann wrote:
    > * Layer-Set per page
    > David F. waiting for comments from openoffice.org
    
    This is still the case. Any news on this topic?
    
    -- 
    David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
    Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).