[whatwg] Ghosts from the past and the semantic Web
Tab Atkins Jr.
jackalmage at gmail.com
Fri Aug 29 12:54:41 PDT 2008
On Fri, Aug 29, 2008 at 2:33 PM, Ben Adida <ben at adida.net> wrote:
> I'm going to keep my answer somewhat brief because Manu and I have
> privately discussed wrapping up this thread so we don't take up too much
> of people's time. I'll focus on simple points.
> > (Note: I've been discussing just such a CSS-like rdf format with Ben
> > offlist, inspired directly by Eduard's proposal earlier.)
> I think this idea is interesting, but I don't think it can be made to
> work until we get the basic RDFa stuff actually working inline.
> The comparison to CSS is not quite right: with this new proposal, you
> have to first map your HTML to local semantic concepts, then map those
> local concepts to global semantic concepts. That's quite a bit more
> complicated for the average user, and it's not the same at all as the
> separation of presentation that is the huge CSS win.
> There is some benefit for folks who are presenting a lot of content in a
> consistent way.... in other words folks who already have some kind of
> templating engine and who can easily do RDFa in the first place.
> For folks who have ad-hoc HTML, this is more complicated.
> So, like I said, interesting, but I think only a small benefit for large
> publishers, and a significant downside for small publishers. All in all,
> for Creative Commons, for example, this is not as good.
Hmm. It *sounds* like you're arguing that for small authors crdf (or some
similar external meta categorization) is too complex, and for large authors
it's unnecessary because they have templating engines to insert the rdfa for
Is this approximately your intended message? If so, then how do you square
this with the plain-to-see usefulness and heavy adoption of CSS? Small
authors appreciate the clean aesthetics and easy edittability it gives to
their hand-crafted code, and large authors appreciate the reduction in page
weight from it's declare-once-use-everywhere nature. Of course, once upon a
time small authors didn't understand CSS, and templating engines can chug
out table-based layouts as easily as anything else. I'm sure this exact
argument was used against CSS at the time as well.
I also feel the comparison to CSS is quite exact - with CSS you have to
first map your html to semantic categories, and then map those categories to
presentional settings. All crdf changes is that you're mapping the semantic
categories to external metadata categories. There's a hidden benefit that
relatively often you'll be able to reuse the semantic categories for both
Again, I see the benefit of an inline metadata solution, the same as I see
the benefit of inline @style. I just think that it's something that many of
us authors will reject almost automatically in our own coding for the same
reasons that we reject inline @style and use <style> blocks or external css
You want rdf in html5. Fine, that's great, many of us are open to
discussion on this. I'm just trying to get you to realize that there are
*very good reasons* to reject RDFa initially and only let it in as an
alternate metadata syntax for edge cases like non-savvy authors needing
metadata, or machine production of metadata. The web authoring community
has cleaned house in our pages in many ways. We've moved style data to
external CSS and moved behavior data to external JS. Why is it so hard to
believe that we don't want to repeat that process with meta data, and would
rather start with it outside?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg