On 11 Aug 2008, at 11:48, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]
> wrote:
a list could usually be said to be synonymous with a
'single column table' and conversely, a data table is a set of
parallel
lists - they are both special cases of each other.
I think that Michael has hit the nail on
I vote table. It's not really a list, regardless of the title you put on it.
It's a chart.
Jo
On Mon, Aug 11, 2008 at 4:01 AM, 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 "shoul
t 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 l
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
because more than likely
it should really be a table; if the table has only one column, check because it
may be just a list.
- Original Message -
From: Rob Enslin
To: wsg@webstandardsgroup.org
Sent: Monday, August 11, 2008 11:24 AM
Subject: Re: [WSG] Tables for product=>pr
t;Sent: Monday, August 11, 2008 11:38 AM
>To: wsg@webstandardsgroup.org
>Subject: Re: [WSG] Tables for product=>price list
>
>On Mon, Aug 11, 2008 at 8:20 PM, Stuart Foulstone
><[EMAIL PROTECTED]> wrote:
>>
>>
>> On Mon, August 11, 2008 10:38 am, Jame
Rob,
Yeah I have now after extensive research. I have headed the table with a
caption and it uses a . There are various parent sections above the
table that use and .
Cheers.
On Mon, Aug 11, 2008 at 11:24 AM, Rob Enslin <[EMAIL PROTECTED]> wrote:
> James, sounds like you've answered your own q
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 eac
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,
On Mon, Aug 11, 2008 at 8:20 PM, 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
James, sounds like you've answered your own question/doubt then? Perhaps you
should head your 'list' as Prices and not Price List?
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
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 percenta
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 i
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
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 star
Hi James,
My understanding is that if the content is tabular data / data list in
nature then tables should be used. If your page had a dynamic element to it
- say being able to sort your product by price then the best way to mark it
up is by tables (IMO)... with JS.
Would be interesting to get ot
Here is the current mark-up
Body Art
Body Art Price List
Product
Price
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
18 matches
Mail list logo