From W3C Wiki
AWWSW April 1 2008 Homework
Assignment: Specify a relationship between a thing and an HTTP response received in response to a GET of a URI naming the thing.
JAR's response (SKETCH)
What relationship? "corresponds to" in the sense of RFC2616. R is-elicited-by "http://www.usconstitution.net/const.html". R rdf:type http:ResponseMessage. R has-status status:200-ok. By RFC2616, 200 means that "an entity corresponding to the requested resource is sent in the response" "entity" is defined technically as "metainformation in the form of entity-header fields and content in the form of an entity-body". Here the "entity" consists of the Content-Type: field, the Last-Modified: field, and the content. "correspond" is not defined in RFC2616, but it is used there... e.g. "The requested resource corresponds to any one of a set of representations..." suggesting that resources and representations "correspond". R carries-entity E. E rdf:type rfc2616:Entity. E has-content-type contenttype:text--html. E has-last-modified "2008-03-31 17:43:30". E has-content "<!DOCTYPE ...". contenttype:text--html is-specified-by <some document>. E rfc2616:corresponds-to-resource http://www.usconstitution.net/const.html. Most domains and ranges are obvious: is-elicited-by: http:ResponseMessage -> xsd:anyURI has-status: http:Message -> Message-status carries-entity: http:Message -> rfc2616:Entity has-content-type: rfc2616:Entity -> Content-type has-last-modified: rfc2616:Entity -> xsd:date has-content: rfc2616:Entity -> literal rfc2616:corresponds-to-resource: rfc2616:Entity -> rfc2616:Resource or if you prefer rfc2616:corresponds-to-resource: rfc2616:Entity -> awww:InformationResource Tim and Noah don't want to "overfit" to HTTP, so we can permit generalizations beyond "entity": rfc2616:Entity rdfs:subclass jar:GeneralizedEntity. rfc2616:corresponds-to-resource rdfs:subproperty jar:corresponds-to-resource.