% diff -cw 19981008 19990105
*** 19981008 Thu Oct 8 17:55:02 1998
--- 19990105 Wed Jan 6 14:44:16 1999
***************
*** 1,8 ****
<HTML>
<HEAD>
<TITLE>Resource Description Framework (RDF) Model and Syntax Specification</TITLE>
<rdf:Description about=""
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#"
xmlns:ddc="http://purl.org/net/ddc#"
dc:Title="Resource Description Framework (RDF) Model and Syntax Specification"
--- 1,11 ----
<HTML>
<HEAD>
<TITLE>Resource Description Framework (RDF) Model and Syntax Specification</TITLE>
+ <STYLE TYPE="text/css">
+ .EXAMPLE { margin-left: 1em }
+ </STYLE>
<rdf:Description about=""
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#"
xmlns:ddc="http://purl.org/net/ddc#"
dc:Title="Resource Description Framework (RDF) Model and Syntax Specification"
***************
*** 12,18 ****
Web. RDF emphasizes facilities to enable automated processing of
Web resources."
dc:Publisher="World Wide Web Consortium"
! dc:Date="1998-10-08"
dc:Format="text/html"
dc:Type="technical specification"
dc:Language="en">
--- 15,21 ----
Web. RDF emphasizes facilities to enable automated processing of
Web resources."
dc:Publisher="World Wide Web Consortium"
! dc:Date="1999-01-05"
dc:Format="text/html"
dc:Type="technical specification"
dc:Language="en">
***************
*** 25,30 ****
--- 28,34 ----
<dc:Subject
ddc:Class="025.302855741"
ddc:Heading="Applications of computer file organization and access methods" />
+ <dc:Relation resource="http://w3.org/TR/PR-rdf-syntax" />
<dc:Creator>
<rdf:Bag rdf:_1="Ora Lassila"
rdf:_2="Ralph Swick" />
***************
*** 33,42 ****
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF">
- <P align="center"><IMG src="/1998/.status/WD-rdf-syntax-19981008/visibility" alt="Visibility" /></P>
-
<H2 ALIGN="RIGHT"><A HREF="/"><IMG SRC="/Icons/w3c_home" ALT="W3C" BORDER="0" ALIGN="LEFT" /></A>
! WD-rdf-syntax-19981008</H2>
 
--- 37,44 ----
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF">
<H2 ALIGN="RIGHT"><A HREF="/"><IMG SRC="/Icons/w3c_home" ALT="W3C" BORDER="0" ALIGN="LEFT" /></A>
! PR-rdf-syntax-19990105</H2>
 
