[contents]

Representing Content in RDF 1.0

W3C Working Draft 29 October 2009

This version:

http://www.w3.org/TR/2009/WD-Content-in-RDF10-20091029/

Latest version:

http://www.w3.org/TR/Content-in-RDF10/

Previous version:

http://www.w3.org/TR/2008/WD-Content-in-RDF-20080908/

Editors:

Johannes Koch, Fraunhofer-Gesellschaft (Fraunhofer Institute for Applied Information Technology FIT)

Carlos A Velasco, Fraunhofer-Gesellschaft (Fraunhofer Institute for Applied Information Technology FIT)

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

Copyright © 2009 W3C^® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.

Abstract

This document is a specification for a vocabulary to represent content in the Resource Description Framework (RDF). 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, included text, images, or other types of formats. In many cases it can be used together with HTTP Vocabulary in RDF 1.0, which allows quality assurance tools to record the HTTP 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 W3C Evaluation And Report Language (EARL).

Table of Contents

1. Introduction
   • 1.1 Namespaces
   • 1.2 Use Cases
2. Classes
   • 2.1 Content Class
     • 2.1.1 ContentAsBase64 Class
     • 2.1.2 ContentAsText Class
     • 2.1.3 ContentAsXML Class
   • 2.2 DoctypeDecl Class
3. Properties
   • 3.1 bytes Property
   • 3.2 characterEncoding
   • 3.3 chars Property
   • 3.4 declaredEncoding Property
   • 3.5 doctypeName Property
   • 3.6 dtDecl Property
   • 3.7 internalSubset Property
   • 3.8 leadingMisc Property
   • 3.9 publicId Property
   • 3.10 rest Property
   • 3.11 standalone Property
   • 3.12 systemId Property
   • 3.13 version Property
4. Conformance
   • 4.1 Conforming Content-in-RDF graphs
   • 4.2 Producers
   • 4.3 Consumers
5. Usage scenarios
6. Limitations of the vocabulary

Appendices

1. A practical example
2. Terms
3. Mapping between DOM and Content-in-RDF properties
4. Document Changes
5. References

1 Introduction

This document is the specification for a vocabulary to represent Content in the Resource Description Framework (RDF). 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.

This document assumes the following background knowledge:

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

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

The keywords must, required, recommended, should, may, and optional are used in accordance with [RFC2119].

For limitations of this vocabulary, see section 5.

1.1 Namespaces

Table 1 presents the namespaces typically used by this vocabulary. The core namespace has the URI http://www.w3.org/2008/content# and the prefix cnt. 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.

1.2 Use cases

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 (EARL) [EARL]. Typical applications could be:

• 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.
• Applications dealing with the exchange of text documents and other types of media, like Web Services. For example, an AJAX application could exchange document fragments and images with a Web server to react to different user actions.
• 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.

2 Classes

This section presents a description of the classes of this RDF vocabulary. We present every class together with its subclasses. We also include whenever relevant short snippets and examples.

2.1 Content Class

The cnt:Content class is an over arching 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, binary files (e.g., images or movies), XML files, etc.

There are three subclasses from the Content class: cnt:ContentAsBase64, cnt:ContentAsText and cnt:ContentAsXML.

In order to connect resources with different cnt:Content sub-types with each other, use the dct:source property to point to the original version. E.g. if there is an XML resource transmitted via HTTP, the original version would be a cnt:ContentAsBase64 resource. But cnt:ContentAsText and cnt:ContentAsXML resource could also be created and point to the cnt:ContentAsBase64 resource.

Examples

<cnt:ContentAsBase64 rdf:about="http://www.example.org/xml0">
  <!-- ... -->
</cnt:ContentAsBase64>

<cnt:ContentAsText rdf:about="http://www.example.org/xml1">
  <!-- ... -->
  <dct:source rdf:resource="http://www.example.org/xml0"/>
</cnt:ContentAsText>

<cnt:ContentAsXML rdf:about="http://www.example.org/xml2">
  <!-- ... -->
  <dct:source rdf:resource="http://www.example.org/xml0"/>
</cnt:ContentAsXML>

