>  > This sounds like saying, "use a UL instead of a OL because even if
> today the
>  > order is important may be tomorrow it won't".
>  > imho, if "maintenance", "look", etc. go against semantics then they
> should
>  > not play a role in the choice of markup.
> 
> But my argument is that the use of <table> does /not/ go
> against the semantics of the data : the data represent
> one set of table headers and one row of data from
> a potentially larger table ...

imho, it does because using table markup implies you're considering the data
as tabular. 

The way "I" define tabular data is simple. If you do not need to associate a
row with a col to makes sense of the data, then it's not tabular.
I'd say it is only the *left column* in your example that justifies the use
of a table.
If it was just a succession of rows below THs then I'd say using DTs paired
with *multiple* DDs would be more appropriate.
I agree that such presentation (multiple rows) is very challenging and that
table markup makes it easy to display it that way, but still... ;) 

I think we're getting OT, so feel free to reply off-list or start a thread
on WSG if you're a member there too

--
Regards,
Thierry 
www.tjkdesign.com | articles and tutorials 
www.ez-css.org | ultra light CSS framework

______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to