index.html 55.5 KB

Raw Blame History Permalink

<?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 xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
  <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
  <title>Representing Content in RDF 1.0</title>
  <link href="http://www.w3.org/2011/content" rel="alternate" type="application/rdf+xml" />
  <link rel="stylesheet" type="text/css" href="main.css" />
  <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>

<!--// head //-->
<div id="head" class="head">
<p><a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="http://www.w3.org/Icons/w3c_home" /></a></p>

<h1><a id="title" name="title">Representing Content in <acronym title="Resource Description Framework">RDF</acronym> 1.0</a></h1>

<h2><a id="w3c-doctype" name="w3c-doctype">W3C Working Draft 10 May 2011</a></h2>

<dl>
  <dt>This version:</dt>
    <dd><a href="http://www.w3.org/TR/2011/WD-Content-in-RDF10-20110510/">http://www.w3.org/TR/2011/WD-Content-in-RDF10-20110510/</a></dd>
  <dt>Latest version:</dt>
    <dd><a href="http://www.w3.org/TR/Content-in-RDF10/">http://www.w3.org/TR/Content-in-RDF10/</a></dd>
  <dt>Previous version:</dt>
    <dd><a href="http://www.w3.org/TR/2009/WD-Content-in-RDF10-20091029/">http://www.w3.org/TR/2009/WD-Content-in-RDF10-20091029/</a></dd>
  <dt>Editors:</dt>
    <dd>Johannes Koch (until November 2010 while at Fraunhofer Institute for Applied Information Technology FIT)</dd>
    <dd>Carlos A Velasco, Fraunhofer Institute for Applied Information Technology FIT</dd>
    <dd>Philip Ackermann, 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/2011/content">RDF Schema</a> format.</p>

<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><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>This document is a specification for a vocabulary to represent content in the Resource Description Framework (<acronym>RDF</acronym>). This vocabulary is intended to provide a flexible framework within different usage scenarios to semantically represent any type of content, be it on the Web or in local storage media. For example, it can be used by web quality assurance tools such as web accessibility evaluation tools to record a representation of the assessed web content, including text, images, or other types of formats. In many cases, it can be used together with <a href="http://www.w3.org/TR/HTTP-in-RDF10/"><acronym title="Hyper Text Transfer Protocol">HTTP</acronym> Vocabulary in <acronym title="Resource Description Framework">RDF</acronym> 1.0</a>, which allows quality assurance tools to record the <acronym>HTTP</acronym> headers that have been exchanged between a client and a server. This is particularly useful 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>.</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 10 May 2011 Working Draft of Representing Content in <acronym title="Resource Description Framework">RDF</acronym> 1.0 is an update of the previous <a href="http://www.w3.org/TR/2009/WD-Content-in-RDF10-20091029/">Representing Content in <acronym>RDF</acronym> Working Draft of 29 October 2009</a>, and it incorporates all comments received since. This document is part of the <a href="http://www.w3.org/WAI/intro/earl">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 it has addressed all issues brought forth through previous Working Draft iterations. The Working Group encourages feedback about this document, Representing Content in <acronym>RDF</acronym> 1.0, by developers and researchers who have interest in software-supported evaluation and validation of websites, and by developers and researchers who have interest in Semantic Web technologies for content description, annotation, and adaptation. In particular, feedback from the groups involved in the W3C Semantic Web Activity, especially the Semantic Web Coordination Group, the Semantic Web Deployment Working Group, and the Semantic Web Interest Group would be greatly appreciated.</p>

<p>Please send comments on this Representing Content in <acronym>RDF</acronym> 1.0 document by <strong>10 June 2011</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 />