[Editor's note: The working group asks for comments about this use of dct:source.]

Related Properties

dct:source

Points to the original resource.

2.1.1 ContentAsBase64 Class

The cnt:ContentAsBase64 class is a subclass of the cnt:Content class for Base64 encoded binary content (as defined by [RFC2045]) and can be used for any type of content, although its more typical use case is for binary files.

Related Properties

• Domain of:
  • cnt:bytes
  • cnt:characterEncoding
• Range of: none

Examples

<cnt:ContentAsBase64 rdf:about="http://www.w3.org/Icons/w3c_home.png">
  <cnt:bytes>77+9UE5HDQoaCgAAAA1JSERSAAAASAAAADAIAwAAAO+{...}</cnt:bytes>
</cnt:ContentAsBase64>

2.1.2 ContentAsText Class

The cnt:ContentAsText class is a subclass of the cnt:Content class for any type of textual content.

Related Properties

• Domain of:
  • cnt:chars
  • cnt:characterEncoding
• Range of: none

Examples

<cnt:ContentAsText rdf:about="http://example.org/example.css">
  <cnt:characterEncoding>UTF-8</cnt:characterEncoding>
  <cnt:chars>body {
  color: #000;
  background: #fff
}
h1 {
  font-size: 1.6em
}
h2 {
  font-size: 1.3em
}</cnt:chars>
</cnt:ContentAsText>

2.1.3 ContentAsXML Class

The cnt:ContentAsXML class is a subclass of the cnt:Content class only for wellformed XML content.

Related Properties

• Domain of:
  • cnt:declaredEncoding
  • cnt:standalone
  • cnt:version
  • cnt:leadingMisc
  • cnt:dtDecl
  • cnt:rest
  • cnt:characterEncoding
• Range of: none

See the Mapping between the Document Object Model (DOM) and the Content-in-RDF vocabulary.

Examples

<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
  <head>
    <title>The title</title>
  </head>
  <body>
    <p>Some paragraph.</p>
  </body>
</html>

<cnt:ContentAsXML rdf:about="http://example.org/example203.html">
  <cnt:rest rdf:parseType="Literal"><html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
  <head>
    <title>The title</title>
  </head>
  <body>
    <p>Some paragraph.</p>
  </body>
</html></cnt:rest>
</cnt:ContentAsXML>

For the use of leadingMisc and dtDecl see Appendix A: A practical example.

2.2 DoctypeDecl Class

A document type declaration. This class is normally used in conjunction with the ContentAsXML class, when the corresponding XML resource contains a document type declaration. The relation is expressed via the dtDecl property.

Related Properties

• Domain of:
  • cnt:publicId
  • cnt:systemId
  • cnt:internalSubset
  • cnt:doctypeName
• Range of:
  • cnt:dtDecl

See the Mapping between the Document Object Model (DOM) and the Content-in-RDF vocabulary.

Examples

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

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

3 Properties

This section presents a description of the properties of this RDF vocabulary.

3.1 bytes Property

Character string representing the Base64 encoded byte sequence of the given content.

Domain:

cnt:ContentAsBase64

Range:

Literal

3.2 characterEncoding Property

The character encoding.

When used with ContentAsBase64: 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.

When used with ContentAsText: 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.

When used with ContentAsXML: 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. Note: This is the used character encoding, not the one declared in an XML declaration.

Domain:

cnt:Content

Range:

Literal

3.3 chars Property

The character sequence of the given content.

Domain:

cnt:ContentAsText

Range:

Literal

3.4 declaredEncoding Property

The character encoding specified in the XML declaration.

Domain:

cnt:ContentAsXML

Range:

Literal

3.5 doctypeName Property

The document type name.

Domain:

cnt:DoctypeDecl

Range:

Literal

3.6 dtDecl Property

This property relates an XML Content to its Document Type Declaration.

Domain:

cnt:ContentAsXML

Range:

cnt:DoctypeDecl

3.7 internalSubset Property

The internal subset of a document type declaration.

Domain:

cnt:DoctypeDecl

Range:

Literal

3.8 leadingMisc Property

The part of the XML information items (whitespace, comments and processing instructions) following the XML declaration and preceding the document type declaration if there is one.

Domain:

cnt:ContentAsXML

Range:

XML Literal

3.9 publicId Property

The formal public identifier of a document type declaration.

Domain:

cnt:DoctypeDecl

Range:

Literal

3.10 rest Property

• The part of the XML information items following the document type declaration if there is a document type declaration, or
• the part following the XML declaration if there is no document type declaration, or
• the whole XML information items if there is neither XML declaration nor document type declaration.

It contains comments, processing instructions and the root element.

Domain:

cnt:ContentAsXML

Range:

XML Literal

3.11 standalone Property

The standalone document declaration.

Domain:

cnt:ContentAsXML

Range:

Literal

3.12 systemId Property

The system identifier of a document type declaration.

Domain:

cnt:DoctypeDecl

Range:

Literal typed xsd:anyURI

3.13 version Property

The XML version specified in the XML declaration.

Domain:

cnt:ContentAsXML

Range:

Literal

4 Conformance

This section describes conformance with this Content-in-RDF specification. It differentiates between the following entities:

[Editor's note: The working group asks for comments about a more colloquial word for "Content-in-RDF Graph".]

Content-in-RDF Graph

An individual file or collection of files that contain Content-in-RDF data

Content-in-RDF Producer

A software tool or Web-based application that produces Content-in-RDF data

Content-in-RDF Consumer

A software tool or Web-based application that processes Content-in-RDF data

4.1 Conforming Content-in-RDF Graphs

Graphs conforming to this Content-in-RDF specification must meet the following requirements:

1. A ContentAsBase64 must have exactly one bytes (specified by cnt:bytes)..
2. A ContentAsBase64 may have one character encoding (specified by cnt:characterEncoding).
3. A ContentAsText must have exactly one chars (specified by cnt:chars).
4. A ContentAsText may have one character encoding (specified by cnt:characterEncoding).
5. A ContentAsXML must have exactly one XML rest (specified by cnt:rest).
6. A ContentAsXML may have one leadingMisc (specified by cnt:leadingMisc).
7. A ContentAsXML may have one Document type delcaration (referenced by cnt:dtDecl).
8. A ContentAsXML may have one character encoding (specified by cnt:characterEncoding).
9. A ContentAsXML must have exactly one XML version (specified by cnt:version).
10. A ContentAsXML may have one XML character encoding (specified by cnt:declaredEncoding).
11. A ContentAsXML may have one XML standalone declaration (specified by cnt:standalone).
12. A DoctypeDecl must have exactly one Document type name (specified by cnt:doctypeName).
13. A DoctypeDecl may have one public identifier (specified by cnt:publicId).
14. A DoctypeDecl may have one system identifier (specified by cnt:systemId).
15. A DoctypeDecl may have one internal subset (specified by cnt:internalSubset).

4.2 Conforming Producers

Producers conforming to this Content-in-RDF specification must meet the following requirements:

1. A Producer must generate conforming graphs.
2. A Producer must be able to serialize graphs in RDF/XML serialization [RDF-XML] and should also support other RDF serializations.
3. A Producer must generate all of the terms summarized in Appendix B: Terms for which there is information available to it.

4.3 Conforming Consumers

Consumers conforming to this Content-in-RDF specification must meet the following requirements:

1. A Consumer must process conforming graphs.
2. A Consumer must process graphs from any RDF/XML serialization [RDF-XML] and should also support other RDF serializations.
3. A Consumer must process all of the terms summarized in Appendix B: Terms for which there is information available to it.

5 Usage scenarios

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:

Situation A: byte sequence of non-text content

This includes images, multimedia, or other non-text resources. The byte sequence is recorded in Base64 format and represented as a literal using the cnt:bytes property of the cnt:ContentAsBase64. Non-text content should not be represented using cnt:ContentAsText.

Situation B: byte sequence of text content with appropriate character encoding information

This includes HTML, CSS, client-side script, or other text-based resources. Given the byte sequence of text content (byteSeq) received from a Web server and an appropriate character encoding (ce). byteSeq is recorded in Base64 format and represented as a literal using the cnt:bytes property of the cnt:ContentAsBase64.

After transforming the byteSeq to a character sequence charSeq using character encoding ce, charSeq is represented as a literal using the cnt:chars property of the cnt:ContentAsText and ce as a literal usind the cnt:characterEncoding property.

Situation C: byte sequence of text content with inappropriate character encoding information

Given the byte sequence of text content (byteSeq) received from a Web server and an inappropriate character encoding (ce). byteSeq is recorded in Base64 format and represented as a literal using the cnt:bytes property of the cnt:ContentAsBase64. Because transforming byteSeq to a character sequence charSeq using character encoding ce fails, no cnt:ContentAsText resource can be created.

Situation D: character sequence of text content with appropriate character encoding information

Given the character sequence of text content (charSeq) created in memory and an appropriate character encoding (ce). A cnt:ContentAsText resource may be created with a cnt:chars property with an object literal created from charSeq. After transforming charSeq to byte sequence byteSeq using character encoding ce, a cnt:ContentAsBase64 resource may be created with cnt:bytes property with an object literal byteSeq and cnt:characterEncoding property with an object literal ce.

Situation E: byte sequence of XML content with appropriate character encoding information

Given the byte sequence of wellformed XML content (byteSeq) received from a Web server and an appropriate character encoding (ce). cnt:ContentAsBase64 and cnt:ContentAsText resources may be created as in situation B. Additionally, an cnt:ContentAsXML resource may be created.

Situation F: Document Object Model (DOM) changed in memory

Given a DOM Document in memory, originally created by parsing some XML source, but afterwards changed by DOM operations. A cnt:XMLDecl resource may be created from the information in the Document node itself (version, declaredEncoding and standalone), and a cnt:DoctypeDecl resource from the information in the DocumentType node. A cnt:ContentAsXML resource may be created after serializing the relevant child nodes of the Document node to create object literals for cnt:leadingMisc (serialize Comment and ProcessingInstruction nodes preceding a DocumentType node) and cnt:rest (serialize nodes following a DocumentType node). See the Mapping between the Document Object Model (DOM) and Content-in-RDF properties.

6 Limitations of the vocabulary

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:

• Classes to specify the Document Object Model (DOM) of XML or HTML documents.
• Classes to specify the metadata of multimedia content like audio or image files.
• Properties to ensure the integrity of data by providing some kind of checksum algorithm.

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 (EARL) [EARL], leaving the room open for further extensions as new use cases are presented to us.

Appendix A: A practical example

To understand the versatility of the vocabulary, let us assume we have a given XHTML page containing an XML declaration, a comment preceding a document type declaration and some XHTML elements.

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<!-- this is a comment -->
<!DOCTYPE html "-//W3C//DTD XHTML 1.0 Strict//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
  <head>
    <title>The title</title>
  </head>
  <body>
    <p>Some paragraph.</p>
  </body>
</html>

<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:cnt="http://www.w3.org/2008/content#">

  <cnt:ContentAsText rdf:about="http://example.org/example207.html">
    <cnt:chars>&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" 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;</cnt:chars>
  </cnt:ContentAsText>

</rdf:RDF>

<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:cnt="http://www.w3.org/2008/content#"
    xml:base="http://example.org/example208.html">

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

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

</rdf:RDF>

Appendix B: Terms

The following terms are defined by this specification:

Classes

Properties

Appendix C: Mapping between the Document Object Model (DOM) and Content-in-RDF properties

Appendix D: Document Changes

[Editor's note: add changes from this version to WD-Content-in-RDF-20080908]

Appendix E: References

[EARL]

Evaluation and Report Language (EARL) 1.0 Schema. W3C Working Draft 28 April 2009.
http://www.w3.org/TR/EARL10/

[OWL]

OWL Web Ontology Language Overview. W3C Recommendation 10 February 2004.
http://www.w3.org/TR/owl-features/

[RDF]

Resource Description Framework (RDF) Model and Syntax Specification. W3C Recommendation, 22 February 1999.
http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/

[RDF-PRIMER]

RDF Primer. W3C Recommendation, 10 February 2004.
http://www.w3.org/TR/rdf-primer/

[RDFS]

RDF Vocabulary Description Language 1.0: RDF Schema. W3C Recommendation 10 February 2004.
http://www.w3.org/TR/rdf-schema/

[RDF-XML]

RDF/XML Syntax Specification (Revised). W3C Recommendation 10 February 2004.
http://www.w3.org/TR/rdf-syntax-grammar/

[RFC2119]

Request for Comments: 2119. Key words for use in RFCs to Indicate Requirement Levels, March 1997 (IETF).
http://www.ietf.org/rfc/rfc2119.txt

[RFC2045]

Request for Comments: 2045. Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, November 1996 (IETF).
http://www.ietf.org/rfc/rfc2045.txt

[XML]

Extensible Markup Language (XML) 1.0 (Fifth Edition). W3C Recommendation 26 November 2008.
http://www.w3.org/TR/xml/