May 15, 2009
Linked Data and httpRange-14 Concepts and Relationships
Note that unlike httpRange-14, a Linked Data interpretation requires additional, but relatively lightweight, assumptions on the Architecture of the World Wide Web. Here are at least some of them:
- Clients can unambiguously classify a resource as a Real World Object (RWO) either by the presence of a hash in the HTTP URI (deduced prior to the HTTP request) or an HTTP 303 See Other status in the response (deduced after the HTTP request). In comparison, an HTTP 200 OK can be used to unambiguously classify the resource as a Web Document/Information Resource.
- This implies that Real World Object vs. Web/Document/Information Resource are disjoint.
- Every Real World Object needs to have at least one associated Web Document/Information Resource that contains information about it.
- Every Web Document describes one RWO. The fact that some of these RWOs are mash-ups doesn't change this fact. Traditional understandings of the Web commonly fail to identify these Real World Objects with HTTP URIs.
- The Web Document returned by dereferencing a RWO URI is expected to contain information about the RWO. Linked Data/httpRange-14 do not split hairs between data and metadata. It is all just information and information is invariably about something in the real world.
One of the beauties of embracing the Linked Data assumptions as a matter of policy is that they benefit others who may not even be aware of their significance.