Hello Lachlan,
On 10/28/06, Lachlan Hunt <[EMAIL PROTECTED]> wrote:
Charles Iliya Krempeaux wrote:
> I was wondering what people thought about parameterized classes?
>
> <a class="group:x" href="a.html"></a>
> <a class="group:x" href="a.rss"></a>
> <a class="group:x" href="a.atom"></a>
>
> Perhaps the above could be Semantic HTML to mark alternate links.
>
> Where "a.html", "a.rss", and "a.atom" would be a set of alternates.
> And "b.png" and "b.jpg" would be another set of alternates.
What's the specific use case where that would actually be useful to a
user? What's the problem you're trying to solve?
First I should repeat that this is NOT for a Microformat. Just some
Semantic HTML for something else. But having said that...
This is for loosely coupled alternates of the same link.
So that I could say a set of links are "the same" but have them
anywhere on the page. Even interwoven with other link groups.
For example.. here's a simplified version of 2 interwoven link groups...
<a class="group:x" href="a.html"></a>
<a class="group:y" href="b.png"></a>
<a class="group:x" href="a.rss"></a>
<a class="group:x" href="a.atom"></a>
<a class="group:y" href="b.jpg"></a>
> (This would have the advantage where these links could be very very
> loosely coupled. Which is why I might write Semantic HTML like this.)
>
> I believe that CSS would have problems styling these types of class
> names.
It wouldn't be a problem using the selectors .group\:a and .group\:b, but...
> For example, you could NOT do something like:
>
> .group\:* {
> /* CSS stuff here */
> }
... that's not a valid selector.
How would you suggest writing it?
See ya
--
Charles Iliya Krempeaux, B.Sc.
charles @ reptile.ca
supercanadian @ gmail.com
developer weblog: http://ChangeLog.ca/
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
