> > When using DIV, what translate that "hierarchy"?
> 
> <div id="level1">
>   <div id="level2">
>      <div id="level3>I am down the hierarchy :(</div>
>   </div>
> </div>

The indentation in the markup?
Is whitespace required to make sense of DIVs?

The IDs? 
If we need to use attributes to make sense of it, then it'd appear that DIVs 
are not that semantic after all.

The nesting? 
See my comment below about this.

> > This may not make Lists better for construct, but it should
> > show that the div element represents nothing at all (as it says in
> one of
> > the 2 links you posted).
> 
> I thought DIV represents division, some structural group, some
> _generic_ container.

DIVs are used for this, but do they *mean* this? If yes, then why does the 
following validate?
<div class="clearIt"></div>

> > Because if we are talking "hierarchy" and semantics, I think
> "something"
> > should "reveal" the relationship between these elements.
> 
> "something" — like being in the same DIV?

And that's enough? Because in this case the element itself does not translate 
anything. It is the context in which it is found that conveys the information.
With a list I think the markup does a better job at translating "hierarchy" and 
relationship since when nesting occurs, the element used *is* different .

> > In the above example, what are the 2 DIVs used as wrappers (instead
> of the
> > OLs) if they are not just structural hacks?
> 
> Since when using element for the purpose it was created is a hack?

Why would we need to group containers together if it is not for styling 
purpose? 
Do we use a wrapper because it brings more meanings to the document or because 
it let us center our layout, create faux columns etc.?

> > At least with the list construct the wrappers *are* semantic.
> 
> And how many "semantic" wrappers/containers/whatever are you going to
> have in the standard?
> No matter the number there will always be need for the generic one —
> which DIV is.

Once again, I do not say we should *not* use DIVs, I'm only saying we should 
not try to make them look for what they are not.


-- 
Regards,
Thierry | http://www.TJKDesign.com






*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to