Re: Issues of @summary and use of data for "decisions"

Laura Carlson wrote:
> Sam wrote:
> 
>> Data
> 
> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-46654c194f99ed943eb26573a6506818962826ee
> 
>> reason
> 
> Rationale: Why Summary Should Be Provided
> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-222af24a2b1dcdc3afe5e3036551b70f99cf232c
> 
> Rationale: Why Summary Should Not Be Provided
> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-2046cf917919f6d17e0ee7990238686702c17523
> 
>> use cases
> 
> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-4fd8f8462033b251ea8328b598d9482140ff3f1f
> 
>> potential long term solutions
> 
> http://esw.w3.org/topic/HTML/SummaryForTABLE#head-7e7bb8bc3b97dcfae6a5505e462027377b505834

This is all good stuff.  I remembered @summary => @aria-described-by => 
summary, but either forgotten or never fully understood that 
@aria-described by was not an appropriate solution.

Question:  is there consensus on a summary element being the right 
long-term solution?  If so, what is in the critical path to making that 
happen?  Why is @summary now so important to making that happen?

> Best Regards,
> Laura
> 
> --
> Laura L. Carlson

- Sam Ruby