You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1253 lines
83 KiB
1253 lines
83 KiB
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
|
|
<head>
|
|
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type" />
|
|
<link href="http://www.w3.org/2006/http.rdfs" rel="alternate" type="application/rdf+xml" />
|
|
<title>HTTP Vocabulary in RDF 1.0</title>
|
|
<link rel="stylesheet" type="text/css" href="http://www.w3.org/WAI/ER/EARL10/main" />
|
|
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD" />
|
|
</head>
|
|
|
|
<body>
|
|
<p align="center">[<a href="#contents" rel="contents">contents</a>]</p>
|
|
|
|
<div class="head" id="head"><a href="http://www.w3.org/"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72" /></a>
|
|
<h1><a id="title" name="title"><acronym title="Hyper Text Transfer Protocol">HTTP</acronym> Vocabulary in <acronym title="Resource Description Framework">RDF</acronym> 1.0</a></h1>
|
|
<h2><a id="w3c-doctype" name="w3c-doctype">W3C Working Draft 29 October 2009</a></h2>
|
|
|
|
<dl>
|
|
<dt>This version:</dt>
|
|
<dd><a href="http://www.w3.org/TR/2009/WD-HTTP-in-RDF10-20091029/">http://www.w3.org/TR/2009/WD-HTTP-in-RDF10-20091029/</a></dd>
|
|
<dt>Latest version:</dt>
|
|
<dd><a href="http://www.w3.org/TR/HTTP-in-RDF10/">http://www.w3.org/TR/HTTP-in-RDF10/</a></dd>
|
|
<dt>Previous version:</dt>
|
|
<dd><a href="http://www.w3.org/TR/2008/WD-HTTP-in-RDF-20080908/">http://www.w3.org/TR/2008/WD-HTTP-in-RDF-20080908/</a></dd>
|
|
<dt>Editors:</dt>
|
|
<dd>Johannes Koch, Fraunhofer-Gesellschaft (Fraunhofer Institute for Applied Information Technology FIT)</dd>
|
|
<dd>Carlos A Velasco, Fraunhofer-Gesellschaft (Fraunhofer Institute for Applied Information Technology FIT)</dd>
|
|
</dl>
|
|
<p>The terms defined by this document are also provided in <a href="http://www.w3.org/2006/http.rdfs">RDF Schema</a> format.</p>
|
|
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
|
|
</div>
|
|
<hr />
|
|
|
|
<h2><a id="abstract" name="abstract">Abstract</a></h2>
|
|
<p>The identification of resources on the Web by a Uniform Resource Identifier(<acronym>URI</acronym>) alone may not be sufficient, as other factors such as <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the <a href="http://www.w3.org/WAI/intro/earl.php">W3C Evaluation And Report Language (<acronym>EARL</acronym>)</a>. This document provides a representation of the <acronym>HTTP</acronym> vocabulary in the Resource Description Framework (<acronym>RDF</acronym>), to allow quality assurance tools to record the <acronym>HTTP</acronym> headers that have been exchanged between a client and a server. The <acronym>RDF</acronym> terms defined by this document represent the core <acronym>HTTP</acronym> specification defined by <acronym title="Request for Comments">RFC</acronym> 2616, as well as additional <acronym>HTTP</acronym> headers registered by the Internet Assigned Numbers Authority (<acronym>IANA</acronym>). These terms can also be used to record <acronym title="Secure Hyper Text Transfer Protocol">HTTPS</acronym> exchanges.</p>
|
|
|
|
<div id="sotd">
|
|
<h2><a id="status" name="status">Status of this document</a></h2>
|
|
|
|
<p><em>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 <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
|
|
|
|
<p>This 29 October 2009 Working Draft of <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> Vocabulary in <acronym title="Resource Description Framework">RDF</acronym> 1.0 is an update of the previous <a href="http://www.w3.org/TR/2008/WD-HTTP-in-RDF-20080908/"><acronym>HTTP</acronym> Vocabulary in <acronym>RDF</acronym> Working Draft of 8 September 2008</a>, and addresses the comments received since (see history of <a href="#changes">document changes</a>). This document is part of the <a href="http://www.w3.org/WAI/intro/earl.php">W3C Evaluation And Report Language (<acronym>EARL</acronym>)</a> but can be reused in other contexts too. This document is intended to be published and maintained as a W3C Working Group Note after review and refinement.</p>
|
|
|
|
<p>The Evaluation and Repair Tools Working Group (ERT WG) believes to have addressed all issues brought forth through previous Working Draft iterations. The Working Group encourages feedback about this document, <acronym>HTTP</acronym> Vocbulary in <acronym>RDF</acronym> 1.0, by developers and researchers who have interest in software-supported evaluation and validation of Web sites, and by developers and researchers who have interest in Semantic Web technologies for content description, annotation, and adaptation. In particular, the Working Group is looking for final feedback on the proposed classes and properties to help record <acronym>HTTP</acronym> exchanges between clients and servers for any purpose.</p>
|
|
|
|
<p>Please send comments on this <acronym>HTTP</acronym> Vocabulary in <acronym>RDF</acronym> 1.0 document by <strong>30 November 2009</strong> to <a href="mailto:public-earl10-comments@w3.org">public-earl10-comments@w3.org</a> (publicly visible <a href="http://lists.w3.org/Archives/Public/public-earl10-comments/">mailing list archive</a>).</p>
|
|
|
|
<p>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.</p>
|
|
|
|
<p>This document has been produced by the <a href="http://www.w3.org/WAI/ER/">Evaluation and Repair Tools Working Group (ERT WG)</a> as part of the <a href="http://www.w3.org/WAI/Technical/Activity">Web Accessibility Initiative (WAI) Technical Activity</a>.</p>
|
|
|
|
<p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. The group does not expect this document to become a W3C Recommendation. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/32094/status">public list of any patent disclosures</a> 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 <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p>
|
|
|
|
</div><hr />
|
|
<div id="toc">
|
|
<h2><a accesskey="c" id="contents" name="contents">Table of Contents</a></h2>
|
|
<ol>
|
|
<li><a href="#introduction">Introduction</a>
|
|
<ul>
|
|
<li><a href="#namespaces">1.1 Namespaces</a></li>
|
|
<li><a href="#use-cases">1.2 Use Cases</a></li>
|
|
<li><a href="#limitations">1.3 Limitations</a></li>
|
|
</ul>
|
|
</li>
|
|
<li><a href="#classes">Classes</a>
|
|
<ul>
|
|
<li><a href="#ConnectionClass">2.1 Connection Class</a></li>
|
|
<li><a href="#MessageClass">2.2 Message Class</a>
|
|
<ul>
|
|
<li><a href="#RequestClass">2.2.1 Request Class</a></li>
|
|
<li><a href="#ResponseClass">2.2.2 Response Class</a></li>
|
|
</ul></li>
|
|
<li><a href="#MessageHeaderClass">2.3 MessageHeader Class</a></li>
|
|
<li><a href="#HeaderElementClass">2.4 HeaderElement Class</a></li>
|
|
<li><a href="#ParameterClass">2.5 Parameter Class</a></li>
|
|
<li><a href="#MethodClass">2.6 Method Class</a></li>
|
|
<li><a href="#StatusCodeClass">2.7 StatusCode Class</a></li>
|
|
<li><a href="#HeaderNameClass">2.8 HeaderName Class</a></li>
|
|
</ul></li>
|
|
<li><a href="#properties">Properties</a>
|
|
<ul>
|
|
<li><a href="#bodyProperty">3.1 body Property</a></li>
|
|
<li><a href="#connectionAuthorityProperty">3.2 connectionAuthority Property</a></li>
|
|
<li><a href="#elementNameProperty">3.3 elementName Property</a></li>
|
|
<li><a href="#elementValueProperty">3.4 elementValue Property</a></li>
|
|
<li><a href="#fieldNameProperty">3.5 fieldName Property</a></li>
|
|
<li><a href="#fieldValueProperty">3.6 fieldValue Property</a></li>
|
|
<li><a href="#headersProperty">3.7 headers Property</a></li>
|
|
<li><a href="#headerElementsProperty">3.8 headerElements Property</a></li>
|
|
<li><a href="#hdrNameProperty">3.9 hdrName Property</a></li>
|
|
<li><a href="#httpVersionProperty">3.10 httpVersion Property</a></li>
|
|
<li><a href="#mthdProperty">3.11 mthd Property</a></li>
|
|
<li><a href="#methodNameProperty">3.12 methodName Property</a></li>
|
|
<li><a href="#paramsProperty">3.13 params Property</a></li>
|
|
<li><a href="#paramNameProperty">3.14 paramName Property</a></li>
|
|
<li><a href="#paramValueProperty">3.15 paramValue Property</a></li>
|
|
<li><a href="#reasonPhraseProperty">3.16 reasonPhrase Property</a></li>
|
|
<li><a href="#requestsProperty">3.17 requests Property</a></li>
|
|
<li><a href="#requestURIProperty">3.18 requestURI Property</a>
|
|
<ul>
|
|
<li><a href="#absoluteURIProperty">3.18.1 absoluteURI Property</a></li>
|
|
<li><a href="#abs_pathProperty">3.18.2 abs_path Property</a></li>
|
|
<li><a href="#authorityProperty">3.18.3 authority Property</a></li>
|
|
</ul>
|
|
</li>
|
|
<li><a href="#respProperty">3.19 resp Property</a></li>
|
|
<li><a href="#scProperty">3.20 sc Property</a></li>
|
|
<li><a href="#statusCodeNumberProperty">3.21 statusCodeNumber Property</a></li>
|
|
</ul>
|
|
</li>
|
|
<li><a href="#conformance">Conformance</a>
|
|
<ul>
|
|
<li><a href="#graphs">4.1 Conforming HTTP-in-RDF graphs</a></li>
|
|
<li><a href="#producers">4.2 Conforming Producers</a></li>
|
|
<li><a href="#consumers">4.3 Conforming Consumers</a></li>
|
|
</ul>
|
|
</li>
|
|
</ol>
|
|
|
|
<h3><a id="appendices" name="appendices">Appendices</a></h3>
|
|
<ol type="A">
|
|
<li><a href="#example">A practical Example</a></li>
|
|
<li><a href="#terms">Terms</a></li>
|
|
<li><a href="#references">References</a></li>
|
|
<li><a href="#changes">Document Changes</a></li>
|
|
</ol>
|
|
</div>
|
|
<!-- end toc -->
|
|
|
|
<hr />
|
|
<h2><a id="introduction" name="introduction">1 Introduction</a></h2>
|
|
<p>This document defines a representation of the Hypertext Transfer Protocol (<acronym>HTTP</acronym>) using the Resource Description Framework (<acronym>RDF</acronym>). It defines a collection of <acronym>RDF</acronym> classes and properties that represent the <acronym>HTTP</acronym> vocabulary as defined by the <acronym>HTTP</acronym> specification. These <acronym>RDF</acronym> terms can be used to record <acronym>HTTP</acronym> or secure <acronym>HTTP</acronym> request and response messages in <acronym>RDF</acronym> 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 <a href="#use-cases">1.2 Use Cases</a>.</p>
|
|
<p><strong>Note:</strong> The version 1.0 specifies the version of the <acronym>HTTP</acronym> Vocabulary in <acronym>RDF</acronym> document and <strong>not</strong> the version of <acronym>HTTP</acronym>. The vocabulary defined in this specification is usable for <acronym>HTTP</acronym> versions up to 1.1.</p>
|
|
<p class="note">[Editor's note: The working group asks for comments about potential confusion because of the versioning.]</p>
|
|
<p>This document is not intended to be a clarification or extension of the different concepts of the <acronym>HTTP</acronym> specification. The <acronym>HTTP</acronym> specification is defined by a series of Request for Comments (<acronym>RFC</acronym>) publications and other documentation, including <a href="#ref-rfc2616">RFC 2616</a> and <a href="#ref-rfc4229">RFC 4229</a>. These are listed in <a href="#references">Appendix C: References</a>.</p>
|
|
<p>Additionally this document assumes the following background knowledge:</p>
|
|
<ul>
|
|
<li>Basic knowledge of the Extensible Markup Language (<acronym>XML</acronym>) [<a href="#ref-xml">XML</a>] and its associated technologies.</li>
|
|
<li>Basic knowledge about the Semantic Web and <acronym>RDF</acronym>. For references, consult [<a href="#ref-rdf">RDF</a>], [<a href="#ref-rdf-primer">RDF-PRIMER</a>] and [<a href="#ref-rdfs">RDFS</a>].</li>
|
|
</ul>
|
|
<p>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 <strong>must</strong>, <strong>required</strong>, <strong>recommended</strong>, <strong>should</strong>, <strong>may</strong>, and <strong>optional</strong> are used in accordance with [<a href="#ref-rfc2119">RFC2119</a>].</p>
|
|
|
|
<h3><a id="namespaces" name="namespaces">1.1 Namespaces</a></h3>
|
|
<p>The <acronym title="Resource Description Framework">RDF</acronym> representation of the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> vocabulary defined by this document uses the namespace <code>http://www.w3.org/2006/http#</code>. The prefix <code>http</code> is used throughout this document to denote this namespace. <a href="#tab-ns1">Table 1</a> 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. <a href="#tab-externalResources">Table 2</a> presents additional <acronym>RDF</acronym> data used by this document.</p>
|
|
<table id="tab-ns1">
|
|
<caption>Table 1: namespaces used by this document.</caption>
|
|
<tr>
|
|
<th>Namespace prefix</th>
|
|
<th>Namespace <acronym title="Uniform Resource Identifier">URI</acronym></th>
|
|
<th>Description</th>
|
|
</tr>
|
|
<tr>
|
|
<td><code>http</code></td>
|
|
<td><code>http://www.w3.org/2006/http#</code></td>
|
|
<td>Namespace for the core terms of <acronym>HTTP</acronym> vocabulary in <acronym>RDF</acronym>.</td>
|
|
</tr>
|
|
<tr>
|
|
<td scope="row"><code>cnt</code></td>
|
|
<td><code>http://www.w3.org/2008/content#</code></td>
|
|
<td>Namespace for Representing Content in <acronym>RDF</acronym> [<a href="#ref-content-in-rdf">Content-in-RDF</a>].</td>
|
|
</tr>
|
|
<tr>
|
|
<td scope="row"><code>dct</code></td>
|
|
<td><code>http://purl.org/dc/terms/</code></td>
|
|
<td>Namespace for the Dublin Core Metadata Terms.</td>
|
|
</tr>
|
|
<tr>
|
|
<td scope="row"><code>rdf</code></td>
|
|
<td><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></td>
|
|
<td>Namespace for <acronym>RDF</acronym> [<a href="#ref-rdf">RDF</a>].</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<table id="tab-externalResources">
|
|
<caption>Table 2: <acronym>RDF</acronym> data used by this document.</caption>
|
|
<tr>
|
|
<th><acronym>URI</acronym></th>
|
|
<th>Description</th>
|
|
</tr>
|
|
<tr>
|
|
<td><code>http://www.w3.org/2008/http-headers</code></td>
|
|
<td><acronym>HTTP</acronym> headers as registered by the <acronym title="Internet Assigned Numbers Authority">IANA</acronym> (see [<a href="#ref-rfc4229">RFC4229</a>], [<a href="#ref-permheaders">Permanent Headers</a>], and [<a href="#ref-provheaders">Provisional Headers</a>]).</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>http://www.w3.org/2008/http-methods</code></td>
|
|
<td><acronym>HTTP</acronym> methods for requests.</td>
|
|
</tr>
|
|
<tr>
|
|
<td><code>http://www.w3.org/2008/http-statusCodes</code></td>
|
|
<td><acronym>HTTP</acronym> status codes for responses.</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<h3><a id="use-cases" name="use-cases">1.2 Use Cases</a></h3>
|
|
<p>The following (non-exhaustive) list of use cases aims to highlight some of the different usages of the terms provided by this document:</p>
|
|
<dl>
|
|
<dt><a id="use-case1" name="use-case1">Reporting Test Results</a></dt>
|
|
<dd>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 <acronym title="Hypertext Transfer Protocol">HTTP</acronym> 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 <acronym title="World Wide Web Consortium">W3C</acronym> Evaluation And Report Language (<acronym>EARL</acronym>) [<a href="#ref-earl">EARL</a>].</dd>
|
|
<dt><a id="use-case2" name="use-case2">Precising Conformance Claims</a></dt>
|
|
<dd>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 (<acronym>WCAG</acronym>) [<a href="#ref-wcag">WCAG</a>], may only be applicable for a certain language of the Web site that is using language negotiation. When provding machine-readable conformance claims, for example using the W3C Protocol for Describing Web Resources (POWDER): Description Resources [<a href="#ref-powder-dr">POWDER-DR</a>], it is important to precise any such constraints that may apply.</dd>
|
|
<dt><a id="use-case3" name="use-case3">Debugging Web Applications</a></dt>
|
|
<dd>Web applications using client-side scripting such as <acronym title="Asynchronous JavaScript and XML">AJAX</acronym> may exchange additional <acronym>HTTP</acronym> messages with the server without using a different <acronym>URI</acronym>. 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 <acronym>HTTP</acronym> messages exchanged bewteen a client and a server. This information could be provided to the developer as a log to help debug errors in the Web application..</dd>
|
|
<dt><a id="use-case4" name="use-case4">Indexing Information Resources</a></dt>
|
|
<dd>When indexing <acronym>RDF</acronym> information resources that are available through the <acronym>HTTP</acronym> protocol (also called "scuttering" in Semantic Web parlance), it is often useful to record information about the <acronym>HTTP</acronym> request and response messages that were exchanged, along with the data for later use. In some instances, different representations of the <acronym>RDF</acronym> information may be retrieved from the server depending on the <acronym>HTTP</acronym> headers and paramters exchanged. The terms provided by this document can be used to supplement the collected data with the <acronym>HTTP</acronym> messages as part of a comprehensive indexing repository.</dd>
|
|
</dl>
|
|
|
|
<h3><a id="limitations" name="limitations">1.3 Limitations</a></h3>
|
|
<p>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 <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> 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 <acronym>HTTP</acronym> 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.</p>
|
|
|
|
|
|
<h2><a id="classes" name="classes">2 Classes</a></h2>
|
|
<p>This section defines <acronym title="Resource Description Framework">RDF</acronym> classes for the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> 1.1 specification according to [<a href="#ref-rfc2616">RFC2616</a>].</p>
|
|
|
|
<h3><a id="ConnectionClass" name="ConnectionClass">2.1 Connection Class</a></h3>
|
|
<p>A connection that is used for the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> transfer.</p>
|
|
<h4><a id="ConnectionClassProperties" name="ConnectionClassProperties">Related Properties</a></h4>
|
|
<ul>
|
|
<li>Domain of:
|
|
<ul>
|
|
<li><a href="#connectionAuthorityProperty"><code>http:connectionAuthority</code></a></li>
|
|
<li><a href="#requestsProperty"><code>http:requests</code></a></li>
|
|
</ul></li>
|
|
<li>Range of: none</li>
|
|
</ul>
|
|
<h4><a id="ConnectionClassExamples" name="ConnectionClassExamples">Examples</a></h4>
|
|
<div class="example">
|
|
<p><strong>Example 2.1:</strong> A <code>Connection</code> resource.</p>
|
|
<pre><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></pre>
|
|
</div>
|
|
|
|
<h3><a id="MessageClass" name="MessageClass">2.2 Message Class</a></h3>
|
|
<p>An <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> message.</p>
|
|
<h4><a id="MessageClassProperties" name="MessageClassProperties">Related Properties</a></h4>
|
|
<ul>
|
|
<li>Domain of:
|
|
<ul>
|
|
<li><a href="#httpVersionProperty"><code>http:httpVersion</code></a></li>
|
|
<li><a href="#headersProperty"><code>http:headers</code></a></li>
|
|
<li><a href="#bodyProperty"><code>http:body</code></a></li>
|
|
</ul></li>
|
|
<li>Range of: none</li>
|
|
</ul>
|
|
<p>It may be appropriate to provide additional information about the Message by using the following from external vocabularies:</p>
|
|
<dl>
|
|
<dt><a href="http://dublincore.org/documents/dcmi-terms/#terms-date"><code>dct:date</code> <img src="http://www.w3.org/Icons/tr.png" alt="external link"/></a></dt>
|
|
<dd>Message date (see the usage of this property in <a href="#dateReq">requests</a> and <a href="#dateResp">responses</a>).</dd>
|
|
</dl>
|
|
<h4><a id="MessageClassExamples" name="MessageClassExamples">Examples</a></h4>
|
|
<div class="example">
|
|
<p><strong>Example 2.2:</strong> A <code>Message</code> resource.</p>
|
|
<pre><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></pre>
|
|
</div>
|
|
<p>There are two subclasses from the <code>http:Message</code> class: <a href="#RequestClass"><code>http:Request</code></a> and <a href="#ResponseClass"><code>http:Response</code></a>.</p>
|
|
|
|
<h4><a id="RequestClass" name="RequestClass">2.2.1 Request Class</a></h4>
|
|
<p>An <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> request. The <code>http:Request</code> class is a subclass of the <a href="#MessageClass"><code>http:Message</code></a> class.</p>
|
|
<h5><a id="RequestClassProperties" name="RequestClassProperties">Related Properties</a></h5>
|
|
<ul>
|
|
<li>Domain of:
|
|
<ul>
|
|
<li><a href="#methodNameProperty"><code>http:methodName</code></a></li>
|
|
<li><a href="#mthdProperty"><code>http:mthd</code></a></li>
|
|
<li><a href="#requestURIProperty"><code>http:requestURI</code></a></li>
|
|
<li><a href="#respProperty"><code>http:resp</code></a></li>
|
|
</ul></li>
|
|
<li>Range of: none</li>
|
|
</ul>
|
|
<p><a id="dateReq" name="dateReq">The <code>dct:date</code> property</a> when used in a <code>Request</code> resource represents the date the request was <strong>sent</strong> by the client.</p>
|
|
<h5><a id="RequestClassExamples" name="RequestClassExamples">Examples</a></h5>
|
|
<div class="example">
|
|
<p><strong>Example 2.3:</strong> A <code>Request</code> resource.</p>
|
|
<pre><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></pre>
|
|
</div>
|
|
|
|
<h4><a id="ResponseClass" name="ResponseClass">2.2.2 Response Class</a></h4>
|
|
<p>An <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> response. The <code>http:Response</code> class is a subclass of the <a href="#MessageClass"><code>http:Message</code></a> class.</p>
|
|
<h5><a id="ResponseClassProperties" name="ResponseClassProperties">Related Properties</a></h5>
|
|
<ul>
|
|
<li>Domain of:
|
|
<ul>
|
|
<li><a href="#statusCodeNumberProperty"><code>http:statusCodeNumber</code></a></li>
|
|
<li><a href="#scProperty"><code>http:sc</code></a></li>
|
|
<li><a href="#reasonPhraseProperty"><code>http:reasonPhrase</code></a></li>
|
|
</ul></li>
|
|
<li>Range of:
|
|
<ul>
|
|
<li><a href="#respProperty"><code>http:resp</code></a></li>
|
|
</ul></li>
|
|
</ul>
|
|
<p><a id="dateResp" name="dateResp">The <code>dct:date</code> property</a> when used in a <code>Response</code> resource represents the date the response was <strong>received</strong> by the client.</p>
|
|
<h5><a id="ResponseClassExamples" name="ResponseClassExamples">Examples</a></h5>
|
|
<div class="example">
|
|
<p><strong>Example 2.4:</strong> A <code>Response</code> resource.</p>
|
|
<pre><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></pre>
|
|
</div>
|
|
|
|
<h3><a id="MessageHeaderClass" name="MessageHeaderClass">2.3 MessageHeader Class</a></h3>
|
|
<p>A header in an <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> message.</p>
|
|
<h4><a id="MessageHeaderClassProperties" name="MessageHeaderClassProperties">Related Properties</a></h4>
|
|
<ul>
|
|
<li>Domain of:
|
|
<ul>
|
|
<li><a href="#fieldNameProperty"><code>http:fieldName</code></a></li>
|
|
<li><a href="#hdrNameProperty"><code>http:hdrName</code></a></li>
|
|
<li><a href="#fieldValueProperty"><code>http:fieldValue</code></a></li>
|
|
<li><a href="#headerElementsProperty"><code>http:headerElements</code></a></li>
|
|
</ul></li>
|
|
<li>Range of: none</li>
|
|
</ul>
|
|
<h4><a id="MessageHeaderClassExamples" name="MessageHeaderClassExamples">Examples</a></h4>
|
|
<div class="example">
|
|
<p><strong>Example 2.5:</strong> A <code>MessageHeader</code> resource.</p>
|
|
<pre><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></pre>
|
|
</div>
|
|
|
|
<h3><a id="HeaderElementClass" name="HeaderElementClass">2.4 HeaderElement Class</a></h3>
|
|
<p>An element in a header value, if a <a href="#MessageHeaderClass">Message Header</a> value can be decomposed into several parts.</p>
|
|
<h4><a id="HeaderElementClassProperties" name="HeaderElementClassProperties">Related Properties</a></h4>
|
|
<ul>
|
|
<li>Domain of:
|
|
<ul>
|
|
<li><a href="#elementNameProperty"><code>http:elementName</code></a></li>
|
|
<li><a href="#elementValueProperty"><code>http:elementValue</code></a></li>
|
|
<li><a href="#paramsProperty"><code>http:params</code></a></li>
|
|
</ul></li>
|
|
<li>Range of: none</li>
|
|
</ul>
|
|
<h4><a id="HeaderElementClassExamples" name="HeaderElementClassExamples">Examples</a></h4>
|
|
<div class="example">
|
|
<p><strong>Example 2.6:</strong> A <code>HeaderElement</code> resource.</p>
|
|
<pre><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></pre>
|
|
</div>
|
|
|
|
<h3><a id="ParameterClass" name="ParameterClass">2.5 Parameter Class</a></h3>
|
|
<p>A parameter in a <a href="#HeaderElementClass">Header Element</a>.</p>
|
|
<h4><a id="ParameterClassProperties" name="ParameterClassProperties">Related Properties</a></h4>
|
|
<ul>
|
|
<li>Domain of:
|
|
<ul>
|
|
<li><a href="#paramNameProperty"><code>http:paramName</code></a></li>
|
|
<li><a href="#paramValueProperty"><code>http:paramValue</code></a></li>
|
|
</ul></li>
|
|
<li>Range of: none</li>
|
|
</ul>
|
|
<h4><a id="ParameterClassExamples" name="ParameterClassExamples">Examples</a></h4>
|
|
<div class="example">
|
|
<p><strong>Example 2.7:</strong> A <code>Parameter</code> resource.</p>
|
|
<pre><http:Parameter rdf:ID="param0">
|
|
<http:paramName>q</http:paramName>
|
|
<http:paramValue>0.8</http:paramValue>
|
|
</http:Parameter></pre>
|
|
</div>
|
|
|
|
<h3><a id="MethodClass" name="MethodClass">2.6 Method Class</a></h3>
|
|
<p>The <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> 1.1 specification defines eight methods: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, CONNECT. The <acronym title="Resource Description Framework">RDF</acronym> graph available in <acronym>RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym> at <a href="http://www.w3.org/2008/http-methods"><code>http://www.w3.org/2008/http-methods</code></a> provides <code>http:Method</code> resources for each of these to be used as objects for the <a href="#mthdProperty"><code>http:mthd</code></a> property. A resource of type <code>http:Method</code> represents the name of a method used with <acronym>HTTP</acronym>.</p>
|
|
<h4><a id="MethodClassProperties" name="MethodClassProperties">Related Properties</a></h4>
|
|
<ul>
|
|
<li>Domain of: none</li>
|
|
<li>Range of:
|
|
<ul>
|
|
<li><a href="#mthdProperty"><code>http:mthd</code></a></li>
|
|
</ul></li>
|
|
</ul>
|
|
|
|
<h3><a id="StatusCodeClass" name="StatusCodeClass">2.7 StatusCode Class</a></h3>
|
|
<p>[<a href="#ref-status-codes">HTTP Status Codes</a>] is a registry for status codes too be used in <acronym title="Hyper Text Transfer Protocol">HTTP</acronym>. The <acronym title="Resource Description Framework">RDF</acronym> graph available in <acronym>RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym> at <a href="http://www.w3.org/2008/http-statusCodes"><code>http://www.w3.org/2008/http-statusCodes</code></a> provides <code>http:StatusCode</code> resources for each of these to be used as objects for the <a href="#scProperty"><code>http:sc</code></a> property. A resource of type <code>http:StatusCode</code> represents a status code.</p>
|
|
<h4><a id="StatusCodeClassProperties" name="StatusCodeClassProperties">Related Properties</a></h4>
|
|
<ul>
|
|
<li>Domain of: none</li>
|
|
<li>Range of:
|
|
<ul>
|
|
<li><a href="#scProperty"><code>http:sc</code></a></li>
|
|
</ul></li>
|
|
</ul>
|
|
|
|
<h3><a id="HeaderNameClass" name="HeaderNameClass">2.8 HeaderName Class</a></h3>
|
|
<p>Header names to be used in <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> are registered by the <acronym title="Internet Assigned Numbers Authority">IANA</acronym> (see [<a href="#ref-rfc4229">RFC4229</a>], [<a href="#ref-permheaders">Permanent Headers</a>], and [<a href="#ref-provheaders">Provisional Headers</a>]). The <acronym title="Resource Description Framework">RDF</acronym> graph available in <acronym>RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym> at <a href="http://www.w3.org/2008/http-headers"><code>http://www.w3.org/2008/http-headers</code></a> provides <code>http:HeaderName</code> resources for each of these to be used as objects for the <a href="#hdrNameProperty"><code>http:hdrName</code></a> property. A resource of type <code>http:HeaderName</code> represents the name of a header used with <acronym>HTTP</acronym>.</p>
|
|
<h4><a id="HeaderNameClassProperties" name="HeaderNameClassProperties">Related Properties</a></h4>
|
|
<p>Properties defined by this document:</p>
|
|
<ul>
|
|
<li>Domain of: none</li>
|
|
<li>Range of:
|
|
<ul>
|
|
<li><a href="#hdrNameProperty"><code>http:hdrName</code></a></li>
|
|
</ul></li>
|
|
</ul>
|
|
|
|
|
|
<h2><a id="properties" name="properties">3 Properties</a></h2>
|
|
<p>This section defines <acronym title="Resource Description Framework">RDF</acronym> properties for the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> 1.1 specification according to [<a href="#ref-rfc2616">RFC2616</a>].</p>
|
|
|
|
<h3><a id="bodyProperty" name="bodyProperty">3.1 body Property</a></h3>
|
|
<p>This property relates a resource object of the type <code>Message</code> to a resource object of the type <code>cnt:Content</code> or a subclass thereof to be the Message's entity body as defined in [<a href="#ref-rfc2616">RFC2616</a>]. <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> bodies are series of bytes. Thus for the resource object, it is appropriate to point to a <code>cnt:ContentAsBase64</code> resource (see [<a href="#ref-content-in-rdf">Content-in-RDF</a>] for more information on content representations using the Resource Desription Framework (<acronym>RDF</acronym>)).</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#MessageClass"><code>http:Message</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd><a href="http://www.w3.org/TR/Content-in-RDF/#contentBase64Class"><code>cnt:ContentAsBase64</code> <img src="http://www.w3.org/Icons/tr.png" alt="external link" /></a></dd>
|
|
</dl>
|
|
<h4><a id="bodyPropertyExamples" name="bodyPropertyExamples">Examples</a></h4>
|
|
<div class="example">
|
|
<p><strong>Example 3.1:</strong> The entity body of a message.</p>
|
|
<pre><http:Message rdf:ID="mess0">
|
|
<http:body>
|
|
<cnt:ContentAsBase64 rdf:ID="cont0-bin"/>
|
|
</http:body>
|
|
</http:Message></pre>
|
|
</div>
|
|
|
|
<h3><a id="connectionAuthorityProperty" name="connectionAuthorityProperty">3.2 connectionAuthority Property</a></h3>
|
|
<p>Connection authority - server host and port for a connection.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#ConnectionClass"><code>http:Connection</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="elementNameProperty" name="elementNameProperty">3.3 elementName Property</a></h3>
|
|
<p>Header element name (Literal).</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#HeaderElementClass"><code>http:HeaderElement</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="elementValueProperty" name="elementValueProperty">3.4 elementValue Property</a></h3>
|
|
<p>Header element value (Literal).</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#HeaderElementClass"><code>http:HeaderElement</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="fieldNameProperty" name="fieldNameProperty">3.5 fieldName Property</a></h3>
|
|
<p>Header name (Literal).</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#MessageHeaderClass"><code>http:MessageHeader</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="fieldValueProperty" name="fieldValueProperty">3.6 fieldValue Property</a></h3>
|
|
<p>Header value (Literal).</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#MessageHeaderClass"><code>http:MessageHeader</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="headersProperty" name="headersProperty">3.7 headers Property</a></h3>
|
|
<p><acronym title="Hyper Text Transfer Protocol">HTTP</acronym> headers sent with the message.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#MessageClass"><code>http:Message</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>unspecified</dd>
|
|
</dl>
|
|
|
|
<h3><a id="headerElementsProperty" name="headerElementsProperty">3.8 headerElements Property</a></h3>
|
|
<p>Header value elements.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#MessageHeaderClass"><code>http:MessageHeader</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>unspecified</dd>
|
|
</dl>
|
|
|
|
<h3><a id="hdrNameProperty" name="hdrNameProperty">3.9 hdrName Property</a></h3>
|
|
<p>This property relates a resource of type <code>http:MessageHeader</code> to a resource of type <code>http:HeaderName</code>.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#MessageHeaderClass"><code>http:MessageHeader</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd><a href="#HeaderNameClass"><code>http:HeaderName</code></a></dd>
|
|
</dl>
|
|
|
|
<h3><a id="httpVersionProperty" name="httpVersionProperty">3.10 httpVersion Property</a></h3>
|
|
<p>Property representing the <acronym title="Hyper Text Transfer Protocol">HTTP</acronym> version number as a Literal (the format is <em>'digit.digit'</em>).</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#MessageClass"><code>http:Message</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="mthdProperty" name="mthdProperty">3.11 mthd Property</a></h3>
|
|
<p><acronym title="Hyper Text Transfer Protocol">HTTP</acronym> method.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#RequestClass"><code>http:Request</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd><a href="#MethodClass"><code>http:Method</code></a></dd>
|
|
</dl>
|
|
|
|
<h3><a id="methodNameProperty" name="methodNameProperty">3.12 methodName Property</a></h3>
|
|
<p><acronym title="Hyper Text Transfer Protocol">HTTP</acronym> method name (Literal).</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#RequestClass"><code>http:Request</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="paramsProperty" name="paramsProperty">3.13 params Property</a></h3>
|
|
<p>Header element parameters.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#HeaderElementClass"><code>http:HeaderElement</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>unspecified</dd>
|
|
</dl>
|
|
|
|
<h3><a id="paramNameProperty" name="paramNameProperty">3.14 paramName Property</a></h3>
|
|
<p>Parameter name.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#ParameterClass"><code>http:Parameter</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="paramValueProperty" name="paramValueProperty">3.15 paramValue Property</a></h3>
|
|
<p>Parameter value.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#ParameterClass"><code>http:Parameter</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="reasonPhraseProperty" name="reasonPhraseProperty">3.16 reasonPhrase Property</a></h3>
|
|
<p>Reason phrase sent by the server.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#ResponseClass"><code>http:Response</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h3><a id="requestsProperty" name="requestsProperty">3.17 requests Property</a></h3>
|
|
<p><acronym title="Hyper Text Transfer Protocol">HTTP</acronym> requests sent via the connection.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#ConnectionClass"><code>http:Connection</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>unspecified</dd>
|
|
</dl>
|
|
|
|
<h3><a id="requestURIProperty" name="requestURIProperty">3.18 requestURI Property</a></h3>
|
|
<p>The request <acronym title="Uniform Resource Identifier">URI</acronym> as specified in section 5.1.2 of [<a href="#ref-rfc2616">RFC2616</a>]. This vocabulary defines the following sub-properties:</p>
|
|
<ul>
|
|
<li><a href="#absoluteURIProperty"><code>http:absoluteURI</code></a></li>
|
|
<li><a href="#abs_pathProperty"><code>http:abs_path</code></a></li>
|
|
<li><a href="#authorityProperty"><code>http:authority</code></a></li>
|
|
</ul>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#RequestClass"><code>http:Request</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
<h4><a id="requestURIPropertyExamples" name="requestURIPropertyExamples">Examples</a></h4>
|
|
<div class="example">
|
|
<p><strong>Example 3.2:</strong> The use of the <code>requestURI</code> property.</p>
|
|
<pre><http:Request>
|
|
<http:methodName>OPTIONS</http:methodName>
|
|
<http:requestURI>*</http:requestURI>
|
|
...
|
|
</http:Request></pre>
|
|
</div>
|
|
|
|
<h4><a id="absoluteURIProperty" name="absoluteURIProperty">3.18.1 absoluteURI Property</a></h4>
|
|
<p>Request <acronym title="Uniform Resource Identifier">URI</acronym> that is an absolute <acronym>URI</acronym>.</p>
|
|
<p><strong>Conformance Note:</strong> The object for this property must be a Literal (absolute <acronym>URI</acronym>).</p>
|
|
<h5><a id="absoluteURIPropertyExamples" name="absoluteURIPropertyExamples">Examples</a></h5>
|
|
<div class="example">
|
|
<p><strong>Example 3.3:</strong> The use of the <code>absoluteURI</code> property.</p>
|
|
<pre><http:Request>
|
|
<http:methodName>GET</http:methodName>
|
|
<http:absoluteURI>http://www.example.org:80/foo/bar</http:absoluteURI>
|
|
...
|
|
</http:Request></pre>
|
|
</div>
|
|
|
|
<h4><a id="abs_pathProperty" name="abs_pathProperty">3.18.2 abs_path Property</a></h4>
|
|
<p>Request <acronym title="Uniform Resource Identifier">URI</acronym> that is an absolute path.</p>
|
|
<p><strong>Conformance Note:</strong> The object for this property must be a Literal (absolute path).</p>
|
|
<h5><a id="abs_pathPropertyExamples" name="abs_pathPropertyExamples">Examples</a></h5>
|
|
<div class="example">
|
|
<p><strong>Example 3.4:</strong> The use of the <code>abs_path</code> property.</p>
|
|
<pre><http:Request>
|
|
<http:methodName>GET</http:methodName>
|
|
<http:abs_path>/foo/bar</http:abs_path>
|
|
...
|
|
</http:Request></pre>
|
|
</div>
|
|
|
|
<h4><a id="authorityProperty" name="authorityProperty">3.18.3 authority Property</a></h4>
|
|
<p>Request <acronym title="Uniform Resource Identifier">URI</acronym> that is an authority.</p>
|
|
<p><strong>Conformance Note:</strong> The object for this property must be a Literal (host and optional port number).</p>
|
|
<h5><a id="authorityPropertyExamples" name="authorityPropertyExamples">Examples</a></h5>
|
|
<div class="example">
|
|
<p><strong>Example 3.5:</strong> The use of the <code>authority</code> property.</p>
|
|
<pre><http:Request>
|
|
<http:methodName>CONNECT</http:methodName>
|
|
<http:authority>www.example.org:80</http:authority>
|
|
...
|
|
</http:Request></pre>
|
|
</div>
|
|
|
|
<h3><a id="respProperty" name="respProperty">3.19 resp Property</a></h3>
|
|
<p>This property relates a resource of type <code>http:Request</code> to a resource of type <code>http:Response</code>.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#RequestClass"><code>http:Request</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd><a href="#ResponseClass"><code>http:Response</code></a></dd>
|
|
</dl>
|
|
|
|
<h3><a id="scProperty" name="scProperty">3.20 sc Property</a></h3>
|
|
<p>This property relates a resource of type <code>http:Response</code> to a resource of type <code>http:StatusCode</code>.</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#ResponseClass"><code>http:Response</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd><a href="#StatusCodeClass"><code>http:StatusCode</code></a></dd>
|
|
</dl>
|
|
|
|
<h3><a id="statusCodeNumberProperty" name="statusCodeNumberProperty">3.21 statusCodeNumber Property</a></h3>
|
|
<p>The status code sent by the server (Literal).</p>
|
|
<dl>
|
|
<dt>Domain:</dt>
|
|
<dd><a href="#ResponseClass"><code>http:Response</code></a></dd>
|
|
<dt>Range:</dt>
|
|
<dd>Literal</dd>
|
|
</dl>
|
|
|
|
<h2><a id="conformance" name="conformance">4 Conformance</a></h2>
|
|
<p>This section describes conformance with this HTTP-in-RDF specification. It differentiates between the following entities:</p>
|
|
<p class="note">[Editor's note: The working group asks for comments about a more colloquial word for "HTTP-in-RDF Graph".]</p>
|
|
<dl>
|
|
<dt><a name="Graph" id="Graph">HTTP-in-RDF Graph</a></dt>
|
|
<dd>An individual file or collection of files that contain HTTP-in-RDF data</dd>
|
|
<dt><a name="Producer" id="Producer">HTTP-in-RDF Producer</a></dt>
|
|
<dd>A software tool or Web-based application that produces HTTP-in-RDF data</dd>
|
|
<dt><a name="Consumer" id="Consumer">HTTP-in-RDF Consumer</a></dt>
|
|
<dd>A software tool or Web-based application that processes HTTP-in-RDF data</dd>
|
|
</dl>
|
|
|
|
<h3><a id="graphs" name="graphs">4.1 Conforming HTTP-in-RDF graphs</a></h3>
|
|
<p>Graphs conforming to this HTTP-in-RDF specification <strong class="keyword">must</strong> meet the following requirements:</p>
|
|
<ol>
|
|
<li>A <a href="#ConnectionClass">Connection</a> <strong class="keyword">must</strong> have exactly one connection authority (specified by <code><a href="#connectionAuthorityProperty">http:connectionAuthority</a></code>).</li>
|
|
<li>A <a href="#ConnectionClass">Connection</a> <strong class="keyword">may</strong> have one collection of <a href="#RequestClass">Requests</a> (referenced by <code><a href="#requestsProperty">http:requests</a></code>).</li>
|
|
<li>A <a href="#MessageClass">Message</a> <strong class="keyword">must</strong> have exactly one <acronym title="Hypertext Transfer Protocol">HTTP</acronym> version (specified by <code><a href="#httpVersionProperty">http:httpVersion</a></code>).</li>
|
|
<li>A <a href="#MessageClass">Message</a> <strong class="keyword">may</strong> have one collection of <a href="#MessageHeaderClass">Message Headers</a> (referenced by <code><a href="#headersProperty">http:headers</a></code>).</li>
|
|
<li>A <a href="#MessageClass">Message</a> <strong class="keyword">may</strong> have one message body (referenced by <code><a href="#bodyProperty">http:body</a></code>).</li>
|
|
<li>A <a href="#MessageClass">Message</a> <strong class="keyword">may</strong> have one date (specified by <code><a href="http://dublincore.org/documents/dcmi-terms/#terms-date">dct:date <img src="http://www.w3.org/Icons/tr.png" alt="external link" /></a></code>).</li>
|
|
<li>A <a href="#RequestClass">Request</a> <strong class="keyword">must</strong> have exactly one method name (specified by <code><a href="#methodNameProperty">http:methodName</a></code>).</li>
|
|
<li>A <a href="#RequestClass">Request</a> <strong class="keyword">must</strong> have exactly one request <acronym title="Uniform Resource Identifier">URI</acronym> (specified by <code><a href="#requestURIProperty">http:requestURI</a></code>).</li>
|
|
<li>A <a href="#RequestClass">Request</a> <strong class="keyword">may</strong> be connected to one <a href="#MethodClass">Method</a> (referenced by <code><a href="#mthdProperty">http:mthd</a></code>).</li>
|
|
<li>A <a href="#RequestClass">Request</a> <strong class="keyword">may</strong> be connected to one <a href="#ResponseClass">Response</a> (referenced by <code><a href="#respProperty">http:resp</a></code>).</li>
|
|
<li>A <a href="#ResponseClass">Response</a> <strong class="keyword">must</strong> have exactly one status code number (specified by <code><a href="#statusCodeNumberProperty">http:statusCodeNumber</a></code>).</li>
|
|
<li>A <a href="#ResponseClass">Response</a> <strong class="keyword">must</strong> have exactly one reason phrase (specified by <code><a href="#reasonPhraseProperty">http:reasonPhrase</a></code>).</li>
|
|
<li>A <a href="#ResponseClass">Response</a> <strong class="keyword">may</strong> be conected to one <a href="#StatusCodeClass">Status Code</a> (referenced by <code><a href="#scProperty">http:sc</a></code>).</li>
|
|
<li>A <a href="#MessageHeaderClass">Message Header</a> <strong class="keyword">must</strong> have exactly one field name (specified by <code><a href="#fieldNameProperty">http:fieldName</a></code>).</li>
|
|
<li>A <a href="#MessageHeaderClass">Message Header</a> <strong class="keyword">must</strong> have exactly one field value (specified by <code><a href="#fieldValueProperty">http:fieldValue</a></code>).</li>
|
|
<li>A <a href="#MessageHeaderClass">Message Header</a> <strong class="keyword">may</strong> be connected to one <a href="#HeaderNameClass">Header Name</a> (referenced by <code><a href="#hdrNameProperty">http:hdrName</a></code>).</li>
|
|
<li>A <a href="#MessageHeaderClass">Message Header</a> <strong class="keyword">may</strong> have one collection of <a href="#HeaderElementClass">Header Elements</a> (referenced by <code><a href="#headerElementsProperty">http:headerElements</a></code>).</li>
|
|
<li>A <a href="#HeaderElementClass">Header Element</a> <strong class="keyword">must</strong> have exactly one header element name (specified by <code><a href="#elementNameProperty">http:elementName</a></code>).</li>
|
|
<li>A <a href="#HeaderElementClass">Header Element</a> <strong class="keyword">may</strong> have one header element value (specified by <code><a href="#elementValueProperty">http:elementValue</a></code>).</li>
|
|
<li>A <a href="#HeaderElementClass">Header Element</a> <strong class="keyword">may</strong> have one collection of <a href="#ParameterClass">Parameters</a> (referenced by <code><a href="#paramsProperty">http:params</a></code>).</li>
|
|
<li>A <a href="#ParameterClass">Parameter</a> <strong class="keyword">must</strong> have exactly one parameter name (specified by <code><a href="#paramNameProperty">http:paramName</a></code>).</li>
|
|
<li>A <a href="#ParameterClass">Parameter</a> <strong class="keyword">must</strong> have exactly one parameter value (specified by <code><a href="#paramValueProperty">http:paramValue</a></code>).</li>
|
|
<li>The objects for the <code><a href="#headersProperty">headers</a></code> property must be an <acronym title="Resource Description Framework">RDF</acronym> Collection of <a href="#MessageHeaderClass">Message Headers</a>.</li>
|
|
<li>The objects for the <code><a href="#headerElementsProperty">http:headerElements</a></code> property must be an <acronym>RDF</acronym> Collection of <a href="#HeaderElementClass">Header Elements</a>.</li>
|
|
<li>The object for the <code><a href="#paramsProperty">http:params</a></code> property must be an <acronym>RDF</acronym> Collection of <a href="#ParameterClass">Parameters</a>.</li>
|
|
<li>The object for the <code><a href="#requestsProperty">http:requests</a></code> property must be an <acronym>RDF</acronym> Collection of <a href="#RequestClass">Requests</a>.</li>
|
|
<li>Every instance of <code><a href="http://www.w3.org/TR/Content-in-RDF/#ContentAsBase64Class">cnt:ContentAsBase64 <img src="http://www.w3.org/Icons/tr.png" alt="external link" /></a></code> <strong class="keyword">must</strong> conform with the respective specification.</li>
|
|
</ol>
|
|
|
|
<h3><a id="producers" name="producers">4.2 Conforming Producers</a></h3>
|
|
<p>Producers conforming to this HTTP-in-RDF specification <strong class="keyword">must</strong> meet the following requirements:</p>
|
|
<ol>
|
|
<li>A Producer <strong class="keyword">must</strong> generate <a href="#graphs">conforming graphs</a></li>
|
|
<li>A Producer <strong class="keyword">must</strong> be able to generate graphs in <acronym title="Resource Description Framework">RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym> serialization and <strong class="keyword">should</strong> also support other <acronym>RDF</acronym> serializations</li>
|
|
<li>A Producer <strong class="keyword">must</strong> generate all of the terms summarized in <a href="#terms">Appendix B: Terms</a> for which there is information available to it</li>
|
|
</ol>
|
|
|
|
<h3><a id="consumers" name="consumers">4.3 Conforming Consumers</a></h3>
|
|
<p>Consumers conforming to this HTTP-in-RDF specification <strong class="keyword">must</strong> meet the following requirements:</p>
|
|
<ol>
|
|
<li>A Consumer <strong class="keyword">must</strong> process <a href="#graphs">conforming graphs</a></li>
|
|
<li>A Consumer <strong class="keyword">must</strong> process graphs in any <acronym title="Resource Description Framework">RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym> serialization and <strong class="keyword">should</strong> also support other <acronym>RDF</acronym> serializations</li>
|
|
<li>A Consumer <strong class="keyword">must</strong> process all of the terms summarized in <a href="#terms">Appendix B: Terms</a> for which there is information available to it</li>
|
|
</ol>
|
|
|
|
<hr />
|
|
|
|
<h2><a id="example" name="example">Appendix A: A practical Example</a></h2>
|
|
<p>The following example shows an <acronym title="Resource Description Framework">RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym> representation of an <acronym title="Hypertext Transfer Protocol">HTTP</acronym> request and response pair.</p>
|
|
|
|
<h3><a id="scenario" name="scenario">Scenario Description</a></h3>
|
|
<p>A client sends two requests to a server at <code>www.example.org</code> port 80 via <acronym>HTTP</acronym> 1.1 GET. With each request, it sends request headers. The first request is for a resource in the document root (<code>/</code>), the second for a resource at <code>/image</code>. While handling the second request the server performs content negotiation respecting the request's <code>Accept</code> header and so sends a <acronym title="Portable Netowrk Graphics">PNG</acronym> image. This is indicated by the response's <code>Vary</code> header.</p>
|
|
|
|
<h3><a id="code" name="code">Resulting <acronym>RDF</acronym>/<acronym>XML</acronym></a></h3>
|
|
<pre><?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></pre>
|
|
|
|
<h2><a id="terms" name="terms">Appendix B: Terms</a></h2>
|
|
<p>The following terms are defined by this specification:</p>
|
|
|
|
<h3><a id="terms-classes" name="terms-classes">Classes</a></h3>
|
|
<table>
|
|
<caption>Classes in the HTTP-in-RDF namespace</caption>
|
|
<thead>
|
|
<tr>
|
|
<th scope="col">Class name</th>
|
|
<th scope="col">Label</th>
|
|
<th scope="col">Comment</th>
|
|
<th scope="col">Refinements</th>
|
|
<th scope="col">Related properties</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr id="terms-classes-Connection">
|
|
<td scope="row"><code><a href="#ConnectionClass">http:Connection</a></code></td>
|
|
<td>Connection</td>
|
|
<td>A connection used for <acronym title="Hypertext Transfer Protocol">HTTP</acronym> transfer.</td>
|
|
<td>-</td>
|
|
<td><a href="#connectionAuthorityProperty"><code>http:connectionAuthority</code></a>, <a href="#requestsProperty"><code>http:requests</code></a></td>
|
|
</tr>
|
|
<tr id="terms-classes-HeaderElement">
|
|
<td scope="row"><code><a href="#HeaderElementClass">http:HeaderElement</a></code></td>
|
|
<td>Header Element</td>
|
|
<td>A part of a deconstructed header value.</td>
|
|
<td>-</td>
|
|
<td><a href="#elementNameProperty"><code>http:elementName</code></a>, <a href="#elementValueProperty"><code>http:elementValue</code></a>, <a href="#paramsProperty"><code>http:params</code></a></td>
|
|
</tr>
|
|
<tr id="terms-classes-HeaderName">
|
|
<td scope="row"><code><a href="#HeaderNameClass">http:HeaderName</a></code></td>
|
|
<td>Header Name</td>
|
|
<td>The header name.</td>
|
|
<td>-</td>
|
|
<td></td>
|
|
</tr>
|
|
<tr id="terms-classes-Message">
|
|
<td scope="row"><code><a href="#MessageClass">http:Message</a></code></td>
|
|
<td>Message</td>
|
|
<td>An <acronym>HTTP</acronym> message.</td>
|
|
<td><a href="#RequestClass">http:Request</a>, <a href="#ResponseClass">http:Response</a></td>
|
|
<td><a href="#httpVersionProperty"><code>http:httpVersion</code></a>, <code>dct:date</code>, <a href="#bodyProperty"><code>http:body</code></a>, <a href="#headersProperty"><code>http:headers</code></a></td>
|
|
</tr>
|
|
<tr id="terms-classes-MessageHeader">
|
|
<td scope="row"><code><a href="#MessageHeaderClass">http:MessageHeader</a></code></td>
|
|
<td>Message Header</td>
|
|
<td>A header in an <acronym>HTTP</acronym> message.</td>
|
|
<td>-</td>
|
|
<td><a href="#fieldNameProperty"><code>http:fieldName</code></a>, <a href="#fieldValueProperty"><code>http:fieldValue</code></a>, <a href="#hdrNameProperty"><code>http:hdrName</code></a>, <a href="#headerElementsProperty"><code>http:headerElements</code></a></td>
|
|
</tr>
|
|
<tr id="terms-classes-Method">
|
|
<td scope="row"><code><a href="#MethodClass">http:Method</a></code></td>
|
|
<td>Method</td>
|
|
<td>The <acronym>HTTP</acronym> method used for a request.</td>
|
|
<td>-</td>
|
|
<td></td>
|
|
</tr>
|
|
<tr id="terms-classes-Parameter">
|
|
<td scope="row"><code><a href="#ParameterClass">http:Parameter</a></code></td>
|
|
<td>Parameter</td>
|
|
<td>A parameter for a part of a header value</td>
|
|
<td>-</td>
|
|
<td><a href="#paramNameProperty"><code>http:paramName</code></a>, <a href="#paramValueProperty"><code>http:paramValue</code></a></td>
|
|
</tr>
|
|
<tr id="terms-classes-Request">
|
|
<td scope="row"><code><a href="#RequestClass">http:Request</a></code></td>
|
|
<td>Request</td>
|
|
<td>An <acronym>HTTP</acronym> request.</td>
|
|
<td>-</td>
|
|
<td><a href="#methodNameProperty"><code>http:methodName</code></a>, <a href="#requestURIProperty"><code>http:requestURI</code></a>, <a href="#mthdProperty"><code>http:mthd</code></a>, <a href="#respProperty"><code>http:resp</code></a></td>
|
|
</tr>
|
|
<tr id="terms-classes-Response">
|
|
<td scope="row"><code><a href="#ResponseClass">http:Response</a></code></td>
|
|
<td>Response</td>
|
|
<td>An <acronym>HTTP</acronym> response.</td>
|
|
<td>-</td>
|
|
<td><a href="#statusCodeNumberProperty"><code>http:statusCodeNumber</code></a>, <a href="#reasonPhraseProperty"><code>http:reasonPhrase</code></a>, <a href="#scProperty"><code>http:sc</code></a></td>
|
|
</tr>
|
|
<tr id="terms-classes-StatusCode">
|
|
<td scope="row"><code><a href="#StatusCodeClass">http:StatusCode</a></code></td>
|
|
<td>Status Code</td>
|
|
<td>The status code of an <acronym>HTTP</acronym> response.</td>
|
|
<td>-</td>
|
|
<td></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<h3><a id="terms-properties" name="terms-properties">Properties</a></h3>
|
|
<table>
|
|
<caption>Properties in the HTTP-in-RDF namespace</caption>
|
|
<thead>
|
|
<tr>
|
|
<th scope="col">Property name</th>
|
|
<th scope="col">Label</th>
|
|
<th scope="col">Comment</th>
|
|
<th scope="col">Domain</th>
|
|
<th scope="col">Range</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr id="terms-properties-body">
|
|
<td scope="row"><code><a href="#bodyProperty">http:body</a></code></td>
|
|
<td>Entity body</td>
|
|
<td>The entity body of an <acronym>HTTP</acronym> message.</td>
|
|
<td><a href="#MessageClass"><code>http:Message</code></a></td>
|
|
<td><code>cnt:ContentAsBase64</code></td>
|
|
</tr>
|
|
<tr id="terms-properties-connectionAuthority">
|
|
<td scope="row"><code><a href="#connectionAuthorityProperty">http:connectionAuthority</a></code></td>
|
|
<td>Connection authority</td>
|
|
<td>The authority of a connection used for the <acronym>HTTP</acronym> transfer</td>
|
|
<td><a href="#ConnectionClass"><code>http:Connection</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-elementName">
|
|
<td scope="row"><code><a href="#elementNameProperty">http:elementName</a></code></td>
|
|
<td>Header element name</td>
|
|
<td>The name of a header element</td>
|
|
<td><a href="#HeaderElementClass"><code>http:HeaderElement</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-elementValue">
|
|
<td scope="row"><code><a href="#elementValueProperty">http:elementValue</a></code></td>
|
|
<td>Header element value</td>
|
|
<td>The value of a header element.</td>
|
|
<td><a href="#HeaderElementClass"><code>http:HeaderElement</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-fieldName">
|
|
<td scope="row"><code><a href="#fieldNameProperty">http:fieldName</a></code></td>
|
|
<td>Field name</td>
|
|
<td>The name of an <acronym>HTTP</acronym> header field.</td>
|
|
<td><a href="#MessageHeaderClass"><code>http:MessageHeader</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-fieldValue">
|
|
<td scope="row"><code><a href="#fieldValueProperty">http:fieldValue</a></code></td>
|
|
<td>Field value</td>
|
|
<td>The value of an <acronym>HTTP</acronym> header field.</td>
|
|
<td><a href="#MessageHeaderClass"><code>http:MessageHeader</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-headerElements">
|
|
<td scope="row"><code><a href="#headerElementsProperty">http:headerElements</a></code></td>
|
|
<td>Header elements</td>
|
|
<td>The deconstructed parts of an <acronym>HTTP</acronym> header value.</td>
|
|
<td><a href="#MessageHeaderClass"><code>http:MessageHeader</code></a></td>
|
|
<td>Collection of <a href="#HeaderElementClass"><code>http:HeaderElement</code></a></td>
|
|
</tr>
|
|
<tr id="terms-properties-hdrName">
|
|
<td scope="row"><code><a href="#hdrNameProperty">http:hdrName</a></code></td>
|
|
<td>Header name</td>
|
|
<td>The name of an <acronym>HTTP</acronym> header.</td>
|
|
<td><a href="#MessageHeaderClass"><code>http:MessageHeader</code></a></td>
|
|
<td><a href="#HeaderNameClass"><code>http:HeaderName</code></a></td>
|
|
</tr>
|
|
<tr id="terms-properties-headers">
|
|
<td scope="row"><code><a href="#headersProperty">http:headers</a></code></td>
|
|
<td>Headers</td>
|
|
<td>The headers in an <acronym>HTTP</acronym> message.</td>
|
|
<td><a href="#MessageClass"><code>http:Message</code></a></td>
|
|
<td>Collection of <a href="#MessageHeaderClass"><code>http:MessageHeader</code></a></td>
|
|
</tr>
|
|
<tr id="terms-properties-httpVersion">
|
|
<td scope="row"><code><a href="#httpVersionProperty">http:httpVersion</a></code></td>
|
|
<td><acronym>HTTP</acronym> Version</td>
|
|
<td>The <acronym>HTTP</acronym> version of an <acronym>HTTP</acronym> message.</td>
|
|
<td><a href="#MessageClass"><code>http:Message</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-mthd">
|
|
<td scope="row"><code><a href="#mthdProperty">http:mthd</a></code></td>
|
|
<td>Method</td>
|
|
<td>The <acronym>HTTP</acronym> method used for the <acronym>HTTP</acronym> request.</td>
|
|
<td><a href="#RequestClass"><code>http:Request</code></a></td>
|
|
<td><a href="#MethodClass"><code>http:Method</code></a></td>
|
|
</tr>
|
|
<tr id="terms-properties-methodName">
|
|
<td scope="row"><code><a href="#methodNameProperty">http:methodName</a></code></td>
|
|
<td>Method name</td>
|
|
<td>The <acronym>HTTP</acronym> method name used for the <acronym>HTTP</acronym> request.</td>
|
|
<td><a href="#RequestClass"><code>http:Request</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-paramName">
|
|
<td scope="row"><code><a href="#paramNameProperty">http:paramName</a></code></td>
|
|
<td>Parameter name</td>
|
|
<td>The name of a parameter in a part of a deconstructed <acronym>HTTP</acronym> header value.</td>
|
|
<td><a href="#ParameterClass"><code>http:Parameter</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-params">
|
|
<td scope="row"><code><a href="#paramsProperty">http:params</a></code></td>
|
|
<td>Parameters</td>
|
|
<td>The parameters in a part of a deconstructed <acronym>HTTP</acronym> header value.</td>
|
|
<td><a href="#HeaderElementClass"><code>http:HeaderElement</code></a></td>
|
|
<td>Collection of <a href="#ParameterClass"><code>http:Parameter</code></a></td>
|
|
</tr>
|
|
<tr id="terms-properties-paramValue">
|
|
<td scope="row"><code><a href="#paramValueProperty">http:paramValue</a></code></td>
|
|
<td>Parameter value</td>
|
|
<td>The value of a parameter in a part of a deconstructed <acronym>HTTP</acronym> header value.</td>
|
|
<td><a href="#ParameterClass"><code>http:Parameter</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-reasonPhrase">
|
|
<td scope="row"><code><a href="#reasonPhraseProperty">http:reasonPhrase</a></code></td>
|
|
<td>Reason phrase</td>
|
|
<td>The reason phrase (status text) of an <acronym>HTTP</acronym> response.</td>
|
|
<td><a href="#ResponseClass"><code>http:Response</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-requests">
|
|
<td scope="row"><code><a href="#requestsProperty">http:requests</a></code></td>
|
|
<td>Requests</td>
|
|
<td>The <acronym>HTTP</acronym> requests made via a connection.</td>
|
|
<td><a href="#ConnectionClass"><code>http:Connection</code></a></td>
|
|
<td>Collection of <a href="#RequestClass"><code>http:Request</code></a></td>
|
|
</tr>
|
|
<tr id="terms-properties-requestURI">
|
|
<td scope="row"><code><a href="#requestURIProperty">http:requestURI</a></code></td>
|
|
<td>Request <acronym>URI</acronym></td>
|
|
<td>The request <acronym>URI</acronym> of an <acronym>HTTP</acronym> request.</td>
|
|
<td><a href="#RequestClass"><code>http:Request</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
<tr id="terms-properties-resp">
|
|
<td scope="row"><code><a href="#respProperty">http:resp</a></code></td>
|
|
<td>Response</td>
|
|
<td>The <acronym>HTTP</acronym> response sent in answer to an <acronym>HTTP</acronym> request.</td>
|
|
<td><a href="#RequestClass"><code>http:Request</code></a></td>
|
|
<td><a href="#ResponseClass"><code>http:Response</code></a></td>
|
|
</tr>
|
|
<tr id="terms-properties-sc">
|
|
<td scope="row"><code><a href="#scProperty">http:sc</a></code></td>
|
|
<td>Status code</td>
|
|
<td>The status code of an <acronym>HTTP</acronym> response.</td>
|
|
<td><a href="#ResponseClass"><code>http:Response</code></a></td>
|
|
<td><a href="#StatusCodeClass"><code>http:StatusCode</code></a></td>
|
|
</tr>
|
|
<tr id="terms-properties-statusCodeNumber">
|
|
<td scope="row"><code><a href="#statusCodeNumberProperty">http:statusCodeNumber</a></code></td>
|
|
<td>Status code number</td>
|
|
<td>The status code number of an <acronym>HTTP</acronym> response.</td>
|
|
<td><a href="#ResponseClass"><code>http:Response</code></a></td>
|
|
<td>RDF Literal</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
<h2><a id="references" name="references">Appendix C: References</a></h2>
|
|
<dl>
|
|
<dt>[<a id="ref-content-in-rdf" name="ref-content-in-rdf">Content-in-RDF</a>]</dt>
|
|
<dd><a href="http://www.w3.org/TR/Content-in-RDF10/">Representing Content in <acronym title="Resource Description Framework">RDF</acronym></a> - Johannes Koch, Carlos A Velasco (editors). <acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 17 July 2008.</dd>
|
|
<dt>[<a id="ref-earl" name="ref-earl">EARL</a>]</dt>
|
|
<dd><a href="http://www.w3.org/WAI/intro/earl.php">Evaluation and Report Language (<acronym>EARL</acronym>) Overview</a> - <acronym>W3C</acronym></dd>
|
|
<dt>[<a id="ref-status-codes" name="ref-status-codes">HTTP Status Codes</a>]</dt>
|
|
<dd><a href="http://www.iana.org/assignments/http-status-codes">"<acronym title="Hypertext Transfer Protocol">HTTP</acronym> Status Code Registry"</a> - <acronym title="Internet Assigned Numbers Authority">IANA</acronym>.</dd>
|
|
<dt>[<a id="ref-owl" name="ref-owl">OWL</a>]</dt>
|
|
<dd><a href="http://www.w3.org/2004/OWL/">Web Ontology Language (<acronym>OWL</acronym>) Overview</a> - <acronym>W3C</acronym></dd>
|
|
<dt>[<a id="ref-permheaders" name="ref-permheaders">Permanent Headers</a>]</dt>
|
|
<dd><a href="http://www.iana.org/assignments/message-headers/perm-headers.html">Permanent Message Header Field Names</a> - <acronym>IANA</acronym>.</dd>
|
|
<dt>[<a id="ref-provheaders" name="ref-provheaders">Provisional Headers</a>]</dt>
|
|
<dd><a href="http://www.iana.org/assignments/message-headers/prov-headers.html">Provisional Message Header Field Names</a> - <acronym>IANA</acronym>.</dd>
|
|
<dt>[<a id="ref-powder-dr" name="ref-powder-dr">POWDER-DR</a>]</dt>
|
|
<dd><a href="http://www.w3.org/TR/2009/PR-powder-dr-20090604/">Protocol for Web Description Resources (POWDER): Description Resources</a> - P. Archer, K. Smith, A. Perego (editors). <acronym>W3C</acronym> Proposed Recommendation 04 June 2009.</dd>
|
|
<dt>[<a id="ref-rdf" name="ref-rdf">RDF</a>]</dt>
|
|
<dd><a href="http://www.w3.org/RDF/">Resource Description Framework (<acronym>RDF</acronym>) Overview</a> - <acronym>W3C</acronym></dd>
|
|
<dt>[<a id="ref-rdf-primer" name="ref-rdf-primer">RDF-PRIMER</a>]</dt>
|
|
<dd><a href="http://www.w3.org/TR/rdf-primer/"><acronym>RDF</acronym> Primer</a> - Frank Manola, Eric Miller (editors). W3C Recommendation, 10 February 2004.</dd>
|
|
<dt>[<a id="ref-rdfs" name="ref-rdfs">RDFS</a>]</dt>
|
|
<dd><a href="http://www.w3.org/TR/rdf-schema/"><acronym>RDF</acronym> Vocabulary Description Language 1.0: <acronym>RDF</acronym> Schema</a> - Dan Brickley, R.V. Guha (editors). W3C Recommendation 10 February 2004</dd>
|
|
<dt>[<a id="ref-rfc2119" name="ref-rfc2119">RFC2119</a>]</dt>
|
|
<dd>Request for Comments (<acronym>RFC</acronym>): 2119. <a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in <acronym>RFC</acronym>s to Indicate Requirement Levels</a> - <acronym title="Internet Engineering Task Force">IETF</acronym> March 1997.</dd>
|
|
<dt>[<a id="ref-rfc2616" name="ref-rfc2616">RFC2616</a>]</dt>
|
|
<dd><a href="http://www.ietf.org/rfc/rfc2616.txt">Hypertext Transfer Protocol -- <acronym>HTTP</acronym>/1.1</a> - R. Fielding, J. Gettys, J. Mogul, H. Frystyk Nielsen, L. Masinter, P. Leach and T. Berners-Lee. <acronym>IETF</acronym> June 1999.</dd>
|
|
<dt>[<a id="ref-rfc4229" name="ref-rfc4229">RFC4229</a>]</dt>
|
|
<dd><a href="http://www.ietf.org/rfc/rfc4229.txt"><acronym>HTTP</acronym> Header Field Registrations</a> - M. Nottingham, J. Mogul. <acronym>IETF</acronym> December 2005.</dd>
|
|
<dt>[<a id="ref-wcag" name="ref-wcag">WCAG</a>]</dt>
|
|
<dd><a href="http://www.w3.org/WAI/intro/wcag.php">Web Content Accessibility Guidelines (<acronym>WCAG</acronym>) Overview</a> - <acronym>W3C</acronym>.</dd>
|
|
<dt>[<a id="ref-xml" name="ref-xml">XML</a>]</dt>
|
|
<dd><a href="http://www.w3.org/TR/2008/REC-xml-20081126/">Extensible Markup Language (<acronym>XML</acronym>) 1.0 (Fifth Edition)</a> - Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, François Yergeau (editors). <acronym>W3C</acronym> Recommendation 26 November 2008</dd>
|
|
</dl>
|
|
|
|
<h2><a id="changes" name="changes">Appendix D: Document Changes</a></h2>
|
|
<p>The following is a list of substantial changes since the <a href="http://www.w3.org/TR/2008/WD-HTTP-in-RDF-20080908">8 September 2008 Working Draft</a>:</p>
|
|
<ul>
|
|
<li>at most one <code>body</code> property is allowed for <code>Message</code> resources; this property relates the message to Base64 encoded message content;</li>
|
|
<li>several properties were renamed because their names differed from class names only by case: <code>headername</code> (now <code>hdrName</code>), <code>method</code> (now <code>mthd</code>), <code>response</code> (now <code>resp</code>), <code>statusCode</code> (now <code>sc</code>);</li>
|
|
<li>the <code>asterisk</code> resource was removed in favour of the use of the Literal "*";</li>
|
|
<li>the <code>StatusCodeGroup</code> class was removed in favour of sub-classes of <code>StatusCode</code>;</li>
|
|
<li>a section about conformance was added.</li>
|
|
</ul>
|
|
|
|
</body>
|
|
</html>
|