Re: [oic] Advisory 00007 - Table Rows / Table Columns

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

I created some tests to see what happens when there are multiple <table:table-header-rows> elements in a table, using the model I gave below.  

It was quite interesting.  

When only the first group has a header row, everything works great, except the three headers persist for the entire table page preview, even after the group is long gone.  When the second group has a header row, every row from the first header row to that one is treated as a header row.  Clearly a bug of some sort.  I didn't expect it to matter if I put all of the plain rows in the first group inside of a <table:table-rows> element and, indeed, it did not make any difference.

The test files are in the SVN repository in folder 
<http://tools.oasis-open.org/version-control/svn/oic/TestSuite/trunk/odf12/CalcGroupHeaders/>.


 - Dennis E. Hamilton
   tools for document interoperability,  <http://nfoWorks.org/>
   dennis.hamilton@acm.org  gsm: +1-206-779-9430  @orcmid


 - Dennis

-----Original Message-----
From: oic@lists.oasis-open.org [mailto:oic@lists.oasis-open.org] On Behalf Of Dennis E. Hamilton
Sent: Friday, October 07, 2011 17:24
To: 'Andreas J. Guelzow'
Cc: oic@lists.oasis-open.org
Subject: RE: [oic] Advisory 00007 - Table Rows / Table Columns

The point is, <table:table-rows> and <table:table-columns> never supply anything to header rows or header columns, so it is not necessary to say anything about repeating or not.  

Did you look at the final statement about which has precedence when there is a conflict between the text and the schema for ODF 1.2?

    > IMPORTANT NOTE: The ODF 1.2 Schema is no different.  For ODF 1.2, it
    > is the schema that is authoritative, not the text.  How grand.

I also don't see any reason why the schema can't be completely precise about this.

So consider the following abbreviated element structure:

<table:table>
   <table:table-column> element
    ...
   <table:table-column> element
   <table:table-header-rows> 
       <table:table-row> element 1
       <table:table-row> element 2
   </table:table-header-rows>
   <table:table-row-group>
       <table:table-header-rows>
          <table:table-row> element 3
       </table:table-header-rows>
       <table:table-row> elements
        ...
   </table:table-row-group>
   <table:table-row-group>
       <table:table-header-rows>
          <table:table-row> element 4
       </table:table-header-rows>
       <table:table-row> elements
        ...
   </table:table-row-group>
</table:table>

which appears to be completely legal and also might make perfect sense, recognizing subheadings on subgroups.

 - Dennis


-----Original Message-----
From: oic@lists.oasis-open.org [mailto:oic@lists.oasis-open.org] On Behalf Of Andreas J. Guelzow
Sent: Friday, October 07, 2011 16:32
To: dennis.hamilton@acm.org
Cc: oic@lists.oasis-open.org
Subject: RE: [oic] Advisory 00007 - Table Rows / Table Columns

On Fri, 2011-10-07 at 17:14 -0600, Dennis E. Hamilton wrote:
[ ... ]
> WHO HAS HEADERS WHERE?
> 
> There is a serious ambiguity in the schemas for
> table-columns-and-groups and table-rows-and-groups.  This is not what
> 00007 is about, but it would certainly deserve an advisory of its own.
[ ... ]
> Great pains were taken to have the table-columns-no-group runs permit
> an optional header element in any single place in a run.  It is
> peculiar, after that, that there can be any number of such runs and
> interspersed groups.

This may be what the schema permits, but the text adds additional
condition, e.g. in ODF 1.2 section 9.1.7 (and 9.1.11 for columns):

A table shall not contain more than one <table:table-header-rows>
element, except that the table contains grouped rows defined by one or
more <table:table-row-group> 9.1.9 elements. In this case, the table and
each distinct group may contain one <table:table-header-rows> element,
if and only if the table rows contained in the <table:table-header-rows>
elements are adjacent.


> 
> The table-rows-and-groups pattern works the same way except for rows
> instead of columns.
> 
> IMPORTANT NOTE: The ODF 1.2 Schema is no different.  For ODF 1.2, it
> is the schema that is authoritative, not the text.  How grand.
> 

Andreas


-- 
Andreas J. Guelzow, PhD, FTICA
Concordia University College of Alberta


---------------------------------------------------------------------
To unsubscribe, e-mail: oic-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: oic-help@lists.oasis-open.org


---------------------------------------------------------------------
To unsubscribe, e-mail: oic-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: oic-help@lists.oasis-open.org