Yes both are viable.
I would use the <dl> when I was expecting to have a "few per page"
type layout that would be more like a brochure layout.
I would use the <table> when what I wanted was - you guessed it - "a
table" layout.
My own personal guideline for <table> VS <anything else> is simply
asking myself the question "Is this a table?". If the answer is "Yes"
then I use a table. Otherwise I use an appropriate tag.
In the case of a set of products (or similar, Contacts, Events, News,
in fact mostly any single entity that you may have a collection of
with a name) I regularly use <dl> because you can say all of those
have a "This generic term (e.g. Product Name) equates to this specific
instance (e.g. CSS Stylesheet Editor)" relationship. That is - "this
equals that". (Which is basically what a definition list is
semantically).
But I would use it differently to the original suggestion.......
<dl id="cssed1">
<dt>Photo:</dt>
<dd><img src="csseditor.gif"></dd>
<dt>Name:</dl>
<dd>CSS Stylesheet Editor</dd>
<dt>Description:</dt>
<dd>Great editor for CSS stylesheets</dd>
<dt>Price:</dl>
<dd>For you... $10</dd>
</dl>
That markup has many possibilities (including being able to style each
product individually if you want) I have also used the exact same
markup to provide different "views" of the information depending on
the context of the surrounding container tag (e.g. a main page body
versus a side bar).
Regards
Gary
On Fri, 17 Dec 2004 09:19:22 -0800, Chris Kennon <[EMAIL PROTECTED]> wrote:
> Both are viable solutions, would the <dl> be more scalable for floating
> an image with caption beside it. With the table you mentioned Lynx
> support, does Lynx choke on <dl>?
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
