[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Errata in grammar files for <colspec>
The DocBook 5.1 spec says this for “headers” value for @rowheaders on colspec (http://tdg.docbook.org/tdg/5.1/colspec.html): “Indicates that row headers are identified by use of the headers attribute on entries in the table.” Which is not the same as “the entries of that column are functionally row headers” The DocBook language says that entries are headers *if and only if* those entries specify @headers, otherwise they are not. The DITA language says that those entries are headers. Cheers, E. -- Eliot Kimber http://contrext.com From: Scott Hudson <scott.hudson@jeppesen.com> Sorry for the delay, just digging out of email. The proposals were intended to match DocBook as much as possible to aid with any interchange of content. The original requirements that fed the proposals (for DocBook and DITA) are described here: http://n-faktor.net/featured/docBook_tables.html, https://lists.oasis-open.org/archives/docbook/201303/msg00021/docbook5.1b8_tables.pdf and http://www.ditawriter.com/dita-1-3-and-improved-table-accessibility-for-screen-readers/ I don't see anything in the spec that indicates any kind of default for @rowheader that should be applied. In this case, I think it is an errata issue, since no default should be applied. The RNG (and respective generated DTDs) should not require or specify a default for the @rowheader. I think the semantics is the same as DocBook the way it is described in the 1.3 spec. If <colspec rowheader="headers"> is marked, the entries of that column are functionally row headers. If firstcol is specified, only the first column are row headers, and norowheader indicates that the first column does not have any significance with regard to headers. How does this differ from DocBook? Thanks and best regards, --Scott Voting member: Boeing Data Standards Technical Advisory Board OASIS DocBook TC, Publishers SC (Chair) OASIS DITA TC, Tech Comm SC, LW DITA SC, Learning Content SC (Secretary) OASIS DITA Adoption TC OASIS Augmented Reality in Information Products (ARIP) TC Scott Hudson Jeppesen, A Boeing Company 55 Inverness Drive East Englewood, CO 80112 303-328-6228 | Cell: 303-350-7934 This document contains only administrative, uncontrolled data under U.S. International Traffic in Arms Regulations. From: <dita@lists.oasis-open.org> on behalf of Eliot Kimber <ekimber@contrext.com> This may be our failure to fully check the original proposal, but my understanding from the time was to bring DITA 1.3 into alignment with DocBook on table accessibility, so I would expect them to be identical. But maybe we’re being more correct with respect to the current HTML guidance? I understood the DocBook version of @rowheader=”headers” on colspec to mean “look to @headers on entries, if specified”. Which is a reasonable default (because it will have no effect if @headers is not specified on any entry) but also not necessary to say explicitly, which is probably why it’s not defaulted in DocBook. So there may be two issues here: 1. Need to remove the default 2. DITA semantics for rowheader=”headers” on colspec is incorrect (it certainly doesn’t match DocBook as far as I can tell). I definitely agree with (1). Cheers, E. -- Eliot Kimber http://contrext.com From: Robert D Anderson <robander@us.ibm.com> I ... am not sure. "Add rowheader to the colspec element. Indicates whether or not the entries in the respective column should be considered row headers. "
· If you have a basic table with one or more header rows on top - just put the header row(s) in <thead> and you're done. · If you also want the first column to be treated as a header column (every entry in that column is a header for the row) - set rowheader="firstcol" on the table itself
· If you want a single entry in a column to be a header for its row, set scope="row" on that entry · If you want every entry in a column to be a header for its row, set rowheaders="headers" on that colspec -- basically, it's a shortcut to setting @scope="row" on every entry in the column · If you want a single entry in a row to be a header for its column, but it is outside of <thead>, then set scope="col" or scope="colgroup" on the entry · If you want every entry in a row to be a header for its column, but it is outside of <thead>, then set scope="col" or scope="colgroup" on every entry in that row · If none of that works, and you need to set individual cells as headers for individual entries, use @id on the header cell and @headers on the entry
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: headers Indicates that entries of a column described using the <colspec> element are functionally row headers (for cases with more than one column of row headers). Applies when @rowheader is used on the <colspec> element. 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.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]