[Wsuug] New Web Page

[Kelley Walker]

so how does naming something a class make is have meaning in a way that's 
different from an id? i get why the *name* of the class or id, matters, but 
not why class and id are different in terms of meaning. specificity, yes.

as for microformats, since I'm a big promoter of microformats, I sent that 
along for irony. :)

k

At 07:47 AM 2/18/2010, Ryan Brunsvold wrote:
>Two of the better (or at least better organized) resources for HTML5 and 
>CSS3 that I've found is the HTML5 Doctor 
>(<http://html5doctor.com/>http://html5doctor.com/) and CSS3 Info 
>(<http://www.css3.info/>http://www.css3.info/). As far as Microformats are 
>concerned, I have to disagree with most of Atwood's points. I'd be happy 
>to go into the specifics of my argument if so desired, but for now I'd 
>prefer we use them for a few simple reasons. Namely, that Microformats are...
>
>    * easy to learn
>    * easy to implement
>    * yet another technology that helps us fulfill the original charter of 
> a Refresh Chapter
>
>
>
>On Thu, Feb 18, 2010 at 1:20 AM, Kelley Walker 
><<mailto:kcwalker at inkworkswell.com>kcwalker at inkworkswell.com> wrote:
>ooooo. that's a new one. where can i read up on the semanticness conveyed 
>by class v id? i was unaware that, by themselves, the class and id 
>conveyed semantic meaning *as* class versus id.
>
>i always thought it was the naming that conveyed semantic meaning. thus, 
>andy clarke argued for the use of "branding" to convey the meaning of what 
>people often call the "header" or "masthead". Both header and masthead, 
>Clarke argued, conveyed locational or positional information. heading or 
>masthead might not make sense if you had a page where there was no header 
>and instead a band down the side of the page or the middle contained the 
>branding information.
>
>html5 decided to go with <header>.
>
>so, i've have been using a content-based workflow where i refuse to look 
>at the design and only go by the _content_. i would have only taken the 
>words and functiongs on the refresh mock, getting rid of everything else 
>and marking it up on the basis of content only. that's the method 
>advocated by clarke and by progressive enhancement enthusiasts.
>
>
>
>ken: here's is Nicole's layout: 
><http://wiki.github.com/stubbornella/oocss/template>http://wiki.github.com/stubbornella/oocss/template
>
>notice it uses no IDs.
>
>it's a religion thing. :)
>
>i propose that the first extension of the refresh pages be called Religion.
>
>
>
>Kelley
>
>
>At 09:25 PM 2/17/2010, Zach Young wrote:
> > Ken wrote:
> > I totally agree with her and just think that taking her message as 
> meaning not to write IDs ever is the wrong one. For instance if there was 
> a #branding it does not mean you could not use a CSS object/class with 
> it. I just still think page structure should be ID driven, MHO.
> >
>
>I tend to agree. There's also just a lot of good semanticness that can
>be had with ids (for example the branding id.) Makes more sense
>semantically for that to be an id than a class. Anyway, just my 2
>cents.
>
>I know its out of fashion, but I'm not convinced that its bad to use a
>fair amount of ids (regardless of whether you're styling them based on
>id or not.) Personally I still use ids for my page structure (and
>semantic meaning) and classes for everything else.
>
>Zach
>_______________________________________________
>Wsuug mailing list
><mailto:Wsuug at list.wsuug.org>Wsuug at list.wsuug.org
>http://www.thelinuxlink.net/mailman/listinfo/wsuug
>
>
>_______________________________________________
>Wsuug mailing list
><mailto:Wsuug at list.wsuug.org>Wsuug at list.wsuug.org
>http://www.thelinuxlink.net/mailman/listinfo/wsuug
>
>
>_______________________________________________
>Wsuug mailing list
>Wsuug at list.wsuug.org
>http://www.thelinuxlink.net/mailman/listinfo/wsuug