The identification of resources on the Web by URI may not be sufficient to uniquely resolve a document as other factors such as HTTP content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the Evaluation and Report Language (EARL). This document describes a representation of HTTP vocabulary in RDF. The terms defined by this document allow HTTP headers that have been exchanged between a client and a server to be recorded in RDF format. The terms defined by this document includes vocabulary for HTTPS as well as other extensions to the core specification.
This document defines a representation of the Hyper Text Transfer Protocol (HTTP) using the Resource Description Framework (RDF). It defines a collection of RDF classes and properties that represent the HTTP vocabulary as defined by the HTTP specification. These RDF terms can be used to record HTTP request and response messages in RDF format. For example by automated Web accessibility evaluation tools to describe Web resources, including the various headers exchanged between the client and server during content negotiation. More usage examples for these terms are described in section 1.2. Use Cases.
This document is not inteded to be a clarification of the different concepts of the HTTP specification. The HTTP specification is defined by a series of Request for Comments (RFC) and other documentation. These are listed in Appendix C. References. This document is also not intended to be an introduction to RDF, refer to [RDF] or [RDF-PRIMER] for this purpose.
The RDF representation of the HTTP vocabulary defined by this document uses namespace http://www.w3.org/2006/http#. The prefix http is used throughout this document to denote this namespace.
By default, the vocabulary introduced by this document uses names starting with upper-case letters for classes and names starting with lower-case letters for properties. The names for header properties are all-lower-case and use the same form as defined by the corresponding RFC documentation (e.g. accept-charset for the Accept-Charset header, or soapaction for the SoapAction extension header).
[Editor's Note: the Working Group is intending to elaborate and better describe the use cases listed below. The Working Group invites contribution and suggestions for further use cases.]
The following (non-exhaustive) list of use cases aims to highlight some of the different usages of this vocabulary:
- Reporting Test Results
- When Web resources are tested, for example for accessibility or other quality assurance testing, it may be significant to record the exact headers of the resource, especially those exchanged during content negotiation. RDF reporting languages like [EARL] can use this vocabulary to record these headers, for example POST parameters that were sent through a form and used by the server to generate a response.
- Precising Conformance Claims
- Conformance claims, for example conformance to the [WCAG], are sometimes only applicable to specific versions of a Web resource that is served at the same URI. For example a document that is served in multiple languages using language negotiation. The vocabulary presented by this document can be used to precise specific versions of Web resources for conformance claims.
- Developing Web Applications
- Web authoring tools, for example development tools for rich Web applications with dynamic content, can use this vocabulary to record the information exchanged between the client and the server in order to help developers debug scripts and applications. For example for developing AJAX applications where the Web resource is a composition of small sequences of contents.
This section defines RDF terms for the basic HTTP 1.1 specification according to [RFC 2616].
The Connection class represents a connection that is used for the HTTP transfer. The following properties may appear in nodes of type Connection:
connectionAuthority representing the connected authority (server host and port), andrequest representing an HTTP request.
Example 2.1: A Connection object.
<http:Connection rdf:ID="conn">
<http:connectionAuthority>www.example.org:80</http:connectionAuthority>
<http:request rdf:resource="#req0"/>
</http:Connection>
The Request class represents an HTTP request. There are eight subclasses derived from the Request class, one for each request type defined in [RFC 2616]:
OptionsRequest representing an HTTP Options request,GetRequest representing an HTTP Get request,HeadRequest representing an HTTP Head request,PostRequest representing an HTTP Post request,PutRequest representing an HTTP Put request,DeleteRequest representing an HTTP Delete request,TraceRequest representing an HTTP Trace request, andConnectRequest representing an HTTP Connect request.
The following properties may appear in nodes of type Request:
Example 2.2: A GetRequest object.
<http:GetRequest rdf:ID="req0">
<http:abs_path>/</http:abs_path>
<http:version>1.1</http:version>
<http:accept>text/html;q=1.0, */*;q=0.01</http:accept>
<http:accept-language>de-DE;q=1.0, de;q=0.75, en-GB;q=0.5,
en;q=0.25, *;q=0.01</http:accept-language>
<http:response rdf:resource="#resp0"/>
</http:GetRequest>
The requestURI property represents the request URI as specified in section 5.1.2 of [RFC 2616]. The value of the property is either the constant value http:asterisk or a Literal value of the absolute URI, the absolute path, or an authority. This vocabulary defines the following sub-properties to reference these values:
absoluteURI,abs_path, andauthority.
Example 2.3: The use of the requestURI property and its sub-properties.
<http:OptionsRequest>
<http:requestURI rdf:resource="http://www.w3.org/2006/http#asterisk"/>
...
</http:OptionsRequest>
<http:GetRequest>
<http:absoluteURI>http://www.example.org:80/foo/bar</http:absoluteURI>
...
</http:GetRequest>
<http:GetRequest>
<http:abs_path>/foo/bar</http:abs_path>
...
</http:GetRequest>
<ConnectRequest>
<http:authority>www.example.org:80</http:authority>
...
</ConnectRequest>
The Response class represents an HTTP response as defined in [RFC 2616]. The following properties may appear in nodes of type Response:
Example 2.4: A Response object.
<http:Response rdf:ID="resp0">
<http:version>1.1</http:version>
<http:responseCode rdf:resource="http://www.w3.org/2006/http#200"/>
<http:content-type>application/xhtml+xml;charset=utf-8</http:content-type>
<http:vary>accept, accept-language</http:vary>
<http:body rdf:parseType="Literal">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Hello World!</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
</http:body>
</http:Response>
The header property represents an HTTP header. There are additional properties derived from the header property; every sub-property refers to a header defined in [RFC 2616].
The following properties may appear in nodes of type Request:
accept representing an Accept header,accept-charset representing an Accept-Charset header,accept-encoding representing an Accept-Encoding header,accept-language representing an Accept-Language header,authorization representing an Authorization header,expect representing an Expect header,from representing a From header,host representing a Host header,if-match representing an If-Match header,if-modified-since representing an If-Modified-Since header,if-none-match representing an If-None-Match header,if-range representing an If-Range header,if-unmodified-since representing an If-Unmodified-Since header,max-forwards representing a Max-Forwards header,proxy-authorization representing a Proxy-Authorization header,range representing a Range header,referer representing a Referer header,te representing a TE header, anduser-agent representing a User-Agent header.
The following properties may appear in nodes of type Response:
accept-ranges representing a Accept-Ranges header,age representing an Age header,etag representing an ETag header,location representing a Location header,proxy-authenticate representing a Proxy-Authenticate header,retry-after representing a Retry-After header,server representing a Server header,vary representing a Vary header, andwww-authenticate representing a WWW-Authenticate header.
The following properties may appear in nodes of type Request and Response:
allow representing an Allow header,cache-control representing a Cache-Control header,connection representing a Connection header,content-encoding representing a Content-Encoding header,content-language representing a Content-Language header,content-length representing a Content-Length header,content-location representing a Content-Location header,content-md5 representing a Content-MD5 header,content-range representing a Content-Range header,content-type representing a Content-Type header,date representing a Date header,expires representing an Expires header,last-modified representing a Last-Modified header,mime-version representing a MIME-Version header,pragma representing a Pragma header,trailer representing a Trailer header,transfer-encoding representing a Transfer-Encoding header,upgrade representing an Upgrade header,via representing a Via header, andwarning representing a Warning header.
The body property represents an HTTP entity body as defined in [RFC 2616]. It can appear in nodes of both type Request or Response. HTTP bodies are series of bytes. You must use the following algorithm:
Is the resource a text resource?
Example 2.5: The body property.
For non-text content use Base64 encoding and a data URI:
<http:body rdf:resource="data:base64,aksgbq3833o3gbo4zgblakc8t9ut2">
For XML content use the "Literal" parse type:
<http:body rdf:parseType="Literal">
<foo>
<bar>blah</bar>
</foo>
</http:body>
For non-XML content use the following approach:
<http:body><![CDATA[<head>
<meta name="keywords" content="foo, bar">
</head>]]></http:body>
There are quite a lot of headers used in HTTP, which are not defined in the HTTP 1.1 specification (RFC 2616) itself. This section defines properties for header extensions according to [RFC 4229].
The following extension properties may appear in nodes of type Request:
accept-additions representing an Accept-Additions header (defined in [RFC 2324]),accept-features representing an Accept-Features header (defined in [RFC 2295]),a-im representing an A-IM header (defined in [RFC 3229]),content-id representing a Content-ID header (defined in [DRP]),cookie representing an Cookie header (defined in [RFC 2965]),cookie2 representing an Cookie2 header (defined in [RFC 2965]),c-man representing a C-Man header (defined in [RFC 2774]),c-opt representing a C-Opt header (defined in [RFC 2774]),c-pep representing a C-PEP header (defined in [PEP]),depth representing a Depth header (defined in [RFC 2518]),destination representing a Destination header (defined in [RFC 2518]),differential-id representing a Differential-ID header (defined in [DRP]),if representing an If header (defined in [RFC 2518]),label representing a Label header (defined in [RFC 3253]),man representing a Man header (defined in [RFC 2774]),negotiate representing an Negotiate header (defined in [RFC 2295]),opt representing an Opt header (defined in [RFC 2774]),optional representing an Optional header (defined in [WIRE]),ordering-type representing an Ordering-Type header (defined in [RFC 3648]),overwrite representing an Overwrite header (defined in [RFC 2518]),pep representing a PEP header (defined in [PEP]),position representing a Position header (defined in [RFC 3648]),profileobject representing a ProfileObject header (defined in [Ops-OverHTTP]),proxy-features representing a Proxy-Features header (defined in [Proxy Notification]),resolution-hint representing a Resolution-Hint header (defined in [WIRE]),soapaction representing a SoapAction header (defined in [SOAP1.1]),subok representing a SubOK header (defined in [DupSup]),subst representing a Subst header (defined in [DupSup]),surrogate-capability representing a Surrogate-Capability header (defined in [EdgeArch]),ua-color representing a UA-Color header (defined in [UA Attributes]),ua-media representing a UA-Media header (defined in [UA Attributes]),ua-pixels representing a UA-Pixels header (defined in [UA Attributes]),ua-resolution representing a UA-Resolution header (defined in [UA Attributes]),ua-windowpixels representing a UA-Windowpixels header (defined in [UA Attributes]), andwant-digest representing a Want-Digest header (defined in [RFC 3230]).
The following extension properties may appear in nodes of type Response:
alternates representing an Alternates header (defined in [RFC 2295]),authentication-info representing an Authentication-Info header (defined in [RFC 2617]),compliance representing a Compliance header (defined in [OPTIONS messages]),content-disposition representing a Content-Disposition header (defined in [RFC 2183]),content-script-type representing a Content-Script-Type header (defined in [HTML4]),content-style-type representing a Content-Style-Type header (defined in [HTML4]),cost representing a Cost header (defined in [ObjectHeaders]),c-ext representing a C-Ext header (defined in [RFC 2774]),c-pep-info representing a C-PEP-Info header (defined in [PEP]),dav representing a DAV header (defined in [RFC 2518]),default-style representing a Default-Style header (defined in [HTML4]),delta-base representing a Delta-Base header (defined in [RFC 3229]),digest representing a Digest header (defined in [RFC 3230]),ext representing an Ext header (defined in [RFC 2774]),getprofile representing a GetProfile header (defined in [Ops-OverHTTP]),im representing an IM header (defined in [RFC 3229]),non-compliance representing a Non-Compliance header (defined in [OPTIONS messages]),p3p representing a P3P header (defined in [P3P]),pep-info representing a PEP-Info header (defined in [PEP]),pics-label representing a PICS-Label header (defined in [PICSLabels]),proxy-authentication-info representing a Proxy-Authentication-Info header (defined in [RFC 2617]),proxy-instruction representing a Proxy-Instruction header (defined in [Proxy Notification]),public representing a Public header (defined in [RFC 2068]),refresh representing a Refresh header (defined in [EDD]),resolver-location representing a Resolver-Location header (defined in [WIRE]),safe representing a Safe header (defined in [RFC 2310]),setprofile representing a SetProfile header (defined in [Ops-OverHTTP]),set-cookie representing a Set-Cookie header (defined in [RFC 2109]),set-cookie2 representing a Set-Cookie2 header (defined in [RFC 2965]),status-uri representing a Status-URI header (defined in [RFC 2518]),surrogate-control representing a Surrogate-Control header (defined in [EdgeArch]),tcn representing a TCN header (defined in [RFC 2295]),title representing a Title header (defined in [ObjectHeaders]),variant-vary representing a Variant-Vary header (defined in [RFC 2295]), andversion representing a Version header (defined in [ObjectHeaders]).
The following extension properties may appear in nodes of type Request or Response:
content-base representing a Content-Base header (defined in [RFC 2068]),content-transfer-encoding representing a Content-Transfer-Encoding header (defined in [ObjectHeaders]),content-version representing a Content-Version header (defined in [RFC 2068]),derived-from representing a Derived-From header (defined in [RFC 2068]),link representing a Link header (defined in [RFC 2068]),lock-token representing a Lock-Token header (defined in [RFC 2518]),message-id representing a Message-ID header (defined in [ObjectHeaders]),meter representing a Meter header (defined in [RFC 2227]),protocol representing a Protocol header (defined in [PICSLabels]),protocol-info representing a Protocol-Info header (defined in [JEPI]),protocol-query representing a Protocol-Query header (defined in [JEPI]),protocol-request representing a Protocol-Request header (defined in [PICSLabels]),security-scheme representing a Security-Scheme header (defined in [RFC 2660]),timeout representing a Timeout header (defined in [RFC 2518]), anduri representing a URI header (defined in [RFC 2068]).
For headers not defined in HTTP 1.1 or any of the header extensions, the additionalHeader property can be used in both Request and Response classes. The object of this property is of type MessageHeader and represents a message header according to section 4.2 of [RFC 2616]. Thus the field class MUST have the following properties:
http:fieldName representing a field name;http:fieldValue representing a field value.
Example 4.1: additionalHeader object.
<http:additionalHeader>
<http:MessageHeader>
<http:fieldName>x-foo</http:fieldName>
<http:fieldValue>bar</http:fieldValue>
</http:MessageHeader>
</http:additionalHeader>
Editor's Note: the working group is looking for feedback and comments on the schema defined below, for example on the hierarchy of the classes or the restrictions on the properties.
<![CDATA[<!DOCTYPE rdf:RDF [
<!ENTITY http-ns "http://www.w3.org/2006/http#">
]>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:owl="http://www.w3.org/2002/07/owl#">
<rdf:Description rdf:about="&http-ns;">
<rdfs:comment xml:lang="en">A namespace for describing HTTP messages
(http://www.w3.org/Protocols/rfc2616/rfc2616.html)</rdfs:comment>
</rdf:Description>
<rdfs:Class rdf:about="&http-ns;Connection">
<rdfs:label xml:lang="en">Connection</rdfs:label>
<rdfs:comment xml:lang="en">An HTTP connection</rdfs:comment>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="&http-ns;connectionAuthority"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="&http-ns;connectionAuthority">
<rdfs:label xml:lang="en">Connection authority</rdfs:label>
<rdfs:comment xml:lang="en">An HTTP Connection authority</rdfs:comment>
<rdfs:domain rdf:resource="&http-ns;Connection"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;request">
<rdfs:label xml:lang="en">Request</rdfs:label>
<rdfs:comment xml:lang="en">Has an HTTP request</rdfs:comment>
<rdfs:domain rdf:resource="&http-ns;Connection"/>
<rdfs:range rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdfs:Class rdf:about="&http-ns;Request">
<rdfs:label xml:lang="en">Request</rdfs:label>
<rdfs:comment xml:lang="en">An HTTP request</rdfs:comment>
</rdfs:Class>
<!-- request methods start -->
<rdfs:Class rdf:about="&http-ns;OptionsRequest">
<rdfs:label xml:lang="en">Options</rdfs:label>
<rdfs:comment xml:lang="en">The OPTIONS request</rdfs:comment>
<rdfs:subClassOf rdf:resource="&http-ns;Request"/>
</rdfs:Class>
<rdfs:Class rdf:about="&http-ns;GetRequest">
<rdfs:label xml:lang="en">Get</rdfs:label>
<rdfs:comment xml:lang="en">The GET request</rdfs:comment>
<rdfs:subClassOf rdf:resource="&http-ns;Request"/>
</rdfs:Class>
<rdfs:Class rdf:about="&http-ns;HeadRequest">
<rdfs:label xml:lang="en">Head</rdfs:label>
<rdfs:comment xml:lang="en">The HEAD request</rdfs:comment>
<rdfs:subClassOf rdf:resource="&http-ns;Request"/>
</rdfs:Class>
<rdfs:Class rdf:about="&http-ns;PostRequest">
<rdfs:label xml:lang="en">Post</rdfs:label>
<rdfs:comment xml:lang="en">The POST request</rdfs:comment>
<rdfs:subClassOf rdf:resource="&http-ns;Request"/>
</rdfs:Class>
<rdfs:Class rdf:about="&http-ns;PutRequest">
<rdfs:label xml:lang="en">Put</rdfs:label>
<rdfs:comment xml:lang="en">The PUT request</rdfs:comment>
<rdfs:subClassOf rdf:resource="&http-ns;Request"/>
</rdfs:Class>
<rdfs:Class rdf:about="&http-ns;DeleteRequest">
<rdfs:label xml:lang="en">Delete</rdfs:label>
<rdfs:comment xml:lang="en">The DELETE request</rdfs:comment>
<rdfs:subClassOf rdf:resource="&http-ns;Request"/>
</rdfs:Class>
<rdfs:Class rdf:about="&http-ns;TraceRequest">
<rdfs:label xml:lang="en">Trace</rdfs:label>
<rdfs:comment xml:lang="en">The TRACE request</rdfs:comment>
<rdfs:subClassOf rdf:resource="&http-ns;Request"/>
</rdfs:Class>
<rdfs:Class rdf:about="&http-ns;ConnectRequest">
<rdfs:label xml:lang="en">Connect</rdfs:label>
<rdfs:comment xml:lang="en">The CONNECT request</rdfs:comment>
<rdfs:subClassOf rdf:resource="&http-ns;Request"/>
</rdfs:Class>
<!-- request methods end -->
<rdf:Property rdf:about="&http-ns;requestURI">
<rdfs:label xml:lang="en">Request URI</rdfs:label>
<rdfs:comment xml:lang="en">Has an HTTP request URI</rdfs:comment>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:range rdf:resource="&http-ns;RequestURI"/>
</rdf:Property>
<rdfs:Class rdf:about="&http-ns;RequestURI">
<rdfs:label xml:lang="en">Request URI</rdfs:label>
<rdfs:comment xml:lang="en">The HTTP request URI</rdfs:comment>
<owl:oneOf rdf:parseType="Collection">
<owl:Thing rdf:about="&http-ns;asterisk">
<rdfs:label xml:lang="en">Asterisk</rdfs:label>
<rdfs:comment xml:lang="en">An asterisk used as request URI</rdfs:comment>
</owl:Thing>
<owl:Thing rdf:about="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</owl:oneOf>
</rdfs:Class>
<rdf:Property rdf:about="&http-ns;absoluteURI">
<rdfs:label xml:lang="en">Absolute request URI</rdfs:label>
<rdfs:comment xml:lang="en">An absolute request URI</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;requestURI"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;abs_path">
<rdfs:label xml:lang="en">Absolute path</rdfs:label>
<rdfs:comment xml:lang="en">An absolute path used as request URI</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;requestURI"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;authority">
<rdfs:label xml:lang="en">Authority</rdfs:label>
<rdfs:comment xml:lang="en">An authority used as request URI</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;requestURI"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;response">
<rdfs:label xml:lang="en">Response</rdfs:label>
<rdfs:comment xml:lang="en">Has an HTTP response</rdfs:comment>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:range rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdfs:Class rdf:about="&http-ns;Response">
<rdfs:label xml:lang="en">Response</rdfs:label>
<rdfs:comment xml:lang="en">The HTTP Response</rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="&http-ns;responseCode">
<rdfs:label xml:lang="en">Response code</rdfs:label>
<rdfs:comment xml:lang="en">Has an HTTP response code</rdfs:comment>
<rdfs:domain rdf:resource="&http-ns;Response"/>
<rdfs:range rdf:resource="&http-ns;ResponseCode"/>
</rdf:Property>
<rdfs:Class rdf:about="&http-ns;ResponseCode">
<rdfs:label xml:lang="en">Response code</rdfs:label>
<rdfs:comment xml:lang="en">The HTTP Response Code</rdfs:comment>
<owl:oneOf rdf:parseType="Collection">
<owl:Thing rdf:about="&http-ns;100">
<rdfs:label xml:lang="en">Continue</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;101">
<rdfs:label xml:lang="en">Switching Protocols</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;200">
<rdfs:label xml:lang="en">OK</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;201">
<rdfs:label xml:lang="en">Created</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;202">
<rdfs:label xml:lang="en">Accepted</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;203">
<rdfs:label xml:lang="en">Non-Authoritative Information</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;204">
<rdfs:label xml:lang="en">No Content</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;205">
<rdfs:label xml:lang="en">Reset Content</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;206">
<rdfs:label xml:lang="en">Partial Content</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;300">
<rdfs:label xml:lang="en">Multiple Choices</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;301">
<rdfs:label xml:lang="en">Moved Permanently</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;302">
<rdfs:label xml:lang="en">Found</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;303">
<rdfs:label xml:lang="en">See Other</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;304">
<rdfs:label xml:lang="en">Not Modified</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;305">
<rdfs:label xml:lang="en">Use Proxy</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;306">
<rdfs:label xml:lang="en">(Unused)</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;307">
<rdfs:label xml:lang="en">Temporary Redirect</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;400">
<rdfs:label xml:lang="en">Bad Request</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;401">
<rdfs:label xml:lang="en">Unauthorized</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;402">
<rdfs:label xml:lang="en">Payment Required</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;403">
<rdfs:label xml:lang="en">Forbidden</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;404">
<rdfs:label xml:lang="en">Not Found</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;405">
<rdfs:label xml:lang="en">Method Not Allowed</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;406">
<rdfs:label xml:lang="en">Not Acceptable</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;407">
<rdfs:label xml:lang="en">Proxy Authentication Required</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;408">
<rdfs:label xml:lang="en">Request Timeout</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;409">
<rdfs:label xml:lang="en">Conflict</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;410">
<rdfs:label xml:lang="en">Gone</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;411">
<rdfs:label xml:lang="en">Length Required</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;412">
<rdfs:label xml:lang="en">Precondition Failed</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;413">
<rdfs:label xml:lang="en">Request Entity Too Large</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;414">
<rdfs:label xml:lang="en">Request-URI Too Long</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;415">
<rdfs:label xml:lang="en">Unsupported Media Type</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;416">
<rdfs:label xml:lang="en">Requested Range Not Satisfiable</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;417">
<rdfs:label xml:lang="en">Expectation Failed</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;500">
<rdfs:label xml:lang="en">Internal Server Error</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;501">
<rdfs:label xml:lang="en">Not Implemented</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;502">
<rdfs:label xml:lang="en">Bad Gateway</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;503">
<rdfs:label xml:lang="en">Service Unavailable</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;504">
<rdfs:label xml:lang="en">Gateway Timeout</rdfs:label>
</owl:Thing>
<owl:Thing rdf:about="&http-ns;505">
<rdfs:label xml:lang="en">HTTP Version Not Supported</rdfs:label>
</owl:Thing>
</owl:oneOf>
</rdfs:Class>
<rdf:Property rdf:about="&http-ns;header">
<rdfs:label xml:lang="en">Header</rdfs:label>
<rdfs:comment xml:lang="en">Has an HTTP header</rdfs:comment>
</rdf:Property>
<!-- HTTP 1.1 headers start -->
<rdf:Property rdf:about="&http-ns;accept">
<rdfs:label xml:lang="en">Accept</rdfs:label>
<rdfs:comment xml:lang="en">The Accept header (see RFC 2616,
section 14.1)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;accept-charset">
<rdfs:label xml:lang="en">Accept-Charset</rdfs:label>
<rdfs:comment xml:lang="en">The Accept-Charset header (see RFC 2616,
section 14.2)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;accept-encoding">
<rdfs:label xml:lang="en">Accept-Encoding</rdfs:label>
<rdfs:comment xml:lang="en">The Accept-Encoding header (see RFC 2616,
section 14.3)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;accept-language">
<rdfs:label xml:lang="en">Accept-Language</rdfs:label>
<rdfs:comment xml:lang="en">The Accept-Language header (see RFC 2616,
section 14.4)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;accept-ranges">
<rdfs:label xml:lang="en">Accept-Ranges</rdfs:label>
<rdfs:comment xml:lang="en">The Accept-Ranges header (see RFC 2616,
section 14.5)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;age">
<rdfs:label xml:lang="en">Age</rdfs:label>
<rdfs:comment xml:lang="en">The Age header (see RFC 2616,
section 14.6)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;allow">
<rdfs:label xml:lang="en">Allow</rdfs:label>
<rdfs:comment xml:lang="en">The Allow header (see RFC 2616,
section 14.7)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;authorization">
<rdfs:label xml:lang="en">Authorization</rdfs:label>
<rdfs:comment xml:lang="en">The Authorization header (see RFC 2616,
section 14.8)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;cache-control">
<rdfs:label xml:lang="en">Cache-Control</rdfs:label>
<rdfs:comment xml:lang="en">The Cache-Control header (see RFC 2616,
section 14.9)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;connection">
<rdfs:label xml:lang="en">Connection</rdfs:label>
<rdfs:comment xml:lang="en">The Connection header (see RFC 2616,
section 14.10)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;content-encoding">
<rdfs:label xml:lang="en">Content-Encoding</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Encoding header (see RFC 2616,
section 14.11)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;content-language">
<rdfs:label xml:lang="en">Content-Language</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Language header (see RFC 2616,
section 14.12)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;content-length">
<rdfs:label xml:lang="en">Content-Length</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Length header (see RFC 2616,
section 14.13)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;content-location">
<rdfs:label xml:lang="en">Content-Location</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Location header (see RFC 2616,
section 14.14)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;content-md5">
<rdfs:label xml:lang="en">Content-MD5</rdfs:label>
<rdfs:comment xml:lang="en">The Content-MD5 header (see RFC 2616,
section 14.15)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;content-range">
<rdfs:label xml:lang="en">Content-Range</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Range header (see RFC 2616,
section 14.16)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;content-type">
<rdfs:label xml:lang="en">Content-Type</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Type header (see RFC 2616,
section 14.17)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;date">
<rdfs:label xml:lang="en">Date</rdfs:label>
<rdfs:comment xml:lang="en">The Date header (see RFC 2616,
section 14.18)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;etag">
<rdfs:label xml:lang="en">ETag</rdfs:label>
<rdfs:comment xml:lang="en">The ETag header (see RFC 2616,
section 14.19)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;expect">
<rdfs:label xml:lang="en">Expect</rdfs:label>
<rdfs:comment xml:lang="en">The Expect header (see RFC 2616,
section 14.20)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;expires">
<rdfs:label xml:lang="en">Expires</rdfs:label>
<rdfs:comment xml:lang="en">The Expires header (see RFC 2616,
section 14.21)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;from">
<rdfs:label xml:lang="en">From</rdfs:label>
<rdfs:comment xml:lang="en">The From header (see RFC 2616,
section 14.22)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;host">
<rdfs:label xml:lang="en">Host</rdfs:label>
<rdfs:comment xml:lang="en">The Host header (see RFC 2616,
section 14.23)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;if-match">
<rdfs:label xml:lang="en">If-Match</rdfs:label>
<rdfs:comment xml:lang="en">The If-Match header (see RFC 2616,
section 14.24)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;if-modified-since">
<rdfs:label xml:lang="en">If-Modified-Since</rdfs:label>
<rdfs:comment xml:lang="en">The If-Modified-Since header (see RFC 2616,
section 14.25)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;if-none-match">
<rdfs:label xml:lang="en">If-None-Match</rdfs:label>
<rdfs:comment xml:lang="en">The If-None-Match header (see RFC 2616,
section 14.26)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;if-range">
<rdfs:label xml:lang="en">If-Range</rdfs:label>
<rdfs:comment xml:lang="en">The If-Range header (see RFC 2616,
section 14.27)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;if-unmodified-since">
<rdfs:label xml:lang="en">If-Unmodified-Since</rdfs:label>
<rdfs:comment xml:lang="en">The If-Unmodified-Since header (see RFC
2616, section 14.28)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;last-modified">
<rdfs:label xml:lang="en">Last-Modified</rdfs:label>
<rdfs:comment xml:lang="en">The Last-Modified header (see RFC 2616,
section 14.29)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;location">
<rdfs:label xml:lang="en">Location</rdfs:label>
<rdfs:comment xml:lang="en">The Location header (see RFC 2616,
section 14.30)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;max-forwards">
<rdfs:label xml:lang="en">Max-Forwards</rdfs:label>
<rdfs:comment xml:lang="en">The Max-Forwards header (see RFC 2616,
section 14.31)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;mime-version">
<rdfs:label xml:lang="en">MIME-Version</rdfs:label>
<rdfs:comment xml:lang="en">The MIME-Version header (see RFC 2616,
section 19.4.1)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;pragma">
<rdfs:label xml:lang="en">Pragma</rdfs:label>
<rdfs:comment xml:lang="en">The Pragma header (see RFC 2616,
section 14.32)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;proxy-authenticate">
<rdfs:label xml:lang="en">Proxy-Authenticate</rdfs:label>
<rdfs:comment xml:lang="en">The Proxy-Authenticate header (see RFC
2616, section 14.33)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;proxy-authorization">
<rdfs:label xml:lang="en">Proxy-Authorization</rdfs:label>
<rdfs:comment xml:lang="en">The Proxy-Authorization header (see RFC
2616, section 14.34)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;range">
<rdfs:label xml:lang="en">Range</rdfs:label>
<rdfs:comment xml:lang="en">The Range header (see RFC 2616,
section 14.35)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;referer">
<rdfs:label xml:lang="en">Referer</rdfs:label>
<rdfs:comment xml:lang="en">The Referer header (see RFC 2616,
section 14.36)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;retry-after">
<rdfs:label xml:lang="en">Retry-After</rdfs:label>
<rdfs:comment xml:lang="en">The Retry-After header (see RFC 2616,
section 14.37)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;server">
<rdfs:label xml:lang="en">Server</rdfs:label>
<rdfs:comment xml:lang="en">The Server header (see RFC 2616,
section 14.38)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;te">
<rdfs:label xml:lang="en">TE</rdfs:label>
<rdfs:comment xml:lang="en">The TE header (see RFC 2616,
section 14.39)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;trailer">
<rdfs:label xml:lang="en">Trailer</rdfs:label>
<rdfs:comment xml:lang="en">The Trailer header (see RFC 2616,
section 14.40)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;transfer-encoding">
<rdfs:label xml:lang="en">Transfer-Encoding</rdfs:label>
<rdfs:comment xml:lang="en">The Transfer-Encoding header (see RFC 2616,
section 14.41)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;upgrade">
<rdfs:label xml:lang="en">Upgrade</rdfs:label>
<rdfs:comment xml:lang="en">The Upgrade header (see RFC 2616,
section 14.42)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;user-agent">
<rdfs:label xml:lang="en">User-Agent</rdfs:label>
<rdfs:comment xml:lang="en">The User-Agent header (see RFC 2616,
section 14.43)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;vary">
<rdfs:label xml:lang="en">Vary</rdfs:label>
<rdfs:comment xml:lang="en">The Vary header (see RFC 2616,
section 14.44)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;via">
<rdfs:label xml:lang="en">Via</rdfs:label>
<rdfs:comment xml:lang="en">The Via header (see RFC 2616,
section 14.45)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;warning">
<rdfs:label xml:lang="en">Warning</rdfs:label>
<rdfs:comment xml:lang="en">The Warning header (see RFC 2616,
section 14.46)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;www-authenticate">
<rdfs:label xml:lang="en">WWW-Authenticate</rdfs:label>
<rdfs:comment xml:lang="en">The WWW-Authenticate header (see RFC 2616,
section 14.47)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- HTTP 1.1 headers end -->
<!-- RFC2068 headers start -->
<rdf:Property rdf:about="&http-ns;content-base">
<rdfs:label xml:lang="en">Content-Base</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Base header (see RFC 2068,
section 14.11)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;content-version">
<rdfs:label xml:lang="en">Content-Version</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Version header (see RFC 2068,
section 19.6.2.2)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;derived-from">
<rdfs:label xml:lang="en">Derived-From</rdfs:label>
<rdfs:comment xml:lang="en">The Derived-From header (see RFC 2068,
section 19.6.2.3</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;link">
<rdfs:label xml:lang="en">Link</rdfs:label>
<rdfs:comment xml:lang="en">The Link header (see RFC 2068,
section 19.6.2.4)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;public">
<rdfs:label xml:lang="en">Public</rdfs:label>
<rdfs:comment xml:lang="en">The Public header (see RFC 2068,
section 14.35)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;uri">
<rdfs:label xml:lang="en">URI</rdfs:label>
<rdfs:comment xml:lang="en">The URI header (see RFC 2068,
section 19.6.2.5)</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC2068 headers end -->
<!-- RFC2109 headers start -->
<rdf:Property rdf:about="&http-ns;set-cookie">
<rdfs:label xml:lang="en">Set-Cookie</rdfs:label>
<rdfs:comment xml:lang="en">The Set-Cookie header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC2109 headers end -->
<!-- RFC2227 headers start -->
<rdf:Property rdf:about="&http-ns;meter">
<rdfs:label xml:lang="en">Meter</rdfs:label>
<rdfs:comment xml:lang="en">The Meter header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC2227 headers end -->
<!-- RFC2295 headers start -->
<rdf:Property rdf:about="&http-ns;accept-features">
<rdfs:label xml:lang="en">Accept-Features</rdfs:label>
<rdfs:comment xml:lang="en">The Accept-Features header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;alternates">
<rdfs:label xml:lang="en">Alternates</rdfs:label>
<rdfs:comment xml:lang="en">The Alternates header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;negotiate">
<rdfs:label xml:lang="en">Negotiate</rdfs:label>
<rdfs:comment xml:lang="en">The Negotiate header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;tcn">
<rdfs:label xml:lang="en">TCN</rdfs:label>
<rdfs:comment xml:lang="en">The TCN header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;variant-vary">
<rdfs:label xml:lang="en">Variant-Vary</rdfs:label>
<rdfs:comment xml:lang="en">The Variant-Vary header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC2295 headers end -->
<!-- RFC2310 headers start -->
<rdf:Property rdf:about="&http-ns;safe">
<rdfs:label xml:lang="en">Safe</rdfs:label>
<rdfs:comment xml:lang="en">The Safe header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC2310 headers end -->
<!-- RFC2324 headers start -->
<rdf:Property rdf:about="&http-ns;accept-additions">
<rdfs:label xml:lang="en">Accept-Additions</rdfs:label>
<rdfs:comment xml:lang="en">The Accept-Additions header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<!-- RFC2324 headers end -->
<!-- RFC2518 headers start -->
<rdf:Property rdf:about="&http-ns;dav">
<rdfs:label xml:lang="en">DAV</rdfs:label>
<rdfs:comment xml:lang="en">The DAV header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;depth">
<rdfs:label xml:lang="en">Depth</rdfs:label>
<rdfs:comment xml:lang="en">The Depth header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;destination">
<rdfs:label xml:lang="en">Destination</rdfs:label>
<rdfs:comment xml:lang="en">The Destination header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;if">
<rdfs:label xml:lang="en">If</rdfs:label>
<rdfs:comment xml:lang="en">The If header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;lock-token">
<rdfs:label xml:lang="en">Lock-Token</rdfs:label>
<rdfs:comment xml:lang="en">The Lock-Token header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;overwrite">
<rdfs:label xml:lang="en">Overwrite</rdfs:label>
<rdfs:comment xml:lang="en">The Overwrite header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;status-uri">
<rdfs:label xml:lang="en">Status-URI</rdfs:label>
<rdfs:comment xml:lang="en">The Status-URI header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;timeout">
<rdfs:label xml:lang="en">Timeout</rdfs:label>
<rdfs:comment xml:lang="en">The Timeout header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC2518 headers end -->
<!-- RFC2617 headers start -->
<rdf:Property rdf:about="&http-ns;authentication-info">
<rdfs:label xml:lang="en">Authentication-Info</rdfs:label>
<rdfs:comment xml:lang="en">The Authentication-Info
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;proxy-authentication-info">
<rdfs:label xml:lang="en">Proxy-Authentication-Info</rdfs:label>
<rdfs:comment xml:lang="en">The Proxy-Authentication-Info
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC2617 headers end -->
<!-- RFC2660 headers start -->
<rdf:Property rdf:about="&http-ns;security-scheme">
<rdfs:label xml:lang="en">Security-Scheme</rdfs:label>
<rdfs:comment xml:lang="en">The Security-Scheme
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC2660 headers end -->
<!-- RFC2774 headers start -->
<rdf:Property rdf:about="&http-ns;c-ext">
<rdfs:label xml:lang="en">C-Ext</rdfs:label>
<rdfs:comment xml:lang="en">The C-Ext header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;c-man">
<rdfs:label xml:lang="en">C-Man</rdfs:label>
<rdfs:comment xml:lang="en">The C-Man header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;c-opt">
<rdfs:label xml:lang="en">C-Opt</rdfs:label>
<rdfs:comment xml:lang="en">The C-Opt header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;ext">
<rdfs:label xml:lang="en">Ext</rdfs:label>
<rdfs:comment xml:lang="en">The Ext header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;man">
<rdfs:label xml:lang="en">Man</rdfs:label>
<rdfs:comment xml:lang="en">The Man header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;opt">
<rdfs:label xml:lang="en">Opt</rdfs:label>
<rdfs:comment xml:lang="en">The Opt header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<!-- RFC2774 headers end -->
<!-- RFC2965 headers start -->
<rdf:Property rdf:about="&http-ns;cookie">
<rdfs:label xml:lang="en">Cookie</rdfs:label>
<rdfs:comment xml:lang="en">The Cookie header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;cookie2">
<rdfs:label xml:lang="en">Cookie2</rdfs:label>
<rdfs:comment xml:lang="en">The Cookie2 header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;set-cookie2">
<rdfs:label xml:lang="en">Set-Cookie2</rdfs:label>
<rdfs:comment xml:lang="en">The Set-Cookie2 header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC2965 headers end -->
<!-- RFC3229 headers start -->
<rdf:Property rdf:about="&http-ns;a-im">
<rdfs:label xml:lang="en">A-IM</rdfs:label>
<rdfs:comment xml:lang="en">The A-IM header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;delta-base">
<rdfs:label xml:lang="en">Delta-Base</rdfs:label>
<rdfs:comment xml:lang="en">The Delta-Base header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;im">
<rdfs:label xml:lang="en">IM</rdfs:label>
<rdfs:comment xml:lang="en">The IM header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- RFC3229 headers end -->
<!-- RFC3230 headers start -->
<rdf:Property rdf:about="&http-ns;digest">
<rdfs:label xml:lang="en">Digest</rdfs:label>
<rdfs:comment xml:lang="en">The Digest header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;want-digest">
<rdfs:label xml:lang="en">Want-Digest</rdfs:label>
<rdfs:comment xml:lang="en">The Want-Digest header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<!-- RFC3230 headers end -->
<!-- RFC3253 headers start -->
<rdf:Property rdf:about="&http-ns;label">
<rdfs:label xml:lang="en">Label</rdfs:label>
<rdfs:comment xml:lang="en">The Label header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<!-- RFC3253 headers end -->
<!-- RFC3648 headers start -->
<rdf:Property rdf:about="&http-ns;ordering-type">
<rdfs:label xml:lang="en">Ordering-Type</rdfs:label>
<rdfs:comment xml:lang="en">The Ordering-Type
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;position">
<rdfs:label xml:lang="en">Position</rdfs:label>
<rdfs:comment xml:lang="en">The Position header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<!-- RFC3648 headers end -->
<!-- DRP headers start -->
<!-- http://www.w3.org/TR/NOTE-drp-19970825 -->
<rdf:Property rdf:about="&http-ns;content-id">
<rdfs:label xml:lang="en">Content-ID</rdfs:label>
<rdfs:comment xml:lang="en">The Content-ID header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;differential-id">
<rdfs:label xml:lang="en">Differential-ID</rdfs:label>
<rdfs:comment xml:lang="en">The Differential-ID
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<!-- DRP headers end -->
<!-- Duplicate Suppression headers start -->
<!--
http://www.ietf.org/proceedings/98dec/I-D/draft-mogul-http-dupsup-00.txt
-->
<rdf:Property rdf:about="&http-ns;subok">
<rdfs:label xml:lang="en">SubOK</rdfs:label>
<rdfs:comment xml:lang="en">The SubOK header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<!--rdfs:domain rdf:resource="&http-ns;Request"/-->
</rdf:Property>
<rdf:Property rdf:about="&http-ns;subst">
<rdfs:label xml:lang="en">Subst</rdfs:label>
<rdfs:comment xml:lang="en">The Subst header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<!--rdfs:domain rdf:resource="&http-ns;Request"/-->
</rdf:Property>
<!-- Duplicate Suppression headers end -->
<!-- Exploration of dynamic documents headers start -->
<rdf:Property rdf:about="&http-ns;refresh">
<rdfs:label xml:lang="en">Refresh</rdfs:label>
<rdfs:comment xml:lang="en">The Refresh header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- Exploration of dynamic documents headers end -->
<!-- edge-arch headers start -->
<!-- http://www.w3.org/TR/2001/NOTE-edge-arch-20010804 -->
<rdf:Property rdf:about="&http-ns;surrogate-capability">
<rdfs:label xml:lang="en">Surrogate-Capability</rdfs:label>
<rdfs:comment xml:lang="en">The Surrogate-Capability
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;surrogate-control">
<rdfs:label xml:lang="en">Surrogate-Control</rdfs:label>
<rdfs:comment xml:lang="en">The Surrogate-Control
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- edge-arch headers end -->
<!-- HTML 4 headers start -->
<!-- http://www.w3.org/TR/1999/REC-html401-19991224/ -->
<rdf:Property rdf:about="&http-ns;content-script-type">
<rdfs:label xml:lang="en">Content-Script-Type</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Script-Type
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;content-style-type">
<rdfs:label xml:lang="en">Content-Style-Type</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Style-Type
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;default-style">
<rdfs:label xml:lang="en">Default-Style</rdfs:label>
<rdfs:comment xml:lang="en">The Default-Style
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- HTML 4 headers end -->
<!-- Object Headers headers start -->
<!-- http://www.w3.org/Protocols/HTTP/Object_Headers.html -->
<rdf:Property rdf:about="&http-ns;content-transfer-encoding">
<rdfs:label xml:lang="en">Content-Transfer-Encoding</rdfs:label>
<rdfs:comment xml:lang="en">The Content-Transfer-Encoding
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;cost">
<rdfs:label xml:lang="en">Cost</rdfs:label>
<rdfs:comment xml:lang="en">The Cost header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;message-id">
<rdfs:label xml:lang="en">Message-ID</rdfs:label>
<rdfs:comment xml:lang="en">The Message-ID header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;title">
<rdfs:label xml:lang="en">Title</rdfs:label>
<rdfs:comment xml:lang="en">The Title header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;version">
<rdfs:label xml:lang="en">Version</rdfs:label>
<rdfs:comment xml:lang="en">The Version header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- Object Headers headers end -->
<!-- OPS over HTTP headers start -->
<!-- http://www.w3.org/TR/NOTE-OPS-OverHTTP -->
<rdf:Property rdf:about="&http-ns;getprofile">
<rdfs:label xml:lang="en">GetProfile</rdfs:label>
<rdfs:comment xml:lang="en">The GetProfile header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;profileobject">
<rdfs:label xml:lang="en">ProfileObject</rdfs:label>
<rdfs:comment xml:lang="en">The ProfileObject
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;setprofile">
<rdfs:label xml:lang="en">SetProfile</rdfs:label>
<rdfs:comment xml:lang="en">The SetProfile header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- OPS over HTTP headers end -->
<!-- OPTIONS messages headers start -->
<!--
http://www.watersprings.org/pub/id/draft-ietf-http-options-02.txt
-->
<rdf:Property rdf:about="&http-ns;compliance">
<rdfs:label xml:lang="en">Compliance</rdfs:label>
<rdfs:comment xml:lang="en">The Compliance header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<!--rdfs:domain rdf:resource="&http-ns;Response"/-->
</rdf:Property>
<rdf:Property rdf:about="&http-ns;non-compliance">
<rdfs:label xml:lang="en">Non-Compliance</rdfs:label>
<rdfs:comment xml:lang="en">The Non-Compliance
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<!--rdfs:domain rdf:resource="&http-ns;Response"/-->
</rdf:Property>
<!-- OPTIONS messages headers end -->
<!-- P3P headers start -->
<!-- http://www.w3.org/TR/2002/REC-P3P-20020416/ -->
<rdf:Property rdf:about="&http-ns;p3p">
<rdfs:label xml:lang="en">P3P</rdfs:label>
<rdfs:comment xml:lang="en">The P3P header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- P3P headers end -->
<!-- PEP headers start -->
<!-- http://www.w3.org/TR/WD-http-pep-970526 -->
<rdf:Property rdf:about="&http-ns;c-pep">
<rdfs:label xml:lang="en">C-PEP</rdfs:label>
<rdfs:comment xml:lang="en">The C-PEP header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;c-pep-info">
<rdfs:label xml:lang="en">C-PEP-Info</rdfs:label>
<rdfs:comment xml:lang="en">The C-PEP-Info header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;pep">
<rdfs:label xml:lang="en">PEP</rdfs:label>
<rdfs:comment xml:lang="en">The PEP header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;pep-info">
<rdfs:label xml:lang="en">Pep-Info</rdfs:label>
<rdfs:comment xml:lang="en">The Pep-Info header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- PEP headers end -->
<!-- PICSLabels headers start -->
<!-- http://www.w3.org/TR/WD-http-pep-960820 -->
<!-- http://www.w3.org/TR/REC-PICS-labels-961031 -->
<rdf:Property rdf:about="&http-ns;pics-label">
<rdfs:label xml:lang="en">PICS-Label</rdfs:label>
<rdfs:comment xml:lang="en">The PICS-Label header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;protocol">
<rdfs:label xml:lang="en">Protocol</rdfs:label>
<rdfs:comment xml:lang="en">The Protocol header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;protocol-request">
<rdfs:label xml:lang="en">Protocol-Request</rdfs:label>
<rdfs:comment xml:lang="en">The Protocol-Request
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- PICSLabels headers end -->
<!-- Proxy Notification headers start -->
<!-- http://www.w3.org/TR/WD-proxy-960221 -->
<rdf:Property rdf:about="&http-ns;proxy-features">
<rdfs:label xml:lang="en">Proxy-Features</rdfs:label>
<rdfs:comment xml:lang="en">The Proxy-Features
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;proxy-instruction">
<rdfs:label xml:lang="en">Proxy-Instruction</rdfs:label>
<rdfs:comment xml:lang="en">The Proxy-Instruction
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- Proxy Notification headers end -->
<!-- Selecting Payment Mechanisms headers start -->
<!-- http://www.w3.org/TR/WD-http-pep-960820 -->
<!-- http://www.w3.org/TR/NOTE-jepi-970519 -->
<rdf:Property rdf:about="&http-ns;protocol-info">
<rdfs:label xml:lang="en">Protocol-Info</rdfs:label>
<rdfs:comment xml:lang="en">The Protocol-Info
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;protocol-query">
<rdfs:label xml:lang="en">Protocol-Query</rdfs:label>
<rdfs:comment xml:lang="en">The Protocol-Query
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- Selecting Payment Mechanisms headers end -->
<!-- SOAP headers start -->
<!-- http://www.w3.org/TR/2000/NOTE-SOAP-20000508 -->
<rdf:Property rdf:about="&http-ns;soapaction">
<rdfs:label xml:lang="en">SoapAction</rdfs:label>
<rdfs:comment xml:lang="en">The SoapAction header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<!-- SOAP headers end -->
<!-- UA Attributes headers start -->
<!--
http://www.watersprings.org/pub/id/draft-mutz-http-attributes-00.txt
-->
<rdf:Property rdf:about="&http-ns;ua-color">
<rdfs:label xml:lang="en">UA-Color</rdfs:label>
<rdfs:comment xml:lang="en">The UA-Color header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;ua-media">
<rdfs:label xml:lang="en">UA-Media</rdfs:label>
<rdfs:comment xml:lang="en">The UA-Media header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;ua-pixels">
<rdfs:label xml:lang="en">UA-Pixels</rdfs:label>
<rdfs:comment xml:lang="en">The UA-Pixels header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;ua-resolution">
<rdfs:label xml:lang="en">UA-Resolution</rdfs:label>
<rdfs:comment xml:lang="en">The UA-Resolution
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;ua-windowpixels">
<rdfs:label xml:lang="en">UA-Windowpixels</rdfs:label>
<rdfs:comment xml:lang="en">The UA-Windowpixels
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<!-- UA Attributes headers end -->
<!-- WIRE headers start -->
<!--
http://www.ietf.org/proceedings/98dec/I-D/draft-girod-w3-id-res-ext-00.txt
-->
<rdf:Property rdf:about="&http-ns;optional">
<rdfs:label xml:lang="en">Optional</rdfs:label>
<rdfs:comment xml:lang="en">The Optional header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;resolution-hint">
<rdfs:label xml:lang="en">Resolution-Hint</rdfs:label>
<rdfs:comment xml:lang="en">The Resolution-Hint
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Request"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;resolver-location">
<rdfs:label xml:lang="en">Resolver-Location</rdfs:label>
<rdfs:comment xml:lang="en">The Resolver-Location
header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:domain rdf:resource="&http-ns;Response"/>
</rdf:Property>
<!-- WIRE headers end -->
<!-- additional headers start -->
<rdf:Property rdf:about="&http-ns;additionalHeader">
<rdfs:label xml:lang="en">Additional header</rdfs:label>
<rdfs:comment xml:lang="en">Has an additional header</rdfs:comment>
<rdfs:subPropertyOf rdf:resource="&http-ns;header"/>
<rdfs:range rdf:resource="&http-ns;MessageHeader"/>
</rdf:Property>
<rdfs:Class rdf:about="&http-ns;MessageHeader">
<rdfs:label xml:lang="en">Message header</rdfs:label>
<rdfs:comment xml:lang="en">A message header according to section 4.2 of HTTP 1.1</rdfs:comment>
<rdfs:subClassOf rdf:parseType="Collection">
<owl:Restriction>
<owl:onProperty rdf:resource="&http-ns;fieldName"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="&http-ns;fieldValue"/>
<owl:minCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:minCardinality>
<owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#nonNegativeInteger">1</owl:maxCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</rdfs:Class>
<rdf:Property rdf:about="&http-ns;fieldName">
<rdfs:label xml:lang="en">Field name</rdfs:label>
<rdfs:comment xml:lang="en">Has a field name</rdfs:comment>
<rdfs:domain rdf:resource="&http-ns;MessageHeader"/>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;fieldValue">
<rdfs:label xml:lang="en">Field value</rdfs:label>
<rdfs:comment xml:lang="en">Has a field value</rdfs:comment>
<rdfs:domain rdf:resource="&http-ns;MessageHeader"/>
</rdf:Property>
<!-- additional headers end -->
<rdf:Property rdf:about="&http-ns;version">
<rdfs:label xml:lang="en">Version</rdfs:label>
<rdfs:comment xml:lang="en">The HTTP version</rdfs:comment>
</rdf:Property>
<rdf:Property rdf:about="&http-ns;body">
<rdfs:label xml:lang="en">Entity body</rdfs:label>
<rdfs:comment xml:lang="en">The HTTP entity body</rdfs:comment>
</rdf:Property>
</rdf:RDF>]]>
The serialization of HTTP messages in RDF format brings about a significant limitation regarding the order of header information. According to the RDF model, the order in which properties are serialized is not relevant. However, the order in which HTTP headers are exchanged between the client and the server can be significant. For example the following sequence of headers describes a specific content encoding, namely "compress" after "gzip":
content-encoding: gzipcontent-encoding: compress
To keep the schema defined by this document simple, sequences of HTTP headers of the same type MUST be serialized in a single RDF property using a comma separated string as defined by [RFC 2616]. The order of the individual header values MUST reflect the order in which they were exchanged. For example, the sequence of headers from above must be represented in the following way:
<http:content-encoding>gzip, compress</http:content-encoding>
Editor's Note: are there cases in which the order of different header types can be significant? The working group has not identified any such restrictions.
There are also noteable schema limitations with regards to security and privacy since the content recorded by this vocabulary could potentially contain sensitive information. For example authentication information in HTTP headers or other information (login user name, passwords, etc.) within the body of the message. Since the schema of this document is limited to terms defined by the HTTP vocabulary, security and privacy considerations need to be made at the application level. For example, certain parts of the data may be restricted to appropriate user permissions or obfuscated.
The following terms are defined by this specification:
Classes in the HTTP namespace
| Class name |
Label |
Allowable types |
Suggested types |
Required properties |
Optional properties |
http:Connection |
Connection |
|
|
http:connectionAuthority |
http:request |
http:Request |
Request |
|
http:OptionsRequest,
http:GetRequest,
http:HeadRequest,
http:PostRequest,
http:PutRequest,
http:DeleteRequest,
http:TraceRequest,
http:ConnectRequest |
|
http:requestURI,
http:version,
http:header,
http:body,
http:response |
http:RequestURI |
Request URI |
http:asterisk, http:Literal |
|
|
|
http:Response |
Response |
|
|
|
http:responseCode,
http:version,
http:header,
http:body |
http:ResponseCode |
Response Code |
http:100,
http:101,
http:200,
http:201,
http:202,
http:203,
http:204,
http:205,
http:206,
http:300,
http:301,
http:302,
http:303,
http:304,
http:305,
http:306,
http:307,
http:400,
http:401,
http:402,
http:403,
http:404,
http:405,
http:406,
http:407,
http:408,
http:409,
http:410,
http:411,
http:412,
http:413,
http:414,
http:415,
http:416,
http:417,
http:500,
http:501,
http:502,
http:503,
http:504,
http:505 |
|
|
|
The following example shows an RDF/XML representation of an HTTP request and response pair.
A client requests a resource in the document root (/foo/bar) at www.example.org port 80 via HTTP 1.1. With the request, it sends request headers. The server uses content negotiation. Some of the request headers (accept and accept-language) are relevant for the creation or choice of the result as indicated by the vary reponse header. Thus, at least these request headers are recorded in the representation of the request. In addition to the content-type and vary headers, the server sends an unknown header (x-foo) which appears as a Message Header. The body property contains the result as an XML literal.
<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:http="http://www.w3.org/2006/http#">
<http:Connection rdf:ID="conn">
<http:connectionAuthority>www.example.org:80</http:connectionAuthority>
<http:request rdf:resource="#req0"/>
<http:request rdf:resource="#req1"/>
</http:Connection>
<http:GetRequest rdf:ID="req0">
<http:abs_path>/foo/bar</http:abs_path>
<http:version>1.1</http:version>
<http:accept>text/html;q=1.0, application/xml;q=0.9, */*;q=0.01</http:accept>
<http:accept-language>de-DE;q=1.0, de;q=0.75, en-GB;q=0.5,
en;q=0.25, *;q=0.01</http:accept-language>
<http:response rdf:resource="#resp0"/>
</http:GetRequest>
<http:GetRequest rdf:ID="req1">
<http:abs_path>/images/foo.png</http:abs_path>
<http:version>1.1</http:version>
<http:accept>image/png;q=1.0, image/jpeg;q=0.9, */*;q=0.01</http:accept>
<http:response rdf:resource="#resp1"/>
</http:GetRequest>
<http:Response rdf:ID="resp0">
<http:responseCode rdf:resource="http://www.w3.org/2006/http#200"/>
<http:version>1.1</http:version>
<http:content-type>application/xhtml+xml;charset=utf-8</http:content-type>
<http:vary>accept, accept-language</http:vary>
<http:additionalHeader>
<http:MessageHeader rdf:ID="addH0">
<http:fieldName>x-foo</http:fieldName>
<http:fieldValue>bar</http:fieldValue>
</http:MessageHeader>
</http:additionalHeader>
<http:body rdf:parseType="Literal">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Hello World!</title>
</head>
<body>
<p>Hello World!
<img src="/images/foo.png" alt="foo" /></p>
</body>
</html>
</http:body>
</http:Response>
<http:Response rdf:ID="resp1">
<http:responseCode rdf:resource="http://www.w3.org/2006/http#200"/>
<http:version>1.1</http:version>
<http:content-type>image/png</http:content-type>
<http:body rdf:resource="data:base64,vjbo38g53oguo3w82ghin24oz284hhghlw"/>
</http:Response>
</rdf:RDF>
The following is a list of changes since the 20 December, 2006 Working Draft:
- added a wrapper
http:Connection class to describe the actual TCP connection
- added
http:response property to the request class to relate responses
- dropped URI property (and namespace) in favor of a requestURI property
- dropped references to RFC 822 (not needed for the scope of this work)
- added pre-defined constant values for the
http:responseCode property
- added list of terms that describe the classes, properties, and values in the schema
- changed the usage of the body property to allow any type of data (using an algorithm)
- [DRP]
- "The HTTP Distribution and
Replication Protocol" – Arthur van Hoff, John Giannandrea, Mark Hapner, Steve
Carter, Milo Medin, W3C Member Submission, 25 August 1997.
- [DupSup]
- "Duplicate
Suppression in HTTP" – Jeffrey Mogul, Arthur van Hoff, IETF Internet-Draft, 15
April 1998.
- [EARL Schema]
- "Evaluation and
Report Language (EARL) 1.0 Schema" – Charles McCathieNevile, Shadi Abou-Zahra,
W3C Editors' Working Draft 01 January 2006.
- [EDD]
- "An
exploration of dynamic documents" – Netscape, 1999.
- [EdgeArch]
- "Edge Architecture
Specification" – Mark Nottingham, Xiang Liu, W3C Note, 04 August 2001.
- [HTML4]
- "HTML 4.01
Specification" – Dave Raggett, Arnaud Le Hors, Ian Jacobs, W3C Recommendation,
24 December 1999.
- [JEPI]
- "White Paper: Joint Electronic
Payment Initiative" – Eui-Suk Chung, Daniel Dardailler, W3C NOTE, 19 May
1997.
- "Object Header
lines in HTTP" – T. Berners-Lee, May 1994.
- [OPS-OverHTTP]
- "Implementation of OPS Over
HTTP" – Pat Hensley, Max Metral, Upendra Shardanand, Donna Converse, Mike
Myers, W3C Member Submission, 02 June 1997.
- [OPTIONS
messages]
- "Specification
of HTTP/1.1 OPTIONS messages" – J. Mogul, J. Cohen, S. Lawrence, IETF
Internet-Draft, 26 August 1997.
- [P3P]
- "The Platform for
Privacy Preferences 1.0 (P3P1.0) Specification" – Lorrie Cranor, Marc
Langheinrich, Massimo Marchiori, Martin Presler-Marshall, Joseph Reagle, W3C
Recommendation, 16 April 2002.
- [PEP]
- "PEP - an Extension
Mechanism for HTTP" – Henrik Frystyk Nielsen, Dan Connolly, Rohit Khare, Eric
Prud'hommeaux, W3C Working Draft, 21 November 1997.
- [PICSLabels]
- "PICS Label Distribution
Label Syntax and Communication Protocols, Version 1.1" – Tim Krauskopf, Jim
Miller, Paul Resnick, Win Treese, W3C Recommendation, 31 October 1996.
- [Proxy
Notification]
- "Notification for Proxy
Caches" – Phillip M. Hallam-Baker, W3C Working Draft, 21 February 1996.
- [RDF]
- "Resource Description Framework
(RDF): Concepts and Abstract Syntax" – Graham Klyne, Jeremy J. Carroll, W3C
Recommendation, 10 February 2004.
- [RDF-PRIMER]
- RDF Primer – Frank Manola,
Eric Miller (eds.). W3C Recommendation, 10 February 2004.
- [RFC2068]
- "Hypertext Transfer Protocol --
HTTP/1.1" – R. Fielding, J. Gettys, J. Mogul, H. Frystyk, T. Berners-Lee,
January 1997.
- [RFC2109]
- "HTTP State Management
Mechanism" – D. Kristol, L. Montulli, February 1997.
- [RFC2183]
- "Communicating Presentation
Information in Internet Messages: The Content-Disposition Header Field" – R.
Troost, S. Dorner, K. Moore, August 1997.
- [RFC2227]
- "Simple Hit-Metering and
Usage-Limiting for HTTP" – J. Mogul, P. Leach, October 1997.
- [RFC2295]
- "Transparent Content Negotiation
in HTTP" – K. Holtman, A. Mutz, March 1998.
- [RFC2310]
- "The Safe Response Header
Field" – K. Holtman, April 1998.
- [RFC2324]
- "Hyper Text Coffee Pot Control
Protocol (HTCPCP/1.0)" – L. Masinter, 1 April 1998.
- [RFC2397]
- "The 'data' URL scheme" – L. Masinter, August 1998.
- [RFC2518]
- "HTTP Extensions for Distributed
Authoring -- WEBDAV" – Y. Goland, E. Whitehead, A. Faizi, S. Carter, D.
Jensen, February 1999.
- [RFC2616]
- "Hypertext Transfer Protocol --
HTTP/1.1" – R. Fielding, J. Gettys, J. Mogul, H. Frystyk Nielsen, L. Masinter,
P. Leach and T. Berners-Lee, June 1999.
- [RFC2617]
- "HTTP Authentication: Basic and
Digest Access Authentication" – J. Franks, P. Hallam-Baker, J. Hostetler, S.
Lawrence, P. Leach, A. Luotonen, L. Stewart, June 1999.
- [RFC2660]
- "The Secure HyperText Transfer
Protocol" – E. Rescorla, A. Schiffman, August 1999.
- [RFC2774]
- "An HTTP Extension
Framework" – H. Nielsen, P. Leach, S. Lawrence, February 2000.
- [RFC2965]
- "HTTP State Management
Mechanism" – D. Kristol, L. Montulli, October 2000.
- [RFC3229]
- "Delta encoding in HTTP" –
J. Mogul, B. Krishnamurthy, F. Douglis, A. Feldmann, Y. Goland, A. van Hoff, D.
Hellerstein, January 2002.
- [RFC3230]
- "Instance Digests in HTTP" –
J. Mogul, A. van Hoff, January 2002.
- [RFC3253]
- "Versioning Extensions to WebDAV
(Web Distributed Authoring and Versioning)" – G. Clemm, J. Amsden, T. Ellison,
C. Kaler, J. Whitehead, March 2002.
- [RFC3648]
- "Web Distributed Authoring and
Versioning (WebDAV) Ordered Collections Protocol" – J. Whitehead, J. Reschke,
Ed., December 2003.
- [RFC3986]
- "Uniform Resource Identifier
(URI): Generic Syntax" – T. Berners-Lee, R. Fielding, L. Masinter, January
2005.
- [RFC4229]
- "HTTP Header Field
Registrations" – M. Nottingham, J. Mogul. December 2005.
- [SOAP1.1]
- "Simple Object Access
Protocol (SOAP) 1.1" – Don Box, David Ehnebuske, Gopal Kakivaya, Andrew
Layman, Noah Mendelsohn, Henrik Frystyk Nielsen, Satish Thatte, Dave Winer, W3C
Note, 08 May 2000.
- [UA Attributes]
- "User-Agent
Display Attributes Headers" – A. Mutz, L. Montulli, L. Masinter, IETF
Internet-Draft, 12 June 1996.
- [WCAG]
- @@@TBD@@@
- [WIRE]
- "WIRE
- W3 Identifier Resolution Extensions" – Lewis Girod, Benjie Chen, Henrik
Frystyk, John Mallery, IETF Internet-Draft, 13 March 1998.