<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>
        </ul></li>
      <li><a href="#classes">Classes</a> <ul>
          <li><a href="#ContentClass">2.1 Content Class</a> <ul>
              <li><a href="#ContentAsBase64Class">2.1.1 ContentAsBase64
              Class</a></li>
              <li><a href="#ContentAsTextClass">2.1.2 ContentAsText
              Class</a></li>
              <li><a href="#ContentAsXMLClass">2.1.3 ContentAsXML Class</a></li>
            </ul></li>
          <li><a href="#DoctypeDeclClass">2.2 DoctypeDecl Class</a></li>
        </ul></li>
      <li><a href="#properties">Properties</a> <ul>
          <li><a href="#bytesProperty">3.1 bytes Property</a></li>
          <li><a href="#characterEncodingProperty">3.2
          characterEncoding</a></li>
          <li><a href="#charsProperty">3.3 chars Property</a></li>
          <li><a href="#declaredEncodingProperty">3.4 declaredEncoding
          Property</a></li>
          <li><a href="#doctypeNameProperty">3.5 doctypeName Property</a></li>
          <li><a href="#dtDeclProperty">3.6 dtDecl Property</a></li>
          <li><a href="#internalSubsetProperty">3.7 internalSubset
          Property</a></li>
          <li><a href="#leadingMiscProperty">3.8 leadingMisc Property</a></li>
          <li><a href="#publicIdProperty">3.9 publicId Property</a></li>
          <li><a href="#restProperty">3.10 rest Property</a></li>
          <li><a href="#standaloneProperty">3.11 standalone Property</a></li>
          <li><a href="#systemIdProperty">3.12 systemId Property</a></li>
          <li><a href="#versionProperty">3.13 version Property</a></li>
        </ul></li>
      <li><a href="#scenarios">Usage scenarios</a></li>
      <li><a href="#limitations">Limitations of the vocabulary</a></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="#dom-mapping">Mapping between <acronym>DOM</acronym> and Content-in-RDF properties</a></li>
      <li><a href="#references">References</a></li>
      <li><a href="#contributors">Contributors</a></li>
      <li><a href="#history">Document Changes</a></li>
    </ol> <!-- end toc --> <hr /> <h2><a id="introduction" name="introduction">1
  Introduction</a></h2> <p>This document is the specification for a vocabulary
  to represent Content in the Resource Description Framework
  (<acronym>RDF</acronym>). There is a wide variety of scenarios (see section
  below) where a representation of any type of content, either on the Web or in
  any local storage media, is necessary. This specification provides an
  <acronym>RDF</acronym> application that allows to present semantically such
  content. The vocabulary is built in a flexible manner, thus there are no
  limitations known at the time of writing this specification. It also provides
  opportunities for extensions to match particular needs of its users.</p>
  <p>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>The terms defined by this document can be used as part of the <a href="http://www.w3.org/WAI/intro/earl">W3C Evaluation And Report Language (<acronym>EARL</acronym>)</a> and in other contexts too. <a href="http://www.w3.org/TR/EARL10-Guide/">Developer Guide for Evaluation and Report Language (EARL) 1.0</a> explains how to implement and use EARL, including conformance requirements for software tools.</p>
  <p>Although the concepts of the Semantic Web are simple, their
  abstraction with <acronym>RDF</acronym> is known to bring difficulties to
  beginners. It is recommended to read carefully the aforementioned references
  and other tutorials found on the Web. It must be also borne in mind that
  <acronym>RDF</acronym> is primarily targeted to be machine processable, and
  therefore, some of its expressions are not very intuitive for developers used
  to work with <acronym>XML</acronym> only. The examples will be serialized
  using the abbreviated <acronym>RDF</acronym>/<acronym>XML</acronym>
  notation.</p> <p>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> <p>For
  limitations of this vocabulary, see <a href="#limitations">section 5</a>.</p>
  <h3><a id="namespaces" name="namespaces">1.1 Namespaces</a></h3> <p><a
  href="#tab-namespaces">Table 1</a> presents the namespaces typically used by
  this vocabulary. The core namespace has the <acronym
  title="Uniform Resource Identifier">URI</acronym>
  <code>http://www.w3.org/2011/content#</code> and the prefix <code>cnt</code>.
  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.</p>
  <table id="tab-namespaces">
      <caption>Table 1: namespaces used by this document.</caption>
      <thead>
        <tr>
          <th>Namespace prefix</th>
          <th>Namespace <acronym>URI</acronym></th>
          <th>Description</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td scope="row"><code>cnt</code></td>
          <td><code>http://www.w3.org/2011/content#</code></td>
          <td>Namespace for Representing Content in <acronym>RDF</acronym>.</td>
        </tr>
        <tr>
          <td scope="row"><code>dct</code></td>
          <td><code>http://purl.org/dc/terms/</code></td>
          <td>Namespace for Dublin Core Metadata Terms.</td>
        </tr>
        <tr>
          <td><code>owl</code></td>
          <td><code>http://www.w3.org/2002/07/owl#</code></td>
          <td>Namespace for <acronym>OWL</acronym> [<a
          href="#ref-owl">OWL</a>].</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>
      </tbody>
    </table> <h3><a id="use-cases" name="use-cases">1.2 Use cases</a></h3> <p>As
  stated earlier, this framework is designed in an open way to facilitate
  different implementation scenarios. The origin of the application comes from
  vocabularies describing testing scenarios like the Evaluation And Report
  Language (<acronym>EARL</acronym>) [<a href="#ref-earl">EARL</a>]. Typical
  applications could be:</p> <ul>
      <li>Applications dealing with retrieval, editing and storage of content.
      For example, an archiving application could store in a database annotated
      media content that includes a serialization of the media files with this
      vocabulary.</li>
      <li>Applications dealing with the exchange of text documents and other
      types of media, like Web Services. For example, an <acronym
      title="Asynchronous JavaScript and XML">AJAX</acronym> application could
      exchange document fragments and images with a Web server to react to
      different user actions.</li>
      <li>Applications dealing with the testing and/or repair of content. For
      example, an accessibility testing tool could store together with the
      results of a compliance test, the tested Web resources to ensure that the
      correct version of the tested subject is available to the developers.</li>
    </ul> <!-- end intro --> <h2><a id="classes" name="classes">2
  Classes</a></h2> <p>This section presents a description of the classes of this
  <acronym title="Resource Description Framework">RDF</acronym> vocabulary. We
  present every class together with its subclasses. We also include whenever
  relevant short snippets and examples.</p> <h3><a id="ContentClass"
  name="ContentClass">2.1 Content Class</a></h3>

