CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 date: Fri, 01 Aug 2025 14:12:13 GMT content-type: text/html; charset=utf-8 content-location: Overview.html last-modified: Tue, 31 Jan 2017 22:20:04 GMT cache-control: public, max-age=86400 vary: Accept-Encoding,Origin link: ;rel="timegate" access-control-allow-origin: * x-backend: www-mirrors x-request-id: 9685eddb89579dfa strict-transport-security: max-age=15552000; includeSubdomains; preload content-security-policy: frame-ancestors 'self' https://cms.w3.org/ https://cms-dev.w3.org/; upgrade-insecure-requests cf-cache-status: BYPASS set-cookie: __cf_bm=ZkAUWKGygjsr20Zsi9ez8ZaKcPO30JC0x2qmrGYgFfI-1754057533-1.0.1.1-xV0286kHWsxrOJz6k71IsqrCKXLvOVgIfaOZUwhr.a7j2YNCkUuhVtI.eAeq3DKzg83KHQezks3cTybNcFmniyqZ.lJ0XvqGYtiC9ScJU7s; path=/; expires=Fri, 01-Aug-25 14:42:13 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None server: cloudflare cf-ray: 9685eddb89579dfa-BLR content-encoding: gzip alt-svc: h3=":443"; ma=86400 HTTP Vocabulary in RDF 1.0

HTTP Vocabulary in RDF 1.0

W3C Working Group Note 2 February 2017

This version:: https://www.w3.org/TR/2017/NOTE-HTTP-in-RDF10-20170202/
Latest version:: https://www.w3.org/TR/HTTP-in-RDF10/
Previous version:: https://www.w3.org/TR/2011/WD-HTTP-in-RDF10-20110510/
Editors:: Johannes Koch (until November 2010 while at Fraunhofer Institute for Applied Information Technology FIT); Carlos A Velasco, Fraunhofer Institute for Applied Information Technology FIT; Philip Ackermann, Fraunhofer Institute for Applied Information Technology FIT

The terms defined by this document are also provided in RDF Schema format.

Abstract

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.

Status of this Document

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 https://www.w3.org/TR/.

This HTTP Vocabulary in RDF 1.0 is published as a W3C Working Group Note because the Evaluation and Repair Tools Working Group (ERT WG) reached the end of its Charter.

HTTP Vocabulary in RDF 1.0 is a supporting document for the Evaluation and Report Language (EARL) 1.0 Schema but can be used in other contexts too. It is considered to be complete and mature but at this time there are not sufficient implementations to finalize this work.

If you wish to make comments regarding this HTTP Vocabulary in RDF 1.0 document, please send them to public-earl10-comments@w3.org (publicly visible mailing list archive).

Publication as a Working Group Note 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 has been produced by the Evaluation and Repair Tools Working Group (ERT WG) as part of the Web Accessibility Initiative (WAI) Technical Activity.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. 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 is governed by the 1 September 2015 W3C Process Document.

1 Introduction

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 [RFC2616]. 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.

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:

Basic knowledge of the Extensible Markup Language (XML) [XML] and its associated technologies.
Basic knowledge about the Semantic Web and RDF. For references, consult [RDF], [RDFS], [RDF-PRIMER] and [OWL].

The terms defined by this document can be used as part of the W3C Evaluation And Report Language (EARL) and in other contexts too. Developer Guide for Evaluation and Report Language (EARL) 1.0 explains how to implement and use EARL, including conformance requirements for software tools.

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].

1.1 Namespaces

The RDF representation of the HTTP vocabulary defined by this document uses the namespace https://www.w3.org/2011/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.

Table 1: namespaces used by this document.
Namespace prefix	Namespace URI	Description
`http`	`https://www.w3.org/2011/http#`	Namespace for the core terms of HTTP vocabulary in RDF.
`cnt`	`https://www.w3.org/2011/content#`	Namespace for Representing Content in RDF [Content-in-RDF].
`dct`	`https://purl.org/dc/terms/`	Namespace for the Dublin Core Metadata Terms.
`owl`	`https://www.w3.org/2002/07/owl#`	Namespace for OWL [OWL].
`rdf`	`https://www.w3.org/1999/02/22-rdf-syntax-ns#`	Namespace for RDF [RDF].

Table 2: RDF data used by this document.
URI	Description
`https://www.w3.org/2011/http-headers`	HTTP headers as registered by the IANA (see [RFC4229], [Permanent Headers], and [Provisional Headers]).
`https://www.w3.org/2011/http-methods`	HTTP methods for requests.
`https://www.w3.org/2011/http-statusCodes`	HTTP status codes for responses.

