|
I see they used exactly what I was thinking, so if I am crazy I am not
alone. My concern in adding extra semantics is page bloat and
complexity. Is it worth it to add to page size and complexity if it
doesn't add anything to the end user experience? I'll risk page complexity
and size to fix incorrect semantics, but if the semantics are correct, how much
to you risk to make it more correct? I feel like I'm in Philosophy
101.
<dt>Posts:</dt> <dd>34</dd>
versus
<li>Posts: 34</li>
In this example, neither is wrong. The use of a definition list is
certainly more correct, but it makes the size bigger (27 bytes vs. 18
bytes) and the code less human readable.
Even using a definition list, it becomes even more complex because how
do you make a line break for the next dt if you want the number of posts
inline with the title Posts, without using a <br/>? float:left it?
Bleh. On the other hand it offers the possibility to visually distinguish
between the two like making "Posts" bold.
Is it worth it?
Paul
Please forgive the top posting, stupid OE.
|
- Re: [WSG CMS] Semantic Forums Jan Brasna
- Re: [WSG CMS] Semantic Forums Christian Montoya
- Re: [WSG CMS] Semantic Forums Paul Bryson
- Re: [WSG CMS] Semantic Forums Stefan Hayden
- RE: [WSG CMS] Semantic Forums Chris Harrington