<p class="note">[Editor's note: The Working Group has introduced the use of the properties <code>dct:hasFormat</code> and <code>dct:isFormatOf</code> to allow different representations of the same content; comments on this approach is welcome.]</p>
   <p>The <code>cnt:Content</code>
  class is an overarching class for any content that could be found on the Web,
  in an Intranet or in local storage media, for example. It is recommended
  always to use one of its subclasses. There is no restriction within the
  vocabulary scope on what can be represented with this class: textual content,
  <acronym title="Extensible Markup Language">XML</acronym> files, binary files
  (<abbr>e.g.</abbr>, images or movies), <abbr>etc.</abbr></p> <p>There are
  three subclasses from the <code>Content</code> class: <a
  href="#ContentAsBase64Class"><code>cnt:ContentAsBase64</code></a>, <a
  href="#ContentAsTextClass"><code>cnt:ContentAsText</code></a> and <a
  href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a>.</p> <p>In order
  to connect resources with different <code>cnt:Content</code> sub-types with
  each other, use the <code>dct:hasFormat</code> and <code>dct:isFormatOf</code>
  properties to point to each other. <abbr>E.g.</abbr> if there is an
  <acronym>XML</acronym> resource transmitted via <acronym
  title="Hypertext Transfer Protocol">HTTP</acronym>, the original version would
  be a <code>cnt:ContentAsBase64</code> resource. But
  <code>cnt:ContentAsText</code> and <code>cnt:ContentAsXML</code> resource
  could also be created and point to the <code>cnt:ContentAsBase64</code>
  resource.</p> <h4><a id="ContentClassExamples"
  name="ContentClassExamples">Examples</a></h4> <div class="example">
  <p><strong>Example 2.1:</strong> This example shows how to relate derived
  resources to the original resource.</p> <pre>&lt;cnt:ContentAsBase64 rdf:ID="xml0"&gt;
  &lt;!-- ... --&gt;
  &lt;dct:isFormatOf rdf:resource="http://www.example.org/index.html"/&gt;
  &lt;dct:hasFormat rdf:resource="#xml1"/&gt;
  &lt;dct:hasFormat rdf:resource="#xml2"/&gt;
&lt;/cnt:ContentAsBase64&gt;

&lt;cnt:ContentAsText rdf:ID="xml1"&gt;
  &lt;!-- ... --&gt;
  &lt;dct:isFormatOf rdf:resource="http://www.example.org/index.html"/&gt;
  &lt;dct:hasFormat rdf:resource="#xml0"/&gt;
  &lt;dct:hasFormat rdf:resource="#xml2"/&gt;
&lt;/cnt:ContentAsText&gt;

&lt;cnt:ContentAsXML rdf:ID="xml2"&gt;
  &lt;!-- ... --&gt;
  &lt;dct:isFormatOf rdf:resource="http://www.example.org/index.html"/&gt;
  &lt;dct:hasFormat rdf:resource="#xml0"/&gt;
  &lt;dct:hasFormat rdf:resource="#xml1"/&gt;
&lt;/cnt:ContentAsXML&gt;</pre> </div>
 <h4><a id="ContentClassProperties"
  name="ContentClassProperties">Related Properties</a></h4> <ul>
      <li>Domain of: <ul>
          <li><a
          href="http://dublincore.org/documents/dcmi-terms/#terms-hasFormat"><code>dct:hasFormat
          <img alt="external link"
          src="http://www.w3.org/Icons/tr.png" /></code></a></li>
          <li><a
          href="http://dublincore.org/documents/dcmi-terms/#terms-isFormatOf"><code>dct:isFormatOf
          <img alt="external link"
          src="http://www.w3.org/Icons/tr.png" /></code></a></li>
        </ul></li>
      <li>Range of: none</li>
    </ul> <h4><a id="ContentAsBase64Class" name="ContentAsBase64Class">2.1.1
  ContentAsBase64 Class</a></h4> <p>The <code>cnt:ContentAsBase64</code> class
  is a subclass of the <a href="#ContentClass"><code>cnt:Content</code></a>
  class for Base64 encoded binary content (as defined by [<a
  href="#ref-rfc2045">RFC2045</a>]) and can be used for any type of content,
  although its more typical use case is for binary files.</p> <h5><a
  id="ContentAsBase64ClassProperties"
  name="ContentAsBase64ClassProperties">Related Properties</a></h5> <ul>
      <li>Domain of: <ul>
          <li><a href="#bytesProperty"><code>cnt:bytes</code></a></li>
          <li><a
          href="#characterEncodingProperty"><code>cnt:characterEncoding</code></a></li>
        </ul></li>
      <li>Range of: none</li>
    </ul> <h5><a id="ContentAsBase64ClassExamples"
  name="ContentAsBase64ClassExamples">Examples</a></h5> <div class="example">
  <p><strong>Example 2.2:</strong> This example displays the representation of
  the <a href="http://www.w3.org/Icons/w3c_home">W3C logo</a> as a
  <code>ContentAsBase64</code> resource. (Note: due to its length, the encoded
  string has been chunked until <code>{...}</code>.)</p> <pre>&lt;cnt:ContentAsBase64&gt;
  &lt;cnt:bytes&gt;77+9UE5HDQoaCgAAAA1JSERSAAAASAAAADAIAwAAAO+{...}&lt;/cnt:bytes&gt;
  &lt;dct:isFormatOf rdf:resource="http://www.w3.org/Icons/w3c_home.png"/&gt;
&lt;/cnt:ContentAsBase64&gt;</pre> </div> <h4><a id="ContentAsTextClass"
  name="ContentAsTextClass">2.1.2 ContentAsText Class</a></h4> <p>The
  <code>cnt:ContentAsText</code> class is a subclass of the <a
  href="#ContentClass"><code>cnt:Content</code></a> class for any type of
  textual content.</p> <h5><a id="ContentAsTextClassProperties"
  name="ContentAsTextClassProperties">Related Properties</a></h5> <ul>
      <li>Domain of: <ul>
          <li><a href="#charsProperty"><code>cnt:chars</code></a></li>
          <li><a
          href="#characterEncodingProperty"><code>cnt:characterEncoding</code></a></li>
        </ul></li>
      <li>Range of: none</li>
    </ul> <h5><a id="ContentAsTextClassExamples"
  name="ContentAsTextClassExamples">Examples</a></h5> <div class="example">
  <p><strong>Example 2.3:</strong> The following example represents a Cascading
  Style Sheet (<acronym>CSS</acronym>) file as a <code>ContentAsText</code>
  resource.</p> <pre>&lt;cnt:ContentAsText&gt;
  &lt;cnt:characterEncoding&gt;UTF-8&lt;/cnt:characterEncoding&gt;
  &lt;cnt:chars&gt;body {
  color: #000;
  background: #fff
}
h1 {
  font-size: 1.6em
}
h2 {
  font-size: 1.3em
}&lt;/cnt:chars&gt;
  &lt;dct:isFormatOf rdf:resource="http://example.org/example.css"/&gt;
&lt;/cnt:ContentAsText&gt;</pre> </div> <h4><a id="ContentAsXMLClass"
  name="ContentAsXMLClass">2.1.3 ContentAsXML Class</a></h4> <p>The
  <code>cnt:ContentAsXML</code> class is a subclass of the <a
  href="#ContentClass"><code>cnt:Content</code></a> class only for wellformed
  <acronym title="Extensible Markup Language">XML</acronym> content.</p> <h5><a
  id="ContentAsXMLClassProperties" name="ContentAsXMLClassProperties">Related
  Properties</a></h5> <ul>
      <li>Domain of: <ul>
          <li><a
          href="#characterEncodingProperty"><code>cnt:characterEncoding</code></a></li>
          <li><a
          href="#declaredEncodingProperty"><code>cnt:declaredEncoding</code></a></li>
          <li><a href="#dtDeclProperty"><code>cnt:dtDecl</code></a></li>
          <li><a
          href="#leadingMiscProperty"><code>cnt:leadingMisc</code></a></li>
          <li><a href="#restProperty"><code>cnt:rest</code></a></li>
          <li><a href="#standaloneProperty"><code>cnt:standalone</code></a></li>
          <li><a href="#versionProperty"><code>cnt:version</code></a></li>
        </ul></li>
      <li>Range of: none</li>
    </ul> <p>See the <a href="#dom-mapping">Mapping between the Document Object
  Model (<acronym>DOM</acronym>) and the Content-in-RDF vocabulary</a>.</p>
  <h5><a id="ContentAsXMLClassExamples"
  name="ContentAsXMLClassExamples">Examples</a></h5> <div class="example">
  <p><strong>Example 2.4:</strong> The <acronym
  title="Extensible Hypertext Markup Language">XHTML</acronym> page with the
  following source code:</p> <pre>&lt;html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"&gt;
  &lt;head&gt;
    &lt;title&gt;The title&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;
    &lt;p&gt;Some paragraph.&lt;/p&gt;
  &lt;/body&gt;
&lt;/html&gt;</pre> <p>could be represented as this <code>ContentAsXML</code>
  resource.</p> <pre>&lt;cnt:ContentAsXML&gt;
  &lt;cnt:rest rdf:parseType="Literal"&gt;&lt;html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"&gt;
  &lt;head&gt;
    &lt;title&gt;The title&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;
    &lt;p&gt;Some paragraph.&lt;/p&gt;
  &lt;/body&gt;
&lt;/html&gt;&lt;/cnt:rest&gt;
  &lt;dct:isFormatOf rdf:resource="http://example.org/example203.html"/&gt;
&lt;/cnt:ContentAsXML&gt;</pre> </div> <p>For the use of
  <code>leadingMisc</code> and <code>dtDecl</code> see <a
  href="#example">Appendix A: A practical example</a>.</p> <h3><a
  id="DoctypeDeclClass" name="DoctypeDeclClass">2.2 DoctypeDecl Class</a></h3>
  <p>A document type declaration. This class is normally used in conjunction
  with the <a href="#ContentAsXMLClass"><code>ContentAsXML</code></a> class,
  when the corresponding <acronym
  title="Extensible Markup language">XML</acronym> resource contains a document
  type declaration. The relation is expressed via the <code>dtDecl</code>
  property.</p> <h4><a id="DoctypeDeclClassProperties"
  name="DoctypeDeclClassProperties">Related Properties</a></h4> <ul>
      <li>Domain of: <ul>
          <li><a
          href="#doctypeNameProperty"><code>cnt:doctypeName</code></a></li>
          <li><a
          href="#internalSubsetProperty"><code>cnt:internalSubset</code></a></li>
          <li><a href="#publicIdProperty"><code>cnt:publicId</code></a></li>
          <li><a href="#systemIdProperty"><code>cnt:systemId</code></a></li>
        </ul></li>
      <li>Range of: <ul>
          <li><a href="#dtDeclProperty"><code>cnt:dtDecl</code></a></li>
        </ul></li>
    </ul> <p>See the <a href="#dom-mapping">Mapping between the Document Object
  Model (<acronym>DOM</acronym>) and the Content-in-RDF vocabulary</a>.</p>
  <h4><a id="DoctypeDeclClassExamples"
  name="DoctypeDeclClassExamples">Examples</a></h4> <div class="example">
  <p><strong>Example 2.6:</strong> A typical <acronym
  title="Extensible Hypertext Markup Language">XHTML</acronym> 1.0 Strict
  document type declaration:</p> <pre>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&gt;</pre> <p>could be
  represented as the following <code>DoctypeDecl</code> resource:</p> <pre>&lt;cnt:DoctypeDecl rdf:ID="dtd0"&gt;
  &lt;cnt:doctypeName&gt;html&lt;/cnt:doctypeName&gt;
  &lt;cnt:publicId&gt;-//W3C//DTD XHTML 1.0 Strict//EN&lt;/cnt:publicId&gt;
  &lt;cnt:systemId&gt;http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd&lt;/cnt:systemId&gt;
&lt;/cnt:DoctypeDecl&gt;</pre> </div> <!-- end Classes --> <h2><a
  id="properties" name="properties">3 Properties</a></h2> <p>This section
  presents a description of the properties of this <acronym
  title="Resource Description Framework">RDF</acronym> vocabulary.</p> <h3><a
  id="bytesProperty" name="bytesProperty">3.1 bytes Property</a></h3>
  <p>Character string representing the Base64 encoded byte sequence of the given
  content.</p> <dl>
      <dt>Domain:</dt>
      <dd><a
      href="#ContentAsBase64Class"><code>cnt:ContentAsBase64</code></a></dd>
      <dt>Range:</dt>
      <dd>Base64 encoded bytes
      (<code>http://www.w3.org/2001/XMLSchema#base64Binary</code>)</dd>
    </dl> <h3><a id="characterEncodingProperty"
  name="characterEncodingProperty">3.2 characterEncoding Property</a></h3>
  <p>The character encoding.</p> <ul>
      <li>When used with <code>ContentAsBase64</code>: If the byte sequence was
      created from a given character sequence this property can be used to store
      the character encoding that was applied to create the byte sequence.</li>
      <li>When used with <code>ContentAsText</code>: If the character sequence
      was created from a given byte sequence this property can be used to store
      the character encoding that was applied to create the character
      sequence.</li>
      <li>When used with <code>ContentAsXML</code>: If the parser's input
      character stream was created from a given byte stream this property can be
      used to store the character encoding that was applied to create the
      character stream. <strong>Note:</strong> This is the <strong>used</strong>
      character encoding, not the one declared in an <acronym
      title="Extensible Markup Language">XML</acronym> declaration.</li>
    </ul><dl>
      <dt>Domain:</dt>
      <dd><a href="#ContentClass"><code>cnt:Content</code></a></dd>
      <dt>Range:</dt>
      <dd>Literal</dd>
    </dl> <h3><a id="charsProperty" name="charsProperty">3.3 chars
  Property</a></h3> <p>The character sequence of the given content.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#ContentAsTextClass"><code>cnt:ContentAsText</code></a></dd>
      <dt>Range:</dt>
      <dd>Literal</dd>
    </dl> <h3><a id="declaredEncodingProperty"
  name="declaredEncodingProperty">3.4 declaredEncoding Property</a></h3> <p>The
  character encoding specified in the <acronym
  title="Extensible Markup Language">XML</acronym> declaration.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></dd>
      <dt>Range:</dt>
      <dd>Literal</dd>
    </dl> <h3><a id="doctypeNameProperty" name="doctypeNameProperty">3.5
  doctypeName Property</a></h3> <p>The document type name.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></dd>
      <dt>Range:</dt>
      <dd>Literal</dd>
    </dl> <h3><a id="dtDeclProperty" name="dtDeclProperty">3.6 dtDecl
  Property</a></h3> <p>This property relates an <acronym
  title="Extensible Markup Language">XML</acronym> Content to its Document Type
  Declaration.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></dd>
      <dt>Range:</dt>
      <dd><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></dd>
    </dl> <h3><a id="internalSubsetProperty" name="internalSubsetProperty">3.7
  internalSubset Property</a></h3> <p>The internal subset of a document type
  declaration.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></dd>
      <dt>Range:</dt>
      <dd>Literal</dd>
    </dl> <h3><a id="leadingMiscProperty" name="leadingMiscProperty">3.8
  leadingMisc Property</a></h3> <p>The part of the <acronym
  title="Extensible Markup Language">XML</acronym> information items
  (whitespace, comments and processing instructions) following the
  <acronym>XML</acronym> declaration and preceding the document type declaration
  if there is one.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></dd>
      <dt>Range:</dt>
      <dd><acronym>XML</acronym> Literal</dd>
    </dl> <h3><a id="publicIdProperty" name="publicIdProperty">3.9 publicId
  Property</a></h3> <p>The formal public identifier of a document type
  declaration.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></dd>
      <dt>Range:</dt>
      <dd>Literal</dd>
    </dl> <h3><a id="restProperty" name="restProperty">3.10 rest
  Property</a></h3> <ul>
      <li>The part of the <acronym
      title="Extensible Markup Language">XML</acronym> information items
      following the document type declaration if there is a document type
      declaration, or</li>
      <li>the part following the <acronym>XML</acronym> declaration if there is
      no document type declaration, or</li>
      <li>the whole <acronym>XML</acronym> information items if there is neither
      <acronym>XML</acronym> declaration nor document type declaration.</li>
    </ul> <p>It contains comments, processing instructions and the root
  element.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></dd>
      <dt>Range:</dt>
      <dd><acronym>XML</acronym> Literal</dd>
    </dl> <h3><a id="standaloneProperty" name="standaloneProperty">3.11
  standalone Property</a></h3> <p>The standalone document declaration.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></dd>
      <dt>Range:</dt>
      <dd>Literal</dd>
    </dl> <h3><a id="systemIdProperty" name="systemIdProperty">3.12 systemId
  Property</a></h3> <p>The system identifier of a document type declaration.</p>
  <dl>
      <dt>Domain:</dt>
      <dd><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></dd>
      <dt>Range:</dt>
      <dd>Literal typed as URI
      (<code>http://www.w3.org/2001/XMLSchema#anyURI</code>)</dd>
    </dl> <h3><a id="versionProperty" name="versionProperty">3.13 version
  Property</a></h3> <p>The <acronym
  title="Extensible Markup Language">XML</acronym> version specified in the
  <acronym>XML</acronym> declaration.</p> <dl>
      <dt>Domain:</dt>
      <dd><a href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></dd>
      <dt>Range:</dt>
      <dd>Literal</dd>
    </dl> <!-- end Properties --> <h2><a id="scenarios" name="scenarios">5 Usage
  scenarios</a></h2> <p>We have identified some situations to make clear when to
  create which type of content resources. The following are only recommendations
  and are non-normative:</p> <h3><a id="situationA" name="situationA">Situation
  A: byte sequence of non-text content</a></h3> <p>This includes images,
  multimedia, or other non-text resources. The byte sequence is recorded in
  Base64 format and represented as a literal using the <code>cnt:bytes</code>
  property of the <code>cnt:ContentAsBase64</code>. Non-text content should not
  be represented using <code>cnt:ContentAsText</code>.</p> <h3><a
  id="situationB" name="situationB">Situation B: byte sequence of text content
  with appropriate character encoding information</a></h3> <p>This includes
  <acronym title="Hypertext Markup Language">HTML</acronym>, <acronym
  title="Cascading Style Sheets">CSS</acronym>, client-side script, or other
  text-based resources. Given the byte sequence of text content
  (<var>byteSeq</var>) received from a Web server and an appropriate character
  encoding (<var>ce</var>). <var>byteSeq</var> is recorded in Base64 format and
  represented as a literal using the <code>cnt:bytes</code> property of the
  <code>cnt:ContentAsBase64</code>.</p> <p>After transforming the
  <var>byteSeq</var> to a character sequence <var>charSeq</var> using character
  encoding <var>ce</var>, <var>charSeq</var> is represented as a literal using
  the <code>cnt:chars</code> property of the <code>cnt:ContentAsText</code> and
  <code>ce</code> as a literal usind the <code>cnt:characterEncoding</code>
  property.</p> <h3><a id="situationC" name="situationC">Situation C: byte
  sequence of text content with inappropriate character encoding
  information</a></h3> <p>Given the byte sequence of text content
  (<var>byteSeq</var>) received from a Web server and an inappropriate character
  encoding (<var>ce</var>). <var>byteSeq</var> is recorded in Base64 format and
  represented as a literal using the <code>cnt:bytes</code> property of the
  <code>cnt:ContentAsBase64</code>. Because transforming <var>byteSeq</var> to a
  character sequence <var>charSeq</var> using character encoding <var>ce</var>
  fails, no <code>cnt:ContentAsText</code> resource can be created.</p> <h3><a
  id="situationD" name="situationD">Situation D: character sequence of text
  content with appropriate character encoding information</a></h3> <p>Given the
  character sequence of text content (<var>charSeq</var>) created in memory and
  an appropriate character encoding (<var>ce</var>). A
  <code>cnt:ContentAsText</code> resource may be created with a
  <code>cnt:chars</code> property with an object literal created from
  <code>charSeq</code>. After transforming <var>charSeq</var> to byte sequence
  <var>byteSeq</var> using character encoding <var>ce</var>, a
  <code>cnt:ContentAsBase64</code> resource may be created with
  <code>cnt:bytes</code> property with an object literal <var>byteSeq</var> and
  <code>cnt:characterEncoding</code> property with an object literal
  <var>ce</var>.</p> <h3><a id="situationE" name="situationE">Situation E: byte
  sequence of <acronym title="Extensible Markup Language">XML</acronym> content
  with appropriate character encoding information</a></h3> <p>Given the byte
  sequence of wellformed <acronym>XML</acronym> content (<var>byteSeq</var>)
  received from a Web server and an appropriate character encoding
  (<var>ce</var>). <code>cnt:ContentAsBase64</code> and
  <code>cnt:ContentAsText</code> resources may be created as in situation B.
  Additionally, an <code>cnt:ContentAsXML</code> resource may be created.</p>
  <h3><a id="situationF" name="situationF">Situation F: Document Object Model
  (<acronym>DOM</acronym>) changed in memory</a></h3> <p>Given a
  <acronym>DOM</acronym> Document in memory, originally created by parsing some
  <acronym>XML</acronym> source, but afterwards changed by
  <acronym>DOM</acronym> operations. A <code>cnt:XMLDecl</code> resource may be
  created from the information in the Document node itself (version,
  declaredEncoding and standalone), and a <code>cnt:DoctypeDecl</code> resource
  from the information in the DocumentType node. A <code>cnt:ContentAsXML</code>
  resource may be created after serializing the relevant child nodes of the
  Document node to create object literals for <code>cnt:leadingMisc</code>
  (serialize Comment and ProcessingInstruction nodes preceding a DocumentType
  node) and <code>cnt:rest</code> (serialize nodes following a DocumentType
  node). See the <a href="#dom-mapping">Mapping between the Document Object
  Model (<acronym>DOM</acronym>) and Content-in-RDF properties</a>.</p> <!-- end Usage scenarios -->
  <h2><a id="limitations" name="limitations">6 Limitations of the
  vocabulary</a></h2> <p>The vocabulary provides a framework that allows the
  representation of any type of content. Of course, there are many possibilities
  for extensions that will allow the inclusion of additional metadata, like,
  <abbr>e.g.</abbr>, that included in some multimedia formats. Typical scenarios
  for extensions could be:</p> <ul>
      <li>Classes to specify the <a href="http://www.w3.org/DOM/DOMTR">Document
      Object Model (<acronym>DOM</acronym>)</a> of <acronym>XML</acronym> or
      HTML documents.</li>
      <li>Classes to specify the metadata of multimedia content like audio or
      image files.</li>
      <li>Properties to ensure the integrity of data by providing some kind of
      checksum algorithm.</li>
    </ul> <p>However, at the point of writing this specification, the Working
  Group has decided to provide the basic framework that will support the
  immediate needs of vocabularies using this specification like the Evaluation
  and Report Language (<acronym>EARL</acronym>) [<a href="#ref-earl">EARL</a>],
  leaving the room open for further extensions as new use cases are presented to
  us.</p> <!-- end Limitations --> <h2><a id="example" name="example">Appendix
  A: A practical example</a></h2> <p>To understand the versatility of the
  vocabulary, let us assume we have a given <acronym
  title="Extensible Hypertext Markup Language">XHTML</acronym> page containing
  an <acronym title="Extensible Markup Language">XML</acronym> declaration, a
  comment preceding a document type declaration and some
  <acronym>XHTML</acronym> elements.</p> <div class="example">
  <p><strong>Example 2.6:</strong> A typical <acronym>XHTML</acronym> page.</p>
  <pre>&lt;?xml version="1.0" encoding="UTF-8" standalone="no" ?&gt;
&lt;!-- this is a comment --&gt;
&lt;!DOCTYPE html "-//W3C//DTD XHTML 1.0 Strict//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&gt;
&lt;html xmlns="http://www.w3.org/1999/xhtml" lang="en"&gt;
  &lt;head&gt;
    &lt;title&gt;The title&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;
    &lt;p&gt;Some paragraph.&lt;/p&gt;
  &lt;/body&gt;
&lt;/html&gt;</pre> <p>This page could be represented as simple <a
  href="#ContentAsTextClass"><code>ContentAsText</code></a>:</p> <pre>&lt;rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:cnt="http://www.w3.org/2011/content#"&gt;

  &lt;cnt:ContentAsText&gt;
    &lt;cnt:chars&gt;&amp;lt;?xml version="1.0" encoding="UTF-8" standalone="no" ?&amp;gt;
&amp;lt;!-- this is a comment --&amp;gt;
&amp;lt;!DOCTYPE html "-//W3C//DTD XHTML 1.0 Strict//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&amp;gt;
&amp;lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"&amp;gt;
  &amp;lt;head&amp;gt;
    &amp;lt;title&amp;gt;The title&amp;lt;/title&amp;gt;
  &amp;lt;/head&amp;gt;
  &amp;lt;body&amp;gt;
    &amp;lt;p&amp;gt;Some paragraph.&amp;lt;/p&amp;gt;
  &amp;lt;/body&amp;gt;
&amp;lt;/html&amp;gt;&lt;/cnt:chars&gt;
    &lt;dct:isFormatOf rdf:resource="http://example.org/example207.html"/&gt;
  &lt;/cnt:ContentAsText&gt;

&lt;/rdf:RDF&gt;</pre> <p>or likewise as <a
  href="#ContentAsXMLClass"><code>ContentAsXML</code></a>. As the comment
  <code>&lt;!-- this is a comment --&gt;</code> precedes the document type
  declaration a <code>cnt:leadingMisc</code> property is created with its object
  literal containing the comment. The document type declaration is modelled as a
  <code>DoctypeDecl</code> resource and refered to from the
  <code>cnt:ContentAsXML</code> resource by the <code>cnt:dtDecl</code>
  property.</p> <pre>&lt;rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:cnt="http://www.w3.org/2011/content#"
    xml:base="http://example.org/example208.html"&gt;

  &lt;cnt:DoctypeDecl rdf:ID="dtd0"&gt;
    &lt;cnt:systemId&gt;http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd&lt;/cnt:systemId&gt;
    &lt;cnt:publicId&gt;-//W3C//DTD XHTML 1.0 Strict//EN&lt;/cnt:publicId&gt;
    &lt;cnt:doctypeName&gt;html&lt;/cnt:doctypeName&gt;
  &lt;/cnt:DoctypeDecl&gt;

  &lt;cnt:ContentAsXML&gt;
    &lt;cnt:version&gt;1.0&lt;/cnt:version&gt;
    &lt;cnt:declaredEncoding&gt;UTF-8&lt;/cnt:declaredEncoding&gt;
    &lt;cnt:standalone&gt;no&lt;/cnt:standalone&gt;
    &lt;cnt:leadingMisc rdf:parseType="Literal"&gt;&lt;!-- this is a comment --&gt;&lt;/cnt:leadingMisc&gt;
    &lt;cnt:dtDecl rdf:resource="#dtd0" /&gt;
    &lt;cnt:rest rdf:parseType="Literal"&gt;&lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"&gt;
  &lt;head&gt;
    &lt;title&gt;The title&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;
    &lt;p&gt;Some paragraph.&lt;/p&gt;
  &lt;/body&gt;
&lt;/html&gt;&lt;/cnt:rest&gt;
    &lt;dct:isFormatOf rdf:resource="http://example.org/example208.html"/&gt;
  &lt;/cnt:ContentAsXML&gt;

&lt;/rdf:RDF&gt;</pre> </div> <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 Content-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-Content">
          <td scope="row"><code><a
          href="#ContentClass">cnt:Content</a></code></td>
          <td>Content</td>
          <td>The content.</td>
          <td><a href="#ContentAsBase64Class">cnt:ContentAsBase64</a>, <a
          href="#ContentAsTextClass">cnt:ContentAsText</a>, <a
          href="#ContentAsXMLClass">cnt:ContentAsXML</a></td>
          <td></td>
        </tr>
        <tr id="terms-classes-ContentAsBase64">
          <td scope="row"><code><a
          href="#ContentAsBase64Class">cnt:ContentAsBase64</a></code></td>
          <td>Base64 Content</td>
          <td>The base64 encoded content (can be used for binary content).</td>
          <td>-</td>
          <td><a href="#bytesProperty">cnt:bytes</a>, <a
          href="#characterEncodingProperty">cnt:characterEncoding</a></td>
        </tr>
        <tr id="terms-classes-ContentAsText">
          <td scope="row"><code><a
          href="#ContentAsTextClass">cnt:ContentAsText</a></code></td>
          <td>Text Content</td>
          <td>The text content (can be used for text content).</td>
          <td>-</td>
          <td><a href="#charsProperty">cnt:chars</a>, <a
          href="#characterEncodingProperty">cnt:characterEncoding</a></td>
        </tr>
        <tr id="terms-classes-ContentAsXML">
          <td scope="row"><code><a
          href="#ContentAsXMLClass">cnt:ContentAsXML</a></code></td>
          <td><acronym title="Extensible Markup Language">XML</acronym>
          content</td>
          <td>The <acronym>XML</acronym> content (can be used for
          <acronym>XML</acronym>-wellformed content).</td>
          <td>-</td>
          <td><a href="#versionProperty">cnt:version</a>, <a
          href="#declaredEncodingProperty">cnt:declaredEncoding</a>, <a
          href="#standaloneProperty">cnt:standalone</a>, <a
          href="#leadingMiscProperty">cnt:leadingMisc</a>, <a
          href="#dtDeclProperty">cnt:dtDecl</a>, <a
          href="#restProperty">cnt:rest</a>, <a
          href="#characterEncodingProperty">cnt:characterEncoding</a></td>
        </tr>
        <tr id="terms-classes-DoctypeDecl">
          <td scope="row"><code><a
          href="#DoctypeDeclClass">cnt:DoctypeDecl</a></code></td>
          <td>Document type declaration</td>
          <td>The document type declaration.</td>
          <td>-</td>
          <td><a href="#doctypeNameProperty">cnt:doctypeName</a>, <a
          href="#internalSubsetProperty">cnt:internalSubset</a>, <a
          href="#publicIdProperty">cnt:publicId</a>, <a
          href="#systemIdProperty">cnt:systemId</a></td>
        </tr>
      </tbody>
    </table> <h3><a id="terms-properties"
  name="terms-properties">Properties</a></h3> <table>
      <caption>Properties in the Content-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-bytes">
          <td scope="row"><code><a
          href="#bytesProperty">cnt:bytes</a></code></td>
          <td>Base64 encoded byte sequence</td>
          <td>The Base64 encoded byte sequence of the content.</td>
          <td><a
          href="#ContentAsBase64Class"><code>cnt:ContentAsBase64</code></a></td>
          <td><code>http://www.w3.org/2001/XMLSchema#base64Binary</code></td>
        </tr>
        <tr id="terms-properties-characterEncoding">
          <td scope="row"><code><a
          href="#characterEncodingProperty">cnt:characterEncoding</a></code></td>
          <td>Character encoding</td>
          <td>The character encoding used to create a character sequence from a
          byte sequence or vice versa.</td>
          <td><a href="#ContentClass"><code>cnt:Content</code></a></td>
          <td>RDF Literal</td>
        </tr>
        <tr id="terms-properties-chars">
          <td scope="row"><code><a
          href="#charsProperty">cnt:chars</a></code></td>
          <td>Character sequence</td>
          <td>The character sequence of the text content.</td>
          <td><a
          href="#ContentAsTextClass"><code>cnt:ContentAsText</code></a></td>
          <td>RDF Literal</td>
        </tr>
        <tr id="terms-properties-declaredEncoding">
          <td scope="row"><code><a
          href="#declaredEncodingProperty">cnt:declaredEncoding</a></code></td>
          <td><acronym>XML</acronym> character encoding</td>
          <td>The character encoding declared in the <acronym>XML</acronym>
          declaration.</td>
          <td><a
          href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></td>
          <td>RDF Literal</td>
        </tr>
        <tr id="terms-properties-doctypeName">
          <td scope="row"><code><a
          href="#doctypeNameProperty">cnt:doctypeName</a></code></td>
          <td>Document type name</td>
          <td>The document type name.</td>
          <td><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></td>
          <td>RDF Literal</td>
        </tr>
        <tr id="terms-properties-dtDecl">
          <td scope="row"><code><a
          href="#dtDeclProperty">cnt:dtDecl</a></code></td>
          <td>Document type declaration</td>
          <td>The document type declaration.</td>
          <td><a
          href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></td>
          <td><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></td>
        </tr>
        <tr id="terms-properties-internalSubset">
          <td scope="row"><code><a
          href="#internalSubsetProperty">cnt:internalSubset</a></code></td>
          <td>Internal <acronym title="Document Type Definition">DTD</acronym>
          subset</td>
          <td>The internal document type definition subset within the document
          type declarations.</td>
          <td><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></td>
          <td>RDF Literal</td>
        </tr>
        <tr id="terms-properties-leadingMisc">
          <td scope="row"><code><a
          href="#leadingMiscProperty">cnt:leadingMisc</a></code></td>
          <td><acronym>XML</acronym> leading misc</td>
          <td>The <acronym>XML</acronym> content preceding the document type
          declaration.</td>
          <td><a
          href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></td>
          <td>XML Literal</td>
        </tr>
        <tr id="terms-properties-publicId">
          <td scope="row"><code><a
          href="#publicIdProperty">cnt:publicId</a></code></td>
          <td>Public ID</td>
          <td>The document type declarations's public identifier.</td>
          <td><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></td>
          <td>RDF Literal</td>
        </tr>
        <tr id="terms-properties-rest">
          <td scope="row"><code><a href="#restProperty">cnt:rest</a></code></td>
          <td><acronym>XML</acronym> rest</td>
          <td>The <acronym>XML</acronym> content following the document type
          declaration.</td>
          <td><a
          href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></td>
          <td>XML Literal</td>
        </tr>
        <tr id="terms-properties-standalone">
          <td scope="row"><code><a
          href="#standaloneProperty">cnt:standalone</a></code></td>
          <td><acronym>XML</acronym> standalone document declaration</td>
          <td>The standalone declaration in the <acronym>XML</acronym>
          declaration.</td>
          <td><a
          href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></td>
          <td>RDF Literal</td>
        </tr>
        <tr id="terms-properties-systemId">
          <td scope="row"><code><a
          href="#systemIdProperty">cnt:systemId</a></code></td>
          <td>System ID</td>
          <td>The document type declarations's system identifier (typed:
          xsd:anyURI)</td>
          <td><a href="#DoctypeDeclClass"><code>cnt:DoctypeDecl</code></a></td>
          <td><code>http://www.w3.org/2001/XMLSchema#anyURI</code></td>
        </tr>
        <tr id="terms-properties-version">
          <td scope="row"><code><a
          href="#versionProperty">cnt:version</a></code></td>
          <td><acronym>XML</acronym> version</td>
          <td>The <acronym>XML</acronym> version declared in the
          <acronym>XML</acronym> declaration.</td>
          <td><a
          href="#ContentAsXMLClass"><code>cnt:ContentAsXML</code></a></td>
          <td>RDF Literal</td>
        </tr>
      </tbody>
    </table> <h2><a id="dom-mapping" name="dom-mapping">Appendix C: Mapping
  between the Document Object Model (<acronym>DOM</acronym>) and Content-in-RDF
  properties</a></h2> <table>
      <thead>
        <tr>
          <th><acronym>DOM</acronym> property</th>
          <th>Content-in-RDF property</th>
        </tr>
      </thead>
      <tbody>
        <tr>
          <td><code>Document.xmlVersion</code></td>
          <td><code>version</code></td>
        </tr>
        <tr>
          <td><code>Document.xmlEncoding</code></td>
          <td><code>declaredEncoding</code></td>
        </tr>
        <tr>
          <td><code>Document.xmlStandalone</code></td>
          <td><code>standalone</code></td>
        </tr>
        <tr>
          <td><code>Document.doctype</code></td>
          <td><code>dtDecl</code></td>
        </tr>
        <tr>
          <td><code>DocumentType.name</code></td>
          <td><code>doctypeName</code></td>
        </tr>
        <tr>
          <td><code>DocumentType.publicId</code></td>
          <td><code>publicId</code></td>
        </tr>
        <tr>
          <td><code>DocumentType.systemId</code></td>
          <td><code>systemId</code></td>
        </tr>
        <tr>
          <td><code>DocumentType.internalSubset</code></td>
          <td><code>internalSubset</code></td>
        </tr>
      </tbody>
    </table>

  <h2><a id="references" name="references">Appendix D: References</a></h2> <dl>
      <dt>[<a id="ref-earl" name="ref-earl">EARL</a>]</dt>
      <dd><a href="http://www.w3.org/TR/EARL10/">Evaluation and Report Language
      (<acronym>EARL</acronym>) 1.0 Schema</a>. W3C Working Draft 28 April
      2009.<br /><code>http://www.w3.org/TR/EARL10/</code></dd>
      <dt>[<a id="ref-rdf" name="ref-rdf">RDF</a>]</dt>
      <dd><a href="http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/">Resource
      Description Framework (<acronym>RDF</acronym>) Model and Syntax
      Specification</a>. W3C Recommendation, 22 February
      1999.<br /><code>http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/</code></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>. W3C Recommendation, 10 February
      2004.<br /><code>http://www.w3.org/TR/rdf-primer/</code></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>.
      W3C Recommendation 10 February
      2004.<br /><code>http://www.w3.org/TR/rdf-schema/</code></dd>
      <dt>[<a id="ref-rdf-xml" name="ref-rdf-xml">RDF-XML</a>]</dt>
      <dd><a
      href="http://www.w3.org/TR/rdf-syntax-grammar/"><acronym>RDF</acronym>/<acronym>XML</acronym>
      Syntax Specification (Revised)</a>. W3C Recommendation 10 February
      2004.<br /><code>http://www.w3.org/TR/rdf-syntax-grammar/</code></dd>
      <dt>[<a id="ref-rfc2119" name="ref-rfc2119">RFC2119</a>]</dt>
      <dd>Request for Comments: 2119. <a
      href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to
      Indicate Requirement Levels</a>, March 1997 (<acronym
      title="Internet Engineering Task Force">IETF</acronym>).<br /><code>http://www.ietf.org/rfc/rfc2119.txt</code></dd>
      <dt>[<a id="ref-rfc2045" name="ref-rfc2045">RFC2045</a>]</dt>
      <dd>Request for Comments: 2045. <a
      href="http://www.ietf.org/rfc/rfc2045.txt">Multipurpose Internet Mail
      Extensions (MIME) Part One: Format of Internet Message Bodies</a>,
      November 1996
      (<acronym>IETF</acronym>).<br /><code>http://www.ietf.org/rfc/rfc2045.txt</code></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-xml" name="ref-xml">XML</a>]</dt>
      <dd><a href="http://www.w3.org/TR/xml/">Extensible Markup Language
      (<acronym>XML</acronym>) 1.0 (Fifth Edition)</a>. W3C Recommendation 26
      November 2008.<br /><code>http://www.w3.org/TR/xml/</code></dd>
    </dl>

<h2><a name="contributors" id="contributors">Appendix E: Contributors</a></h2>
<p>Contributors to this Working Draft: Shadi Abou-Zahra, Philip Ackermann, Carlos Iglesias, Johannes Koch, Michael Squillace, and Carlos Velasco.</p>

<h2><a id="history" name="history">Appendix F: Document Changes</a></h2>
<p>The following is a list of substantial changes since the
<a href="http://www.w3.org/TR/2009/WD-Content-in-RDF10-20091029/">29 October
2009 Working Draft</a>:</p>
<ul>
  <li>removed <code>dct:source</code> from <code>Content</code> class</li>
  <li>added <code>dct:hasFormat</code> and <code>dct:isFormatOf</code> to <code>Content</code> class</li>
  <li>removed conformance section</li>
  <li>class and property tables corrected</li>
  <li>schema and schema references updated</li>
  <li>bytes property given a correct datatype</li>
  <li>minor style corrections</li>
</ul>

</body>
</html>