This question was intended to divide the results more so than the first two. While there isn’t much context included with the examples, I think what I got out of the discussion that followed is that either method is good depending on the situation.
“I choose A, ’cause a definition-list consists of a term and a description. “Robots” is not a description of the term “A List of Stuff”.”
While this is true, others defend the use of a definition list for other applications, later in the discussion.
Dave Shea asks:
“…what constitutes a term/definition pairing? Is the term a word, can it be a phrase, can it be an image?”
A good question, and again I think is cleared up somewhat later on.
“How about nested lists?”
Nested lists can certainly be useful as well, as an alternative.
Doug Bowman pretty much writes the wrap-up for me here:
“… My answer: ‘C’: depends.”
And after quoting an important sentence from the W3 specification for
Another application of DL, for example, is for marking up dialogues, with each DT naming a speaker, and each DD containing his or her words.
“Clearly, there are uses for definition lists far beyond the traditional term and description.”
Doug goes on to give some good examples of definition lists with multiple descriptions — creating relationships between terms and multiple descriptions. A nice example of using a defintion list for more than just term/description pairs.
Defining lists with section dividers (I’ll refrain from using the the term “headings” here) has unlimited possibilities. Using the right combination depends heavily on the context. Some things to keep in mind:
- Definition lists can not only be used for strict term/description pairings, but also for grouping separate lists together that are related.
- Since search engines treat heading tags with greater importance, that should factor in your decision on whether or not to use them. (The W3 spec prohibits block-level elements within a
See all quiz questions and wrap-ups in chronological order.