Re: summarization information delivery options: attribute or element

Hi Gregory,

> 1. ascertain the position of working group members on summary as an
>   attribute versus summary as an element;

It might help if  the group came to consensus on a table summary's
current and future functional requirements.

1. Purpose: Concise overview of the structure of the table? Long
description? Or something else?
2. Text string, restricted inline content, inline content, or block
level content?
3. Invisible, visible, or some combination by default?
3. Visibility settings via user agent or markup?

Discussion and a survey on something like this might help to make
progress. Right now the survey results are divided [1].

Best Regards,
Laura
[1] http://www.w3.org/2002/09/wbs/44061/20100225_summary/results
--
Laura Carlson

Received on Thursday, 25 February 2010 21:23:19 UTC