Another abandoned server code base... this is kind of an ancestor of taskrambler.
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.
 
 
 
 
 
 

1302 lines
63 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="application/xhtml+xml; charset=UTF-8" http-equiv="Content-Type" />
<title>Representing Content in RDF</title>
<style type="text/css">
.schema {
color: black;
background-color: #ccddcc;
}
.example {
margin: 1em 2em 1em 2em;
color: #000;
background-color: #fff;
padding: 0.5em;
border: 1px dotted #e63232;
}
.note {
background-color: #adff2f;
}
.keyword {
font-weight: bold;
font-style: italic;
}
pre {
border: 1px dotted #000;
color: #000;
background-color: #f4f3e7;
font-size: 110%;
}
table {
margin: 1ex 2%;
width: 90%;
border-collapse: collapse;
}
thead,tfoot,tbody,tr {
margin: 0;
padding: 0;
}
th,td {
margin: 0;
padding: 0.2em 1em;
border: solid 1px #000;
}
abbr,acronym {
font-weight: inherit;
font-style: normal;
border-bottom-width: 1px;
border-bottom-style: dotted;
border-bottom-color: inherit;
}
span.type {
font-family: monospace;
}
</style>
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD" />
</head>
<body>
<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">Representing Content in <acronym title="Resource Description Framework">RDF</acronym></a></h1>
<h2><a id="w3c-doctype" name="w3c-doctype"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 8 September 2008</a></h2>
<dl>
<dt>This version:</dt>
<dd><a href="http://www.w3.org/TR/2008/WD-Content-in-RDF-20080908">http://www.w3.org/TR/2008/WD-Content-in-RDF-20080908</a></dd>
<dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/Content-in-RDF/">http://www.w3.org/TR/Content-in-RDF/</a></dd>
<dt>Editors:</dt>
<dd>Johannes Koch, Fraunhofer Institute for Applied Information Technology (<acronym title="Fraunhofer Institute for Applied Information Technology">FIT</acronym>)</dd>
<dd>Carlos A Velasco, Fraunhofer Institute for Applied Information Technology (<acronym title="Fraunhofer Institute for Applied Information Technology">FIT</acronym>)</dd>
</dl>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2008 <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.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. <acronym title="World Wide Web Consortium">W3C</acronym> <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 <acronym title="Resource Description Framework">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 accessibility evaluation tools to record a representation of the assessed Web content in an <a href="http://www.w3.org/TR/EARL10-Schema/">Evaluation And Report Language (EARL) 1.0 Schema</a> evaluation report. The document contains introductory information on its usage and some examples.</p>
<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 <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
<p>This First Public Working Draft of the Representing Content in <acronym title="Resource Description Framework">RDF</acronym> document was published on 8 September 2008 by the <a href="http://www.w3.org/WAI/ER/">Evaluation and Repair Tools Working Group (ERT WG)</a>. It presents an RDF approach for recording different representations of content on the Web or in local storage media. This document is part of the <a href="http://www.w3.org/WAI/intro/earl.php">W3C Evaluation And Report Language (EARL)</a>. It is expected to be published as a W3C Working Group Note after further review and refinement.</p>
<p>The RDF terms defined by this document can be used to extend the <a href="http://www.w3.org/TR/EARL10-Schema/">Evaluation And Report Language (EARL) 1.0 Schema</a>, but can also be used separately to record different representations of content for any purpose. For example it can be used together with the <a href="http://www.w3.org/TR/HTTP-in-RDF/">HTTP Vocabulary in RDF</a> to describe Web content that has been retrieved from a server using specific HTTP headers. The Working Group believes that this document is fairly stable despite being a first public working draft. The group encourages feedback about the approach, as well as about the completeness and maturity of this document by developers and researchers who have interest in representing content in RDF format. Feedback from the <a href="http://www.w3.org/QA/IG/">W3C Quality Assurance Interest Group</a>, the <a href="http://www.w3.org/2001/sw/interest/">W3C Semantic Web Interest Group</a>, and the <a href="http://www.w3.org/2007/powder/">Protocol for Web Description Resources Working Group</a> is particularly welcome. Please send comments on this document by 29 September 2008 to the public mailing list of the working group <a href="mailto:public-wai-ert@w3.org">public-wai-ert@w3.org</a>. The <a href="http://lists.w3.org/Archives/Public/public-wai-ert/">archives of the working group mailing list</a> are publicly available.</p>
<p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> 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 was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. The group does not expect this document to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/32094/status" rel="disclosure">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 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p>
<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.3. Use Cases</a></li>
</ul>
</li>
<li><a href="#classesProperties">Vocabulary usage: classes and properties</a>
<ul>
<li><a href="#contentClass">2.1. Content class</a></li>
<li><a href="#base64ContentClass">2.2. Base64Content class</a></li>
<li><a href="#textContentClass">2.3. TextContent class</a></li>
<li><a href="#xmlContentClass">2.4. XMLContent class</a></li>
<li><a href="#xmlDeclClass">2.5. XMLDecl class</a></li>
<li><a href="#doctypeDeclClass">2.6. DoctypeDecl class</a></li>
<li><a href="#example">2.7. A practical example</a></li>
</ul>
</li>
<li><a href="#scenarios">Usage scenarios</a></li>
<li><a href="#extensions">Extensions to the vocabulary</a></li>
</ol>
<h3><a id="appendices" name="appendices">Appendices</a></h3>
<ol type="A">
<li><a href="#schema">Schema in <acronym title="Resource Description Framework">RDF</acronym>/<acronym title="Extensible Markup Language">XML</acronym></a></li>
<li><a href="#terms-Content">Vocabulary Terms</a></li>
<li><a href="#dom-mapping">Mapping between DOM and Content-in-RDF properties</a></li>
<li><a href="#history">Document Changes</a></li>
<li><a href="#references">References</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 <acronym title="Resource Description Framework">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 RDF 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 <acronym title="Extensible Markup Language">XML</acronym> <a href="#ref-xml">[XML]</a> and its associated technologies.</li>
<li>Basic knowledge about the Semantic Web and RDF. 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>Although the concepts of the Semantic Web are simple, their abstraction with RDF 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 XML only. The examples will be serialized using the abbreviated RDF/XML 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>
<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 (<code>rdfs</code> and <code>owl</code> namespaces are normally only used in the schema). The core namespace has the <acronym title="Uniform Resource Identifier">URI</acronym> <code>http://www.w3.org/2007/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: Representing Content in RDF namespaces.</caption>
<thead>
<tr>
<th>Namespace prefix</th>
<th>Namespace URI</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td scope="row"><code>cnt</code></td>
<td><code>http://www.w3.org/2007/content#</code></td>
<td>The default namespace for Representing Content in RDF.</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>Default RDF namespace [<a href="#ref-rdf">RDF</a>].</td>
</tr>
<tr>
<td scope="row"><code>rdfs</code></td>
<td><code>http://www.w3.org/2000/01/rdf-schema#</code></td>
<td>Default RDF schema namespace [<a href="#ref-rdfs">RDFS</a>].</td>
</tr>
<tr>
<td scope="row"><code>owl</code></td>
<td><code>http://www.w3.org/2002/07/owl#</code></td>
<td>Default <acronym title="Web Ontology Language">OWL</acronym> namespace [<a href="#ref-owl">OWL</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 <acronym title="Evaluation And Report Language">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>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><p>This list is not exclusive and several other scenarios could be developed.</p>
<!-- end intro --> <h2><a id="classesProperties" name="classesProperties">2. Vocabulary
usage: classes and properties</a></h2><p>This section presents a description of the
classes and properties of this <acronym>RDF</acronym> vocabulary. We present every class
together with its properties and subclasses. We also include whenever relevant short
snippets and examples.</p> <h3><a id="contentClass" name="contentClass">2.1. Content
class</a></h3><p>The <span class="type">Content</span> class is an over arching class
with no properties. It is recommended always to use one of its subclasses. A resource of
type <span class="type">Content</span> represents any content that could be found on the
Web, in an Intranet or in local storage media, for example. There is no restriction
within the vocabulary scope on what can be represented with this class: textual content,
binary files (e.g., images or movies), XML files, etc.</p> <p>There are three subclasses
from the <span class="type">Content</span> class: <a href="#base64ContentClass"><span
class="type">Base64Content</span></a>, <a href="#textContentClass"><span
class="type">TextContent</span></a> and <a href="#xmlContentClass"><span
class="type">XMLContent</span></a>.</p> <h3><a id="base64ContentClass"
name="base64ContentClass">2.2. Base64Content class</a></h3> <p>The <span
class="type">Base64Content</span> class is a subclass of the <a
href="#contentClass"><span class="type">Content</span></a> class. A resource of type
<span class="type">Base64Content</span> represents 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> <p>The following
property <strong>may</strong> appear in resources of type <span
class="type">Base64Content</span> (with a maximum cardinality of 1):</p> <dl>
<dt><var>characterEncoding</var></dt>
<dd>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.</dd>
</dl> <p>The following property <strong>must</strong> appear in resources of type
<span class="type">Base64Content</span>:</p> <dl>
<dt><var>bytes</var></dt>
<dd>Character string representing the Base64 encoded byte sequence of the given
content.</dd>
</dl> <div class="example"> <p><strong>Example 2.1:</strong> This example displays the
representation of the <a href="http://www.w3.org/Icons/w3c_home">W3C logo</a> as a <span
class="type">Base64Content</span> resource. (Note: due to its length, the encoded string
has been chunked until <code>{...}</code>.)</p> <pre>&lt;rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cnt="http://www.w3.org/2007/content#"&gt;
&lt;cnt:Base64Content rdf:about="http://www.w3.org/Icons/w3c_home.png"&gt;
&lt;cnt:bytes&gt;77+9UE5HDQoaCgAAAA1JSERSAAAASAAAADAIAwAAAO+{...}&lt;/cnt:bytes&gt;
&lt;/cnt:Base64Content&gt;
&lt;/rdf:RDF&gt;</pre> </div> <h3><a id="textContentClass" name="textContentClass">2.3.
TextContent class</a></h3> <p>The <span class="type">TextContent</span> class is a
subclass of the <a href="#contentClass"><span class="type">Content</span></a> class. A
resource of type <span class="type">TextContent</span> represents any type of textual
content.</p> <p>The following property <strong>may</strong> appear in resources of type
<span class="type">TextContent</span> (with a maximum cardinality of 1):</p> <dl>
<dt><var>characterEncoding</var></dt>
<dd>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.</dd>
</dl> <p>The following property <strong>must</strong> appear in resources of type
<span class="type">TextContent</span>:</p> <dl>
<dt><var>chars</var></dt>
<dd>Character string representing the character sequence of the given content.</dd>
</dl> <div class="example"> <p><strong>Example 2.2:</strong> The following example
represents a <acronym>CSS</acronym> file as a <span class="type">TextContent</span>
resource.</p> <pre>&lt;rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cnt="http://www.w3.org/2007/content#"&gt;
&lt;cnt:TextContent rdf:about="http://example.org/example.css"&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;/cnt:TextContent&gt;
&lt;/rdf:RDF&gt;</pre> </div> <h3><a id="xmlContentClass" name="xmlContentClass">2.4.
XMLContent class</a></h3> <p>The <span class="type">XMLContent</span> class is a
subclass of the <a href="#contentClass"><span class="type">Content</span></a> class. A
resource of type <span class="type">XMLContent</span> represents <acronym>XML</acronym>
content.</p> <p>The following properties <strong>may</strong> appear in resources of
type <span class="type">XMLContent</span> (with a maximum cardinality of 1):</p> <dl>
<dt><var>characterEncoding</var></dt>
<dd>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>XML</acronym> declaration.</dd>
<dt><var>xmlDecl</var></dt>
<dd>Property pointing to an <a href="#xmlDeclClass">XMLDecl</a> resource
representing the <acronym>XML</acronym> declaration.</dd>
<dt><var>xmlLeadingMisc</var></dt>
<dd>Property representing as an <acronym>XML</acronym> Literal the part of the
<acronym>XML</acronym> (comments and processing instructions) following the
<acronym>XML</acronym> declaration and preceding the document type declaration if
there is one.</dd>
<dt><var>doctypeDecl</var></dt>
<dd>Property pointing to a <a href="#doctypeDeclClass">DoctypeDecl</a> resource
representing the document type declaration.</dd>
</dl> <p>The following property <strong>must</strong> appear in resources of type
<span class="type">XMLContent</span>:</p> <dl>
<dt><var>xmlRest</var></dt>
<dd>Property representing as an <acronym>XML</acronym> Literal <ul>
<li>the part of the <acronym>XML</acronym> 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> if there is neither <acronym>XML</acronym>
declaration nor document type declaration.</li>
</ul> It contains comments, processing instructions and the root element.</dd>
</dl> <div class="example"> <p><strong>Example 2.3:</strong> The
<acronym>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 <span class="type">XMLContent</span>
resource.</p> <pre>&lt;rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cnt="http://www.w3.org/2007/content#"&gt;
&lt;cnt:XMLContent rdf:about="http://example.org/example203.html"&gt;
&lt;cnt:xmlRest 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:xmlRest&gt;
&lt;/cnt:XMLContent&gt;
&lt;/rdf:RDF&gt;</pre> </div> <p>For the use of <var>xmlDecl</var>,
<var>xmlLeadingMisc</var> and <var>doctypeDecl</var> see <a href="#example">2.7. A
practical example</a>.</p> <h3><a id="xmlDeclClass" name="xmlDeclClass">2.5. XMLDecl
class</a></h3> <p>A resource of type <span class="type">XMLDecl</span> represents an
<acronym>XML</acronym> declaration. This class is normally used in conjunction with the
<a href="#xmlContentClass"><span class="type">XMLContent</span></a> class, when the
corresponding <acronym>XML</acronym> file has an <acronym>XML</acronym> declaration. The
resources are linked via the <var>xmlDecl</var> property.</p> <p>The following
properties <strong>may</strong> appear in resources of type <span
class="type">XMLDecl</span>:</p> <dl>
<dt><var>xmlEncoding</var></dt>
<dd>Property representing the character encoding specified in the
<acronym>XML</acronym> declaration.</dd>
<dt><var>xmlStandalone</var></dt>
<dd>Property representing the standalone document declaration.</dd>
</dl> <p>The following property <strong>must</strong> appear in resources of type
<span class="type">XMLDecl</span>:</p> <dl>
<dt><var>xmlVersion</var></dt>
<dd>Property representing the <acronym>XML</acronym> version specified in the
<acronym>XML</acronym> declaration.</dd>
</dl> <div class="example"> <p><strong>Example 2.4:</strong> A typical
<acronym>XML</acronym> declaration:</p> <pre>&lt;?xml version="1.0" encoding="UTF-8" standalone="no" ?&gt;</pre>
<p>Can be expressed as the following <code>XMLDecl</code> resource:</p> <pre>&lt;rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cnt="http://www.w3.org/2007/content#"&gt;
&lt;cnt:XMLDecl rdf:ID="xmld0"&gt;
&lt;cnt:xmlStandalone&gt;no&lt;/cnt:xmlStandalone&gt;
&lt;cnt:xmlEncoding&gt;UTF-8&lt;/cnt:xmlEncoding&gt;
&lt;cnt:xmlVersion&gt;1.0&lt;/cnt:xmlVersion&gt;
&lt;/cnt:XMLDecl&gt;
&lt;/rdf:RDF&gt;</pre> </div> <h3><a id="doctypeDeclClass" name="doctypeDeclClass">2.6.
DoctypeDecl class</a></h3> <p>A resource of type <span class="type">DoctypeDecl</span>
represents a document type declaration. Likewise <a href="#xmlDeclClass"><span
class="type">XMLDecl</span></a>, this class is normally used in conjunction with the <a
href="#xmlContentClass"><span class="type">XMLContent</span></a> class, when the
corresponding <acronym>XML</acronym> file has a document type declaration. The resources
are linked via the <var>doctypeDecl</var> property.</p> <p>The following properties
<strong>may</strong> appear in resources of type <span
class="type">DoctypeDecl</span>:</p> <dl>
<dt><var>publicId</var></dt>
<dd>Property representing the formal public identifier.</dd>
<dt><var>systemId</var></dt>
<dd>Property representing the system identifier.</dd>
<dt><var>internalSubset</var></dt>
<dd>Property representing the internal subset.</dd>
</dl> <p>The following property <strong>must</strong> appear in resources of type
<span class="type">DoctypeDecl</span>:</p> <dl>
<dt><var>doctypeName</var></dt>
<dd>Property representing the document type name.</dd>
</dl> <div class="example"> <p><strong>Example 2.5:</strong> A typical
<acronym>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;rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cnt="http://www.w3.org/2007/content#"&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;/rdf:RDF&gt;</pre> </div> <h3><a id="example" name="example">2.7. A practical
example</a></h3> <p>To understand the versatility of the vocabulary, let us assume we
have a given <acronym>XHTML</acronym> page containing an <acronym>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="#textContentClass"><span class="type">TextContent</span></a>:</p> <pre>&lt;rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cnt="http://www.w3.org/2007/content#"&gt;
&lt;cnt:TextContent rdf:about="http://example.org/example207.html"&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;/cnt:TextContent&gt;
&lt;/rdf:RDF&gt;</pre> <p>or likewise as <a href="#xmlContentClass"><span
class="type">XMLContent</span></a>. The information from the XML declaration is modelled
as an <span class="type">XMLDecl</span> resource and refered to from the <span
class="type">XMLContent</span> resource by the <var>xmlDecl</var> property. As the
comment <code>&lt;!-- this is a comment --&gt;</code> precedes the document type
declaration a <var>xmlLeadingMisc</var> property is created with its object literal
containing the comment. The document type declaration is modelled as a <span
class="type">DoctypeDecl</span> resource and refered to from the <span
class="type">XMLContent</span> resource by the <var>doctypeDecl</var> property.</p>
<pre>&lt;rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cnt="http://www.w3.org/2007/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:XMLDecl rdf:ID="xmld0"&gt;
&lt;cnt:xmlStandalone&gt;no&lt;/cnt:xmlStandalone&gt;
&lt;cnt:xmlEncoding&gt;UTF-8&lt;/cnt:xmlEncoding&gt;
&lt;cnt:xmlVersion&gt;1.0&lt;/cnt:xmlVersion&gt;
&lt;/cnt:XMLDecl&gt;
&lt;cnt:XMLContent rdf:about="#"&gt;
&lt;cnt:xmlLeadingMisc rdf:parseType="Literal"&gt;&lt;!-- this is a comment --&gt;&lt;/cnt:xmlLeadingMisc&gt;
&lt;cnt:doctypeDecl rdf:resource="#dtd0" /&gt;
&lt;cnt:xmlDecl rdf:resource="#xmld0" /&gt;
&lt;cnt:xmlRest 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:xmlRest&gt;
&lt;/cnt:XMLContent&gt;
&lt;/rdf:RDF&gt;</pre> </div> <!-- end Classes and Properties --> <h2><a id="scenarios"
name="scenarios">3. 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><ul>
<li>Situation A: Given the byte sequence of non-text content (<var>byteSeq</var>)
read from a file system. A <span class="type">cnt:Base64Content</span> resource may
be created with a <var>cnt:bytes</var> property with an object literal created from
<var>byteSeq</var>. But no <span class="type">cnt:TextContent</span> resource must
be created, although in some cases it is technically possible to create a character
sequence from the byte sequence <var>byteSeq</var> using some character
encoding.</li>
<li>Situation B: Given the byte sequence of text content (<var>byteSeq</var>)
received from a Web server and an appropriate character encoding (<var>ce</var>). A
<span class="type">cnt:Base64Content</span> resource may be created with a
<var>cnt:bytes</var> property with an object literal created from
<var>byteSeq</var>. After transforming <var>byteSeq</var> to character sequence
<var>charSeq</var> using character encoding <var>ce</var>, a <span
class="type">cnt:TextContent</span> resource may be created with
<var>cnt:chars</var> property with an object literal <var>charSeq</var> and
<var>cnt:characterEncoding</var> property with an object literal <var>ce</var>.</li>
<li>Situation C: Given the byte sequence of text content (<var>byteSeq</var>)
received from a Web server and an inappropriate character encoding (<var>ce</var>).
A <span class="type">cnt:Base64Content</span> resource may be created with a
<var>cnt:bytes</var> property with an object literal created from
<var>byteSeq</var>. Because transforming <var>byteSeq</var> to a character sequence
<var>charSeq</var> using character encoding <var>ce</var> fails, no <span
class="type">cnt:TextContent</span> resource can be created.</li>
<li>Situation D: Given the character sequence of text content (<var>charSeq</var>)
created in memory and an appropriate character encoding (<var>ce</var>). A <span
class="type">cnt:TextContent</span> resource may be created with a
<var>cnt:chars</var> property with an object literal created from
<var>charSeq</var>. After transforming <var>charSeq</var> to byte sequence
<var>byteSeq</var> using character encoding <var>ce</var>, a <span
class="type">cnt:Base64Content</span> resource may be created with
<var>cnt:bytes</var> property with an object literal <var>byteSeq</var> and
<var>cnt:characterEncoding</var> property with an object literal <var>ce</var>.</li>
<li>Situation E: 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>). <span class="type">cnt:Base64Content</span> and <span
class="type">cnt:TextContent</span> resources may be created as in situation B.
Additionally, an <span class="type">cnt:XMLContent</span> resource may be
created.</li>
<li>Situation F: Given a <acronym title="Document Object Model">DOM</acronym>
Document in memory, originally created by parsing some <acronym>XML</acronym>
source, but afterwards changed by <acronym>DOM</acronym> operations. A <span
class="type">cnt:XMLDecl</span> resource may be created from the information in the
Document node itself, and a <span class="type">cnt:DoctypeDecl</span> resource from
the information in the DocumentType node. A <span class="type">cnt:XMLContent</span>
resource may be created after serializing the relevant child nodes of the Document
node (1. Comment and ProcessingInstruction nodes preceding a DocumentType node, and
2. nodes following a DocumentType node) to create object literals for
<var>cnt:xmlLeadingMisc</var> and <var>cnt:xmlRest</var>. See the <a
href="#dom-mapping">Mapping between DOM and the Content-in-RDF vocabulary</a>.</li>
</ul> <h2><a id="extensions" name="extensions">4. Extensions to 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, e.g., 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 <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> <h2><a id="schema" name="schema">Appendix A: Schema in
<acronym title="Resource Description Framework">RDF</acronym>/<acronym
title="Extensible Markup Language">XML</acronym></a></h2><pre class="schema">&lt;rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns="http://www.w3.org/2007/content#"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xml:base="http://www.w3.org/2007/content"&gt;
&lt;owl:Ontology rdf:about=""&gt;
&lt;owl:versionInfo rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
&gt;Copyright © 2008 World Wide Web Consortium&lt;/owl:versionInfo&gt;
&lt;/owl:Ontology&gt;
&lt;!-- Classes --&gt;
&lt;rdfs:Class rdf:ID="Base64Content"&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:cardinality&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#bytes"/&gt;
&lt;/owl:onProperty&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#characterEncoding"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:label xml:lang="en"&gt;Base64 content&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The base64 encoded content (can be used for all types of content)&lt;/rdfs:comment&gt;
&lt;rdfs:subClassOf rdf:resource="#Content"/&gt;
&lt;/rdfs:Class&gt;
&lt;rdfs:Class rdf:about="#Content"&gt;
&lt;rdfs:label xml:lang="en"&gt;Content&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The message body content&lt;/rdfs:comment&gt;
&lt;/rdfs:Class&gt;
&lt;rdfs:Class rdf:ID="DoctypeDecl"&gt;
&lt;rdfs:label xml:lang="en"&gt;Document type declaration&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The document type declaration&lt;/rdfs:comment&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#doctypeName"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:cardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#internalSubset"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#publicId"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#systemId"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;/rdfs:Class&gt;
&lt;rdfs:Class rdf:ID="TextContent"&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:cardinality&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#chars"/&gt;
&lt;/owl:onProperty&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#characterEncoding"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:label xml:lang="en"&gt;Text content&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The text content (can be used for non-XML-wellformed text resources)&lt;/rdfs:comment&gt;
&lt;rdfs:subClassOf rdf:resource="#Content"/&gt;
&lt;/rdfs:Class&gt;
&lt;rdfs:Class rdf:ID="XMLContent"&gt;
&lt;rdfs:label xml:lang="en"&gt;XML content&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The XML content (can be used for XML-wellformed resource)&lt;/rdfs:comment&gt;
&lt;rdfs:subClassOf rdf:resource="#Content"/&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#characterEncoding"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#xmlDecl"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#doctypeDecl"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#xmlLeadingMisc"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#xmlRest"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:cardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;/rdfs:Class&gt;
&lt;rdfs:Class rdf:ID="XMLDecl"&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:cardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:cardinality&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#xmlVersion"/&gt;
&lt;/owl:onProperty&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:comment xml:lang="en"&gt;The XML declaration&lt;/rdfs:comment&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#xmlEncoding"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:subClassOf&gt;
&lt;owl:Restriction&gt;
&lt;owl:onProperty&gt;
&lt;rdf:Property rdf:about="#xmlStandalone"/&gt;
&lt;/owl:onProperty&gt;
&lt;owl:maxCardinality rdf:datatype="http://www.w3.org/2001/XMLSchema#int"
&gt;1&lt;/owl:maxCardinality&gt;
&lt;/owl:Restriction&gt;
&lt;/rdfs:subClassOf&gt;
&lt;rdfs:label xml:lang="en"&gt;XML declaration&lt;/rdfs:label&gt;
&lt;/rdfs:Class&gt;
&lt;!-- Properties --&gt;
&lt;rdf:Property rdf:about="#bytes"&gt;
&lt;rdfs:label xml:lang="en"&gt;Base64 encoded byte sequence&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The Base64 encoded byte sequence of the content&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#Base64Content"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#characterEncoding"&gt;
&lt;rdfs:label xml:lang="en"&gt;Character encoding&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The character encoding used create a character sequence from a byte
sequence or vice versa&lt;/rdfs:comment&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#chars"&gt;
&lt;rdfs:comment xml:lang="en"&gt;The character sequence of the content&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#TextContent"/&gt;
&lt;rdfs:label xml:lang="en"&gt;Character sequence&lt;/rdfs:label&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#doctypeDecl"&gt;
&lt;rdfs:label xml:lang="en"&gt;Document type declaration&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The document type declaration&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#XMLContent"/&gt;
&lt;rdfs:range rdf:resource="#DoctypeDecl"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#doctypeName"&gt;
&lt;rdfs:label xml:lang="en"&gt;Document type name&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The document type name&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#DoctypeDecl"/&gt;
&lt;rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#internalSubset"&gt;
&lt;rdfs:comment rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
&gt;The internal subset of the DTD&lt;/rdfs:comment&gt;
&lt;rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string"
&gt;Internal DTD subset&lt;/rdfs:label&gt;
&lt;rdfs:domain rdf:resource="#DoctypeDecl"/&gt;
&lt;rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#publicId"&gt;
&lt;rdfs:label xml:lang="en"&gt;Public ID&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The document type declarations's public identifier&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#DoctypeDecl"/&gt;
&lt;rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#systemId"&gt;
&lt;rdfs:label xml:lang="en"&gt;System ID&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The document type declarations's system identifier (typed: xsd:anyURI)&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#DoctypeDecl"/&gt;
&lt;rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#xmlDecl"&gt;
&lt;rdfs:label xml:lang="en"&gt;XML declaration&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The XML declaration&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#XMLContent"/&gt;
&lt;rdfs:range rdf:resource="#XMLDecl"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#xmlEncoding"&gt;
&lt;rdfs:label xml:lang="en"&gt;XML character encoding&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The XML character encoding&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#XMLDecl"/&gt;
&lt;rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#xmlLeadingMisc"&gt;
&lt;rdfs:label xml:lang="en"&gt;XML leading misc&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The XML content preceding the document type declaration&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#XMLContent"/&gt;
&lt;rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#XMLLiteral"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#xmlRest"&gt;
&lt;rdfs:label xml:lang="en"&gt;XML rest&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The XML content following the document type declaration&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#XMLContent"/&gt;
&lt;rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#XMLLiteral"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#xmlStandalone"&gt;
&lt;rdfs:label xml:lang="en"&gt;XML standalone document declaration&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The XML standalone document declaration&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#XMLDecl"/&gt;
&lt;rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/&gt;
&lt;/rdf:Property&gt;
&lt;rdf:Property rdf:about="#xmlVersion"&gt;
&lt;rdfs:label xml:lang="en"&gt;XML version&lt;/rdfs:label&gt;
&lt;rdfs:comment xml:lang="en"&gt;The XML version&lt;/rdfs:comment&gt;
&lt;rdfs:domain rdf:resource="#XMLDecl"/&gt;
&lt;rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/&gt;
&lt;/rdf:Property&gt;
&lt;/rdf:RDF&gt;</pre> <h2><a id="terms-Content" name="terms-Content">Appendix B:
Vocabulary 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 Representing Content in <acronym>RDF</acronym>
namespace.</caption>
<thead>
<tr>
<th scope="col">Class name</th>
<th scope="col">Label</th>
<th scope="col">Allowable types</th>
<th scope="col">Required properties</th>
<th scope="col">Optional properties</th>
</tr>
</thead>
<tbody>
<tr id="terms-classes-Base64Content">
<td scope="row"><span class="type">cnt:Base64Content</span></td>
<td>Base64 encoded binary content</td>
<td></td>
<td><a href="#terms-properties-bytes"><var>cnt:bytes</var></a></td>
<td><a
href="#terms-properties-characterEncoding"><var>cnt:characterEncoding</var></a></td>
</tr>
<tr id="terms-classes-Content">
<td scope="row"><span class="type">cnt:Content</span></td>
<td>Content</td>
<td><a href="#terms-classes-Base64Content"><span
class="type">cnt:Base64Content</span></a>, <a
href="#terms-classes-TextContent"><span class="type">cnt:TextContent</span></a>,
<a href="#terms-classes-XMLContent"><span
class="type">cnt:XMLContent</span></a></td>
<td></td>
<td></td>
</tr>
<tr id="terms-classes-DoctypeDecl">
<td scope="row"><span class="type">cnt:DoctypeDecl</span></td>
<td>Document type declaration</td>
<td></td>
<td><a href="#terms-properties-doctypeName"><var>cnt:doctypeName</var></a></td>
<td><a href="#terms-properties-publicId"><var>cnt:publicId</var></a>, <a
href="#terms-properties-systemId"><var>cnt:systemId</var></a>, <a
href="#terms-properties-internalSubset"><var>cnt:internalSubset</var></a></td>
</tr>
<tr id="terms-classes-TextContent">
<td scope="row"><span class="type">cnt:TextContent</span></td>
<td>Textual content</td>
<td></td>
<td><a href="#terms-properties-chars"><var>cnt:chars</var></a></td>
<td><a
href="#terms-properties-characterEncoding"><var>cnt:characterEncoding</var></a></td>
</tr>
<tr id="terms-classes-XMLContent">
<td scope="row"><span class="type">cnt:XMLContent</span></td>
<td>XML content</td>
<td></td>
<td><a href="#terms-properties-xmlRest"><var>cnt:xmlRest</var></a></td>
<td><a
href="#terms-properties-characterEncoding"><var>cnt:characterEncoding</var></a>,
<a href="#terms-properties-xmlLeadingMisc"><var>cnt:xmlLeadingMisc</var></a>, <a
href="#terms-properties-doctypeDecl"><var>cnt:doctypeDecl</var></a></td>
</tr>
<tr id="terms-classes-XMLDecl">
<td scope="row"><span class="type">cnt:XMLDecl</span></td>
<td>XML declaration</td>
<td></td>
<td><a href="#terms-properties-xmlVersion"><var>cnt:xmlVersion</var></a></td>
<td><a href="#terms-properties-xmlEncoding"><var>cnt:xmlEncoding</var></a>, <a
href="#terms-properties-xmlStandalone"><var>cnt:xmlStandalone</var></a></td>
</tr>
</tbody>
</table> <h3><a id="terms-properties"
name="terms-properties">Properties</a></h3><table>
<caption>Properties in the Representing Content in <acronym>RDF</acronym>
namespace.</caption>
<thead>
<tr>
<th scope="col">Property name</th>
<th scope="col">Label</th>
<th scope="col">Domain</th>
<th scope="col">Range</th>
<th>Restriction</th>
</tr>
</thead>
<tbody>
<tr id="terms-properties-bytes">
<td scope="row"><var>cnt:bytes</var></td>
<td>Bytes</td>
<td><a href="#terms-classes-Base64Content"><span
class="type">cnt:Base64Content</span></a></td>
<td>Literal</td>
<td>Exactly one per <span class="type">cnt:Base64Content</span></td>
</tr>
<tr id="terms-properties-characterEncoding">
<td scope="row"><var>cnt:characterEncoding</var></td>
<td>Character encoding</td>
<td></td>
<td>Literal</td>
<td>At most one per <span class="type">cnt:Base64Content</span>, <span
class="type">cnt:TextContent</span> or <span
class="type">cnt:XMLContent</span></td>
</tr>
<tr id="terms-properties-chars">
<td scope="row"><var>cnt:chars</var></td>
<td>Characters</td>
<td><a href="#terms-classes-TextContent"><span
class="type">cnt:TextContent</span></a></td>
<td>Literal</td>
<td>Exactly one per <span class="type">cnt:TextContent</span></td>
</tr>
<tr id="terms-properties-doctypeDecl">
<td scope="row"><var>cnt:doctypeDecl</var></td>
<td>Document type declaration</td>
<td><a href="#terms-classes-XMLContent"><span
class="type">cnt:XMLContent</span></a></td>
<td><a href="#terms-classes-DoctypeDecl"><span
class="type">cnt:DoctypeDecl</span></a></td>
<td>At most one per <span class="type">cnt:XMLContent</span></td>
</tr>
<tr id="terms-properties-doctypeName">
<td scope="row"><var>cnt:doctypeName</var></td>
<td>Document type name</td>
<td><a href="#terms-classes-DoctypeDecl"><span
class="type">cnt:DoctypeDecl</span></a></td>
<td>Literal</td>
<td>Exactly one per <span class="type">cnt:DoctypeDecl</span></td>
</tr>
<tr id="terms-properties-internalSubset">
<td scope="row"><var>cnt:internalSubset</var></td>
<td>Internal subset</td>
<td><a href="#terms-classes-DoctypeDecl"><span
class="type">cnt:DoctypeDecl</span></a></td>
<td>Literal</td>
<td>At most one per <span class="type">cnt:DoctypeDecl</span></td>
</tr>
<tr id="terms-properties-publicId">
<td scope="row"><var>cnt:publicId</var></td>
<td>Formal public identifier</td>
<td><a href="#terms-classes-DoctypeDecl"><span
class="type">cnt:DoctypeDecl</span></a></td>
<td>Literal</td>
<td>At most one per <span class="type">cnt:DoctypeDecl</span></td>
</tr>
<tr id="terms-properties-systemId">
<td scope="row"><var>cnt:systemId</var></td>
<td>System identifier</td>
<td><a href="#terms-classes-DoctypeDecl"><span
class="type">cnt:DoctypeDecl</span></a></td>
<td>Literal</td>
<td>At most one per <span class="type">cnt:DoctypeDecl</span></td>
</tr>
<tr id="terms-properties-xmlDecl">
<td scope="row"><var>cnt:xmlDecl</var></td>
<td>XML declaration</td>
<td><a href="#terms-classes-XMLContent"><span
class="type">cnt:XMLContent</span></a></td>
<td><a href="#terms-classes-XMLDecl"><span
class="type">cnt:XMLDecl</span></a></td>
<td>At most one per <span class="type">cnt:XMLContent</span></td>
</tr>
<tr id="terms-properties-xmlEncoding">
<td scope="row"><var>cnt:xmlEncoding</var></td>
<td>XML character encoding</td>
<td><a href="#terms-classes-XMLDecl"><span
class="type">cnt:XMLDecl</span></a></td>
<td>Literal</td>
<td>At most one per <span class="type">cnt:XMLDecl</span></td>
</tr>
<tr id="terms-properties-xmlLeadingMisc">
<td scope="row"><var>cnt:xmlLeadingMisc</var></td>
<td>XML preceding the document type declaration</td>
<td><a href="#terms-classes-XMLContent"><span
class="type">cnt:XMLContent</span></a></td>
<td>XML Literal</td>
<td>At most one per <span class="type">cnt:XMLContent</span></td>
</tr>
<tr id="terms-properties-xmlRest">
<td scope="row"><var>cnt:xmlRest</var></td>
<td>XML following the document type declaration</td>
<td><a href="#terms-classes-XMLContent"><span
class="type">cnt:XMLContent</span></a></td>
<td>XML Literal</td>
<td>Exactly one per <span class="type">cnt:XMLContent</span></td>
</tr>
<tr id="terms-properties-xmlStandalone">
<td scope="row"><var>cnt:xmlStandalone</var></td>
<td>XML standalone document declaration</td>
<td><a href="#terms-classes-XMLDecl"><span
class="type">cnt:XMLDecl</span></a></td>
<td>Literal</td>
<td>At most one per <span class="type">cnt:XMLDecl</span></td>
</tr>
<tr id="terms-properties-xmlVersion">
<td scope="row"><var>cnt:xmlVersion</var></td>
<td>XML version</td>
<td><a href="#terms-classes-XMLDecl"><span
class="type">cnt:XMLDecl</span></a></td>
<td>Literal</td>
<td>Exactly one per <span class="type">cnt:XMLDecl</span></td>
</tr>
</tbody>
</table> <h2><a id="dom-mapping" name="dom-mapping">Appendix C: Mapping between DOM
and Content-in-RDF properties</a></h2><table>
<thead>
<tr>
<th>DOM property</th>
<th>Content-in-RDF property</th>
</tr>
</thead>
<tbody>
<tr>
<td><var>Document.xmlVersion</var></td>
<td><var>xmlVersion</var></td>
</tr>
<tr>
<td><var>Document.xmlEncoding</var></td>
<td><var>xmlEncoding</var></td>
</tr>
<tr>
<td><var>Document.xmlStandalone</var></td>
<td><var>xmlStandalone</var></td>
</tr>
<tr>
<td><var>Document.doctype</var></td>
<td><var>doctypeDecl</var></td>
</tr>
<tr>
<td><var>DocumentType.name</var></td>
<td><var>doctypeName</var></td>
</tr>
<tr>
<td><var>DocumentType.publicId</var></td>
<td><var>publicId</var></td>
</tr>
<tr>
<td><var>DocumentType.systemId</var></td>
<td><var>systemId</var></td>
</tr>
<tr>
<td><var>DocumentType.internalSubset</var></td>
<td><var>internalSubset</var></td>
</tr>
</tbody>
</table> <h2><a id="history" name="history">Appendix D: Document
Changes</a></h2><p>Since the 23 June editorial draft, only minor editorial changes have
happened. Since the 20 February 2008 editorial draft, this document has changed as
follows:</p><ul>
<li>Added <var>characterEncoding</var> property to <span
class="type">Base64Content</span>, <span class="type">TextContent</span>, <span
class="type">XMLContent</span>.</li>
<li>Clarified definition text for <var>xmlLeadingMisc</var> and <var>xmlRest</var>
properties.</li>
<li>Changed <var>docTypeDecl</var> to <var>doctypeDecl</var>, and <span
class="type">DocTypeDecl</span> to <span class="type">DoctypeDecl</span>.</li>
<li>Changed <var>dtdName</var> to <var>doctypename</var>.</li>
<li>Changed examples 2.6, 2.7, 2.8 into one (2.6).</li>
<li>Added section "When to create which resources?".</li>
<li>Added appendix "Mapping between DOM and the Content-in-RDF vocabulary"</li>
<li>Some minor editorial changes.</li>
</ul> <h2><a id="references" name="references">Appendix E: References</a></h2><dl>
<dt><a id="ref-earl" name="ref-earl">[<acronym
title="Evaluation and Report Language">EARL</acronym>]</a></dt>
<dd><a href="http://www.w3.org/TR/EARL10/">Evaluation and Report Language (EARL) 1.0
Schema</a>. W3C Working Draft 23 March
2007.<br /><code>http://www.w3.org/TR/EARL10/</code></dd>
<dt><a id="ref-rdf" name="ref-rdf">[<acronym
title="Resource Description Framework">RDF</acronym>]</a></dt>
<dd><a href="http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/">Resource
Description Framework (RDF) 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">[<acronym
title="Resource Description Framework">RDF</acronym>-PRIMER]</a></dt>
<dd><a href="http://www.w3.org/TR/rdf-primer/"><acronym
title="Resource Description Framework">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">[<acronym
title="Resource Description Framework Schema">RDFS</acronym>]</a></dt>
<dd><a href="http://www.w3.org/TR/rdf-schema/"><acronym
title="Resource Description Framework">RDF</acronym> Vocabulary Description Language
1.0: <acronym title="Resource Description Framework">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">[<acronym
title="Resource Description Framework">RDF</acronym>-XML]</a></dt>
<dd><a href="http://www.w3.org/TR/rdf-syntax-grammar/"><acronym
title="Resource Description Framework">RDF</acronym>/XML 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">[<acronym
title="Request For Comments">RFC</acronym>2119]</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">[<acronym
title="Request For Comments">RFC</acronym>2045]</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
title="Internet Engineering Task Force">IETF</acronym>).<br /><code>http://www.ietf.org/rfc/rfc2045.txt</code></dd>
<dt><a id="ref-owl" name="ref-owl">[<acronym
title="Ontology Web Language">OWL</acronym>]</a></dt>
<dd><a href="http://www.w3.org/TR/owl-features/"><acronym
title="Ontology Web Language">OWL</acronym> Web Ontology Language Overview</a>. W3C
Recommendation 10 February 2004
.<br /><code>http://www.w3.org/TR/owl-features/</code></dd>
<dt><a id="ref-xml" name="ref-xml">[<acronym
title="Extensible Markup Language">XML</acronym>]</a></dt>
<dd><a href="http://www.w3.org/TR/xml/">Extensible Markup Language (XML) 1.0 (Fourth
Edition)</a>. W3C Recommendation 16 August 2006, edited in place 29 September
2006.<br /><code>http://www.w3.org/TR/xml/</code></dd>
</dl></body>
</html>