***************
*** 44,62 ****
<H1>Resource Description Framework<BR />
(RDF) Model and Syntax Specification</H1>
! <H3>W3C Working Draft 08 October 1998</H3>
! <A href="/1998/.status/WD-rdf-syntax-19981008/status"><img src="/1998/.status/WD-rdf-syntax-19981008/statusimg" border="0" alt="Status of this Document" /></A></center>
<DL>
<DT>This Version: </DT>
! <DD><A HREF="/1998/10/WD-rdf-syntax-19981008">http://www.w3.org/1998/10/WD-rdf-syntax-19981008</A><br />
</DD>
<DT>Newest Version: </DT>
! <DD><A HREF="/TR/WD-rdf-syntax">http://www.w3.org/TR/WD-rdf-syntax</A><br />
</DD>
<DT>Editors: </DT>
--- 46,64 ----
<H1>Resource Description Framework<BR />
(RDF) Model and Syntax Specification</H1>
! <H3>W3C Proposed Recommendation 05 January 1999</H3>
! <A href="/1999/.status/PR-rdf-syntax-19990105/status"><img src="/1999/.status/PR-rdf-syntax-19990105/statusimg" border="0" alt="Status of this Document" /></A></center>
<DL>
<DT>This Version: </DT>
! <DD><A HREF="/TR/1999/PR-rdf-syntax-19990105">http://www.w3.org/TR/1999/PR-rdf-syntax-19990105</A><br />
</DD>
<DT>Newest Version: </DT>
! <DD><A HREF="/TR/PR-rdf-syntax">http://www.w3.org/TR/PR-rdf-syntax</A><br />
</DD>
<DT>Editors: </DT>
***************
*** 67,116 ****
World Wide Web Consortium</DD>
</DL>
! <P><A href="/1998/.status/WD-rdf-syntax-19981008/status">Document Status</A></P>
! <P><FONT SIZE="-1"><A HREF="http://www.w3.org/Consortium/Legal/ipr-notice.html#Copyright">Copyright</A> © 1997,1998
! <A HREF="http://www.w3.org">W3C</A> (<A HREF="http://www.lcs.mit.edu">MIT</A>,
<A HREF="http://www.inria.fr/">INRIA</A>, <A HREF="http://www.keio.ac.jp/">Keio</A>
! ), All Rights Reserved. W3C <A HREF="http://www.w3.org/Consortium/Legal/ipr-notice.html#LegalDisclaimer">liability,</A>
! <A HREF="http://www.w3.org/Consortium/Legal/ipr-notice.html#W3CTrademarks">trademark</A>,
! <A HREF="http://www.w3.org/Consortium/Legal/copyright-documents.html">document
! use</A> and <A HREF="http://www.w3.org/Consortium/Legal/copyright-software.html">software
licensing</A> rules apply.</FONT></P>
<H2>Status of This Document</H2>
! <P>This document is a revision of the
! <A href="/TR/1998/WD-rdf-syntax-19980819">public working draft
! dated 1998-08-19</A> incorporating suggestions
! <A HREF="http://www.w3.org/Archives/Public/www-rdf-comments">received
! in review comments</A> and further deliberations of the W3C RDF Model
! and Syntax Working Group. With the publication of this draft, the RDF
! Model and Syntax Specification enters "last call." The last call
! period will end on October 23, 1998.</P>
!
! <P>Comments on this specification may be sent to
! <A href="mailto:www-rdf-comments@w3.org">www-rdf-comments@w3.org</A>.
The archive of public comments is available at
! <A href="http://www.w3.org/Archives/Public/www-rdf-comments">http://www.w3.org/Archives/Public/www-rdf-comments</A>.</P>
!
! <P>Significant changes from the previous draft are highlighted in
! <A HREF="#changes">Appendix E</A>.</P>
! <P>While we do not anticipate substantial changes, we still caution
! that further changes are possible. Therefore while we encourage
! active implementation to test this specification we also recommend that
! only software that can be easily field-upgraded be implemented to this
! specification at this time.</P>
!
! <P>This is
! a W3C Working Draft for review by W3C members and other interested
! parties. Publication as a working draft does not imply endorsement
! by the W3C membership. The RDF Model and Syntax Working Group will not allow
! early implementation to constrain their ability to make changes to
! this specification prior to final release. This is a draft document
and may be updated, replaced or obsoleted by other documents at any
! time. It is inappropriate to cite W3C Working Drafts as other than
"work in progress".</P>
<P>This work is part of the <A HREF="/Metadata/Activity">W3C Metadata
--- 69,116 ----
World Wide Web Consortium</DD>
</DL>
! <P><A href="/1999/.status/PR-rdf-syntax-19990105/status">Document Status</A></P>
! <P><FONT SIZE="-1"><A HREF="http://w3.org/Consortium/Legal/ipr-notice.html#Copyright">Copyright</A> © 1997,1998,1999
! <A HREF="http://w3.org">W3C</A> (<A HREF="http://www.lcs.mit.edu">MIT</A>,
<A HREF="http://www.inria.fr/">INRIA</A>, <A HREF="http://www.keio.ac.jp/">Keio</A>
! ), All Rights Reserved. W3C <A HREF="http://w3.org/Consortium/Legal/ipr-notice.html#LegalDisclaimer">liability,</A>
! <A HREF="http://w3.org/Consortium/Legal/ipr-notice.html#W3CTrademarks">trademark</A>,
! <A HREF="http://w3.org/Consortium/Legal/copyright-documents.html">document
! use</A> and <A HREF="http://w3.org/Consortium/Legal/copyright-software.html">software
licensing</A> rules apply.</FONT></P>
<H2>Status of This Document</H2>
! <P>This document is a
! <A HREF="/Consortium/Process/#RecsPR">Proposed Recommendation</A> of the
! <A HREF="http://w3.org/">World Wide Web Consortium</A>. Review comments
! on this specification should be sent by 2359Z February 3, 1999 to
! <<A HREF="mailto:www-rdf-comments@w3.org">www-rdf-comments@w3.org</A>>.
The archive of public comments is available at
! <A href="http://w3.org/Archives/Public/www-rdf-comments">http://w3.org/Archives/Public/www-rdf-comments</A>.
! W3C Members may send their formal comments, visible only to W3C staff, to
! <<A HREF="mailto:w3c-rdf-ballot@w3.org">w3c-rdf-ballot@w3.org</A>>.</P>
!
!
! <P>This specification is a revision of the
! <A href="/TR/1998/WD-rdf-syntax-19981008">public working draft
! dated 1998-10-08</A> incorporating suggestions received in
! <A HREF="http://w3.org/Archives/Public/www-rdf-comments">
! review comments</A>.
! Significant changes from the public working draft are highlighted in
! <A HREF="#changes">Appendix E</A>.
! The detailed <A HREF="lastCallDiff">differences</A>
! are available for reviewers to compare.</P>
!
! <P>The Working Group anticipates no further substantial changes to
! this specification. We encourage active implementation to test this
! specification during the Proposed Recommendation review period.</P>
! <P>Publication as a Proposed Recommendation 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 W3C Drafts as other than
"work in progress".</P>
<P>This work is part of the <A HREF="/Metadata/Activity">W3C Metadata
***************
*** 161,172 ****
<P>The World Wide Web was originally built
for human consumption, and although everything on it is <I>machine-readable</I>,
this data is not <I>machine-understandable</I>. It is very hard to automate
! anything on the web, and because of the volume of information the web contains,
it is not possible to manage it manually. The solution proposed here is
! to use <I>metadata</I> to describe the data contained on the web. Metadata
is "data about data" (for example, a library catalog is metadata,
since it describes publications) or specifically in the context of this
! specification "data describing web resources". The distinction
between "data" and "metadata" is not an absolute one;
it is a distinction created primarily by a particular application, and
many times the same resource will be interpreted in both ways simultaneously.
--- 161,172 ----
<P>The World Wide Web was originally built
for human consumption, and although everything on it is <I>machine-readable</I>,
this data is not <I>machine-understandable</I>. It is very hard to automate
! anything on the Web, and because of the volume of information the Web contains,
it is not possible to manage it manually. The solution proposed here is
! to use <I>metadata</I> to describe the data contained on the Web. Metadata
is "data about data" (for example, a library catalog is metadata,
since it describes publications) or specifically in the context of this
! specification "data describing Web resources". The distinction
between "data" and "metadata" is not an absolute one;
it is a distinction created primarily by a particular application, and
many times the same resource will be interpreted in both ways simultaneously.
***************
*** 184,201 ****
<I>collections of pages</I> that represent a single logical "document",
for describing <I>intellectual property rights</I> of Web pages, and for
expressing the <I>privacy preferences</I> of a user as well as the <I>privacy
! policies</I> of a web site. RDF with <I>digital signatures</I> will be
key to building the "Web of Trust" for electronic commerce, collaboration,
and other applications. </P>
<P>This document introduces a model for representing RDF metadata as well
as a syntax for encoding and transporting this metadata in a manner that
! maximizes the interoperability of independently developed web servers and
clients. The syntax presented here uses the Extensible Markup Language
[XML]: one of the goals of RDF is to make it possible to specify semantics
for data based on XML in a standardized, interoperable manner. RDF and
! XML are complementary: RDF is a model of metadata and only superficially
! addresses many of the encoding issues that transportation and file storage
require (such as internationalization, character sets, etc.). For these
issues, RDF relies on the support of XML. It is also important to understand
that this XML syntax is only one possible syntax for RDF and that alternate
--- 184,201 ----
<I>collections of pages</I> that represent a single logical "document",
for describing <I>intellectual property rights</I> of Web pages, and for
expressing the <I>privacy preferences</I> of a user as well as the <I>privacy
! policies</I> of a Web site. RDF with <I>digital signatures</I> will be
key to building the "Web of Trust" for electronic commerce, collaboration,
and other applications. </P>
<P>This document introduces a model for representing RDF metadata as well
as a syntax for encoding and transporting this metadata in a manner that
! maximizes the interoperability of independently developed Web servers and
clients. The syntax presented here uses the Extensible Markup Language
[XML]: one of the goals of RDF is to make it possible to specify semantics
for data based on XML in a standardized, interoperable manner. RDF and
! XML are complementary: RDF is a model of metadata and only addresses by
! reference many of the encoding issues that transportation and file storage
require (such as internationalization, character sets, etc.). For these
issues, RDF relies on the support of XML. It is also important to understand
that this XML syntax is only one possible syntax for RDF and that alternate
***************
*** 209,215 ****
<P>This specification will be followed by other documents that will complete
the framework. Most importantly, to facilitate the definition of metadata
! RDF will have a class system not unlike many object-oriented programming
and modeling systems. A collection of classes (typically authored for a
specific purpose or domain) is called a <I>schema</I>. Classes are organized
in a hierarchy, and offer extensibility through subclass refinement. This
--- 209,215 ----
<P>This specification will be followed by other documents that will complete
the framework. Most importantly, to facilitate the definition of metadata
! RDF will have a class system much like many object-oriented programming
and modeling systems. A collection of classes (typically authored for a
specific purpose or domain) is called a <I>schema</I>. Classes are organized
in a hierarchy, and offer extensibility through subclass refinement. This
***************
*** 233,242 ****
<P>As a result of many communities coming together and agreeing on basic
principles of metadata representation and transport, RDF has drawn influence
from several different sources. The main influences have come from the
! <I>web standardization community</I> itself in the form of HTML metadata
and PICS, the <I>library community</I>, the <I>structured document community</I>
in the form of SGML and more importantly XML, and also the <I>knowledge
! representation community</I>. There are also other areas of technology
that contributed to the RDF design; these include object-oriented programming
and modeling languages, as well as databases.
While RDF draws from the KR community, readers familiar with that field
--- 233,242 ----
<P>As a result of many communities coming together and agreeing on basic
principles of metadata representation and transport, RDF has drawn influence
from several different sources. The main influences have come from the
! <I>Web standardization community</I> itself in the form of HTML metadata
and PICS, the <I>library community</I>, the <I>structured document community</I>
in the form of SGML and more importantly XML, and also the <I>knowledge
! representation (KR) community</I>. There are also other areas of technology
that contributed to the RDF design; these include object-oriented programming
and modeling languages, as well as databases.
While RDF draws from the KR community, readers familiar with that field
***************
*** 264,270 ****
expressions. The data model representation is used to evaluate equivalence
in meaning. Two RDF expressions are equivalent if and only if their data
model representations are the same. This definition of equivalence permits
! some syntactic variation in expression without altering the meaning.</P>
<P>The basic data model consists of three object types:</P>
--- 264,273 ----
expressions. The data model representation is used to evaluate equivalence
in meaning. Two RDF expressions are equivalent if and only if their data
model representations are the same. This definition of equivalence permits
! some syntactic variation in expression without altering the meaning.
! (See <A HREF="#stringComparison">Section 6.</A> for additional discussion
! of string comparison issues.)
! </P>
<P>The basic data model consists of three object types:</P>
***************
*** 274,284 ****
<TD>All things being described by RDF expressions are called
<I>resources</I>.
! A resource may be an entire web page; such as the HTML document
! "http://www.w3.org/Overview.html" for example.
! A resource may be a part of a web page; e.g. a specific HTML or XML element
within the document source. A resource may also be a whole collection of
! pages; e.g. an entire web site. A resource may also be an object that
is not directly accessible via the Web; e.g. a printed book.
Resources are always named by URIs plus optional anchor IDs (see
[<A HREF="http://www.ietf.org/internet-drafts/draft-fielding-uri-syntax-04.txt">URI</A>]).
--- 277,287 ----
<TD>All things being described by RDF expressions are called
<I>resources</I>.
! A resource may be an entire Web page; such as the HTML document
! "http://w3.org/Overview.html" for example.
! A resource may be a part of a Web page; e.g. a specific HTML or XML element
within the document source. A resource may also be a whole collection of
! pages; e.g. an entire Web site. A resource may also be an object that
is not directly accessible via the Web; e.g. a printed book.
Resources are always named by URIs plus optional anchor IDs (see
[<A HREF="http://www.ietf.org/internet-drafts/draft-fielding-uri-syntax-04.txt">URI</A>]).
***************
*** 306,313 ****
that property for that resource is an RDF <I>statement</I>.
These three individual parts of a statement are called, respectively,
the <I>subject</I>, the <I>predicate</I>, and the <I>object</I>.
! The object of a statement (i.e. the property value) can be another
! resource or it can be a literal; i.e. a resource (specified by a URI)
or a simple string or other primitive datatype defined by XML. In RDF
terms, a <I>literal</I> may have content that is XML markup
but is not further evaluated by the RDF processor. There are some
--- 309,316 ----
that property for that resource is an RDF <I>statement</I>.
These three individual parts of a statement are called, respectively,
the <I>subject</I>, the <I>predicate</I>, and the <I>object</I>.
! The object of a statement (i.e., the property value) can be another
! resource or it can be a literal; i.e., a resource (specified by a URI)
or a simple string or other primitive datatype defined by XML. In RDF
terms, a <I>literal</I> may have content that is XML markup
but is not further evaluated by the RDF processor. There are some
***************
*** 430,436 ****
and using metadata. A concrete syntax is also needed for the purposes of
creating and exchanging this metadata. This specification of RDF uses
the <A HREF="http://www.w3.org/TR/REC-xml">Extensible Markup Language</A>
! [XML] encoding as its interchange syntax. RDF also requires the <A HREF="http://www.w3.org/TR/1998/WD-xml-names">XML
namespace facility</A> to precisely associate each property with the
schema that defines the property; see
<A HREF="#schemas">Section 2.2.3.</A>, Schemas and Namespaces.</P>
--- 433,439 ----
and using metadata. A concrete syntax is also needed for the purposes of
creating and exchanging this metadata. This specification of RDF uses
the <A HREF="http://www.w3.org/TR/REC-xml">Extensible Markup Language</A>
! [XML] encoding as its interchange syntax. RDF also requires the <A HREF="http://www.w3.org/TR/PR-xml-names">XML
namespace facility</A> to precisely associate each property with the
schema that defines the property; see
<A HREF="#schemas">Section 2.2.3.</A>, Schemas and Namespaces.</P>
***************
*** 464,470 ****
has been designed to accomodate this easily by grouping multiple statements
for the same resource into a <TT>Description</TT> element. The <TT>Description</TT>
element names, in an <TT>about</TT> attribute, the resource to which each
! of the statements apply. If the resource does not yet exist (i.e.
does not yet have a resource identifier) then a <TT>Description</TT>
element can create
the identifer for the resource using an <TT>ID</TT> attribute.</P>
--- 467,473 ----
has been designed to accomodate this easily by grouping multiple statements
for the same resource into a <TT>Description</TT> element. The <TT>Description</TT>
element names, in an <TT>about</TT> attribute, the resource to which each
! of the statements apply. If the resource does not yet exist (i.e.,
does not yet have a resource identifier) then a <TT>Description</TT>
element can create
the identifer for the resource using an <TT>ID</TT> attribute.</P>
***************
*** 486,492 ****
[11] URI-reference ::= string, interpreted per [<A HREF="http://www.isi.edu/in-notes/rfc2396.txt">URI</A>]
[12] IDsymbol ::= (any legal <A HREF="http://www.w3.org/TR/REC-xml#NT-Nmtoken">XML name symbol</A>)
[13] name ::= (any legal XML name symbol)
! [14] NSprefix ::= (any legal <A HREF="/TR/1998/WD-xml-names#ns-qualnames">XML namespace prefix</A>)
[15] string ::= (any XML text, with "<", ">", and "&" escaped)
</PRE>
--- 489,495 ----
[11] URI-reference ::= string, interpreted per [<A HREF="http://www.isi.edu/in-notes/rfc2396.txt">URI</A>]
[12] IDsymbol ::= (any legal <A HREF="http://www.w3.org/TR/REC-xml#NT-Nmtoken">XML name symbol</A>)
[13] name ::= (any legal XML name symbol)
! [14] NSprefix ::= (any legal <A HREF="/TR/PR-xml-names#ns-qualnames">XML namespace prefix</A>)
[15] string ::= (any XML text, with "<", ">", and "&" escaped)
</PRE>
***************
*** 513,519 ****
form as specified by [URI]. If a fragment identifier is included
in the URI-reference then the resource identifier refers only to the
subcomponent of the containing resource that is identifed by the
! corresponding anchor id internal to that containing resource (see
[<A HREF="http://www.acm.org/pubs/citations/journals/cacm/1994-37-2/p30-halasz/">Dexter94</A>]),
otherwise the
identifier refers to the entire resource specified by the URI.
--- 516,522 ----
form as specified by [URI]. If a fragment identifier is included
in the URI-reference then the resource identifier refers only to the
subcomponent of the containing resource that is identifed by the
! corresponding fragment id internal to that containing resource (see anchor in
[<A HREF="http://www.acm.org/pubs/citations/journals/cacm/1994-37-2/p30-halasz/">Dexter94</A>]),
otherwise the
identifier refers to the entire resource specified by the URI.
***************
*** 552,567 ****
quoting and escaping mechanisms may be used if the string contains character
sequences (e.g. "<" and "&") that violate the
well-formedness rules or that otherwise might look like markup.
! In this version of RDF there is no supported mechanism to specify that
! the value of a property is XML content containing markup other than by
! escaping the markup or writing the property using the attribute form
! shown in <A HREF="#abbreviatedSyntax">Section 2.2.2.</A></P>
! <P>Property names must always be associated with a schema. This can be
done by qualifying the element names with a namespace prefix to unambiguously
connect the property definition with the corresponding RDF schema
or by declaring a default namespace as specified in
! [<A HREF="/TR/1998/WD-xml-names#dt-defaultNS">NAMESPACES</A>].</P>
<P>The example sentence from Section 2.1.1</P>
--- 555,569 ----
quoting and escaping mechanisms may be used if the string contains character
sequences (e.g. "<" and "&") that violate the
well-formedness rules or that otherwise might look like markup.
! See <A HREF="#grammar">Section 6.</A> for additional syntax to specify
! a property value with well-formed XML content containing markup such that
! the markup is not interpreted by RDF.</P>
! <P>Property names must be associated with a schema. This can be
done by qualifying the element names with a namespace prefix to unambiguously
connect the property definition with the corresponding RDF schema
or by declaring a default namespace as specified in
! [<A HREF="/TR/PR-xml-names#dt-defaultNS">NAMESPACES</A>].</P>
<P>The example sentence from Section 2.1.1</P>
***************
*** 571,577 ****
<P>is represented in RDF/XML as:</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator>Ora Lassila</<I>s</I>:Creator>
</<I>rdf</I>:Description>
--- 573,579 ----
<P>is represented in RDF/XML as:</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator>Ora Lassila</<I>s</I>:Creator>
</<I>rdf</I>:Description>
***************
*** 599,607 ****
<P>The complete XML document containing the description above would be:</P>
! <PRE> <?xml version="1.0"?>
<rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:s="http://description.org/schema/">
<rdf:Description about="http://www.w3.org/Home/Lassila">
<s:Creator>Ora Lassila</s:Creator>
--- 601,609 ----
<P>The complete XML document containing the description above would be:</P>
! <PRE CLASS="EXAMPLE"><?xml version="1.0"?>
<rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:s="http://description.org/schema/">
<rdf:Description about="http://www.w3.org/Home/Lassila">
<s:Creator>Ora Lassila</s:Creator>
***************
*** 610,621 ****
</PRE>
<P>Using the default namespace syntax defined in
! [<A HREF="http://www.w3.org/TR/1998/WD-xml-names#dt-defaultNS">NAMESPACES</A>]
for the RDF namespace itself, this document could also be written as:</P>
! <PRE> <?xml version="1.0"?>
<RDF
! xmlns="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:s="http://description.org/schema/">
<Description about="http://www.w3.org/Home/Lassila">
<s:Creator>Ora Lassila</s:Creator>
--- 612,623 ----
</PRE>
<P>Using the default namespace syntax defined in
! [<A HREF="http://www.w3.org/TR/PR-xml-names#dt-defaultNS">NAMESPACES</A>]
for the RDF namespace itself, this document could also be written as:</P>
! <PRE CLASS="EXAMPLE"><?xml version="1.0"?>
<RDF
! xmlns="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:s="http://description.org/schema/">
<Description about="http://www.w3.org/Home/Lassila">
<s:Creator>Ora Lassila</s:Creator>
***************
*** 627,634 ****
an individual <tt>Description</tt> element or even an individual
propertyElt element as in:</P>
! <PRE> <?xml version="1.0"?>
! <RDF xmlns="http://www.w3.org/TR/WD-rdf-syntax#">
<Description about="http://www.w3.org/Home/Lassila">
<s:Creator xmlns:s="http://description.org/schema/">Ora Lassila</s:Creator>
</Description>
--- 629,636 ----
an individual <tt>Description</tt> element or even an individual
propertyElt element as in:</P>
! <PRE CLASS="EXAMPLE"><?xml version="1.0"?>
! <RDF xmlns="http://w3.org/TR/1999/PR-rdf-syntax-19990105#">
<Description about="http://www.w3.org/Home/Lassila">
<s:Creator xmlns:s="http://description.org/schema/">Ora Lassila</s:Creator>
</Description>
***************
*** 638,645 ****
<P>As XML namespace declarations may be nested, the previous example
may be further condensed to:</P>
! <PRE> <?xml version="1.0"?>
! <RDF xmlns="http://www.w3.org/TR/WD-rdf-syntax#">
<Description about="http://www.w3.org/Home/Lassila">
<Creator xmlns="http://description.org/schema/">Ora Lassila</Creator>
</Description>
--- 640,647 ----
<P>As XML namespace declarations may be nested, the previous example
may be further condensed to:</P>
! <PRE CLASS="EXAMPLE"><?xml version="1.0"?>
! <RDF xmlns="http://w3.org/TR/1999/PR-rdf-syntax-19990105#">
<Description about="http://www.w3.org/Home/Lassila">
<Creator xmlns="http://description.org/schema/">Ora Lassila</Creator>
</Description>
***************
*** 647,653 ****
</PRE>
<P>Highly condensed expressions such as this are discouraged, however,
! when the RDF/XML encoding is written by hand or expected to be editted
in a plain text editor. Though unambiguous, the possibility of error
is greater than if explicit prefixes are used consistently. Note that an
RDF/XML fragment that is intended to be inserted in other documents
--- 649,655 ----
</PRE>
<P>Highly condensed expressions such as this are discouraged, however,
! when the RDF/XML encoding is written by hand or expected to be edited
in a plain text editor. Though unambiguous, the possibility of error
is greater than if explicit prefixes are used consistently. Note that an
RDF/XML fragment that is intended to be inserted in other documents
***************
*** 665,676 ****
well-structured XML DTDs to be directly interpreted as RDF models.</P>
<P>Three forms of abbreviation are defined for the basic serialization
! syntax. The first is useable for properties that are not repeated within
a <TT>Description</TT> and where the values of those properties are literals.
In this case, the properties may be written as XML attributes of the
<TT>Description</TT> element. The previous example then becomes:</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila"
<I>s</I>:Creator="Ora Lassila" />
</<I>rdf</I>:RDF>
--- 667,678 ----
well-structured XML DTDs to be directly interpreted as RDF models.</P>
<P>Three forms of abbreviation are defined for the basic serialization
! syntax. The first is usable for properties that are not repeated within
a <TT>Description</TT> and where the values of those properties are literals.
In this case, the properties may be written as XML attributes of the
<TT>Description</TT> element. The previous example then becomes:</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila"
<I>s</I>:Creator="Ora Lassila" />
</<I>rdf</I>:RDF>
***************
*** 682,688 ****
<P>Here is another example of the use of this same abbreviation form:</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org">
<<I>s</I>:Publisher>World Wide Web Consortium</<I>s</I>:Publisher>
<<I>s</I>:Title>W3C Home Page</<I>s</I>:Title>
--- 684,690 ----
<P>Here is another example of the use of this same abbreviation form:</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org">
<<I>s</I>:Publisher>World Wide Web Consortium</<I>s</I>:Publisher>
<<I>s</I>:Title>W3C Home Page</<I>s</I>:Title>
***************
*** 693,699 ****
<P>is equivalent for RDF purposes to</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org"
<I>s</I>:Publisher="World Wide Web Consortium"
<I>s</I>:Title="W3C Home Page"
--- 695,701 ----
<P>is equivalent for RDF purposes to</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org"
<I>s</I>:Publisher="World Wide Web Consortium"
<I>s</I>:Title="W3C Home Page"
***************
*** 728,734 ****
<P>is written in RDF/XML using explicit serialization form as</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator <I>rdf</I>:resource="<TT>http://www.w3.org/staffId/85740</TT>"/>
</<I>rdf</I>:Description>
--- 730,736 ----
<P>is written in RDF/XML using explicit serialization form as</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator <I>rdf</I>:resource="<TT>http://www.w3.org/staffId/85740</TT>"/>
</<I>rdf</I>:Description>
***************
*** 746,752 ****
way to make this relationship more obvious to the human reader. Note that
to the machine, there is no difference:</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator>
<<I>rdf</I>:Description about="<TT>http://www.w3.org/staffId/85740</TT>">
--- 748,754 ----
way to make this relationship more obvious to the human reader. Note that
to the machine, there is no difference:</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator>
<<I>rdf</I>:Description about="<TT>http://www.w3.org/staffId/85740</TT>">
***************
*** 762,768 ****
element and its contained property expressions can be written as attributes
of the Creator element:</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator <I>rdf</I>:resource="<TT>http://www.w3.org/staffId/85740</TT>"
<I>v</I>:Name="Ora Lassila"
--- 764,770 ----
element and its contained property expressions can be written as attributes
of the Creator element:</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator <I>rdf</I>:resource="<TT>http://www.w3.org/staffId/85740</TT>"
<I>v</I>:Name="Ora Lassila"
***************
*** 797,803 ****
http://www.w3.org/staffId/85740 represents an instance of a Person, we
would write this in full serialization syntax as:</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator>
<<I>rdf</I>:Description about="<TT>http://www.w3.org/staffId/85740</TT>">
--- 799,805 ----
http://www.w3.org/staffId/85740 represents an instance of a Person, we
would write this in full serialization syntax as:</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator>
<<I>rdf</I>:Description about="<TT>http://www.w3.org/staffId/85740</TT>">
***************
*** 812,818 ****
and using this third abbreviated form as:
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator>
<<I>s</I>:Person about="<TT>http://www.w3.org/staffId/85740</TT>">
--- 814,820 ----
and using this third abbreviated form as:
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila">
<<I>s</I>:Creator>
<<I>s</I>:Person about="<TT>http://www.w3.org/staffId/85740</TT>">
***************
*** 972,978 ****
<P>the RDF model is</P>
! <CENTER><P><IMG SRC="fig4.gif" ALT="Simple bag container" /><A href="fig4.html">D</A></P></CENTER>
<CENTER><P>Figure 4: Simple Bag container</P></CENTER>
--- 974,980 ----
<P>the RDF model is</P>
! <CENTER><P><IMG SRC="fig4.gif" ALT="Simple Bag container" /><A href="fig4.html">D</A></P></CENTER>
<CENTER><P>Figure 4: Simple Bag container</P></CENTER>
***************
*** 1022,1028 ****
<P>Note that RDF/XML uses <TT>li</TT> as a convenience element to avoid
having to explicitly number each member. The <TT>li</TT> element assigns
! the properties <tt>_1</tt>, <tt>_2</tt>, and so on as necessary.</P>
<P>An <TT>Alt</TT> container is required to have at least one member. This
member will be identified by the property <tt>_1</tt> and is the
--- 1024,1033 ----
<P>Note that RDF/XML uses <TT>li</TT> as a convenience element to avoid
having to explicitly number each member. The <TT>li</TT> element assigns
! the properties <tt>_1</tt>, <tt>_2</tt>, and so on as necessary.
! The element name <TT>li</TT> was chosen to be mnemonic with the term
! "list item"
! from <A HREF="http://www.w3.org/TR/REC-html40">HTML</A>.</P>
<P>An <TT>Alt</TT> container is required to have at least one member. This
member will be identified by the property <tt>_1</tt> and is the
***************
*** 1048,1054 ****
<P>is written in RDF/XML as</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://mycollege.edu/courses/6.001">
<<I>s</I>:students>
<<I>rdf</I>:Bag>
--- 1053,1059 ----
<P>is written in RDF/XML as</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://mycollege.edu/courses/6.001">
<<I>s</I>:students>
<<I>rdf</I>:Bag>
***************
*** 1076,1082 ****
<P>is written in RDF/XML as</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://x.org/packages/X11">
<<I>s</I>:DistributionSite>
<<I>rdf</I>:Alt>
--- 1081,1087 ----
<P>is written in RDF/XML as</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://x.org/packages/X11">
<<I>s</I>:DistributionSite>
<<I>rdf</I>:Alt>
***************
*** 1104,1110 ****
<P>The following example: </P>
! <PRE> <<I>rdf</I>:Bag ID="pages">
<<I>rdf</I>:li resource="http://foo.org/foo.html" />
<<I>rdf</I>:li resource="http://bar.org/bar.html" />
</<I>rdf</I>:Bag>
--- 1109,1115 ----
<P>The following example: </P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:Bag ID="pages">
<<I>rdf</I>:li resource="http://foo.org/foo.html" />
<<I>rdf</I>:li resource="http://bar.org/bar.html" />
</<I>rdf</I>:Bag>
***************
*** 1115,1123 ****
</PRE>
<P>expresses that "Ora Lassila" is the creator
! of the bag "pages". It does not, however, say anything about
! the individual pages, the members of the bag. The referent of the <TT>Description</TT>
! is the container (the bag), not its members. One would sometimes like to
write a statement about each of the contained objects individually, instead
of the container itself. In order to express that "Ora Lassila"
is the creator of each of the pages, a different kind of referent is called
--- 1120,1128 ----
</PRE>
<P>expresses that "Ora Lassila" is the creator
! of the Bag "pages". It does not, however, say anything about
! the individual pages, the members of the Bag. The referent of the <TT>Description</TT>
! is the container (the Bag), not its members. One would sometimes like to
write a statement about each of the contained objects individually, instead
of the container itself. In order to express that "Ora Lassila"
is the creator of each of the pages, a different kind of referent is called
***************
*** 1130,1136 ****
<P>As an example, if we wrote </P>
! <PRE> <<I>rdf</I>:Description aboutEach="#pages">
<<i>s</i>:Creator>Ora Lassila</<i>s</i>:Creator>
</<I>rdf</I>:Description>
</PRE>
--- 1135,1141 ----
<P>As an example, if we wrote </P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:Description aboutEach="#pages">
<<i>s</i>:Creator>Ora Lassila</<i>s</i>:Creator>
</<I>rdf</I>:Description>
</PRE>
***************
*** 1155,1161 ****
to the resources "foo" and "bar", the above example
is equivalent to </P>
! <PRE> <<I>rdf</I>:Description about="http://foo.org/foo.html">
<<i>s</i>:Creator>Ora Lassila</<i>s</i>:Creator>
</<I>rdf</I>:Description>
--- 1160,1166 ----
to the resources "foo" and "bar", the above example
is equivalent to </P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:Description about="http://foo.org/foo.html">
<<i>s</i>:Creator>Ora Lassila</<i>s</i>:Creator>
</<I>rdf</I>:Description>
***************
*** 1167,1174 ****
<H3><A name="URIPrefix">3.4.</A> Containers Defined By A URI Pattern</H3>
<P>One very frequent use of metadata is to make statements about "all
! pages at my web site", or "all pages in this branch of my
! web site". In many cases it is impractical or even undesirable
to try to list each such resource explicitly and identify it as a
member of a container. RDF therefore has a second distributive
referent type. This second distributive referent type is a
--- 1172,1179 ----
<H3><A name="URIPrefix">3.4.</A> Containers Defined By A URI Pattern</H3>
<P>One very frequent use of metadata is to make statements about "all
! pages at my Web site", or "all pages in this branch of my
! Web site". In many cases it is impractical or even undesirable
to try to list each such resource explicitly and identify it as a
member of a container. RDF therefore has a second distributive
referent type. This second distributive referent type is a
***************
*** 1191,1197 ****
http://foo.org/doc/page2 exist then we can say that each of them
has a copyright property by writing</P>
! <PRE> <<I>rdf</I>:Description aboutEachPrefix="http://foo.org/doc">
<<i>s</i>:Copyright>© 1998, The Foo Organization</<i>s</i>:Copyright>
</<I>rdf</I>:Description>
</PRE>
--- 1196,1202 ----
http://foo.org/doc/page2 exist then we can say that each of them
has a copyright property by writing</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:Description aboutEachPrefix="http://foo.org/doc">
<<i>s</i>:Copyright>© 1998, The Foo Organization</<i>s</i>:Copyright>
</<I>rdf</I>:Description>
</PRE>
***************
*** 1199,1205 ****
<P>If these are the only two resources whose URIs start with that
string then the above is equivalent to both of the following alternatives:</P>
! <PRE> <<I>rdf</I>:Description about="http://foo.org/doc/page1">
<<i>s</i>:Copyright>© 1998, The Foo Organization</<i>s</i>:Copyright>
</<I>rdf</I>:Description>
<<I>rdf</I>:Description about="http://foo.org/doc/page2">
--- 1204,1210 ----
<P>If these are the only two resources whose URIs start with that
string then the above is equivalent to both of the following alternatives:</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:Description about="http://foo.org/doc/page1">
<<i>s</i>:Copyright>© 1998, The Foo Organization</<i>s</i>:Copyright>
</<I>rdf</I>:Description>
<<I>rdf</I>:Description about="http://foo.org/doc/page2">
***************
*** 1209,1215 ****
<P>and</P>
! <PRE> <<I>rdf</I>:Description aboutEach="#docpages">
<<i>s</i>:Copyright>© 1998, The Foo Organization</<i>s</i>:Copyright>
</<I>rdf</I>:Description>
<<I>rdf</I>:Bag ID="docpages">
--- 1214,1220 ----
<P>and</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:Description aboutEach="#docpages">
<<i>s</i>:Copyright>© 1998, The Foo Organization</<i>s</i>:Copyright>
</<I>rdf</I>:Description>
<<I>rdf</I>:Bag ID="docpages">
***************
*** 1221,1227 ****
<H3><A name="RepeatedProperties">3.5.</A> Containers Versus Repeated Properties</H3>
<P>A resource may have multiple statements with the same predicate
! (i.e. using the same property).
This is not the same as having a single statement whose object is a container
containing multiple members. The choice of which to use in any particular
circumstance is in part made by the person who designs the schema and in
--- 1226,1232 ----
<H3><A name="RepeatedProperties">3.5.</A> Containers Versus Repeated Properties</H3>
<P>A resource may have multiple statements with the same predicate
! (i.e., using the same property).
This is not the same as having a single statement whose object is a container
containing multiple members. The choice of which to use in any particular
circumstance is in part made by the person who designs the schema and in
***************
*** 1273,1279 ****
<H2><A NAME="higherorder"></A>4. Statements about Statements</H2>
! <P>In addition to making statements about web resources, RDF can be used
for making statements about other RDF statements; we will refer to these
as <I>higher-order statements</I>. In order to make a statement about another
statement, we actually have to build a model of the original statement;
--- 1278,1284 ----
<H2><A NAME="higherorder"></A>4. Statements about Statements</H2>
! <P>In addition to making statements about Web resources, RDF can be used
for making statements about other RDF statements; we will refer to these
as <I>higher-order statements</I>. In order to make a statement about another
statement, we actually have to build a model of the original statement;
***************
*** 1364,1377 ****
"Ralph Swick"). Using base-level RDF/XML syntax, this could be
written as </P>
! <PRE> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:a="http://description.org/schema/">
<rdf:Description>
<rdf:subject resource="http://www.w3.org/Home/Lassila" />
<rdf:predicate resource="http://description.org/schema#Creator" />
<rdf:object>Ora Lassila</rdf:object>
! <rdf:type resource="http://www.w3.org/TR/WD-rdf-syntax#Statement" />
<a:attributedTo>Ralph Swick</a:attributedTo>
</rdf:Description>
</rdf:RDF>
--- 1369,1382 ----
"Ralph Swick"). Using base-level RDF/XML syntax, this could be
written as </P>
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:a="http://description.org/schema/">
<rdf:Description>
<rdf:subject resource="http://www.w3.org/Home/Lassila" />
<rdf:predicate resource="http://description.org/schema#Creator" />
<rdf:object>Ora Lassila</rdf:object>
! <rdf:type resource="http://w3.org/TR/1999/PR-rdf-syntax-19990105#Statement" />
<a:attributedTo>Ralph Swick</a:attributedTo>
</rdf:Description>
</rdf:RDF>
***************
*** 1390,1400 ****
model does not need a special construct for <TT>Description</TT>s; since
<TT>Description</TT>s really are collections of statements, a <TT>Bag</TT>
container is used to indicate that a set of statements came from the same
! (syntactic) <TT>Description.</TT> This bag is created by reifying each
statement of a <TT>Description</TT>, and making the reified statements
! members of the bag. As an example, the RDF fragment</P>
! <PRE> <<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila" bagID="D_001">
<<i>s</i>:Creator>Ora Lassila</<i>s</i>:Creator>
<<i>s</i>:Title>Ora's Home Page</<i>s</i>:Title>
--- 1395,1405 ----
model does not need a special construct for <TT>Description</TT>s; since
<TT>Description</TT>s really are collections of statements, a <TT>Bag</TT>
container is used to indicate that a set of statements came from the same
! (syntactic) <TT>Description.</TT> This Bag is created by reifying each
statement of a <TT>Description</TT>, and making the reified statements
! members of the Bag. As an example, the RDF fragment</P>
! <PRE CLASS="EXAMPLE"><<I>rdf</I>:RDF>
<<I>rdf</I>:Description about="http://www.w3.org/Home/Lassila" bagID="D_001">
<<i>s</i>:Creator>Ora Lassila</<i>s</i>:Creator>
<<i>s</i>:Title>Ora's Home Page</<i>s</i>:Title>
***************
*** 1427,1440 ****
<H3><A NAME="reificationShorthand">4.2.</A> Syntactic Shorthand for Statements About Statements</H3>
<P>Since attaching a <TT>bagID</TT> to a <TT>Description</TT> results in
! including in the model a bag of the reified statements of the <TT>Description</TT>,
we can use this as a syntactic shorthand when making statements about statements.
For example, if we wanted to say that Ralph states that Ora is the creator
of http://www.w3.org/Home/Lassila and that he also states that the title
! of that resource is "Ora's Home Page" we can simply add to
the example above</P>
! <PRE> <<i>rdf</i>:Description aboutEach="#D_001">
<<i>a</i>:attributedTo>Ralph Swick</<i>a</i>:attributedTo>
</<i>rdf</i>:Description>
</PRE>
--- 1432,1445 ----
<H3><A NAME="reificationShorthand">4.2.</A> Syntactic Shorthand for Statements About Statements</H3>
<P>Since attaching a <TT>bagID</TT> to a <TT>Description</TT> results in
! including in the model a Bag of the reified statements of the <TT>Description</TT>,
we can use this as a syntactic shorthand when making statements about statements.
For example, if we wanted to say that Ralph states that Ora is the creator
of http://www.w3.org/Home/Lassila and that he also states that the title
! of that resource is "Ora's Home Page", we can simply add to
the example above</P>
! <PRE CLASS="EXAMPLE"><<i>rdf</i>:Description aboutEach="#D_001">
<<i>a</i>:attributedTo>Ralph Swick</<i>a</i>:attributedTo>
</<i>rdf</i>:Description>
</PRE>
***************
*** 1655,1717 ****
<P>The complete BNF for RDF is reproduced here from previous sections.
The precise interpretation of the grammar in terms of the formal model
is also given. Syntactic features inherited from XML are not
! reproduced here. These include all well-formedness constraints as
well as the use of either double or single quotes around attribute values.
This section is intended for implementors who are building
tools that read and interpret RDF/XML syntax.</P>
! <PRE> [6.1] RDF ::= '<<I>rdf</I>:RDF>' obj* '</<I>rdf</I>:RDF>'
! [6.2] obj ::= description | container
! [6.3] description ::= '<<I>rdf</I>:Description' idAboutAttr? bagIdAttr? propAttr* '/>'
! | '<<I>rdf</I>:Description' idAboutAttr? bagIdAttr? propAttr* '>'
! propertyElt* '</<I>rdf</I>:Description>'
! | typedNode
! [6.4] container ::= sequence | bag | alternative
! [6.5] idAboutAttr ::= idAttr | aboutAttr | aboutEachAttr
! [6.6] idAttr ::= 'ID="' IDsymbol '"'
! [6.7] aboutAttr ::= 'about="' URI-reference '"'
! [6.8] aboutEachAttr ::= 'aboutEach="' URI-reference '"'
! | 'aboutEachPrefix="' string '"'
! [6.9] bagIdAttr ::= 'bagID="' IDsymbol '"'
! [6.10] propAttr ::= typeAttr
! | propName '="' string '"' (with embedded quotes escaped)
! [6.11] typeAttr ::= 'type="' URI-reference '"'
! [6.12] propertyElt ::= '<' propName idAttr? '>' value '</' propName '>'
! | '<' propName idRefAttr? bagIdAttr? propAttr* '/>'
! [6.13] typedNode ::= '<' typeName idAboutAttr? bagIdAttr? propAttr* '/>'
! | '<' typeName idAboutAttr? bagIdAttr? propAttr* '>'
! propertyElt* '</' typeName '>'
! [6.14] propName ::= Qname
! [6.15] typeName ::= Qname
! [6.16] idRefAttr ::= idAttr | resourceAttr
! [6.17] value ::= obj | string
! [6.18] resourceAttr ::= 'resource="' URI-reference '"'
! [6.19] Qname ::= [ NSprefix ':' ] name
! [6.20] URI-reference ::= string, interpreted per [<A HREF="http://www.isi.edu/in-notes/rfc2396.txt">URI</A>]
! [6.21] IDsymbol ::= (any legal <A HREF="http://www.w3.org/TR/REC-xml#NT-Nmtoken">XML name symbol</A>)
! [6.22] name ::= (any legal XML name symbol)
! [6.23] NSprefix ::= (any legal XML namespace prefix)
! [6.24] string ::= (any XML text, with "<", ">", and "&" escaped)
! [6.25] sequence ::= '<<I>rdf</I>:Seq' idAttr? '>' member* '</<I>rdf</I>:Seq>'
! | '<<I>rdf</I>:Seq' idAttr? memberAttr* '/>'
! [6.26] bag ::= '<<I>rdf</I>:Bag' idAttr? '>' member* '</<I>rdf</I>:Bag>'
! | '<<I>rdf</I>:Bag' idAttr? memberAttr* '/>'
! [6.27] alternative ::= '<<I>rdf</I>:Alt' idAttr? '>' member+ '</<I>rdf</I>:Alt>'
! | '<<I>rdf</I>:Alt' idAttr? memberAttr? '/>'
! [6.28] member ::= referencedItem | inlineItem
! [6.29] referencedItem ::= '<<I>rdf</I>:li' resourceAttr '/>'
! [6.30] inlineItem ::= '<<I>rdf</I>:li>' value </<I>rdf</I>:li>'
! [6.31] memberAttr ::= '<I>rdf</I>:_<I>n</I>="' string '"' (where <I>n</I> is an integer)
</PRE>
<P>The formal namespace name for the properties and classes defined in
! this specification is <tt>http://www.w3.org/TR/WD-rdf-syntax#</tt>.
When an RDF processor encounters an XML element or attribute name
that is declared to be from a namespace whose name begins with
the string <A NAME="reservedURI"></A>
"http://www.w3.org/TR/REC-rdf-syntax" and the
processor does not recognize the semantics of that name then the
! processor is required to skip (i.e. generate no tuples for) the entire
XML element, including its content, whose name is unrecognized or that
has an attribute whose name is unrecognized.</P>
--- 1660,1738 ----
<P>The complete BNF for RDF is reproduced here from previous sections.
The precise interpretation of the grammar in terms of the formal model
is also given. Syntactic features inherited from XML are not
! reproduced here. These include all well-formedness constraints, the
! use of whitespace around attributes and the '=', as
well as the use of either double or single quotes around attribute values.
This section is intended for implementors who are building
tools that read and interpret RDF/XML syntax.</P>
! <P>Where used below, the keywords "SHOULD",
! "MUST", and "MUST NOT" are to be interpreted
! as described in RFC 2119 [<A HREF="http://www.isi.edu/in-notes/rfc2119.txt">RFC2119</A>].
! However, for readability,
! these words do not appear in all uppercase letters in this specification.</P>
!
! <PRE> [6.1] <A NAME="RDF">RDF</A> ::= ['<<I>rdf</I>:RDF>'] <A HREF="#obj">obj</A>* ['</<I>rdf</I>:RDF>']
! [6.2] <A NAME="obj">obj</A> ::= <A HREF="#description">description</A> | <A HREF="#container">container</A>
! [6.3] <A NAME="description">description</A> ::= '<<I>rdf</I>:Description' <A HREF="#idAboutAttr">idAboutAttr</A>? <A HREF="#bagIdAttr">bagIdAttr</A>? <A HREF="#propAttr">propAttr</A>* '/>'
! | '<<I>rdf</I>:Description' <A HREF="#idAboutAttr">idAboutAttr</A>? <A HREF="#bagIdAttr">bagIdAttr</A>? <A HREF="#propAttr">propAttr</A>* '>'
! <A HREF="#propertyElt">propertyElt</A>* '</<I>rdf</I>:Description>'
! | <A HREF="#typedNode">typedNode</A>
! [6.4] <A NAME="container">container</A> ::= <A HREF="#sequence">sequence</A> | <A HREF="#bag">bag</A> | <A HREF="#alternative">alternative</A>
! [6.5] <A NAME="idAboutAttr">idAboutAttr</A> ::= <A HREF="#idAttr">idAttr</A> | <A HREF="#aboutAttr">aboutAttr</A> | <A HREF="#aboutEachAttr">aboutEachAttr</A>
! [6.6] <A NAME="idAttr">idAttr</A> ::= ' ID="' <A HREF="#IDsymbol">IDsymbol</A> '"'
! [6.7] <A NAME="aboutAttr">aboutAttr</A> ::= ' about="' <A HREF="#URI-reference">URI-reference</A> '"'
! [6.8] <A NAME="aboutEachAttr">aboutEachAttr</A> ::= ' aboutEach="' <A HREF="#URI-reference">URI-reference</A> '"'
! | ' aboutEachPrefix="' <A HREF="#string">string</A> '"'
! [6.9] <A NAME="bagIdAttr">bagIdAttr</A> ::= ' bagID="' <A HREF="#IDsymbol">IDsymbol</A> '"'
! [6.10] <A NAME="propAttr">propAttr</A> ::= <A HREF="#typeAttr">typeAttr</A>
! | <A HREF="#propName">propName</A> '="' <A HREF="#string">string</A> '"' (with embedded quotes escaped)
! [6.11] <A NAME="typeAttr">typeAttr</A> ::= ' type="' <A HREF="#URI-reference">URI-reference</A> '"'
! [6.12] <A NAME="propertyElt">propertyElt</A> ::= '<' <A HREF="#propName">propName</A> <A HREF="#idAttr">idAttr</A>? '>' <A HREF="#value">value</A> '</' <A HREF="#propName">propName</A> '>'
! | '<' <A HREF="#propName">propName</A> <A HREF="#idAttr">idAttr</A>? <A HREF="#parseLiteral">parseLiteral</A> '>'
! <A HREF="#literal">literal</A> '</' <A HREF="#propName">propName</A> '>'
! | '<' <A HREF="#propName">propName</A> <A HREF="#idAttr">idAttr</A>? <A HREF="#parseResource">parseResource</A> '>'
! <A HREF="#propertyElt">propertyElt</A>* '</' <A HREF="#propName">propName</A> '>'
! | '<' <A HREF="#propName">propName</A> <A HREF="#idRefAttr">idRefAttr</A>? <A HREF="#bagIdAttr">bagIdAttr</A>? <A HREF="#propAttr">propAttr</A>* '/>'
! [6.13] <A NAME="typedNode">typedNode</A> ::= '<' <A HREF="#typeName">typeName</A> <A HREF="#idAboutAttr">idAboutAttr</A>? <A HREF="#bagIdAttr">bagIdAttr</A>? <A HREF="#propAttr">propAttr</A>* '/>'
! | '<' <A HREF="#typeName">typeName</A> <A HREF="#idAboutAttr">idAboutAttr</A>? <A HREF="#bagIdAttr">bagIdAttr</A>? <A HREF="#propAttr">propAttr</A>* '>'
! <A HREF="#propertyElt">propertyElt</A>* '</' <A HREF="#typeName">typeName</A> '>'
! [6.14] <A NAME="propName">propName</A> ::= <A HREF="#Qname">Qname</A>
! [6.15] <A NAME="typeName">typeName</A> ::= <A HREF="#Qname">Qname</A>
! [6.16] <A NAME="idRefAttr">idRefAttr</A> ::= <A HREF="#idAttr">idAttr</A> | <A HREF="#resourceAttr">resourceAttr</A>
! [6.17] <A NAME="value">value</A> ::= <A HREF="#obj">obj</A> | <A HREF="#string">string</A>
! [6.18] <A NAME="resourceAttr">resourceAttr</A> ::= ' resource="' <A HREF="#URI-reference">URI-reference</A> '"'
! [6.19] <A NAME="Qname">Qname</A> ::= [ <A HREF="#NSprefix">NSprefix</A> ':' ] <A HREF="#name">name</A>
! [6.20] <A NAME="URI-reference">URI-reference</A> ::= <A HREF="#string">string</A>, interpreted per [<A HREF="http://www.isi.edu/in-notes/rfc2396.txt">URI</A>]
! [6.21] <A NAME="IDsymbol">IDsymbol</A> ::= (any legal <A HREF="http://www.w3.org/TR/REC-xml#NT-Nmtoken">XML name symbol</A>)
! [6.22] <A NAME="name">name</A> ::= (any legal <A HREF="http://www.w3.org/TR/REC-xml#NT-Nmtoken">XML name symbol</A>)
! [6.23] <A NAME="NSprefix">NSprefix</A> ::= (any legal XML namespace prefix)
! [6.24] <A NAME="string">string</A> ::= (any XML text, with "<", ">", and "&" escaped)
! [6.25] <A NAME="sequence">sequence</A> ::= '<<I>rdf</I>:Seq' <A HREF="#idAttr">idAttr</A>? '>' <A HREF="#member">member</A>* '</<I>rdf</I>:Seq>'
! | '<<I>rdf</I>:Seq' <A HREF="#idAttr">idAttr</A>? <A HREF="#memberAttr">memberAttr</A>* '/>'
! [6.26] <A NAME="bag">bag</A> ::= '<<I>rdf</I>:Bag' <A HREF="#idAttr">idAttr</A>? '>' <A HREF="#member">member</A>* '</<I>rdf</I>:Bag>'
! | '<<I>rdf</I>:Bag' <A HREF="#idAttr">idAttr</A>? <A HREF="#memberAttr">memberAttr</A>* '/>'
! [6.27] <A NAME="alternative">alternative</A> ::= '<<I>rdf</I>:Alt' <A HREF="#idAttr">idAttr</A>? '>' <A HREF="#member">member</A>+ '</<I>rdf</I>:Alt>'
! | '<<I>rdf</I>:Alt' <A HREF="#idAttr">idAttr</A>? <A HREF="#memberAttr">memberAttr</A>? '/>'
! [6.28] <A NAME="member">member</A> ::= <A HREF="#referencedItem">referencedItem</A> | <A HREF="#inlineItem">inlineItem</A>
! [6.29] <A NAME="referencedItem">referencedItem</A> ::= '<<I>rdf</I>:li' <A HREF="#resourceAttr">resourceAttr</A> '/>'
! [6.30] <A NAME="inlineItem">inlineItem</A> ::= '<<I>rdf</I>:li' '>' <A HREF="#value">value</A> </<I>rdf</I>:li>'
! | '<<I>rdf</I>:li' <A HREF="#parseLiteral">parseLiteral</A> '>' <A HREF="#literal">literal</A> </<I>rdf</I>:li>'
! | '<<I>rdf</I>:li' <A HREF="#parseResource">parseResource</A> '>' <A HREF="#propertyElt">propertyElt</A>* </<I>rdf</I>:li>'
! [6.31] <A NAME="memberAttr">memberAttr</A> ::= ' <I>rdf</I>:_<I>n</I>="' <A HREF="#string">string</A> '"' (where <I>n</I> is an integer)
! [6.32] <A NAME="parseLiteral">parseLiteral</A> ::= ' parseType="Literal"'
! [6.33] <A NAME="parseResource">parseResource</A> ::= ' parseType="Resource"'
! [6.34] <A NAME="literal">literal</A> ::= (any well-formed XML)
</PRE>
<P>The formal namespace name for the properties and classes defined in
! this specification is <tt>http://w3.org/TR/1999/PR-rdf-syntax-19990105#</tt>.
When an RDF processor encounters an XML element or attribute name
that is declared to be from a namespace whose name begins with
the string <A NAME="reservedURI"></A>
"http://www.w3.org/TR/REC-rdf-syntax" and the
processor does not recognize the semantics of that name then the
! processor is required to skip (i.e., generate no tuples for) the entire
XML element, including its content, whose name is unrecognized or that
has an attribute whose name is unrecognized.</P>
***************
*** 1723,1729 ****
of <I>E</I>.
This expansion is generated by concatenating the namespace
name given in the namespace declaration with the
! <A HREF="/TR/WD-xml-names#NT-LocalPart">LocalPart</A>
of the qualified name.
</LI>
--- 1744,1750 ----
of <I>E</I>.
This expansion is generated by concatenating the namespace
name given in the namespace declaration with the
! <A HREF="/TR/PR-xml-names#NT-LocalPart">LocalPart</A>
of the qualified name.
</LI>
***************
*** 1733,1751 ****
<LI>the resource whose identifier is given by the value of the <TT>about</TT>
attribute of the <TT>Description</TT> or</LI>
! <LI>a new resource whose identification is the value of the <TT>ID</TT>
attribute of the <TT>Description</TT>, if present; else the new resource
! has no identification.</LI>
</UL></LI>
<LI>If <I>E</I> is an empty element (no content), v is the resource whose
identifier is given by the <TT>resource</TT> attribute of <I>E</I>. If the content
! of <I>E</I> contains no XML markup, v is the content of <I>E</I> (a string).
Otherwise, the content of <I>E</I> must be another <TT>Description</TT>
or container and v is the resource named by the (possibly implicit) <TT>ID</TT>
or <TT>about</TT> of that <TT>Description</TT> or container.</LI>
</OL>
<P>URI-References are resolved to resource identifiers by first resolving
the URI-reference to absolute form as specified by
[<A HREF="http://www.isi.edu/in-notes/rfc2396.txt">URI</A>]
--- 1754,1802 ----
<LI>the resource whose identifier is given by the value of the <TT>about</TT>
attribute of the <TT>Description</TT> or</LI>
! <LI>a new resource whose identifier is the value of the <TT>ID</TT>
attribute of the <TT>Description</TT>, if present; else the new resource
! has no identifier.</LI>
</UL></LI>
<LI>If <I>E</I> is an empty element (no content), v is the resource whose
identifier is given by the <TT>resource</TT> attribute of <I>E</I>. If the content
! of <I>E</I> contains no XML markup or if <TT>parseType="Literal"</TT>
! is specified in the start tag of <I>E</I> then v is the content of <I>E</I>
! (a literal).
Otherwise, the content of <I>E</I> must be another <TT>Description</TT>
or container and v is the resource named by the (possibly implicit) <TT>ID</TT>
or <TT>about</TT> of that <TT>Description</TT> or container.</LI>
</OL>
+ <P>The <TT>parseType</TT> attribute changes the interpretation of the
+ element content. The <TT>parseType</TT> attribute should have one of
+ the values 'Literal' or 'Resource'. The value is case-sensitive.
+ The value 'Literal' specifies that the element
+ content is to be treated as an RDF/XML literal; that is, the
+ content must not be interpreted by an RDF processor. The
+ value 'Resource' specifies that the element content must be
+ treated as if it were the content of a <TT>Description</TT> element.
+ Other values of <TT>parseType</TT> are reserved for future
+ specification by RDF. With RDF 1.0 other values must
+ be treated as identical to 'Literal'. In all cases, the content
+ of an element having a <TT>parseType</TT> attribute must be
+ well-formed XML. The content of an element having a
+ <TT>parseType="Resource"</TT> attribute must further match the
+ production for the content of a <TT>Description</TT> element.</P>
+
+ <BLOCKQUOTE>
+ The RDF Model and Syntax Working Group acknowledges that the
+ parseType='Literal' mechanism is a minimum-level solution to the
+ requirement to express an RDF statement with a value that
+ has XML markup. Additional complexities of XML such as
+ canonicalization of whitespace are not yet well defined.
+ Future work of the W3C is expected to resolve such issues in
+ a uniform manner for all applications based on XML. Future
+ versions of RDF will inherit this work and may extend it as
+ we gain insight from further application experience.
+ </BLOCKQUOTE>
+
<P>URI-References are resolved to resource identifiers by first resolving
the URI-reference to absolute form as specified by
[<A HREF="http://www.isi.edu/in-notes/rfc2396.txt">URI</A>]
***************
*** 1753,1761 ****
fragment identifier is included in the URI-reference then the resource
identifier refers only to a subcomponent of the containing resource;
this subcomponent is identifed by the corresponding anchor id internal
! to that containing resource, otherwise the resource identifier refers
to the entire item specified by the URI.</P>
<A NAME="DescriptionElement"></A>
<P>The <TT>Description</TT> element itself creates an instance of a Bag
resource. The members of this Bag are the resources corresponding to
--- 1804,1829 ----
fragment identifier is included in the URI-reference then the resource
identifier refers only to a subcomponent of the containing resource;
this subcomponent is identifed by the corresponding anchor id internal
! to that containing resource and the extent of the subcomponent is
! defined by the fragment identifier in conjunction with the content
! type of the containing resource, otherwise
! the resource identifier refers
to the entire item specified by the URI.</P>
+ <blockquote>
+ Note: Although non-ASCII characters in URIs are not allowed by
+ [<A HREF="http://www.isi.edu/in-notes/rfc2396.txt">URI</A>],
+ [<A HREF="http://www.w3.org/TR/REC-xml">XML</A>]
+ specifies a convention to avoid unnecessary
+ incompatibilities in extended URI syntax. Implementors of RDF
+ are encouraged to avoid further incompatibility and use the
+ XML convention for system identifiers. Namely, that a non-ASCII
+ character in a URI be represented in UTF-8 as one
+ or more bytes, and then these bytes be escaped with the URI escaping
+ mechanism (i.e., by converting each byte to %HH, where HH is
+ the hexadecimal notation of the byte value).
+ </blockquote>
+
<A NAME="DescriptionElement"></A>
<P>The <TT>Description</TT> element itself creates an instance of a Bag
resource. The members of this Bag are the resources corresponding to
***************
*** 1773,1779 ****
<TT>ID</TT> attribute of the <TT>Description</TT> element, if present.
When another <TT>Description</TT> or property value refers to the in-line
resource it will use the value of the <TT>ID</TT> in an <TT>about</TT>
! attribute. When the other <TT>Description</TT> refers to the bag of resources
corresponding to the reified statements it will use the value of <TT>bagID</TT>
in an <TT>about</TT> attribute. Either <TT>ID</TT> or <TT>about</TT> may
be specified on <TT>Description</TT> but not both together in the same
--- 1841,1847 ----
<TT>ID</TT> attribute of the <TT>Description</TT> element, if present.
When another <TT>Description</TT> or property value refers to the in-line
resource it will use the value of the <TT>ID</TT> in an <TT>about</TT>
! attribute. When the other <TT>Description</TT> refers to the Bag of resources
corresponding to the reified statements it will use the value of <TT>bagID</TT>
in an <TT>about</TT> attribute. Either <TT>ID</TT> or <TT>about</TT> may
be specified on <TT>Description</TT> but not both together in the same
***************
*** 1800,1810 ****
for each r that is a member of the container.</P>
<A NAME="CollectionElement"></A>
! <P>Seq, Bag, and Alt create an instance of a Sequence, Bag, or Alternative
container resource type respectively. A triple {RDF:type,c,t} is created
where c is the collection resource and t is one of RDF:Seq, RDF:Bag, or
RDF:Alt. The members of the collection are denoted by <TT>li</TT>. Each
! <TT>li</TT> corresponds to one member of the collection and results in
the creation of a triple {p,c,v} where:</P>
<OL>
--- 1868,1880 ----
for each r that is a member of the container.</P>
<A NAME="CollectionElement"></A>
! <P><TT>Seq</TT>, <TT>Bag</TT>, and <TT>Alt</TT> create an instance
! of a Sequence, Bag, or Alternative
container resource type respectively. A triple {RDF:type,c,t} is created
where c is the collection resource and t is one of RDF:Seq, RDF:Bag, or
RDF:Alt. The members of the collection are denoted by <TT>li</TT>. Each
! <TT>li</TT> element <I>E</I>
! corresponds to one member of the collection and results in
the creation of a triple {p,c,v} where:</P>
<OL>
***************
*** 1816,1829 ****
<LI>(same as rule 3 above) If <I>E</I> is an empty element (no content),
v is the resource whose resource identifier is given by the <TT>resource</TT> attribute
! of <I>E</I>. If the content of <I>E</I> contains no XML markup, v is the
! content of <I>E</I> (a string). Otherwise, the content of <I>E</I> must
be another <TT>Description</TT> or container and v is the resource named
by the(possibly implicit) <TT>ID</TT> or <TT>about</TT> of that <TT>Description</TT>
or container.</LI>
</OL>
! <P>The URI identifies (after resolution) the target resource; i.e. the resource to which the
<TT>Description</TT> applies or the resource that is included in the container.
The <TT>bagID</TT> attribute on a <TT>Description</TT> element and the
<TT>ID</TT> attribute on a container element permit that <TT>Description</TT>
--- 1886,1901 ----
<LI>(same as rule 3 above) If <I>E</I> is an empty element (no content),
v is the resource whose resource identifier is given by the <TT>resource</TT> attribute
! of <I>E</I>. If the content of <I>E</I> contains no XML markup
! or if <TT>parseType="Literal"</TT> is specified in the start tag of
! <I>E</I> then v is the
! content of <I>E</I> (a literal). Otherwise, the content of <I>E</I> must
be another <TT>Description</TT> or container and v is the resource named
by the(possibly implicit) <TT>ID</TT> or <TT>about</TT> of that <TT>Description</TT>
or container.</LI>
</OL>
! <P>The URI identifies (after resolution) the target resource; i.e., the resource to which the
<TT>Description</TT> applies or the resource that is included in the container.
The <TT>bagID</TT> attribute on a <TT>Description</TT> element and the
<TT>ID</TT> attribute on a container element permit that <TT>Description</TT>
***************
*** 1836,1842 ****
<P>Within propertyElt (production [6.12]), the URI used in a
<TT>resource</TT> attribute identifies (after resolution)
the resource that is the object of the statement
! (i.e. the value of this property). The value of
the <TT>ID</TT> attribute, if specified, is the identifier for the resource
that represents the reification of the statement.
If an RDF expression (that is, content with RDF/XML markup)
--- 1908,1914 ----
<P>Within propertyElt (production [6.12]), the URI used in a
<TT>resource</TT> attribute identifies (after resolution)
the resource that is the object of the statement
! (i.e., the value of this property). The value of
the <TT>ID</TT> attribute, if specified, is the identifier for the resource
that represents the reification of the statement.
If an RDF expression (that is, content with RDF/XML markup)
***************
*** 1849,1860 ****
XML; the usual XML content quoting and escaping mechanisms may be
used if the string contains character sequences (e.g. "<"
and "&") that violate the well-formedness rules or that otherwise
! might look like markup.</P>
<P>It is recommended that property names always be qualified with a namespace
prefix to unambiguously connect the property definition with the corresponding
schema.</P>
<P>As defined by XML, the character repertoire of an RDF string is ISO/IEC
10646 [ISO10646]. An actual RDF string, whether in an XML document or in
some other representation of the RDF data model, may be stored using a
--- 1921,1938 ----
XML; the usual XML content quoting and escaping mechanisms may be
used if the string contains character sequences (e.g. "<"
and "&") that violate the well-formedness rules or that otherwise
! might look like markup.
!
! The attribute <TT>parseType="Literal"</TT> specifies that the element
! content is an RDF literal. Any markup that is part of this content is
! included as part of the literal and not interpreted by RDF.
! </P>
<P>It is recommended that property names always be qualified with a namespace
prefix to unambiguously connect the property definition with the corresponding
schema.</P>
+ <A NAME="stringComparison"></A>
<P>As defined by XML, the character repertoire of an RDF string is ISO/IEC
10646 [ISO10646]. An actual RDF string, whether in an XML document or in
some other representation of the RDF data model, may be stored using a
***************
*** 1874,1884 ****
Unicode Standard [Unicode].</LI>
</OL>
<A NAME="LangAttribute"></A>
<P>The <TT><A HREF="http://www.w3.org/TR/REC-xml#sec-lang-tag">xml:lang</A></TT>
attribute may be used as defined by [<A HREF="/TR/REC-xml">XML</A>] to
associate a language with the property value. There is no specific data
! model representation for <TT>xml:lang</TT> (i.e. it adds no triples to
the data model); the language of a literal is considered by RDF to
be a part of the literal. An application may ignore language tagging
of a string. All RDF applications must specify whether or not language
--- 1952,1977 ----
Unicode Standard [Unicode].</LI>
</OL>
+ <BLOCKQUOTE>
+ Note: The <A HREF="http://www.w3.org/International">W3C I18N WG</A>
+ is working on a definition for string identity
+ matching. This definition will most probably be based on canonical
+ equivalences according to the Unicode standard and on the principle of
+ early uniform normalization. Users of RDF should not rely on any
+ applications matching using the canonical equivalents, but should try
+ to make sure that their data is in the normalized form according to
+ the upcoming definitions.
+ </BLOCKQUOTE>
+
+ <P>This specification does not state a mechanism for determining equivalence
+ between literals that contain markup, nor whether such a mechanism is
+ guaranteed to exist.</P>
+
<A NAME="LangAttribute"></A>
<P>The <TT><A HREF="http://www.w3.org/TR/REC-xml#sec-lang-tag">xml:lang</A></TT>
attribute may be used as defined by [<A HREF="/TR/REC-xml">XML</A>] to
associate a language with the property value. There is no specific data
! model representation for <TT>xml:lang</TT> (i.e., it adds no triples to
the data model); the language of a literal is considered by RDF to
be a part of the literal. An application may ignore language tagging
of a string. All RDF applications must specify whether or not language
***************
*** 1886,1892 ****
is considered when performing string matching or other processing.</P>
<P>Attributes whose names start with
! "<TT><A HREF="/TR/WD-xml-names#dt-attdecl">xmlns</A></TT>"
are namespace
declarations and do not create triples in the data model. There is no
specific data model representation for such namespace declarations.</P>
--- 1979,1985 ----
is considered when performing string matching or other processing.</P>
<P>Attributes whose names start with
! "<TT><A HREF="/TR/PR-xml-names#dt-attdecl">xmlns</A></TT>"
are namespace
declarations and do not create triples in the data model. There is no
specific data model representation for such namespace declarations.</P>
***************
*** 1906,1912 ****
attribute name of <I>A</I>.
This expansion is generated by concatenating the namespace name
given in the namespace declaration with the
! <A HREF="/TR/WD-xml-names#NT-LocalPart">LocalPart</A>
of the qualified name and then resolving this URI according
to the algorithm in Section 5.2., Resolving Relative References to
Absolute Form, in [URI].
--- 1999,2005 ----
attribute name of <I>A</I>.
This expansion is generated by concatenating the namespace name
given in the namespace declaration with the
! <A HREF="/TR/PR-xml-names#NT-LocalPart">LocalPart</A>
of the qualified name and then resolving this URI according
to the algorithm in Section 5.2., Resolving Relative References to
Absolute Form, in [URI].
***************
*** 1966,1972 ****
<LI>r<SUB>2</SUB> is the resource named by the <TT>resource</TT> attribute
if present or a new resource. If the <TT>ID</TT> attribute is given it
! is the identification of this new resource.</LI>
<LI>p<SUB>a1</SUB> ... p<SUB>an</SUB> are the expansion of the namespace-qualified
attribute names.</LI>
--- 2059,2065 ----
<LI>r<SUB>2</SUB> is the resource named by the <TT>resource</TT> attribute
if present or a new resource. If the <TT>ID</TT> attribute is given it
! is the identifier of this new resource.</LI>
<LI>p<SUB>a1</SUB> ... p<SUB>an</SUB> are the expansion of the namespace-qualified
attribute names.</LI>
***************
*** 1995,2001 ****
sorted once by publication date and sorted again alphabetically by
subject:</P>
! <PRE> <RDF xmlns="http://www.w3.org/TR/WD-rdf-syntax#">
<Seq ID="JSPapersByDate">
<li resource="http://www.dogworld.com/Aug96.doc"/>
<li resource="http://www.webnuts.net/Jan97.html"/>
--- 2088,2094 ----
sorted once by publication date and sorted again alphabetically by
subject:</P>
! <PRE CLASS="EXAMPLE"><RDF xmlns="http://w3.org/TR/1999/PR-rdf-syntax-19990105#">
<Seq ID="JSPapersByDate">
<li resource="http://www.dogworld.com/Aug96.doc"/>
<li resource="http://www.webnuts.net/Jan97.html"/>
***************
*** 2006,2012 ****
<li resource="http://www.dogworld.com/Aug96.doc"/>
<li resource="http://www.webnuts.net/Jan97.html"/>
</Seq>
! </RDF></PRE>
<P>This XML example also uses the default namespace declaration syntax
to elide the namespace prefix.</P>
--- 2099,2106 ----
<li resource="http://www.dogworld.com/Aug96.doc"/>
<li resource="http://www.webnuts.net/Jan97.html"/>
</Seq>
! </RDF>
! </PRE>
<P>This XML example also uses the default namespace declaration syntax
to elide the namespace prefix.</P>
***************
*** 2021,2028 ****
with two authors specified alphabetically, a title specified in two different
languages, and having two equivalent locations on the Web:</P>
! <PRE> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.foo.com/cool.html">
<dc:Creator>
--- 2115,2122 ----
with two authors specified alphabetically, a title specified in two different
languages, and having two equivalent locations on the Web:</P>
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.foo.com/cool.html">
<dc:Creator>
***************
*** 2046,2052 ****
</rdf:Alt>
</dc:Title>
</rdf:Description>
! </rdf:RDF> </PRE>
<P>This example illustrates the use of all three types of collection. The
order of the creators is deemed significant so the <i>Sequence</i> container
--- 2140,2147 ----
</rdf:Alt>
</dc:Title>
</rdf:Description>
! </rdf:RDF>
! </PRE>
<P>This example illustrates the use of all three types of collection. The
order of the creators is deemed significant so the <i>Sequence</i> container
***************
*** 2055,2060 ****
--- 2150,2162 ----
a single title and that title has two variants, so the <i>Alternatives</i>
container is used.</P>
+ <blockquote>
+ Note: In many cases, it is impossible to have a preferred language
+ among various language alternatives; all languages are
+ considered to be strictly equivalent. In these cases, the description
+ author should use a <TT>Bag</TT> instead of an <TT>Alt</TT> container.
+ </blockquote>
+
<H3><A NAME="ex-NonBinary"></A>7.3. Non-Binary Relations</H3>
<P>The RDF data model intrinsically only supports binary relations;
***************
*** 2078,2092 ****
The
resulting graph might look like: </P>
! <CENTER><P><IMG SRC="fig14.gif" alt="qualifying values" />
<A href="fig14.html">D</A></P></CENTER>
<CENTER><P>Figure 14: A ternary relation</P></CENTER>
<P>which could be exchanged as: </P>
! <PRE> <RDF
! xmlns="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#"
xmlns:l="http://mycorp.com/schemas/my-schema#">
<Description about="http://www.webnuts.net/Jan97.html">
--- 2180,2195 ----
The
resulting graph might look like: </P>
! <CENTER><P><IMG SRC="fig14.gif" ALT="qualifying values" />
<A href="fig14.html">D</A></P></CENTER>
<CENTER><P>Figure 14: A ternary relation</P></CENTER>
<P>which could be exchanged as: </P>
! <PRE CLASS="EXAMPLE"><RDF
! xmlns="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#"
xmlns:l="http://mycorp.com/schemas/my-schema#">
<Description about="http://www.webnuts.net/Jan97.html">
***************
*** 2094,2100 ****
rdf:value="020 - Library Science"
l:Classification="Dewey Decimal Code"/>
</Description>
! </RDF></PRE>
<P>A common use of this higher-arity capability is when dealing with units
of measure. A person's weight is not just a number such as "200", it also
--- 2197,2212 ----
rdf:value="020 - Library Science"
l:Classification="Dewey Decimal Code"/>
</Description>
! </RDF>
! </PRE>
!
! <blockquote>
! Note: In the example above two namespace declarations exist for the
! same namespace. This is frequently needed when default namespaces
! are declared so that attributes that do not come from the namespace
! of the element may be specified, as is the case with the rdf:value
! attribute in the dc:Subject element above.
! </blockquote>
<P>A common use of this higher-arity capability is when dealing with units
of measure. A person's weight is not just a number such as "200", it also
***************
*** 2102,2124 ****
either pounds or kilograms. We could use a relationship with an additional
arc to record the fact that John Smith is a rather strapping gentleman:</P>
! <CENTER><P><IMG SRC="fig15.gif" alt="unit-qualified value" />
<A href="fig15.html">D</A></P></CENTER>
<CENTER><P>Figure 15: Unit of measure as a ternary relation</P></CENTER>
<P> which can be exchanged as:</P>
! <PRE> <RDF
! xmlns="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:n="http://www.nist.gov/units/">
<Description about="John_Smith">
! <n:weight>
<rdf:value>200</rdf:value>
<n:units rdf:resource="http://www.nist.gov/units/Pounds"/>
</n:weight>
</Description>
! </RDF></PRE>
<P>provided the resource "Pounds" is defined in a NIST schema with the URI
http://www.nist.gov/units/Pounds.</P>
--- 2214,2238 ----
either pounds or kilograms. We could use a relationship with an additional
arc to record the fact that John Smith is a rather strapping gentleman:</P>
! <CENTER><P><IMG SRC="fig15.gif" ALT="unit-qualified value" />
<A href="fig15.html">D</A></P></CENTER>
<CENTER><P>Figure 15: Unit of measure as a ternary relation</P></CENTER>
<P> which can be exchanged as:</P>
! <PRE CLASS="EXAMPLE"><RDF
! xmlns="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:n="http://www.nist.gov/units/">
<Description about="John_Smith">
! <n:weight rdf:parseType="Resource">
<rdf:value>200</rdf:value>
<n:units rdf:resource="http://www.nist.gov/units/Pounds"/>
</n:weight>
</Description>
! </RDF>
! </PRE>
<P>provided the resource "Pounds" is defined in a NIST schema with the URI
http://www.nist.gov/units/Pounds.</P>
***************
*** 2137,2144 ****
<P>Here is a description of a Web site home page using Dublin Core
properties:</P>
! <pre> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.dlib.org">
<dc:Title>D-Lib Program - Research in Digital Libraries</dc:Title>
--- 2251,2258 ----
<P>Here is a description of a Web site home page using Dublin Core
properties:</P>
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.dlib.org">
<dc:Title>D-Lib Program - Research in Digital Libraries</dc:Title>
***************
*** 2158,2169 ****
<dc:Format>text/html</dc:Format>
<dc:Language>en</dc:Language>
</rdf:Description>
! </rdf:RDF></pre>
<P>The second example is of a published magazine.</P>
! <pre> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#"
xmlns:dcq="http://purl.org/metadata/dublin_core_qualifiers#">
<rdf:Description about="http://www.dlib.org/dlib/may98/05contents.html">
--- 2272,2284 ----
<dc:Format>text/html</dc:Format>
<dc:Language>en</dc:Language>
</rdf:Description>
! </rdf:RDF>
! </PRE>
<P>The second example is of a published magazine.</P>
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#"
xmlns:dcq="http://purl.org/metadata/dublin_core_qualifiers#">
<rdf:Description about="http://www.dlib.org/dlib/may98/05contents.html">
***************
*** 2171,2177 ****
- May 1998</dc:Title>
<dc:Description>D-LIB magazine is a monthly compilation of
contributed stories, commentary, and briefings.</dc:Description>
! <dc:Contributor>
<dcq:AgentType
rdf:resource="http://purl.org/metadata/dublin_core_qualifiers#Editor"/>
<rdf:value>Amy Friedlander</rdf:value>
--- 2286,2292 ----
- May 1998</dc:Title>
<dc:Description>D-LIB magazine is a monthly compilation of
contributed stories, commentary, and briefings.</dc:Description>
! <dc:Contributor rdf:parseType="Resource">
<dcq:AgentType
rdf:resource="http://purl.org/metadata/dublin_core_qualifiers#Editor"/>
<rdf:value>Amy Friedlander</rdf:value>
***************
*** 2187,2205 ****
</dc:Subject>
<dc:Format>text/html</dc:Format>
<dc:Identifier>urn:issn:1082-9873</dc:Identifier>
! <dc:Relation>
<dcq:RelationType
rdf:resource="http://purl.org/metadata/dublin_core_qualifiers#IsPartOf"/>
<rdf:value resource="http://www.dlib.org"/>
</dc:Relation>
</rdf:Description>
! </rdf:RDF></pre>
<P>The third example is of a specific article in the magazine referred to
in the previous example.</P>
! <pre> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#"
xmlns:dcq="http://purl.org/metadata/dublin_core_qualifiers#">
<rdf:Description about=
--- 2302,2321 ----
</dc:Subject>
<dc:Format>text/html</dc:Format>
<dc:Identifier>urn:issn:1082-9873</dc:Identifier>
! <dc:Relation rdf:parseType="Resource">
<dcq:RelationType
rdf:resource="http://purl.org/metadata/dublin_core_qualifiers#IsPartOf"/>
<rdf:value resource="http://www.dlib.org"/>
</dc:Relation>
</rdf:Description>
! </rdf:RDF>
! </PRE>
<P>The third example is of a specific article in the magazine referred to
in the previous example.</P>
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#"
xmlns:dcq="http://purl.org/metadata/dublin_core_qualifiers#">
<rdf:Description about=
***************
*** 2230,2247 ****
<dc:Type>Electronic Document</dc:Type>
<dc:Format>text/html</dc:Format>
<dc:Language>en</dc:Language>
! <dc:Relation>
<dcq:RelationType
rdf:resource="http://purl.org/metadata/dublin_core_qualifiers#IsPartOf"/>
<rdf:value resource="http://www.dlib.org/dlib/may98/05contents.html"/>
</dc:Relation>
</rdf:Description>
! </rdf:RDF></pre>
<BLOCKQUOTE>
Note: Schema developers may be tempted to declare the values of
certain properties to use a syntax corresponding to the XML Namespace
! <A HREF="/TR/1998/WD-xml-names#ns-qualnames">qualified name</A> abbreviation.
We advise against using these qualified names inside property
values as this may cause incompatibilities with future XML datatyping
mechanisms. Furthermore, those fully versed in XML 1.0 features may
--- 2346,2364 ----
<dc:Type>Electronic Document</dc:Type>
<dc:Format>text/html</dc:Format>
<dc:Language>en</dc:Language>
! <dc:Relation rdf:parseType="Resource">
<dcq:RelationType
rdf:resource="http://purl.org/metadata/dublin_core_qualifiers#IsPartOf"/>
<rdf:value resource="http://www.dlib.org/dlib/may98/05contents.html"/>
</dc:Relation>
</rdf:Description>
! </rdf:RDF>
! </PRE>
<BLOCKQUOTE>
Note: Schema developers may be tempted to declare the values of
certain properties to use a syntax corresponding to the XML Namespace
! <A HREF="/TR/PR-xml-names#ns-qualnames">qualified name</A> abbreviation.
We advise against using these qualified names inside property
values as this may cause incompatibilities with future XML datatyping
mechanisms. Furthermore, those fully versed in XML 1.0 features may
***************
*** 2251,2257 ****
include user-defined entities.
</BLOCKQUOTE>
! <H3><A NAME="ex-PICS"></A>7.5. PICS Labels</H3>
<P>The <A href="http://www.w3.org/TR/REC-PICS-labels">Platform for
Internet Content Selection</A> (PICS)
--- 2368,2407 ----
include user-defined entities.
</BLOCKQUOTE>
! <H3><A NAME="ex-Literal"></A>7.5. Values Containing Markup</H3>
!
! <P>When a property value is a literal that contains XML markup, the
! following syntax is used to signal to the RDF interpreter not to
! interpret the markup but rather to retain it as part of the value.
! The precise representation of the resulting value is not specified here.</P>
!
! <P>In the following example, the value of the Title property is a literal
! containing some <A HREF="/TR/REC-MathML">MATHML</A> markup.</P>
!
! <PRE CLASS="EXAMPLE"><rdf:Description
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
! xmlns:dc="http://purl.org/metadata/dublin_core#"
! xmlns="http://www.w3.org/TR/REC-mathml"
! rdf:about="http://mycorp.com/papers/NobelPaper1"/>
!
! <dc:Title rdf:parseType="Literal">
! Ramifications of
! <apply>
! <power/>
! <apply>
! <plus/>
! <ci>a</ci>
! <ci>b</ci>
! </apply>
! <cn>2</cn>
! </apply>
! to World Peace
! </dc:Title>
! <dc:Creator>David Hume</dc:Creator>
! </rdf:Description>
! </PRE>
!
! <H3><A NAME="ex-PICS"></A>7.6. PICS Labels</H3>
<P>The <A href="http://www.w3.org/TR/REC-PICS-labels">Platform for
Internet Content Selection</A> (PICS)
***************
*** 2286,2293 ****
ratings (subject 2 density 1 color/hue 1))
-->
! <pre> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/1998/WD-rdf-syntax#"
xmlns:pics="http://www.w3.org/TR/xxxx/WD-PICS-labels#"
xmlns:gcf="http://www.gcf.org/v2.5">
<rdf:Description about="http://w3.org/PICS/Overview.html" bagID="L01"
--- 2436,2443 ----
ratings (subject 2 density 1 color/hue 1))
-->
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:pics="http://www.w3.org/TR/xxxx/WD-PICS-labels#"
xmlns:gcf="http://www.gcf.org/v2.5">
<rdf:Description about="http://w3.org/PICS/Overview.html" bagID="L01"
***************
*** 2298,2304 ****
<rdf:Description about="http://w3.org/PICS/Underview.html" bagID="L02"
gcf:subject="2"
gcf:density="1"
! gcf:color.hue="1">
<rdf:Description aboutEach="#L01"
pics:by="John Doe"
--- 2448,2454 ----
<rdf:Description about="http://w3.org/PICS/Underview.html" bagID="L02"
gcf:subject="2"
gcf:density="1"
! gcf:color.hue="1"/>
<rdf:Description aboutEach="#L01"
pics:by="John Doe"
***************
*** 2309,2315 ****
pics:by="Jane Doe"
pics:on="1994.11.05T08:15-0500"
pics:until="1995.12.31T23:59-0000"/>
! </rdf:RDF></pre>
<P>Note that <TT>aboutEach</TT> is used to indicate that the PICS label
options refer to the individual (rating) statements and not
--- 2459,2466 ----
pics:by="Jane Doe"
pics:on="1994.11.05T08:15-0500"
pics:until="1995.12.31T23:59-0000"/>
! </rdf:RDF>
! </PRE>
<P>Note that <TT>aboutEach</TT> is used to indicate that the PICS label
options refer to the individual (rating) statements and not
***************
*** 2338,2345 ****
;http://www.w3.org/pub/WWW/TheProject.html
-->
! <pre> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/1998/WD-rdf-syntax#"
xmlns:pics="http://www.w3.org/TR/xxxx/WD-PICS-labels#"
xmlns:ages="http://www.ages.org/our-service/v1.0/">
<rdf:Description aboutEachPrefix="http://www.w3.org/WWW/" bagID="L03"
--- 2489,2496 ----
;http://www.w3.org/pub/WWW/TheProject.html
-->
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:pics="http://www.w3.org/TR/xxxx/WD-PICS-labels#"
xmlns:ages="http://www.ages.org/our-service/v1.0/">
<rdf:Description aboutEachPrefix="http://www.w3.org/WWW/" bagID="L03"
***************
*** 2347,2353 ****
<rdf:Description aboutEach="#L03"
pics:by="abaird@w3.org"/>
! </rdf:RDF></pre>
<P>The property <TT>age</TT> with the value "11"
appears on every resource whose URI starts with the string
--- 2498,2505 ----
<rdf:Description aboutEach="#L03"
pics:by="abaird@w3.org"/>
! </rdf:RDF>
! </PRE>
<P>The property <TT>age</TT> with the value "11"
appears on every resource whose URI starts with the string
***************
*** 2358,2368 ****
that "abaird@w3.org" was responsible for creating those
statements.</P>
! <H3><A NAME="ex-Embedding"></A>7.6. Content Hiding For RDF inside HTML</H3>
<P>RDF, being well-formed XML, is suitable for direct inclusion in an
! HTML document as specified in
! [<A HREF="http://www.w3.org/TR/REC-html40/">HTML</A>]. When a
fragment of RDF is incorporated into an HTML document some browsers
will render any exposed string content. Exposed string
content is anything that appears between the ">" that
--- 2510,2521 ----
that "abaird@w3.org" was responsible for creating those
statements.</P>
! <H3><A NAME="ex-Embedding"></A>7.7. Content Hiding For RDF inside HTML</H3>
<P>RDF, being well-formed XML, is suitable for direct inclusion in an
! HTML document when the user agent follows the HTML
! <A HREF="/TR/REC-html40/appendix/notes.html#notes-invalid-docs">recommendations
! for error handling in invalid documents</A>. When a
fragment of RDF is incorporated into an HTML document some browsers
will render any exposed string content. Exposed string
content is anything that appears between the ">" that
***************
*** 2376,2383 ****
first part of the Dublin Core example from Section 7.4. could
be written as:</P>
! <PRE> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.dlib.org"
dc:Title="D-Lib Program - Research in Digital Libraries"
--- 2529,2536 ----
first part of the Dublin Core example from Section 7.4. could
be written as:</P>
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.dlib.org"
dc:Title="D-Lib Program - Research in Digital Libraries"
***************
*** 2386,2399 ****
publishing."
dc:Publisher="Corporation For National Research Initiatives"
dc:Date="1995-01-07"/>
! </rdf:RDF></PRE>
<P>Rewriting to avoid exposed content will work for most common cases.
One common but less obvious case is container descriptions. Consider
the first part of the example in Section 7.2.:</P>
! <PRE> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.foo.com/cool.html">
<dc:Creator>
--- 2539,2553 ----
publishing."
dc:Publisher="Corporation For National Research Initiatives"
dc:Date="1995-01-07"/>
! </rdf:RDF>
! </PRE>
<P>Rewriting to avoid exposed content will work for most common cases.
One common but less obvious case is container descriptions. Consider
the first part of the example in Section 7.2.:</P>
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.foo.com/cool.html">
<dc:Creator>
***************
*** 2403,2414 ****
</rdf:Seq>
</dc:Creator>
</rdf:Description>
! </rdf:RDF> </PRE>
<P>To rewrite this with no exposed content, we use the following form:</P>
! <PRE> <rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.foo.com/cool.html">
<dc:Creator>
--- 2557,2569 ----
</rdf:Seq>
</dc:Creator>
</rdf:Description>
! </rdf:RDF>
! </PRE>
<P>To rewrite this with no exposed content, we use the following form:</P>
! <PRE CLASS="EXAMPLE"><rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="http://www.foo.com/cool.html">
<dc:Creator>
***************
*** 2417,2423 ****
rdf:_2="Jacky Crystal"/>
</dc:Creator>
</rdf:Description>
! </rdf:RDF> </PRE>
<P>Note here that the <TT>li</TT> element cannot be used as an
attribute due to the XML rule forbidding multiple occurrences of the
--- 2572,2579 ----
rdf:_2="Jacky Crystal"/>
</dc:Creator>
</rdf:Description>
! </rdf:RDF>
! </PRE>
<P>Note here that the <TT>li</TT> element cannot be used as an
attribute due to the XML rule forbidding multiple occurrences of the
***************
*** 2427,2436 ****
<P>A complete HTML document containing RDF metadata describing itself is:</P>
! <PRE> <html>
<head>
<rdf:RDF
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="">
<dc:Creator>
--- 2583,2592 ----
<P>A complete HTML document containing RDF metadata describing itself is:</P>
! <PRE CLASS="EXAMPLE"><html>
<head>
<rdf:RDF
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:dc="http://purl.org/metadata/dublin_core#">
<rdf:Description about="">
<dc:Creator>
***************
*** 2444,2450 ****
<body>
<P>This is a fine document.</P>
</body>
! </html></PRE>
<P>The HTML document above should be accepted by all browsers
compliant with HTML 3.2 and later and should only render the
--- 2600,2607 ----
<body>
<P>This is a fine document.</P>
</body>
! </html>
! </PRE>
<P>The HTML document above should be accepted by all browsers
compliant with HTML 3.2 and later and should only render the
***************
*** 2473,2482 ****
of Michigan), Tim Berners-Lee (W3C), Dan Connolly (W3C), Jim Miller (W3C,
emeritus), Ralph Swick (W3C). Dan Brickley (UK Bristol) joined the
RDF Schema activity and brought us lots of sage advice in the final
! stages of this work.</P>
<P>This document is the collective work of the Working Group. The editors
! are indebted to the Working Group for helping to create this specification.</P>
<H2><A NAME="glossary"></A>Appendix A. Glossary</H2>
--- 2630,2645 ----
of Michigan), Tim Berners-Lee (W3C), Dan Connolly (W3C), Jim Miller (W3C,
emeritus), Ralph Swick (W3C). Dan Brickley (UK Bristol) joined the
RDF Schema activity and brought us lots of sage advice in the final
! stages of this work. Martin Dürst (W3C) reviewed several working
! drafts and made a number of suggestions for improvement on behalf of
! the W3C <A HREF="/International">Internationalization Working Group</A>.
! Janne Saarela (W3C) performed a priceless service by creating a 'clean
! room' <A HREF="/RDF/Implementations/SiRPAC">implementation</A> from
! our working drafts.</P>
<P>This document is the collective work of the Working Group. The editors
! are indebted to the Working Group for helping to create and polish
! this specification.</P>
<H2><A NAME="glossary"></A>Appendix A. Glossary</H2>
***************
*** 2495,2503 ****
<TT>name="value"</TT> portions of an XML tag.</DD>
<DT>Element</DT><DD>As used here, this term refers to a specific XML
! syntactic construct; i.e. the material between matching XML start
and end tags.</DD>
<DT>Node</DT><DD>A representation of a resource or a literal in a
graph form; specifically, a vertex in a directed labeled graph.</DD>
--- 2658,2672 ----
<TT>name="value"</TT> portions of an XML tag.</DD>
<DT>Element</DT><DD>As used here, this term refers to a specific XML
! syntactic construct; i.e., the material between matching XML start
and end tags.</DD>
+ <DT>Literal</DT><DD>The most primitive value type represented in RDF,
+ typically a string of characters. The content of a literal is not
+ interpreted by RDF itself and may contain additional XML markup.
+ Literals are distinguished from Resources in that the RDF model
+ does not permit literals to be the subject of a statement.</DD>
+
<DT>Node</DT><DD>A representation of a resource or a literal in a
graph form; specifically, a vertex in a directed labeled graph.</DD>
***************
*** 2544,2554 ****
<LI>The Description may be external to the resource but supplied by the
transfer mechanism in the same retrieval transaction as that which returns
! the resource ("along-with"; e.g. <A HREF="#viaHTTP">via HTTP</A>).</LI>
<LI>The Description may be retrieved independently from the resource, including
! from a different source ("service bureau"; e.g. <A HREF="#serviceBureau">using
! HTTP</A>).</LI>
<LI>The Description may contain the resource ("wrapped"; e.g.
RDF itself).</LI>
--- 2713,2723 ----
<LI>The Description may be external to the resource but supplied by the
transfer mechanism in the same retrieval transaction as that which returns
! the resource ("along-with"; e.g. with HTTP GET or HEAD).</LI>
<LI>The Description may be retrieved independently from the resource, including
! from a different source ("service bureau"; e.g. using
! HTTP GET).</LI>
<LI>The Description may contain the resource ("wrapped"; e.g.
RDF itself).</LI>
***************
*** 2565,2574 ****
on demand. The logic and syntax of RDF schemas are described in a separate
document, [<A HREF="/TR/WD-rdf-schema">RDFSchema</A>].</P>
! <H3><A NAME="embedHTML"></A>B.1. Embedding in HTML</H3>
!
<P>The recommended technique for embedding RDF expressions in an HTML document
! is simply to insert the RDF in-line as shown in Example 7.6. This will
make the resulting document
non-conformant to HTML specifications up to and including HTML 4.0
but the W3C expects that <A HREF="/MarkUp/Activity">the HTML
--- 2734,2742 ----
on demand. The logic and syntax of RDF schemas are described in a separate
document, [<A HREF="/TR/WD-rdf-schema">RDFSchema</A>].</P>
! <A NAME="embedHTML"></A>
<P>The recommended technique for embedding RDF expressions in an HTML document
! is simply to insert the RDF in-line as shown in Example 7.7. This will
make the resulting document
non-conformant to HTML specifications up to and including HTML 4.0
but the W3C expects that <A HREF="/MarkUp/Activity">the HTML
***************
*** 2590,2596 ****
<LI>All HTML browsers conforming to specifications up to and including
HTML 4.0 will render any content appearing in RDF property values expressed
! as XML elements (i.e. production [6.12]).<BR />
<BR />
Authors concerned about preventing their RDF content from rendering
in old browsers may use the abbreviated syntax (propAttr form) to move
--- 2758,2764 ----
<LI>All HTML browsers conforming to specifications up to and including
HTML 4.0 will render any content appearing in RDF property values expressed
! as XML elements (i.e., production [6.12]).<BR />
<BR />
Authors concerned about preventing their RDF content from rendering
in old browsers may use the abbreviated syntax (propAttr form) to move
***************
*** 2605,2617 ****
<PRE> <LINK rel="meta" href="mydocMetadata.DC.RDF"></PRE>
- <H3><A NAME="viaHTTP"></A>B.2. Transporting in HTTP Headers</H3>
-
- <P><I>To Be Specified. We expect to specify a simple extension to HTTP
- that allows a client to request that RDF metadata be included in a header
- along with the document. We will deal here only with the HTTP protocol;
- we hope that other protocols will be similarly extended.</I></P>
-
<H2><A NAME="usage"></A>Appendix C: Notes about Usage</H2>
<H3>C.1. Property Names</H3>
--- 2773,2778 ----
***************
*** 2657,2750 ****
</DD>
<DT>[ISO10646]</DT>
-
<DD>ISO/IEC 10646. The applicable version of this standard is defined in
the XML specification [<A HREF="/TR/REC-xml">XML</A>].</DD>
<DT>[NAMESPACES]</DT>
-
<DD>Namespaces in XML; Bray, Hollander, Layman eds, World Wide Web Consortium
! Working Draft; <A HREF="http://www.w3.org/TR/1998/WD-xml-names-19980916">http://www.w3.org/TR/1998/WD-xml-names-19980916</A>.</DD>
<dt>[PICS]</dt>
-
<dd>PICS Label Distribution Label Syntax and Communication Protocols,
Version 1.1, W3C Recommendation 31-October-96;
<A href="http://www.w3.org/TR/REC-PICS-labels">http://www.w3.org/TR/REC-PICS-labels</A>.</dd>
<DT>[RDFSchema]</DT>
-
<DD>Resource Description Framework (RDF) Schemas; Brickley, Guha,
Layman eds., World Wide Web Consortium Working Draft;
<A HREF="/TR/WD-rdf-schema">http://www.w3.org/TR/WD-rdf-schema</A></DD>
! <DT>[Unicode]</DT>
! <DD>The Unicode Standard. The applicable version of this standard is defined
! in the XML specification [<A HREF="/TR/REC-xml">XML</A>].</DD>
<DT>[URI]</DT>
-
<dd>Uniform Resource Identifiers (URI): Generic Syntax; Berners-Lee,
Fielding, Masinter, Internet Draft Standard August, 1998;
<A HREF="http://www.isi.edu/in-notes/rfc2396.txt">RFC2396</A>.</dd>
<DT>[XML]</DT>
-
<DD>Extensible Markup Language (XML) 1.0; World Wide Web Consortium Recommendation;
<A HREF="http://www.w3.org/TR/REC-xml">http://www.w3.org/TR/REC-xml</A>.</DD>
<DT>[XMLinHTML]</DT>
-
<DD>XML in HTML Meeting Report; Connolly, Wood eds.; World Wide Web Consortium
Note; <A HREF="http://www.w3.org/TR/NOTE-xh">http://www.w3.org/TR/NOTE-xh</A>.</DD>
</DL>
<H2><A NAME="changes"></A>Appendix E: Changes</H2>
! <P>The most significant changes from the
! <A HREF="/TR/1998/WD-rdf-syntax-19980819">1998-08-19 Working Draft</A>
! are listed here.</P>
!
! <OL>
! <LI>To provide a degree of "futureproofing", a
! <A HREF="#reservedURI">part of the URI space</A> is reserved
! for future RDF additions
! such that behavior of processors conforming to the version 1
! specification can be guaranteed. We caution
! against the use of either qualified names or user-defined entities to
! abbreviate property values.</LI><P />
!
! <LI>Several pieces of basic vocabulary have been changed to clarify
! terminology. Of particular note in this regard is the term
! <I>property</I> which previously meant the combination of three
! things; a resource identifier, an attribute (formally called a
! <I>PropertyType</I> in the previous draft), and the value of that
! attribute for that
! resource. Now this combination is formally called a <I>statement</I>
! and the old term PropertyType is shortened to just <I>Property</I>.
! This usage of "property" conforms more closely to common
! usage.</LI><P />
!
! <LI>A second piece of terminology that now has a different usage is
! the <TT>value</TT> property. The <TT>value</TT> property is no longer
! used when reifying statements, but is reserved as a 'convenience'
! property needed by many schemas. See <A HREF="#value">Section
! 2.3</A>.</LI><P />
!
! <LI>
! The recommended representation of higher-arity (non-binary) relations has
! changed in order to establish a better direction for future evolution.
! The property previously named "instanceOf" is renamed
! "type" and a specific production permitting this type
! property to be specified in attribute form is added to the grammar.
! We use the terminology "resource identifier" now replacing "URI reference"
! from earlier drafts where the new term refers to the fully
! resolved URI plus fragment (anchor) identifier that is derived from a
! URI reference.
! Some additional editorial improvements have also been made as
! a result of the comments received on previous drafts.</LI>
! </OL>
<HR WIDTH="100%" />
--- 2818,2882 ----
</DD>
<DT>[ISO10646]</DT>
<DD>ISO/IEC 10646. The applicable version of this standard is defined in
the XML specification [<A HREF="/TR/REC-xml">XML</A>].</DD>
<DT>[NAMESPACES]</DT>
<DD>Namespaces in XML; Bray, Hollander, Layman eds, World Wide Web Consortium
! Working Draft; <A HREF="http://w3.org/TR/1998/PR-xml-names-19981117">http://www.w3.org/TR/1998/PR-xml-names-19981117</A>.</DD>
<dt>[PICS]</dt>
<dd>PICS Label Distribution Label Syntax and Communication Protocols,
Version 1.1, W3C Recommendation 31-October-96;
<A href="http://www.w3.org/TR/REC-PICS-labels">http://www.w3.org/TR/REC-PICS-labels</A>.</dd>
<DT>[RDFSchema]</DT>
<DD>Resource Description Framework (RDF) Schemas; Brickley, Guha,
Layman eds., World Wide Web Consortium Working Draft;
<A HREF="/TR/WD-rdf-schema">http://www.w3.org/TR/WD-rdf-schema</A></DD>
! <DT><A NAME="rfc2119"></A>[RFC2119]</DT>
! <DD>Key words for use in RFCs to Indicate Requirement Levels;
! S. Bradner, March 1997;
! <A HREF="http://www.isi.edu/in-notes/rfc2119.txt">RFC2119</A>.</DD>
! <DT>[Unicode]</DT>
! <DD>The Unicode Standard. The applicable version of this standard is
! the version defined by the XML specification [<A HREF="/TR/REC-xml">XML</A>].</DD>
<DT>[URI]</DT>
<dd>Uniform Resource Identifiers (URI): Generic Syntax; Berners-Lee,
Fielding, Masinter, Internet Draft Standard August, 1998;
<A HREF="http://www.isi.edu/in-notes/rfc2396.txt">RFC2396</A>.</dd>
<DT>[XML]</DT>
<DD>Extensible Markup Language (XML) 1.0; World Wide Web Consortium Recommendation;
<A HREF="http://www.w3.org/TR/REC-xml">http://www.w3.org/TR/REC-xml</A>.</DD>
<DT>[XMLinHTML]</DT>
<DD>XML in HTML Meeting Report; Connolly, Wood eds.; World Wide Web Consortium
Note; <A HREF="http://www.w3.org/TR/NOTE-xh">http://www.w3.org/TR/NOTE-xh</A>.</DD>
</DL>
<H2><A NAME="changes"></A>Appendix E: Changes</H2>
! <P>The most significant change from the
! <A HREF="/TR/1998/WD-rdf-syntax-19981008">1998-10-08 Working Draft</A>
! is the addition of the <TT>parseType</TT> attribute in the XML grammar.
! This attribute addresses two feature requests received from several
! commentors that made the WG agree to reconsider previous decisions:
! the desire to incorporate uninterpreted (by RDF) markup within an
! RDF literal value and the desire for an additional shorthand
! abbreviation for the common case of a property value that is an
! in-line resource.</P>
!
! <P>Clarifications were made to the portions of the specification
! referring to string equivalence with reference to future work of
! the W3C Internationalization Working Group.</P>
!
! <P>Other small editorial corrections and wording clarifications are
! incorporated as a result of comments received from W3C Members and
! from non-Members.</P>
<HR WIDTH="100%" />
***************
*** 2752,2757 ****
--- 2884,2892 ----
Ralph R. Swick <<A HREF="mailto:swick@w3.org">swick@w3.org</A>></FONT></ADDRESS>
<P><FONT SIZE="-1">Revision History:<BR />
+ 5-January-1999: publish as W3C Proposed Recommendation.<BR />
+ 16-December-1998: final draft intended as Proposed Recommendation.<BR />
+ 30-October-1998: incorporate Last Call review comments, add parseType, improve the I18N wordings.<BR />
8-October-1998: final cleanup, move changes to Appendix E, publish as Last Call.<BR />
7-October-1998: reserve a bit of schema URI space for futureproofing, add rdf:value.<BR />
2-October-1998: major renaming; statements, predicates, subjects, objects.<BR />
***************
*** 2774,2786 ****
<BR />
</FONT>
<!-- hhmts start -->
! Last updated: $Date: 1998/10/08 21:55:02 $
<!-- hhmts end -->
</P>
<RDF
! xmlns="http://www.w3.org/TR/WD-rdf-syntax#"
! xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
xmlns:s="http://www.w3.org/TR/WD-rdf-schema#">
<s:Class rdf:ID="Statement"
--- 2909,2921 ----
<BR />
</FONT>
<!-- hhmts start -->
! Last updated: $Date: 1999/01/06 19:44:16 $
<!-- hhmts end -->
</P>
<RDF
! xmlns="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
! xmlns:rdf="http://w3.org/TR/1999/PR-rdf-syntax-19990105#"
xmlns:s="http://www.w3.org/TR/WD-rdf-schema#">
<s:Class rdf:ID="Statement"
***************
*** 2811,2818 ****
s:comment="Identifies the object of a statement when representing the statement in reified form" />
<Property ID="type"
! s:comment="Identifies the Class of a resource"
! s:range="#Class" />
<Property ID="value"
s:comment="Identifies the principal value (usually a string) of a property when the property value is a structured resource" />
--- 2946,2952 ----
s:comment="Identifies the object of a statement when representing the statement in reified form" />
<Property ID="type"
! s:comment="Identifies the Class of a resource" />
<Property ID="value"
s:comment="Identifies the principal value (usually a string) of a property when the property value is a structured resource" />