OASIS Open Document Format for Office Applications (OpenDocument) TC

Expand all | Collapse all

Re: [office] spreadsheet table:cell/table:table (was: [office]OpenDocument TC coordination callminutes 2007-08-13)

  • 1.  Re: [office] spreadsheet table:cell/table:table (was: [office]OpenDocument TC coordination callminutes 2007-08-13)

    Posted 08-21-2007 21:11
    On Tue, 2007-08-21 at 16:14 -0400, Florian Reuter wrote:
    > I'll take a look at the formula spec.
    > 
    > I just want to make sure that we all have the sme understanding of the semantic of tables-in-tables and sub-tables for spreadsheets. 
    
    That's essentially been my argument as well.  If the element is in the
    schema, then the spec should give at least a rudimentary description of
    what it does, and what it represents, to avoid allowing the implementers
    incompatible interpretations of the same construct.
    
    As Lars said, there has already been a discussion of using 


  • 2.  Re: [office] spreadsheet table:cell/table:table

    Posted 09-06-2007 13:07
    Hi Kohei,
    
    we have discussed the topic in the last work call, and the 
    recommendation was to add information about the fact that spreadsheets 
    are not expected to support nested tables to appendix D, which lists 
    which parts of the specification are expected to be supported by typical 
    applications.
    
    If you name other cell content that may not be supported by typical 
    spreadsheet applications, then I think it would be possible to extend 
    the note we add to appendix D accordingly.
    
    Best regards
    
    Michael
    
    
    Kohei Yoshida wrote:
    > On Tue, 2007-08-21 at 16:14 -0400, Florian Reuter wrote:
    >> I'll take a look at the formula spec.
    >>
    >> I just want to make sure that we all have the sme understanding of the semantic of tables-in-tables and sub-tables for spreadsheets. 
    > 
    > That's essentially been my argument as well.  If the element is in the
    > schema, then the spec should give at least a rudimentary description of
    > what it does, and what it represents, to avoid allowing the implementers
    > incompatible interpretations of the same construct.
    > 
    > As Lars said, there has already been a discussion of using