W3C home > Mailing lists > Public > w3c-wai-hc@w3.org > October to December 1997

Re: operational concept for table browsing

From: Al Gilman <asgilman@access.digex.net>
Date: Fri, 10 Oct 1997 09:56:33 -0400 (EDT)
Message-Id: <199710101356.JAA24040@access4.digex.net>
To: dsr@w3.org (Dave Raggett)
Cc: w3c-wai-hc@w3.org
to follow up on what Dave Raggett said:
> 
> The model proposed in the current drafts for HTML 4.0 and CSS2
> give just this kind of flexibility. You choose via the style
> sheet whether you want the A_{i,1} cells spoken or not before
> the other cells. This assumes of course that the A_{i,1} cells
> are marked up as acting as header cells for the X_{i,j} cells.
> This can be done using the the axis/axes/scope attributes for
> instance:
> 
[snip]
> or
>   <td id=a1>a1</td>...<td axes=a1>x14</td>...
> 

I had not considered using AXES to point at a TD because as
defined in the current draft this is illegal.  If we changed the
semantics of AXES so that it could point to TD and TH, to either
a coordinate value or an axis definition, then at least we could
connect all the connections we need.  But it's worth the extra
attribute to keep these separate.

In the "multidimensional space" metaphor, I think it is
sufficiently valuable to distinguish between references to a
coordinate [value] and [the definitions of some] axes so that the
markup should make this distinction known.

We could mark what I call a KEY link with the attribute name
COORDS for "coordinates" and leave AXES for references to axis
definitions as currently stated in the draft.  COORDS gets a list
of IDs of cells containing data values and AXES gets a list of
IDs of cells containing field descriptions or coordinate
definitions.

At least that gives us a name for what I think is missing that
goes better with AXES.

-- Al
Received on Friday, 10 October 1997 09:57:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:56:11 UTC