Even if it where product and price, as in my origional example, a table is still more semantic because the data in the rows relate to the columns i.e. product and price.
On Mon, Aug 11, 2008 at 11:38 AM, James Jeffery < [EMAIL PROTECTED]> wrote: > And the same can be said for my example where each row has data relating to > the product, size, color info and price. > > > On Mon, Aug 11, 2008 at 11:20 AM, Stuart Foulstone < > [EMAIL PROTECTED]> wrote: > >> >> >> On Mon, August 11, 2008 10:38 am, James Jeffery wrote: >> > Disagree. >> > >> >... >> >> > >> > Again, just because something is a list does not mean it should be in a >> > list. Take for example students grades. The school needs to list the >> name, >> > the subject, the expected grade, the outcome (30/30) and a percentage >> > (100%). You could easily say its a list of students grades, because it >> is, >> > but you are not going to put that into a list because it would be wrong >> > to. >> > >> >> You could easily say its a list, but it's not. >> >> It's a table of related student data in which comparisons are made across >> the rows and down the columns. >> >> One compares across the rows for each student's results (expected, actual >> and percentage) and compares down columns for differences between >> students. >> >> Much more than a list. >> >> >> >> >> >> ******************************************************************* >> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >> Help: [EMAIL PROTECTED] >> ******************************************************************* >> >> > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
