Comments on: Emergent Semantics

By: Mike Linksvayer » SemWeb not by committee

Mike Linksvayer » SemWeb not by committee — Sat, 10 Mar 2007 19:59:09 +0000

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

By: Internet de Nueva Generación » Blog Archive » microweb semántica

Internet de Nueva Generación » Blog Archive » microweb semántica — Sat, 10 Feb 2007 20:02:00 +0000

[...] 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 [...]

By: John Y.

John Y. — Thu, 17 Mar 2005 05:24:29 +0000

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.

By: Jeff

Jeff — Tue, 15 Mar 2005 11:29:09 +0000

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.

By: Jeremy Flint

Jeremy Flint — Tue, 15 Mar 2005 05:09:56 +0000

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.

By: Tantek

Tantek — Mon, 14 Mar 2005 18:20:05 +0000

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: 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: a[rel~="external"][rel~="friend"][rel~="met"] Hope that helps, Tantek

By: Jeff

Jeff — Mon, 14 Mar 2005 14:24:58 +0000

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?