"..it doesn't really save any code, and I can't really see how using a definition list is any more semantic than using div tags.."
Colin - The aim is not always to save code, but to make sure the code you choose accurately reflects the content it contains.
In the div example - the code in place for presentational hooks are rather meaningless. A div is the Tupperware of the html world. Effectively it is a container to hold content.
A definition list on the other hand consists of two elements (a definition title and a definition description). A definition list can have multiple terms for a given definition as well as multiple definitions for a given term. Authors can also give a term without a corresponding definition, and vice versa, but such a structure rarely makes sense.
In this case:
<dl>
<dd><img src="../images/padgettLO.jpg" alt="Photo of Shannon Padgett" height="108" width="72"></dd>
<dt>Shannon Padgett, CTA</dt>
<dd>Sr. Account Executive,</dd>
<dd>Huntersville, NC </dd>
<dd>Ext. 2390</dd>
</dl>
describes content better than a div because it gives an association with each other. Which is to say "*anything in these descriptions (dd) relate to this title* *(dt)*"
also - dl's give you much more flexibility to style you content as you have essentially 3 hooks already without using extraneous code (span or div)
*However...*
Your code contains only 2 elements: an image and title. The image doe not fit with a definition title, and questionable if it falls into a "description" category. I don't think that a dl would fit your needs in this situation.
$0.02
Further Reading: http://www.style-sheets.com/html_tutorial/lists/dl.html http://www.maxdesign.com.au/presentation/definition/
****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
