> Thierry Koblentz wrote: > > > DIVs are used for this, but do they *mean* this? If yes, then why > does the following validate? > > <div class="clearIt"></div> > > For the same reason that > > <li class="foo"></li> > > also validates.
You didn't quote an important part of my reply to Rimantas, who was saying: "I thought DIV represents division, some structural group, some _generic_ container." Hence my remark about being allowed to use *empty* DIVs. If their purpose is to be used as containers, then we should use them to contain something. Your LI example is a different matter since "being a container" is not the *basic* definition of a list item... > >>> 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? > > Yes, since the DOM that's constructed is unequivocal about the > structure. > > > It is the context in which it is found that conveys the information. > > It's the overall document structure and the DOM that results from it. > not "context". The DOM? But we're talking about *reading the source code* and the meaning of DIVs in the markup. For the DOM, it doesn't matter if I use DIVs or LIs. The structure would be the same. Or am I missing your point? > > 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 . > > From the DOM's perspective, the hierarchy/relationship is clear in > just > as clear in both cases. ok, then I must be missing your point, because we agree that it'd make no difference. So why bringing the DOM into the picture then? Does it prove that DIVs carry more semantics? > > Why would we need to group containers together if it is not for > styling purpose? > > Because we're saying that anything in the container belongs together > (thematically, content-wise, logically, etc). You're saying that a wrapper is needed to enclose all other elements in a document to give it more meaning? What about *body*? If that wrapper is the only child of body I don't see what it brings to the table in term of semantics. You're saying it is important to enclose three "sections" inside a DIV (i.e. "columns") to convey the fact that they belong together (thematically, content-wise, logically, etc)? Sounds like a list construct to me ;) > > 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.? > > To create meaning, of course. As I say above, what is the meaning of a wrapper over body? Doesn't body implicitly says that anything in there belongs together? -- Regards, Thierry | http://www.TJKDesign.com ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
