W3C home > Mailing lists > Public > www-tag@w3.org > June 2009

Fwd: Splitting vs. Interpreting

From: Sean B. Palmer <sean@miscoranda.com>
Date: Tue, 16 Jun 2009 20:24:36 +0100
Message-ID: <b6bb4d890906161224xdf97531u755af3781a224a41@mail.gmail.com>
To: david@dbooth.org
Cc: www-tag@w3.org
Sorry, looks like I had an old address on file for you.

---------- Forwarded message ----------
From: Sean B. Palmer <sean@miscoranda.com>
Date: Tue, Jun 16, 2009 at 8:23 PM
Subject: Splitting vs. Interpreting
To: David Booth <dbooth@hp.com>
Cc: www-tag@w3.org

You write about ambiguous and specific references here:


When I worked on EARL in 2002, we had to solve httpRange-14, and we
did it in a practical way which your splitting document reminds me of.

We might want to evaluate a tool of some kind in EARL, say the W3C
Validator. But then we didn't know whether validator.w3.org was the
tool itself or a page about the tool. That's httpRange-14 in a
nutshell, before it was “solved” with the 303 hack.

So what we did was this:

<http://validator.w3.org/> earl:tool _:Validator .

The clever bit is that the earl:tool property says: if the subject is
a Document (i.e. an IR), then the object is the Tool described by that
document; whereas if the subject is a Tool, then the object is simply
the same thing as the subject.

And as you can imagine, this is extensible to interpreting ambiguous
resources in all kinds of ways. Now the TAG finding says that it's
removed a certain level of ambiguity, but there are other ambiguities
one might want to resolve when a page 303s and then still doesn't
define carefully what's at the end of it. So the EARL method is much
more practical.

You might also want to think a bit harder about statements such as
“there is no architectural need for Person and IR to be considered
disjoint”. Consider if you were using Facebook and it started
conflating people with groups and games and so on. But of course
people break the rules of the web until they matter, and since there's
no Semantic Web User Agent this rule doesn't matter.

I'm not saying that the TAG finding should be canned because you can
use the kind of interpretation properties that I've described as a way
around it. The point is rendered moot by various architectural
problems. But you ought to compare the 2002 and 2009 architectural
solutions carefully.

Sean B. Palmer, http://inamidst.com/sbp/
Received on Tuesday, 16 June 2009 19:28:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:29 UTC