Steve Pugh wrote:
Stanimir Stamenkov <s7****@netscape.net> wrote:
It is just list of definition (properties).
Does a name and a description define the date? I don't think so.
One could argue
about my use of the DT element but I don't see nothing wrong in the
following construct:
<dl>
<dd class="key">date 1</dd>
<dd>name 1</dd>
<dd>description 1</dd>
</dl>
Now you have "defintions" that aren't defining anything.
I don't define "anything" explicitly just because I don't have a
title (doing just this: entitling) for the items I define, but then
I define them. I do however have a key property which I think could
be set to entitle the items:
<p>
Here's a list of dated items:</p>
<dl>
<dt>date 1</dt>
<dd>... <dd>...
<dt>date 2</dt>
<dd>... <dd>...
</dl>
Might as well
use <div>s with appropriate CSS.
DIVs do clear from duty all the semantics (and typical formatting)
other elements carry, so I would use them as last resort.
Eh, there are many things which could be expressed as table but no,
it is definitely not a table.
Why not? If the same data exists for each date, and your example
implied that it did, then it's perfectly suitable to be a table.
Because tables aren't fully implemented in browsers like Lynx and I
do want to keep simplest formating as possible while keeping
elements distinguishable. Because I have "description" property
which would take more space - a paragraph, and I don't want to put
all the properties in a (table) row (considerably narrowing the
available width for the paragraph). If I could use some advanced
(not yet implemented) CSS3 I can easily format the DL as visual table.
H3 marks up much more general sections than the key elements in the
list (the list is equal weight to a block just as paragraph)
There is no rule about what H3 does or does not mark up other than
that its contents are a level 3 heading. The importance of any given
level of heading in HTML is entirely relative to its place in the
document, nothing else.
I think the same goes for DL, DT, DD. It is much like:
<div class="chapter">
<hx>...
<p>...
<p>...
</div>
I could use:
<ul>
<li class="key">date 1</li>
<li>name 1</li>
<li>description 1</li>
</ul>
<ul>
<li class="key">date 2</li>
<li>name 2</li>
<li>description 2</li>
</ul>
But then it is almost (not to say exactly) identical to the example
in my first comment.
You can still use nested list as per my example, which does keep the
structure that each date is itself a part of a list of dates, and that
each name and description are deeper information than the date.
The properties are equal - "key" is somewhat temporary feature of
the particular property and I don't think I want to use such nested
lists. I just want to emphasize on the "key" property, how one
emphasize: using EM or STRONG to mark a whole still small part of
content, or Hx(eading) and DT (in DL) to mark the beginning of a
larger content part.
Whatever, I'll think more of the "list example" you've proposed.
--
Stanimir