On Mon, 7 Feb 2005 23:07:39 +1100, Michael Cordover <[EMAIL PROTECTED]> wrote:

An ordered list means there is an order, *not* that there is anything
particular assocated with that order.  So, think about it in terms of
set theory, if you will.  An unordered list is like a set: {1, 2, 3}
which is the same as {3, 1, 2}.  An ordered list, like an ordered set
- (1,2,3) which is distinct from (3, 1, 2).  But a definition list is
like a mapping:
{ (1, 1), (2, 5), (3, 6) } which, in set theory, is just a subset of
{1, 2, 3} x {1, 5, 6}.

Apologies to those amongst you who don't "do" set theory.  It'd be
better with diagrams.  But the point is that if you want a starting
attribute in an ordered list you're actually setting up an assocation
between the number and the content of the list item.  So you need a
definition list.  Because an ordered list is just a way of defining a
relationship between the parts of the ordered list, not between the
parts of the ordered list and something outside.

Interesting, but I don't agree :)

IMO list items are "1st", "2nd", "3rd" and so on, and this makes sense
as long as all list items are together, but sometimes you need to split
the list (for example when you display 10 results per page),
so then start makes sense.

There are some usability problems:
WAI says that document must make sense without stylesheets.
From a users point of view:
1. a
2. b
3. c
is very different from:
11. a
12. b
13. c

I don't think that definition list can replace that either.
<dt>11</dt><dd>Foo</dd>

"Foo" does not define "11".
It's just supposed to be 11th element of some list.


-- regards, Kornel Lesiński

******************************************************
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************



Reply via email to