Emergent Semantics

Published 13 years, 1 week ago

Just a quick link to my slide deck (when did that term gain currency, and why didn’t I get a memo?) for “Emergent Semantics“.  I was honestly surprised by the number of attendees, and there were some great questions and ideas from audience members.  Throughout the rest of the day, I had some great conversations with people about their own microformat ideas.  Another measure of the level of interest in microformats and the semantic web was attendance at Tantek’s “The Elements of Meaningful XHTML“, which was so heavy that after the seats and floor space in his room filled up, a knot of people stood outside the door, turning their heads slightly and standing on tiptoe in an attempt to hear what he was saying.

On a very related note, I’ve updated my blogroll with some new met values.  I’ve met a ton of people I’d never met before, and hope to meet still more—so if I do assemble a metroll, it’ll have to wait until I get home.

  1. Eric,

    I just went through your presentation, and I read Tantek’s post on the topic as well. I am curious though would Tantek’s solution of spcae seperated rel values really be effective? At present I use rel to help me differentiate between external and internal links within my site. Tantek’s use of spcae indicative separation though looks like it could get fairly out of hand fairly quickly. I mean we would be looking at a rule similar to (but not exactly like) a[rel~=”external friend met”] :after {content: “*”;} which could lead to rules like a[rel~=author famous celebrity Cleveland OH met SXSW”] :after {content: “*”;} as the rule for “My favorite famous Ohioan’s who live in Clevelans that I met at SXSW links”

    Has there been discussion for using or developing other attributes other than rel to help disperse or simplify this process or is that what emergent semantics ia basically all about is trying to figure out what attributes other than rel are needed?

  2. Jeff wrote:

    a rule … a[rel~=”external friend met”] :after {content: “*”;}

    It sounds like there may be a couple of things being confused here.

    First, you don’t need to include all the rel values you use in your CSS selector in order for it to work.

    To be clear the [~=] selector selects for one term out of a space separated set of terms.

    Thus even if your hyperlink tag looks like:

    <a rel="external friend met" href="...">

    The the following rule will select it and put an asterisk after it in browsers that support CSS2(.1) Selectors (note the corrected plain (not curly) quotes:

    a[rel~="met"]:after {content: "*";}

    Second, a selector like

    a[rel~="external friend met"]

    will not have the effect you’re presumably looking for (requiring that all those values are in the attribute), because as written it would require that all the values appear in that order (and note, the order is semantically irrelevant in the rel (and class) attribute, so you shouldn’t be testing the order in normal circumstances).

    A selector that requires the rel attribute to have each of those relationship values would look like this:


    Hope that helps,


  3. Great presentation Eric. It really tied in well with Tantek’s panel later that day, whether that was the intent or not. I am defnitely going to be looking into some “real world” uses of the hCard and hCal microformats.

  4. Tantek,
    Wow! Thanks for the clarification! I admit, I was a bit confused by how the [~=…] was functioning here. Now I kno so no big mystery. Thanks again.

  5. I told you this at the time, too, but yeah — both your presenation and Tantek’s later were good stuff, particularly how well they tied together.

    I’m still having some flashes of insight into the lowercase semantic web issues now.

    I just wish that Monday’s capital Semantic Web panel had been as good.

  6. […] trata de un paso importante en el avance de esa web semántica con minúsculas que se apoya en la semántica emergente que aparece como fruto de la dinámica social de la Web. Y, aunque en la visión inicial de […]

  7. […] 20050314: Eric Meyer has posted his […]

Leave a Comment

Management reserves the right to edit or remove any comment, especially when abusive or irrelevant to the topic at hand. HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <em> <i> <q cite=""> <s> <strong> <pre class=""> <kbd>

Comment Preview

If you're satisfied with what you've written, then go ahead...