> I cannot see why this is not a valid use of <table>.
> 
> Suppose that there were entries not only for "Support",
> but also for other Organisational Units within the
> organisation.  In that case, one might well (and
> with complete justification) present the data
> in a tabular manner :
> 
> 
> OU              Telephone      E-mail                        Skype
> Support         0000-0000      [email protected]
> [email protected]
> Reservations    1111-1111      [email protected]      <etc>
> Enquiries       2222-2222      [email protected]         <etc>
> 
> Just because there is currently only one OU of
> interest should not prevent the author from creating
> a data structure that will naturally expand to accommodate
> new data.

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.


--
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