The terms defined by this document are also provided in RDF Schema format.
Copyright © 2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
The identification of resources on the Web by a Uniform Resource Identifier(URI) alone may not be sufficient, 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 W3C Evaluation And Report Language (EARL). This document provides a representation of the HTTP vocabulary in the Resource Description Framework (RDF), to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by RFC 2616, as well as additional HTTP headers registered by the Internet Assigned Numbers Authority (IANA). These terms can also be used to record HTTPS exchanges.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This Working Draft of the HTTP Vocabulary in RDF document was published on 8 September 2008 by the Evaluation and Repair Tools Working Group (ERT WG). It is an update of the previous HTTP Vocabulary in RDF Working Draft of 23 March 2007, and addresses the comments received since (see history of document changes). This document is part of the W3C Evaluation And Report Language (EARL). It is expected to be the last working draft before publication as a W3C Working Group Note.
[Editor's note: change text appropriately]
The RDF terms defined by this document can be used to extend the Evaluation And Report Language (EARL) 1.0 Schema, but can also be used separately to record an HTTP exchange between a client and a server for any purpose. The Working Group encourages feedback about the approach, as well as about the completeness and maturity of this document by developers and researchers who have interest in a representation of the HTTP vocabulary in RDF format. Feedback from the W3C Quality Assurance Interest Group, the W3C Semantic Web Interest Group, and the Protocol for Web Description Resources Working Group is particularly welcome. Please send comments on this document by @@@ CHANGE @@@29 September 2008 to the public mailing list of the working group public-wai-ert@w3.org. The archives of the working group mailing list are publicly available.
[Editor's note: change date for comments]
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. The group does not expect this document to become a W3C Recommendation. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This document defines a representation of the Hypertext 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 or secure HTTP request and response messages in RDF format, such as by automated Web accessibility evaluation tools that want 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.
Note: The version 1.0 specifies the version of the HTTP Vocabulary in RDF document and not the version of HTTP. The vocabulary defined in this specification is usable for HTTP versions up to 1.1.
[Editor's note: The working group asks for comments about potential confusion because of the versioning.]
This document is not intended to be a clarification or extension of the different concepts of the HTTP specification. The HTTP specification is defined by a series of Request for Comments (RFC) publications and other documentation, including RFC 2616 and RFC 4229. These are listed in Appendix C: References.
Additionally this document assumes the following background knowledge:
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 keywords must, required, recommended, should, may, and optional are used in accordance with [RFC2119].
The RDF representation of the HTTP vocabulary defined by this document uses the namespace http://www.w3.org/2006/http#
. The prefix http
is used throughout this document to denote this namespace. Table 1 presents the namespaces used by this document. The prefix notation presents the typical conventions used in the Web and in this document to denote a given namespace, and can be freely modified. Table 2 presents additional RDF data used by this document.
Namespace prefix | Namespace URI | Description |
---|---|---|
http |
http://www.w3.org/2006/http# |
Namespace for the core terms of HTTP vocabulary in RDF. |
cnt |
http://www.w3.org/2008/content# |
Namespace for Representing Content in RDF [Content-in-RDF]. |
dct |
http://purl.org/dc/terms/ |
Namespace for the Dublin Core Metadata Terms. |
rdf |
http://www.w3.org/1999/02/22-rdf-syntax-ns# |
Namespace for RDF [RDF]. |
URI | Description |
---|---|
http://www.w3.org/2008/http-headers |
HTTP headers as registered by the IANA (see [RFC4229], [Permanent Headers], and [Provisional Headers]). |
http://www.w3.org/2008/http-methods |
HTTP methods for requests. |
http://www.w3.org/2008/http-statusCodes |
HTTP status codes for responses. |
The following (non-exhaustive) list of use cases aims to highlight some of the different usages of the terms provided by this document:
There are also notable 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, and so on) 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.
This section defines RDF classes for the HTTP 1.1 specification according to [RFC2616].
A connection that is used for the HTTP transfer.
Example 2.1: A Connection
resource.
<http:Connection rdf:ID="conn"> <http:connectionAuthority>www.example.org:80</http:connectionAuthority> <http:requests rdf:parseType="Collection"> <http:Request rdf:ID="req0"/> <http:Request rdf:ID="req1"/> </http:requests> </http:Connection>
An HTTP message.
It may be appropriate to provide additional information about the Message by using the following from external vocabularies:
dct:date
Example 2.2: A Message
resource.
<http:Message rdf:ID="mess0"> <http:httpVersion>1.1</http:httpVersion> <dct:date>2007-09-13</dct:date> <http:headers rdf:parseType="Collection"> <http:MessageHeader rdf:ID="mh0"/> <http:MessageHeader rdf:ID="mh1"/> </http:headers> <http:body> <cnt:Content rdf:ID="cont0"/> </http:body> </http:Message>
There are two subclasses from the http:Message
class: http:Request
and http:Response
.
An HTTP request. The http:Request
class is a subclass of the http:Message
class.
The dct:date
property when used in a Request
resource represents the date the request was sent by the client.
Example 2.3: A Request
resource.
<http:Request rdf:ID="reqs0"> <http:abs_path>/</http:abs_path> <http:methodName>GET</http:methodName> <http:mthd rdf:resource="http://www.w3.org/2008/http-methods#GET"/> <http:resp rdf:resource="#resp0"/> <dct:date>2007-09-13</dct:date> <http:httpVersion>1.1</http:httpVersion> <http:headers rdf:parseType="Collection"> <http:MessageHeader rdf:about="#mh0"/> <http:MessageHeader rdf:about="#mh1"/> </http:headers> </http:Request>
An HTTP response. The http:Response
class is a subclass of the http:Message
class.
The dct:date
property when used in a Response
resource represents the date the response was received by the client.
Example 2.4: A Response
resource.
<http:Response rdf:ID="resp0"> <http:httpVersion>1.1</http:httpVersion> <dct:date>2008-01-11</dct:date> <http:statusCodeNumber>200</http:statusCodeNumber> <http:sc rdf:resource="http://www.w3.org/2008/http-statusCodes#statusCode200"/> <http:headers rdf:parseType="Collection"> <http:MessageHeader rdf:about="#mh2"/> <http:MessageHeader rdf:about="#mh3"/> </http:headers> <http:body> <cnt:Content rdf:ID="cont0"/> </http:body> </http:Response>
A header in an HTTP message.
Example 2.5: A MessageHeader
resource.
<http:MessageHeader rdf:ID="mh0"> <http:fieldValue>text/html, image/png, image/gif;q=0.8</http:fieldValue> <http:fieldName>Accept</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#accept"/> <http:headerElements rdf:parseType="Collection"> <http:HeaderElement rdf:about="#he0"/> <http:HeaderElement rdf:about="#he1"/> <http:HeaderElement rdf:about="#he2"/> </http:headerElements> </http:MessageHeader>
An element in a header value, if a Message Header value can be decomposed into several parts.
Example 2.6: A HeaderElement
resource.
<http:HeaderElement rdf:ID="he0"> <http:elementName>image/gif</http:elementName> <http:params rdf:parseType="Collection"> <http:Parameter rdf:ID="param0"/> </http:params> </http:HeaderElement>
A parameter in a Header Element.
Example 2.7: A Parameter
resource.
<http:Parameter rdf:ID="param0"> <http:paramName>q</http:paramName> <http:paramValue>0.8</http:paramValue> </http:Parameter>
The HTTP 1.1 specification defines eight methods: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, CONNECT. The RDF graph available in RDF/XML at http://www.w3.org/2008/http-methods
provides http:Method
resources for each of these to be used as objects for the http:mthd
property. A resource of type http:Method
represents the name of a method used with HTTP.
[HTTP Status Codes] is a registry for status codes too be used in HTTP. The RDF graph available in RDF/XML at http://www.w3.org/2008/http-statusCodes
provides http:StatusCode
resources for each of these to be used as objects for the http:sc
property. A resource of type http:StatusCode
represents a status code.
Header names to be used in HTTP are registered by the IANA (see [RFC4229], [Permanent Headers], and [Provisional Headers]). The RDF graph available in RDF/XML at http://www.w3.org/2008/http-headers
provides http:HeaderName
resources for each of these to be used as objects for the http:hdrName
property. A resource of type http:HeaderName
represents the name of a header used with HTTP.
Properties defined by this document:
This section defines RDF properties for the HTTP 1.1 specification according to [RFC2616].
This property relates a resource object of the type Message
to a resource object of the type cnt:Content
or a subclass thereof to be the Message's entity body as defined in [RFC2616]. HTTP bodies are series of bytes. Thus for the resource object, it is appropriate to point to a cnt:ContentAsBase64
resource (see [Content-in-RDF] for more information on content representations using the Resource Desription Framework (RDF)).
http:Message
cnt:ContentAsBase64
Example 3.1: The entity body of a message.
<http:Message rdf:ID="mess0"> <http:body> <cnt:ContentAsBase64 rdf:ID="cont0-bin"/> </http:body> </http:Message>
Connection authority - server host and port for a connection.
http:Connection
Header element name (Literal).
http:HeaderElement
Header element value (Literal).
http:HeaderElement
Header name (Literal).
http:MessageHeader
Header value (Literal).
http:MessageHeader
HTTP headers sent with the message.
http:Message
Header value elements.
http:MessageHeader
This property relates a resource of type http:MessageHeader
to a resource of type http:HeaderName
.
http:MessageHeader
http:HeaderName
Property representing the HTTP version number as a Literal (the format is 'digit.digit').
http:Message
HTTP method.
http:Request
http:Method
HTTP method name (Literal).
http:Request
Header element parameters.
http:HeaderElement
Parameter name.
http:Parameter
Parameter value.
http:Parameter
Reason phrase sent by the server.
http:Response
HTTP requests sent via the connection.
http:Connection
The request URI as specified in section 5.1.2 of [RFC2616]. This vocabulary defines the following sub-properties:
http:Request
Example 3.2: The use of the requestURI
property.
<http:Request> <http:methodName>OPTIONS</http:methodName> <http:requestURI>*</http:requestURI> ... </http:Request>
Request URI that is an absolute URI.
Conformance Note: The object for this property must be a Literal (absolute URI).
Example 3.3: The use of the absoluteURI
property.
<http:Request> <http:methodName>GET</http:methodName> <http:absoluteURI>http://www.example.org:80/foo/bar</http:absoluteURI> ... </http:Request>
Request URI that is an absolute path.
Conformance Note: The object for this property must be a Literal (absolute path).
Example 3.4: The use of the abs_path
property.
<http:Request> <http:methodName>GET</http:methodName> <http:abs_path>/foo/bar</http:abs_path> ... </http:Request>
Request URI that is an authority.
Conformance Note: The object for this property must be a Literal (host and optional port number).
Example 3.5: The use of the authority
property.
<http:Request> <http:methodName>CONNECT</http:methodName> <http:authority>www.example.org:80</http:authority> ... </http:Request>
This property relates a resource of type http:Request
to a resource of type http:Response
.
http:Request
http:Response
This property relates a resource of type http:Response
to a resource of type http:StatusCode
.
http:Response
http:StatusCode
The status code sent by the server (Literal).
http:Response
This section describes conformance with this HTTP-in-RDF specification. It differentiates between the following entities:
[Editor's note: The working group asks for comments about a more colloquial word for "HTTP-in-RDF Graph".]
Graphs conforming to this HTTP-in-RDF specification must meet the following requirements:
http:connectionAuthority
).http:requests
).http:httpVersion
).http:headers
).http:body
).dct:date ![external link](https://www.w3.org/Icons/tr.png)
).http:methodName
).http:requestURI
).http:mthd
).http:resp
).http:statusCodeNumber
).http:reasonPhrase
).http:sc
).http:fieldName
).http:fieldValue
).http:hdrName
).http:headerElements
).http:elementName
).http:elementValue
).http:params
).http:paramName
).http:paramValue
).headers
property must be an RDF Collection of Message Headers.http:headerElements
property must be an RDF Collection of Header Elements.http:params
property must be an RDF Collection of Parameters.http:requests
property must be an RDF Collection of Requests.cnt:ContentAsBase64 ![external link](https://www.w3.org/Icons/tr.png)
must conform with the respective specification.Producers conforming to this HTTP-in-RDF specification must meet the following requirements:
Consumers conforming to this HTTP-in-RDF specification must meet the following requirements:
The following example shows an RDF/XML representation of an HTTP request and response pair.
A client sends two requests to a server at www.example.org
port 80 via HTTP 1.1 GET. With each request, it sends request headers. The first request is for a resource in the document root (/
), the second for a resource at /image
. While handling the second request the server performs content negotiation respecting the request's Accept
header and so sends a PNG image. This is indicated by the response's Vary
header.
<?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#" xmlns:cnt="http://www.w3.org/2008/content#" xmlns:dct="http://purl.org/dc/terms/"> <http:Connection rdf:ID="conn"> <http:connectionAuthority>www.example.org:80</http:connectionAuthority> <http:requests rdf:parseType="Collection"> <http:Request rdf:about="#req0"/> <http:Request rdf:about="#req1"/> </http:requests> </http:Connection> <http:Request rdf:about="#req0"> <http:httpVersion>1.1</http:httpVersion> <http:methodName>GET</http:methodName> <http:mthd rdf:resource="http://www.w3.org/2008/http-methods#GET"/> <http:abs_path>/</http:abs_path> <http:headers rdf:parseType="Collection"> <http:MessageHeader> <http:fieldName>Host</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#host"/> <http:fieldValue>www.example.org</http:fieldValue> </http:MessageHeader> <http:MessageHeader> <http:fieldName>User-Agent</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#user-agent"/> <http:fieldValue>My User Agent</http:fieldValue> </http:MessageHeader> <http:MessageHeader> <http:fieldName>Accept</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#accept"/> <http:fieldValue>text/html, image/png, image/gif;q=0.8</http:fieldValue> <http:headerElements rdf:parseType="Collection"> <http:HeaderElement> <http:elementName>text/html</http:elementName> </http:HeaderElement> <http:HeaderElement> <http:elementName>image/png</http:elementName> </http:HeaderElement> <http:HeaderElement> <http:elementName>image/gif</http:elementName> <http:params rdf:parseType="Collection"> <http:Parameter> <http:paramName>q</http:paramName> <http:paramValue>0.8</http:paramValue> </http:Parameter> </http:params> </http:HeaderElement> </http:headerElements> </http:MessageHeader> </http:headers> <http:resp rdf:resource="#resp0"/> </http:Request> <http:Request rdf:about="#req1"> <http:httpVersion>1.1</http:httpVersion> <http:methodName>GET</http:methodName> <http:mthd rdf:resource="http://www.w3.org/2008/http-methods#GET"/> <http:abs_path>/image</http:abs_path> <http:headers rdf:parseType="Collection"> <http:MessageHeader> <http:fieldName>Host</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#host"/> <http:fieldValue>www.example.org</http:fieldValue> </http:MessageHeader> <http:MessageHeader> <http:fieldName>User-Agent</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#user-agent"/> <http:fieldValue>My User Agent</http:fieldValue> </http:MessageHeader> <http:MessageHeader> <http:fieldName>Accept</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#accept"/> <http:fieldValue>image/png, image/gif;q=0.8</http:fieldValue> <http:headerElements rdf:parseType="Collection"> <http:HeaderElement> <http:elementName>image/png</http:elementName> </http:HeaderElement> <http:HeaderElement> <http:elementName>image/gif</http:elementName> <http:params rdf:parseType="Collection"> <http:Parameter> <http:paramName>q</http:paramName> <http:paramValue>0.8</http:paramValue> </http:Parameter> </http:params> </http:HeaderElement> </http:headerElements> </http:MessageHeader> </http:headers> <http:resp rdf:resource="#resp1"/> </http:Request> <http:Response rdf:ID="resp0"> <http:httpVersion>1.1</http:httpVersion> <http:statusCodeNumber>200</http:statusCodeNumber> <http:sc rdf:resource="http://www.w3.org/2008/http-statusCodes#200"/> <http:reasonPhrase>OK</http:reasonPhrase> <http:headers rdf:parseType="Collection"> <http:MessageHeader> <http:fieldName>Date</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#date"/> <http:fieldValue>.......</http:fieldValue> </http:MessageHeader> <http:MessageHeader> <http:fieldName>Content-Type</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#content-type"/> <http:fieldValue>text/html; charset=utf-8</http:fieldValue> <http:headerElements rdf:parseType="Collection"> <http:HeaderElement> <http:elementName>text/html</http:elementName> <http:params rdf:parseType="Collection"> <http:Parameter> <http:paramName>charset</http:paramName> <http:paramValue>utf-8</http:paramValue> </http:Parameter> </http:params> </http:HeaderElement> </http:headerElements> </http:MessageHeader> </http:headers> <http:body> <cnt:ContentAsBase64 rdf:ID="cont0-bin"> <cnt:bytes rdf:datatype="http://www.w3.org/2001/XMLSchema#base64Binary" >ajrq9qguojbglj48z..........</cnt:bytes> </cnt:ContentAsBase64> </http:body> </http:Response> <cnt:XMLContent rdf:ID="cont0-xml"> <dct:source rdf:resource="#cont0-bin"/> <cnt:xmlLeadingMisc rdf:parseType="Literal"><!-- This is the start of the document --> </cnt:xmlLeadingMisc> <cnt:docTypeDecl> <cnt:DocTypeDecl> <cnt:dtdName>html</cnt:dtdName> <cnt:publicId>-//W3C//DTD XHTML 1.0 Strict//EN</cnt:publicId> <cnt:systemId rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI" >http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</cnt:systemId> </cnt:DocTypeDecl> </cnt:docTypeDecl> <cnt:xmlRest rdf:parseType="Literal"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"> <head> <title>My document</title> </head> <body> <p><!-- ...... --></p> </body> </html></cnt:xmlRest> </cnt:XMLContent> <http:Response rdf:ID="resp1"> <http:httpVersion>1.1</http:httpVersion> <http:statusCodeNumber>200</http:statusCodeNumber> <http:sc rdf:resource="http://www.w3.org/2008/http-statusCodes#200"/> <http:reasonPhrase>OK</http:reasonPhrase> <http:headers rdf:parseType="Collection"> <http:MessageHeader> <http:fieldName>Date</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#date"/> <http:fieldValue>.......</http:fieldValue> </http:MessageHeader> <http:MessageHeader> <http:fieldName>Content-Type</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#content-type"/> <http:fieldValue>image/png</http:fieldValue> </http:MessageHeader> <http:MessageHeader> <http:fieldName>Vary</http:fieldName> <http:hdrName rdf:resource="http://www.w3.org/2008/http-headers#vary"/> <http:fieldValue>accept</http:fieldValue> <http:headerElements rdf:parseType="Collection"> <http:HeaderElement> <http:elementName>accept</http:elementName> </http:HeaderElement> </http:headerElements> </http:MessageHeader> </http:headers> <http:body> <cnt:ContentAsBase64> <cnt:bytes rdf:datatype="http://www.w3.org/2001/XMLSchema#base64Binary" >qouh3908t38hohfrf..........</cnt:bytes> </cnt:ContentAsBase64> </http:body> </http:Response> </rdf:RDF>
The following terms are defined by this specification:
Class name | Label | Comment | Refinements | Related properties |
---|---|---|---|---|
http:Connection |
Connection | A connection used for HTTP transfer. | - | http:connectionAuthority , http:requests |
http:HeaderElement |
Header Element | A part of a deconstructed header value. | - | http:elementName , http:elementValue , http:params |
http:HeaderName |
Header Name | The header name. | - | |
http:Message |
Message | An HTTP message. | http:Request, http:Response | http:httpVersion , dct:date , http:body , http:headers |
http:MessageHeader |
Message Header | A header in an HTTP message. | - | http:fieldName , http:fieldValue , http:hdrName , http:headerElements |
http:Method |
Method | The HTTP method used for a request. | - | |
http:Parameter |
Parameter | A parameter for a part of a header value | - | http:paramName , http:paramValue |
http:Request |
Request | An HTTP request. | - | http:methodName , http:requestURI , http:mthd , http:resp |
http:Response |
Response | An HTTP response. | - | http:statusCodeNumber , http:reasonPhrase , http:sc |
http:StatusCode |
Status Code | The status code of an HTTP response. | - |
Property name | Label | Comment | Domain | Range |
---|---|---|---|---|
http:body |
Entity body | The entity body of an HTTP message. | http:Message |
cnt:ContentAsBase64 |
http:connectionAuthority |
Connection authority | The authority of a connection used for the HTTP transfer | http:Connection |
RDF Literal |
http:elementName |
Header element name | The name of a header element | http:HeaderElement |
RDF Literal |
http:elementValue |
Header element value | The value of a header element. | http:HeaderElement |
RDF Literal |
http:fieldName |
Field name | The name of an HTTP header field. | http:MessageHeader |
RDF Literal |
http:fieldValue |
Field value | The value of an HTTP header field. | http:MessageHeader |
RDF Literal |
http:headerElements |
Header elements | The deconstructed parts of an HTTP header value. | http:MessageHeader |
Collection of http:HeaderElement |
http:hdrName |
Header name | The name of an HTTP header. | http:MessageHeader |
http:HeaderName |
http:headers |
Headers | The headers in an HTTP message. | http:Message |
Collection of http:MessageHeader |
http:httpVersion |
HTTP Version | The HTTP version of an HTTP message. | http:Message |
RDF Literal |
http:mthd |
Method | The HTTP method used for the HTTP request. | http:Request |
http:Method |
http:methodName |
Method name | The HTTP method name used for the HTTP request. | http:Request |
RDF Literal |
http:paramName |
Parameter name | The name of a parameter in a part of a deconstructed HTTP header value. | http:Parameter |
RDF Literal |
http:params |
Parameters | The parameters in a part of a deconstructed HTTP header value. | http:HeaderElement |
Collection of http:Parameter |
http:paramValue |
Parameter value | The value of a parameter in a part of a deconstructed HTTP header value. | http:Parameter |
RDF Literal |
http:reasonPhrase |
Reason phrase | The reason phrase (status text) of an HTTP response. | http:Response |
RDF Literal |
http:requests |
Requests | The HTTP requests made via a connection. | http:Connection |
Collection of http:Request |
http:requestURI |
Request URI | The request URI of an HTTP request. | http:Request |
RDF Literal |
http:resp |
Response | The HTTP response sent in answer to an HTTP request. | http:Request |
http:Response |
http:sc |
Status code | The status code of an HTTP response. | http:Response |
http:StatusCode |
http:statusCodeNumber |
Status code number | The status code number of an HTTP response. | http:Response |
RDF Literal |
The following is a list of substantial changes since the 8 September 2008 Working Draft:
body
property is allowed for Message
resources; this property relates the message to Base64 encoded message content;headername
(now hdrName
), method
(now mthd
), response
(now resp
), statusCode
(now sc
);asterisk
resource was removed in favour of the use of the Literal "*";StatusCodeGroup
class was removed in favour of sub-classes of StatusCode
;