1.2 Use Cases

The following (non-exhaustive) list of use cases aims to highlight some of the different usages of the terms provided by this document:

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 exchanged between the server and the client during the testing. Without a record of the exchanged headers, it may not be possible to re-identify the exact resource (or representation of the resource) that has been tested. The terms provided by this document allow quality assurance tools to record the HTTP exchange between a client and a server, for example to record the POST parameters or the headers used during content negotiation. The terms provided by this document can be used in combination with the W3C Evaluation And Report Language (EARL) [EARL].
Precising Conformance Claims: Conformance claims that are made about a Web resource or group of Web resource, are sometimes only applicable under certain constraints. For example, conformance of a Web site to the W3C Web Content Accessibility Guidelines (WCAG) [WCAG], may only be applicable for a certain language of the Web site that is using language negotiation. When providing machine-readable conformance claims, for example using the W3C Protocol for Describing Web Resources (POWDER): Description Resources [POWDER-DR], it is important to precise any such constraints that may apply.
Debugging Web Applications: Web applications using client-side scripting such as AJAX may exchange additional HTTP messages with the server without using a different URI. In order to debug such Web applications, it must be possible to reconstruct the exact history of the states through which the Web application passed. Web authoring tools that are designed to develop and debug Web applications could use the terms provided by this document to record the exact HTTP messages exchanged between a client and a server. This information could be provided to the developer as a log to help debug errors in the Web application.
Indexing Information Resources: When indexing RDF information resources that are available through the HTTP protocol (also called "scuttering" in Semantic Web parlance), it is often useful to record information about the HTTP request and response messages that were exchanged, along with the data for later use. In some instances, different representations of the RDF information may be retrieved from the server depending on the HTTP headers and parameters exchanged. The terms provided by this document can be used to supplement the collected data with the HTTP messages as part of a comprehensive indexing repository.

1.3 Limitations

There are also notable schema limitations in regard 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.

2 Classes

This section defines RDF classes for the HTTP 1.1 specification according to [RFC2616].

2.1 Connection Class

A connection that is used for the HTTP transfer.

Related Properties

Domain of:
- http:connectionAuthority
- http:requests
Range of: none

Class name	Label	Comment	Refinements	Related properties
`http:Connection`	Connection	A connection used for HTTP transfer.	-	`http:connectionAuthority`, `http:requests`
`http:EntityHeader`	Entity Header	An entity header in an HTTP message.	-	`http:fieldName`, `http:fieldValue`, `http:hdrName`, `http:headerElements`
`http:GeneralHeader`	General Header	A general header in an HTTP message.	-	`http:fieldName`, `http:fieldValue`, `http:hdrName`, `http:headerElements`
`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:GeneralHeader, http:RequestHeader, http:ResponseHeader, http:EntityHeader	`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:RequestHeader`	Request Header	A header in an HTTP request message.	-	`http:fieldName`, `http:fieldValue`, `http:hdrName`, `http:headerElements`
`http:Response`	Response	An HTTP response.	-	`http:statusCodeValue`, `http:reasonPhrase`, `http:sc`
`http:ResponseHeader`	Response Header	A general header in an HTTP response message.	-	`http:fieldName`, `http:fieldValue`, `http:hdrName`, `http:headerElements`
`http:StatusCode`	Status Code	The status code of an HTTP response.	-	`http:statusCodeNumber`

Property name	Label	Comment	Domain	Range
`http:absolutePath`	Request URI	Request URI that is an absolute path.	`http:Request`	RDF Literal
`http:absoluteURI`	Request URI	Request URI that is an absolute URI	`http:Request`	RDF Literal
`http:authority`	Request URI	Request URI that is an authority.	`http:Request`	RDF Literal
`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:hdrName`	Header name	The name of an HTTP header.	`http:MessageHeader`	`http:HeaderName`
`http:headerElements`	Header elements	The deconstructed parts of an HTTP header value.	`http:MessageHeader`	Collection of `http:HeaderElement`
`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:methodName`	Method name	The HTTP method name used for the HTTP request.	`http:Request`	RDF Literal
`http:mthd`	Method	The HTTP method used for the HTTP request.	`http:Request`	`http:Method`
`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 standardized status code number.	`http:StatusCode`	`https://www.w3.org/2001/XMLSchema#int`
`http:statusCodeValue`	Status code value	The status code value of an HTTP response.	`http:Response`	RDF Literal