April 12, 2009
Amendment: Strengthening Identity on the Web
[Changed 2008-04-13 to use 302 Found instead of 307 Temporary Redirect.]
A couple of days ago, I blogged about 3 ways to strengthen identity on the Web. The 3rd way is unconventional and requires an example.
The general idea is that a client should be able to navigate/negotiate to representations of a resource that are hosted under a different domain. Here's an example in the context of Linked Data:
| http://example.org/Person/alice | Real World Object URI returning HTTP 303 See Other to... |
| http://example.org/Person/alice/ | negotiable Generic Document URI returning HTTP 302 Found to ... |
| http://famouswiki.com/alicia_foo | returning a Web Document with HTTP 200 OK |
In principle, then, any Web Document on the distributed Web that says something *about* alice as a Real World Object could be reached from a single URI and using conventional HTTP behaviors to automate the process.
0 comments so far