OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

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

Subject: Errata in grammar files for <colspec>

I was trying out some of the accessibility features added for very complex tables. One of the features is the ability to set colspec/@rowheader="headers" -- doing so indicates that the specified column should be treated as a header for all entries in that row. This enhances the DITA 1.0 level support that just allowed you to designate the first column as a header column. Here's the description of that value from the spec topic:

So -- in order to indicate that the second column of a table should be treated as the header column, set rowheader="headers" on the <colspec> element that corresponds to column 2.

Turns out the grammar files actually set this as a default, which is very clearly not the intent. This means every processor that gets a parsed version of a table will view every column as having this attribute ... thus every column is a header column.

This occurs in all versions of the shipped grammar (RNG, DTD, XSD). It's clearly not the intent, based on the description in the spec and based on the fact that the results are nonsensical. We should fix this in the errata by removing the default value.

Relevant spec topic:


Robert D. Anderson
DITA-OT lead and Co-editor DITA 1.3 specification,
Digital Services Group

E-mail: robander@us.ibm.com
Digital Services Group
11501 BURNET RD,, TX, 78758-3400, AUSTIN, USA

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