One way to look at it is that a simple "list" is a list (in the html sense),
whereas a "relational list" is tabular, so it goes in a table.
So, a simple list of 'things to do' would use an HTML list, whereas a list
which required data giving more information about the primary list element
(a relational list) would be semantically more sound in a table.
Bob
www.gwelanmor-internet.co.uk
----- Original Message -----
From: James Jeffery
To: wsg@webstandardsgroup.org
Sent: Monday, August 11, 2008 12:22 PM
Subject: Re: [WSG] Tables for product=>price list
Ian and Micheal, you summed up what I was about to write. Some people got
really defensive.
My argument all along was that a list should not always be marked up as a
list as such. Take ebay for example, they even go to the extent of calling
their results 'lists'. You can see this on results pages where it says "view
as list". Nobody says "oh look here is my table of results on PS3's" they
say "oh look at that long list of PS3 products", even though behind the
scenes its a tables. It would be totally wrong for ebay to mark up their
results as lists, but the way they are styled makes them look like lists to
humans, though strictly they are not.
So a list isn't always a list and my example above was what I was trying to
get across.
Great debate guys! as always :)
James
On Mon, Aug 11, 2008 at 11:46 AM, James Jeffery
<[EMAIL PROTECTED]> wrote:
Rob,
Yeah I have now after extensive research. I have headed the table with a
caption and it uses a <h3>. There are various parent sections above the
table that use <h2> and <h1>.
Cheers.
On Mon, Aug 11, 2008 at 11:24 AM, Rob Enslin <[EMAIL PROTECTED]> wrote:
James, sounds like you've answered your own question/doubt then? Perhaps you
should head your 'list' as <h1>Prices</h1> and not <h1>Price List</h1>?
2008/8/11 James Jeffery <[EMAIL PROTECTED]>
Disagree.
Many shopping carts on the web have product lists or summarys marked up in a
table. When you look at it from the point of view where one column is the
products and the other is the price, and another is VAT per product its more
semantic to do it that way.
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.
James
On Mon, Aug 11, 2008 at 10:24 AM, Stuart Foulstone <[EMAIL PROTECTED]>
wrote:
A list is the most appropriate for a list.
The fact that "price list" states "list" DOES mean a list should be used -
when you use the term "list" that's what the user then expects it to be.
If you don't want to use a list (for whatever pedantic reason) then don't
call it one. If you want to use a table, call it a table.
Not using a list when a list is appropriate is just as bad as not using a
table when a table is appropriate.
On Mon, August 11, 2008 9:31 am, silky wrote:
On Mon, Aug 11, 2008 at 6:01 PM, James Jeffery
<[EMAIL PROTECTED]> wrote:
In the past I have tryed to avoid tables as much as possible and
sometimes
going as far as using lists for data that "should" be placed in tables.
I am
trying to sway away from the 'never use tables' crowd and have started
to
use them when they need to be used.
I am working on a tattoo website and the client wants a list of pricing
for
tattoos and peircings. Would you say this is a good candidate for a
table?
use a table.
those that say 'never use tables' are insane and often think that
'css' and 'tables' are mutually exclusive. i ignore those people.
tables are perfectly appropriate for this situation.
Although 'price list' states list, its not to say that a list should be
used.
Any ideas.
James
--
silky
http://www.themonkeynet.com/armada/
http://www.boxofgoodfeelings.com/
http://www.themonkeynet.com/
http://lets.coozi.com.au/
*******************************************************************
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]
*******************************************************************
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
--
/ Rob Enslin
/ enslin.co.uk
/ twitter.com/robenslin
/ +44759 052 8890
*******************************************************************
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]
*******************************************************************
*******************************************************************
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]
*******************************************************************
