Differences from 1998-10-30 draft to 1999-03-03 draft
1,4c1,6
< <HTML
< xmlns:rdf = "http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs = "http://www.w3.org/TR/WD-rdf-schema#"
< xmlns:dc = "http://purl.org/dc/elements/1.0/#" >
---
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
> "http://www.w3.org/TR/REC-html40/loose.dtd">
>
> <HTML xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs = "http://www.w3.org/TR/1999/PR-rdf-schema-19990303#"
> xmlns:dc = "http://purl.org/dc/elements/1.0/" >
6d7
< <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1" />
8c9,14
<
---
> <STYLE TYPE="text/css">
> .EXAMPLE { margin-left: 1em }
>
> </STYLE>
> <LINK rel="stylesheet" type="text/css" media="screen"
> href="/StyleSheets/TR/W3C-PR">
19c25
< dc:Date="1998-10-30"
---
> dc:Date="1999-03-03"
30,31c36
< rdf:_2="R.V. Guha"
< rdf:_3="Andrew Layman"/>
---
> rdf:_2="R.V. Guha" />
32a38,40
>
> <rdfs:seeAlso rdf:resource="http://www.w3.org/1999/.status/PR-rdf-schema-19990303/status" />
>
38c46
< <BODY BGCOLOR="#ffffff" TEXT="#000000">
---
> <BODY>
40d47
< <DIV ALIGN="right">
42,43c49,50
< <A HREF="/"><IMG SRC="/Icons/w3c_home" ALT="W3C" BORDER="0" ALIGN="LEFT" /></A>
< WD-rdf-schema-19981030</H2></DIV>
---
> <A HREF="/"><IMG SRC="/Icons/w3c_home" ALT="W3C" BORDER="0"></A>
> </H2>
45,46c52
< <BR />
< <CENTER><H1>Resource Description Framework<BR />(RDF) Schema Specification</H1></CENTER>
---
> <CENTER><H1>Resource Description Framework<BR>(RDF) Schema Specification</H1></CENTER>
48c54
< <CENTER><H3>W3C Working Draft 30 October 1998</H3></CENTER>
---
> <CENTER><H3>W3C Proposed Recommendation 03 March 1999</H3></CENTER>
50c56
< <!-- Last CVS check in : $Date: 1999/03/02 23:57:48 $ -->
---
> <!-- Last CVS check in (UoB or MIT): $Date: 1999/03/02 23:57:48 $ -->
53,54c59,60
< <center><a href="/1998/.status/WD-rdf-schema-199801030/status"><IMG
< src="/1998/.status/WD-rdf-schema-19981030/statusimg" border="0"
---
> <center><a href="/1999/.status/PR-rdf-schema-19990303/status"><IMG
> src="/1999/.status/PR-rdf-schema-19990303/statusimg" border="0"
60c66
< HREF="http://www.w3.org/TR/1998/WD-rdf-schema-19981030/">http://www.w3.org/TR/1998/WD-rdf-schema-19981030/</A></DD>
---
> HREF="http://www.w3.org/TR/1999/PR-rdf-schema-19990303">http://www.w3.org/TR/1999/PR-rdf-schema-19990303</A></DD>
63c69
< <DD><A HREF="http://www.w3.org/TR/WD-rdf-schema">http://www.w3.org/TR/WD-rdf-schema</A></DD>
---
> <DD><A HREF="http://www.w3.org/TR/PR-rdf-schema">http://www.w3.org/TR/PR-rdf-schema</A></DD>
68d73
< <DD>Andrew Layman, Microsoft</DD>
71,72c76
< <A HREF="/1998/.status/WD-rdf-schema-19981030/status">Document
< Status</A> and <A HREF="errata">errata</A><BR />
---
> <A HREF="/1999/.status/PR-rdf-schema-19990303/status">Document Status</A> and <A HREF="errata">errata</A><BR />
78,80c82,83
<
< <FONT SIZE="-1"><A HREF="http://www.w3.org/Consortium/Legal/ipr-notice.html#Copyright">Copyright</A>
< ©1998 <A HREF="http://www.w3.org">W3C</A> (<A HREF="http://www.lcs.mit.edu">MIT</A>,
---
> <SMALL><A HREF="http://www.w3.org/Consortium/Legal/ipr-notice.html#Copyright">Copyright</A>
> ©1998,1999 <A HREF="http://www.w3.org">W3C</A> (<A HREF="http://www.lcs.mit.edu">MIT</A>,
86c89
< licensing</A> rules apply.</FONT>
---
> licensing</A> rules apply.</SMALL>
91,95c94,108
< <P>
< This document is a revision of the public working draft dated
< <A HREF="http://www.w3.org/TR/1998/WD-rdf-schema-19980814/">
< 1998-08-14</A> incorporating suggestions
< <A HREF="http://www.w3.org/Archives/Public/www-rdf-comments">received in review
---
>
> <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 March 26, 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 last-call working draft dated
> <A HREF="http://www.w3.org/TR/1998/WD-rdf-schema-19981030/">
> 1998-10-30</A> incorporating suggestions <A
> HREF="http://www.w3.org/Archives/Public/www-rdf-comments">received in review
97,99c110,111
< Significant changes from the previous draft are highlighted in <A HREF="#changes">Appendix
< E</A>. With the publication of this draft, the RDF Schema specification enters
< "last call". The last call period will end on November 30, 1998.</P>
---
> The detailed <A HREF="lastCallDiff">differences</A>
> are available for reviewers to compare.</P>
102,104c114,116
< Comments on this specification may be sent to <A HREF="mailto:www-rdf-comments@w3.org">www-rdf-comments@w3.org</A>.
< The public archive of these comments is available at
< <A HREF="http://lists.w3.org/Archives/Public/www-rdf-comments/">http://lists.w3.org/Archives/Public/www-rdf-comments/</A>.
---
> 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.
108,118c120,124
< 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. The RDF Schema Working Group will not allow early
< implementation to constrain their ability to make changes to this specification prior
< to final release.
< </P>
<
< <P>This is a W3C Working Draft for review by W3C members and other interested
< parties. Publication as a "last call" working draft does not imply endorsement by
< the W3C membership.
---
> 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".
130,142d135
< This is a draft document and may be updated, replaced or obsoleted by
< other documents at any time. It is inappropriate to use W3C Working Drafts
< as reference material or to cite them as other than "work in progress".
< </P>
<
< <P>
< <B>Note:</B> As working drafts are subject to frequent change, you are
< advised to reference the above URL for "Newest version" rather than the
< URLs for working draft versions themselves. The newest version URL will
< always point to the most current version of this draft.
< </P>
<
< <P>
144c137
< HREF="http://www.w3.org/TR/WD-rdf-syntax/#embedHTML">embedded RDF</A> and
---
> HREF="http://www.w3.org/TR/REC-rdf-syntax/#embedHTML">embedded RDF</A> and
163d155
< <LI><A HREF="#figures">Figures</A></LI>
168,169d159
< <LI><A HREF="#openissues">Appendix D: Open Issues</A></LI>
< <LI><A HREF="#changes">Appendix E: Changes</A></LI>
180c170
< Resource Description Framework (RDF) is a foundation for processing
---
> The Resource Description Framework (RDF) is a foundation for processing
192c182
< privacy preferences of a user as well as the privacy policies of a web site.
---
> privacy preferences of a user as well as the privacy policies of a Web site.
195c185
< applications.
---
> applications.
201,205c191,195
< Descriptions used by these applications can be modeled as the
< interrelationships among web resources. The RDF data model, as specified in
< [<A HREF="#refs">RFDMS</A>], defines a simple model for representing named properties and
< property values for describing the interrelations among resources. RDF
< properties may be thought of as attributes of resources and in this sense
---
> Descriptions used by these applications can be modelled as
> relationships among Web resources. The RDF data model, as specified in
> [<A HREF="#refs">RDFMS</A>], defines a simple model for describing
> interrelationships among resources in terms of named properties and values.
> RDF properties may be thought of as attributes of resources and in this sense
211,212c201
< properties and other resources. That is the void this specification seeks
< to fill.
---
> properties and other resources. That is the role of RDF Schema.
219c208
< "subject" are common. For digital certification, attributes such as
---
> "subject" are common. For digital certification, attributes such as
224c213
< also may define the kinds of resources being described (books, web pages,
---
> may also define the kinds of resources being described (books, Web pages,
231,236c220,225
< needed to define such elements, to define the classes of resources they
< connect, to restrict possible combinations of classes and relationships,
< and to detect violations of those restrictions. Thus, this document
< defines a <em>schema specification language</em>. More succinctly, the
< RDF Schema mechanism provides a basic <em>type system</em> for use in RDF
< models. It defines resources and properties such as <em>Class</em> and
---
> needed to define such elements, to define the classes of resources they
> may be used with, to restrict possible combinations of classes and relationships,
> and to detect violations of those restrictions. Thus, this document
> defines a <em>schema specification language</em>. More succinctly, the
> RDF Schema mechanism provides a basic <em>type system</em> for use in RDF
> models. It defines resources and properties such as <em>Class</em> and
242c231
< resources and properties.
---
> resources and properties.
259c248
< metadata vocabulary to be represented in a different syntax. Within RDF,
---
> metadata vocabulary to be represented in a different syntax. In RDF,
270c259
< Descriptions (DTDs). Unlike an XML DTD, which gives specific
---
> Definitions (DTDs). Unlike an XML DTD, which gives specific
284,285c273,274
< RDF Schemas aim not at theoretical issues, but at solving a small number
< of immediate problems. Its creators expect that other problems (some of
---
> The RDF Schema specification is not aimed at theoretical issues, but at solving a
> small number of immediate problems. Its creators expect that other problems (some of
288c277
< specification.
---
> specification.
300,304c289,291
< [<A HREF="#refs">PICS</A>],
< however it requires augmentation by features such as the ability
< to describe in a machine interpretable way the rating categories
< used in a particular PICS rating system. One such mapping of PICS into
< RDF is presented <A HREF="#picsexample">below</A>.
---
> [<A HREF="#refs">PICS</A>], however it does not provide a general-purpose
> mapping from PICS rating systems into an RDF representation. One such
> mapping is presented in <A HREF="#picsexample">section 7</A>.
310c297
< One obvious application for RDF is in the description of web pages.
---
> One obvious application for RDF is in the description of Web pages.
313c300
< applicable to describing web resources to enable their discovery. The Dublin
---
> applicable to describing Web resources to enable their discovery. The Dublin
315c302
< consideration in the development of the Dublin Core was to allow simple
---
> consideration in the development of the Dublin Core was to not only allow simple
333,334c320,321
< Future extensions are likely to specify the structure of the values of
< the properties, which will involve defining classes, the properties
---
> Future extensions to the Dublin Core are likely to specify the structure of the
> values of the properties, which will involve defining classes, the properties
346,349c333,336
< is a classification system that might be used by content creators or trusted third parties
< to organise or classify Web resources.
< The RDF Schema specification provides a mechanism in which vocabularies
< for these applications can be defined.
---
> is a classification system that might be used by content creators or trusted
> third parties to organise or classify Web resources.
> The RDF Schema specification provides a mechanism for defining the vocabularies
> needed for such applications.
357c344
< logical structure of thesauri (and other library classification systems).
---
> logical structure of thesauri (and other library classification systems).
373a361,369
> <P>Although personal data collection practices could be described
> using an application-specific XML tagset, there are benefits to
> using a general metadata model for this data. Using a metadata
> schema to describe the formal structure of privacy practice
> descriptions will permit privacy practice data to be used along
> with other metadata in a query during resource discovery, and will
> permit a generic software agent to act on privacy metadata using
> the same techniques as used for other descriptive metadata.
> </P>
397,399c393,395
< on the Web. Since changing a schema risks breaking other RDF models which
< depend on that schema, this specification recommends that a new URI
< is used whenever an RDF schema is changed.
---
> on the Web. Since changing the logical structure of a schema risks
> breaking other RDF models which depend on that schema, this specification
> recommends that a new URI is used whenever an RDF schema is changed.
403,411c399,407
< In effect, changing a schema creates a new one; new schema namespaces
< should have their own URI to avoid ambiguity. Since an RDF Schema URI
< unambiguously identifies a single version of a schema, software that uses
< or manages RDF (eg. Web caches) should be able to safely store copies of
< RDF schema models for an indefinite period.
< The problems of RDF schema evolution share many characteristics with
< XML DTD version management and the general problem of Web resource versioning.
< A general approach to these issues is beyond the scope of this
< specification.
---
> In effect, changing the RDF statements which constitute a schema creates a
> new one; new schema namespaces should have their own URI to avoid
> ambiguity. Since an RDF Schema URI unambiguously identifies a single
> version of a schema, software that uses or manages RDF (eg. caches)
> should be able to safely store copies of RDF schema models for an
> indefinite period. The problems of RDF schema evolution share many
> characteristics with XML DTD version management and the general problem
> of Web resource versioning. A general approach to these issues is beyond
> the scope of this specification.
435c431
<
---
>
439c435
< property and class names:
---
> property and class names:
444c440
< the class name are also capitalized, e.g.,
---
> the class name are also capitalized, e.g.,
446,453d441
<
< <LI> Property names do NOT have the first letter capitalized,
< e.g., <code> rdfs:domain </code>.
< However, additional words in
< the name are capitalized,
< e.g., <code> rdfs:subClassOf</code> </LI>
<
< </OL>
454a443,447
> <LI> Property names do not have the first letter capitalized,
> e.g., <code> rdfs:domain</code>.
> However, additional words in
> the name are capitalized,
> e.g., <code> rdfs:subClassOf</code>. </LI>
455a449
> </OL>
463,465c457,458
< The following resources belong to the core RDF Schema. We first define
< the type system and then introduce properties for expressing various
< kinds of constraints.
---
> In this section we describe the core RDF Schema. We first define
> the type system and then introduce the core classes and properties.
471,472c464,465
< The RDF Schema defined in this specification is a collection of RDF resources
< that can be used to describe properties of other RDF resources (including properties)
---
> The RDF Schema defined in this specification is a collection of RDF resources
> that can be used to describe properties of other RDF resources (including properties)
482,486c475,479
< fashion, for example the class 'dog' might be considered a subclass of 'animal'
< which is a subclass of 'organism' etc., meaning that any resource which is
< of <code>rdf:type</code> 'dog' is <em>ipso facto</em> also of
< <code>rdf:type</code> 'animal' and so on. This specification describes a
< property, <code>rdfs:subClassOf</code>, to denote such relationships
---
> fashion, for example the class 'dog' might be considered a sub-class of
> 'animal' which is a sub-class of 'organism' etc., meaning that any
> resource which is of <code>rdf:type</code> 'dog' is <em>ipso facto</em> also of
> <code>rdf:type</code> 'animal' and so on. This specification describes a
> property, <code>rdfs:subClassOf</code>, to denote such relationships
492,493c485,486
< specification introduces a number of
< other resources for making statements about constraints on the consistent use of
---
> specification introduces a number of
> other resources for making statements about constraints on the consistent use of
495,496c488,489
< limitations on the types of values that are valid for some property, or on the classes
< to which it makes sense to ascribe such properties.
---
> limitations on the types of values that are valid for some property, or on the classes
> to which it makes sense to ascribe such properties.
498c491
< say whether or how an application must process the constraint information.
---
> say whether or how an application must process the constraint information.
513a507,552
>
> <h4> 2.1.1 Figure 1: Classes and Resources as Sets and Elements</h4>
>
> <B>Figure 1</B> illustrates the concepts of class, sub-class, and
> resource. A class is depicted by a rounded rectangle, a resource is
> depicted by a large dot. In the figure below, arrows are drawn from a
> resource to the class it defines. A sub-class is shown by having a rounded rectangle (the
> sub-class) completely enclosed by another (the super-class). If a resource
> is inside a class, then there exists either an explicit or implicit
> <code>rdf:type</code> property of that resource whose value is the resource defining the
> containing class. (These properties are shown as arcs in the directed labelled
> graph representation in figure 2). The RDF resources depicted in figure 1
> are described either in the remainder of this specification, or in the RDF
> Model and Syntax specification.
>
> <CENTER>
> <P>
> <IMG SRC="sets.gif" ALT="Figure 1: Classes and Resources as Sets and Elements" />
> <BR /><B>Figure 1</B>: Classes and Resources as Sets and Elements
> <BR />
> </P>
> </CENTER>
>
> <H4>2.1.2 Figure 2: Class Hierarchy for the RDF Schema</H4>
>
> <P>
> <B>Figure 2</B> shows the same information about the class hierarchy
> as in figure 1, but does so using a "nodes and arcs" graph representation of
> the RDF data model.
> If a class is a subset of another, then there is an <code>rdfs:subClassOf</code>
> arc from the node
> representing the first class to the node representing the second. Similarly,
> if a Resource was an instance of a Class, then there is an <code>rdf:type</code>
> arc from the resource to the node representing the class. (Not all such arcs are shown.
> We only show the arc to the most tightly encompassing class, and rely on the transitivity
> of the <code>rdfs:subClassOf</code> relation to provide the rest).
> </P>
>
> <CENTER>
> <P>
> <IMG SRC="hierarchy.gif" ALT="Figure 2: Class Hierarchy for the RDF Schema" />
> <BR /><B>Figure 2</B>: Class Hierarchy for the RDF Schema
> </P>
> </CENTER>
>
>
517c556,557
< RDF Schema machinery. Every RDF model (implicitly) includes these.
---
> RDF Schema machinery. Every RDF model that draws upon the RDF
> Schema vocabulary namespace (implicitly) includes these.
523c563
< considered to be instances of the class <code>rdfs:Resource</code>.
---
> considered to be instances of the class <code>rdfs:Resource</code>.
525c565
< represents the set called 'Resources' in the formal model for RDF presented in section 5 of
---
> represents the set called 'Resources' in the formal model for RDF presented in section 5 of
529a570,576
> <P>Note that the class <code>rdfs:Resource</code>
> is unrelated to the syntactic attribute 'resource' used in the RDF/XML
> serialization syntax (just as the resource 'Description' defined by
> the Dublin Core element set is unconnected to the syntactic element
> 'Description' used in the RDF/XML syntax).
> </P>
>
533,534c580,581
< i.e., all the elements of the set introduced as 'Properties' in section 5 of the Model
< and Syntax specification [<A HREF="#rdfms">RDFSMS</A>].
---
> i.e., all the elements of the set introduced as 'Properties' in section 5 of the Model
> and Syntax specification [<A HREF="#rdfms">RDFSMS</A>].
541c588
< programming languages such as Java.
---
> programming languages such as Java.
544c591
< RDF classes can be defined to represent almost anything, such as web pages, people, document types,
---
> RDF classes can be defined to represent almost anything, such as Web pages, people, document types,
551c598
< also (implicitly) includes the following core properties.
---
> also (implicitly) includes the following core properties.
561c608
< When a resource has an <code>rdf:type</code> property whose value is
---
> When a resource has an <code>rdf:type</code> property whose value is
565c612
< another resource which must be an instance of <code>rdfs:Class</code>.
---
> another resource which must be an instance of <code>rdfs:Class</code>.
570c617
< of more than one class.
---
> of more than one class.
575c622
< This property indicates the subset/superset relation between classes.
---
> This property specifies a subset/superset relation between classes.
593d639
<
595c641
<
---
>
597,600c643,647
< This is a very simple example that expresses the following class
< hierarchy. We first define a class 'Automobile'. We then define 3 subclasses
< of 'Automobile', namely 'PassengerVehicle', 'Truck' and 'Van'. We then define
< a class 'Minivan' which is a subclass of both 'Van' and 'PassengerVehicle'.
---
> This is a very simple example that expresses the following class
> hierarchy. We first define a class 'MotorVehicle'. We then define 3
> subclasses of 'MotorVehicle', namely 'PassengerVehicle', 'Truck' and
> 'Van'. We then define a class 'Minivan' which is a sub-class of both
> 'Van' and 'PassengerVehicle'.
602a650,653
>
> <CENTER><P><IMG SRC="car_classes.gif" ALT="Figure showing example class
> hierarchy" /></P></CENTER>
>
611c662
< 'V_323' and that it is an instance of the class <code>Van</code>.
---
> 'v_323' and that it is an instance of the class <code>Van</code>.
615c666
< these initial examples do not take advantage of the <code>rdf:type</code>
---
> these initial examples do not take advantage of the <code>rdf:type</code>
625,631c676,689
< <rdf:RDF
< xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs="http://www.w3.org/TR/WD-rdf-schema#">
<
< <rdf:Description ID="Automobile">
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-schema#Class"/>
< <rdfs:subClassOf resource="http://www.w3.org/TR/WD-rdf-schema#Resource"/>
---
> <rdf:RDF xml:lang="en"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#">
>
> <!-- Note: this RDF schema would typically be used in RDF instance data
> by referencing it with an XML namespace declaration, for example
> xmlns:xyz="http://w3.org/examples/vehicles#". This allows us to use
> abbreviations such as xyz:MotorVehicle to refer unambiguously to the
> RDF class 'MotorVehicle'. -->
>
> <rdf:Description ID="MotorVehicle">
> <rdf:type resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Class"/>
> <rdfs:subClassOf
> rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
635,636c693,694
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-schema#Class"/>
< <rdfs:subClassOf resource="#Automobile"/>
---
> <rdf:type resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Class"/>
> <rdfs:subClassOf rdf:resource="#MotorVehicle"/>
640,641c698,699
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-schema#Class"/>
< <rdfs:subClassOf resource="#Automobile"/>
---
> <rdf:type resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Class"/>
> <rdfs:subClassOf rdf:resource="#MotorVehicle"/>
645,646c703,704
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-schema#Class"/>
< <rdfs:subClassOf resource="#Automobile"/>
---
> <rdf:type resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Class"/>
> <rdfs:subClassOf rdf:resource="#MotorVehicle"/>
650,652c708,710
< <rdf:type resource="#Class"/>
< <rdfs:subClassOf resource="#Van"/>
< <rdfs:subClassOf resource="#PassengerVehicle"/>
---
> <rdf:type resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Class"/>
> <rdfs:subClassOf rdf:resource="#Van"/>
> <rdfs:subClassOf rdf:resource="#PassengerVehicle"/>
661c719
<
---
>
665,669c723,727
< An instance of property that is used to specify that one
< property is a specialization of another. A property may have
< zero, one or more properties that it is a
< specialization of. If some property P1 is a subPropertyOf another more
< general property P2, and if a resource A has a P2 property with a value B,
---
> An instance of <code>rdf:Property</code> that is used to specify that one
> property is a specialization of another. A property may have
> zero, one, or more properties that it is a
> specialization of. If some property P2 is a subPropertyOf another more
> general property P1, and if a resource A has a P2 property with a value B,
673a732,740
> <P>
> A property can never be declared to be a sub-property of itself, nor of
> any of its own sub-properties. Note that this constraint is <em>not</em>
> expressible using the RDF Schema constraint facilities provided below,
> and so does not appear in the RDF version of this specification given in
> Appendix A.
> </P>
>
>
678c745
< <code>biologicalFather</code> of John, then it is implied that Fred is also the
---
> <code>biologicalFather</code> of John, then it is implied that Fred is also the
682a750
>
687,689c755,757
< <rdf:RDF
< xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs="http://www.w3.org/TR/WD-rdf-schema#">
---
> <rdf:RDF xml:lang="en"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#">
692c760
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
696,697c764,765
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:subPropertyOf resource="#biologicalParent"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:subPropertyOf rdf:resource="#biologicalParent"/>
706a775,829
>
> <H4>2.3.4 seeAlso</H4>
>
> <P>
> The property <code>rdfs:seeAlso</code>
> specifies a resource that contains information about the subject resource. This
> property may be specialized using <code>rdfs:subPropertyOf</code> to more precisely
> indicate the nature of the information the object resource has about the
> subject resource. The object and the subject resources are <A
> HREF="#constraints">constrained</A> only to be instances of the class
> <code>rdfs:Resource</code>.
> </P>
>
>
> <H4>2.3.5 isDefinedBy</H4>
>
> <P>
> The property <code>rdfs:isDefinedBy</code> is a sub-property of
> <code>rdfs:seeAlso</code>, and indicates the resource
> defining the subject resource. As with <code>rdf:seeAlso</code>, this
> property can be applied to any instance of <code>rdfs:Resource</code> and may have
> as its value any <code>rdfs:Resource</code>.
> </P>
>
> <P>
> The most common anticipated usage is to identify the RDF schema given a
> name for one of the properties or classes defined by that schema.
> Although XML namespace declarations will typically provide the URI where
> RDF
> vocabulary resources are defined, there are cases where additional
> information is required.
> </P>
>
> <P>
> For example, constructs such as <br />
> <code><rdfs:subPropertyOf
> rdf:resource="http://purl.org/dc/elements/1.0/Creator"/></code><br />
> do not
> indicate the URI of the schema that includes the vocabulary item
> <code>Creator</code> (ie., <code>http://purl.org/dc/elements/1.0/</code>).
> </P>
>
> <P>
> In such cases, the <code>rdfs:isDefinedBy</code> property can be used to explicitly
> represent that
> information. This approach will also work when the URIs of the namespace and its
> components have no obvious relationship, as would be the case if they
> were identified using schemes such as GUIDs or MD-5 hashes.
> </P>
>
>
>
>
>
>
716c839
< This is the role of the <code>rdfs:domain</code> and
---
> This is the role of the <code>rdfs:domain</code> and
721,723c844,846
< "author" of type "Literal". The benefits of this property-centric
< approach are that it is very easy for anyone to say anything they want
< about existing resources, which is one of the axioms of the web.
---
> "author" of type "Literal". One benefit of this property-centric
> approach is that it is very easy for anyone to say anything they want
> about existing resources, which is one of the axioms of the Web.
736c859
< certain properties "make sense".
---
> certain properties "make sense".
750c873,880
< A model that violates a constraint is an <em>inconsistent model</em>.
---
> An RDF model that violates any of the consistency
> constraints specified in this document is said to be
> an <em>inconsistent</em> model. The following constraints are specified:
> <code>rdfs:domain</code> and <code>rdfs:range</code>
> constraints on property usage, the rule that <code>rdfs:subPropertyOf</code> and
> <code>rdfs:subClassOf</code> properties should not form loops, plus any
> further consistency constraints defined using the
> <code>rdfs:ConstraintResource</code> extensibility mechanism.
752c882
< face of an inconsistent model. Some examples of constraints include:
---
> face of an inconsistent model.
753a884
>
755,761c886,888
< <UL>
< <LI>
< That the value of a property should be a resource of a designated class.
< This is expressed by the <em>range</em> property. For example, a range
< constraint applying to the 'author' property may express that the
< value of an 'author' property must be a resource of class 'Person'.
< </LI>
---
> <P>
> Some examples of constraints include:
> </P>
763,768c890,903
< <LI>
< That a property may only be used on resources of a certain class.
< For example, that an 'author' property could only originate from a
< resource that was an instance of class 'Book'.
< This is expressed using the <em>domain</em> property.
< </LI>
---
> <UL>
> <LI>
> That the value of a property should be a resource of a designated class.
> This is expressed by the <em>range</em> property. For example, a range
> constraint applying to the 'author' property may express that the
> value of an 'author' property must be a resource of class 'Person'.
> </LI>
>
> <LI>
> That a property may only be used on resources of a certain class.
> For example, that an 'author' property could only originate from a
> resource that was an instance of class 'Book'.
> This is expressed using the <em>domain</em> property.
> </LI>
774c909
< identify classes and properties, it is possible to create new properties
---
> identify classes and properties, it is possible to create new properties
778a914,933
>
> <P>
> The RDF Schema uses the constraint properties to constrain how its
> own properties can be used. These constraints are shown below in
> <B>figure 3</B>. Nodes with <b>bold</b> outlines are instances of
> rdfs:Class.
> </P>
>
> <CENTER>
>
> <P>
> <IMG SRC="constraints.gif" ALT="Figure 3: Constraints in the RDF Schema" />
> <BR /><B>Figure 3</B>: Constraints in the RDF Schema
> </P>
>
> </CENTER>
>
>
>
>
783c938
< This resource defines a sub-class of <code>rdfs:Resource</code> whose
---
> This resource defines a sub-class of <code>rdfs:Resource</code> whose
785c940
< constraints. The purpose of this class is to provide a mechanism
---
> constraints. The purpose of this class is to provide a mechanism
801,802c956,957
< that class representing properties. Both <code>rdfs:domain</code> and
< <code>rdfs:range</code> are instances of
---
> that class representing properties. Both <code>rdfs:domain</code> and
> <code>rdfs:range</code> are instances of
808c963
<
---
> <A NAME="range_description"></A>
817c972,987
< which case, the class of the property value is unconstrained.
---
> which case the class of the property value is unconstrained.
> </P>
>
> <P>
> Although it is not possible to express two or more range constraints on a property,
> a similar outcome can be achieved by defining a common superclass for any classes
> that represent appropriate values for some property. For example, to express the
> constraint that a property <code>xyz:drivesMotorVehicle</code> can have
> values which are Vans, Trucks or PassengerVehicles, we assert that
> <code>xyz:drivesMotorVehicle</code> has a <code>rdfs:range</code> of
> <code>MotorVehicle</code>. If <code>Van</code>, <code>Truck</code> and
> <code>PassengerVehicle</code> are known to be sub-classes of
> <code>MotorVehicle</code>, then all these types of resource are acceptable
> values for
> <code>xyz:drivesMotorVehicle</code>. In cases where a common super-class
> does not exist, one can be defined in a schema in the normal manner.
825a996,997
>
> <A NAME="domain_description"></A>
831c1003
< zero, one or more than one class as its domain. If there is no domain
---
> zero, one, or more than one class as its domain. If there is no domain
835c1007
< If there is more than one domain property, the constrained property
---
> If there is more than one domain property, the constrained property
837c1009
< those domain properties).
---
> those domain properties).
842,843c1014,1015
< <P>
< Continuing with our earlier example of Automobiles, in this example,
---
> <P>
> Continuing with our earlier example of MotorVehicle, in this example,
845c1017
< The 'registeredTo' property is applicable to any Automobile and
---
> The 'registeredTo' property is applicable to any MotorVehicle and
847c1019
< this example, 'rearSeatLegRoom' only applies to Minivans and
---
> this example, 'rearSeatLegRoom' only applies to Minivans and
850c1022
< which is the number of inches of rear seat legroom.
---
> which is the number of centimetres of rear seat legroom.
857,859c1029,1031
< <rdf:RDF
< xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs="http://www.w3.org/TR/WD-rdf-schema#">
---
> <rdf:RDF xml:lang="en"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#">
862,863c1034,1035
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:domain rdf:resource="#Automobile"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:domain rdf:resource="#MotorVehicle"/>
868c1040
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
871c1043
< <rdfs:range rdf:resource="http://www.w3.org/TR/datatypes#Number"/>
---
> <rdfs:range rdf:resource="http://www.w3.org/datatypes#Number"/>
886c1058
< provided by XML and by the RDF Model and Syntax.
---
> provided by XML and by the RDF Model and Syntax.
917c1089
< their predecessors.
---
> their predecessors.
923c1095
< in future W3C activity.
---
> in future W3C Activity.
936c1108
< <code>V1:Van</code>.
---
> <code>V1:Van</code>.
950c1122
< This specification defines a subclass of resources known as 'constraint
---
> This specification defines a sub-class of resources known as 'constraint
959,960c1131,1132
< of <em>consistent</em> and <em>inconsistent</em> RDF models. As yet
< unknown constraint properties may contribute to a more expressive
---
> of <em>consistent</em> and <em>inconsistent</em> RDF models. As yet
> unknown constraints may contribute to a more expressive
968,969c1140,1141
< knowledge to evaluate models for consistency with respect to
< resources defined using those constraints.
---
> knowledge to evaluate models for consistency when vocabulary items are
> defined using those unknown constraints.
973c1145
< provide enough information to enable its use in consistency checking.
---
> provide enough information to enable its use in consistency checking.
981c1153
< it is used in that fashion.
---
> it is used in that fashion.
988,992c1160,1164
< Web Languages NOTE [<A HREF="#refs">EXTWEB</A>]. By flagging new forms
< of constraint as members of this class, we indicate that they are intended to express Schema
< language contraints whose semantics must be understood for
< consistency checking to be undertaken accurately. Membership of the class
< suggests, but does not imply, that those semantics may be inexpressible
---
> Web Languages W3C NOTE [<A HREF="#refs">EXTWEB</A>]. By flagging new forms
> of constraint as members of this class, we indicate that they are intended to express Schema
> language contraints whose semantics must be understood for
> consistency checking to be possible. Membership of the class
> suggests, but does not imply, that those semantics may be inexpressible
1006,1007c1178,1179
< of that class, since this specification provides no mechanism for learning
< about such constraints through the interpretation of RDF statements.
---
> of that class, since this specification provides no mechanism for learning
> about such constraints through the interpretation of RDF statements.
1009,1010c1181,1182
< define sub-classes of <code>ConstraintProperty</code> to classify new constructs
< according to whether or not they had inexpressible semantics.
---
> define sub-classes of <code>ConstraintProperty</code> to classify new constructs
> according to whether or not they had inexpressible semantics.
1015,1016d1186
<
<
1026c1196
< to provider richer documentation.
---
> to provide richer documentation.
1032c1202
< This is used to provide a human readable natural language description of
---
> This is used to provide a human-readable natural language description of
1039c1209
< This is used to provide a human readable version of a resource name.
---
> This is used to provide a human-readable version of a resource name.
1049,1050c1219
< reference is http://www.w3.org/TR/WD-rdf-syntax#. The RDF Model and Syntax document
< itself includes an embedded RDF Schema definition for these resources. In
---
> reference is http://www.w3.org/1999/02/22-rdf-syntax-ns#. In
1055c1224
< an RDF resource belongs to the http://www.w3.org/TR/WD-rdf-syntax#
---
> an RDF resource belongs to the <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code>
1057,1059c1226,1232
< that resource's definition. <A HREF="#xmlcore">Appendix A</A> provides an
< RDF/XML schema for the RDF resources defined in this document, including
< RDF Model concepts such as <code>Literal</code> and <code>Resource</code>.
---
> that resource's definition.
> </P>
>
> <P>
> <A HREF="#xmlcore">Appendix A</A> provides an RDF/XML schema for the RDF resources
> defined in this document, including RDF Model concepts such as
> <code>Literal</code> and <code>Resource</code>.
1073c1246
< This corresponds to the set called the 'Literals' in the formal model for RDF
---
> This corresponds to the set called the 'Literals' in the formal model for RDF
1075,1076c1248,1249
< specification [<A HREF="#refs">RDFMS</A>]. Atomic values such as textual strings are examples of
< RDF literals.
---
> specification [<A HREF="#refs">RDFMS</A>]. Atomic values such as textual strings are examples of
> RDF literals.
1081c1254
< This corresponds to the set called the 'Statement' in the formal model for RDF
---
> This corresponds to the set called the 'Statement' in the formal model for RDF
1083c1256
< specification [<A HREF="#refs">RDFMS</A>].
---
> specification [<A HREF="#refs">RDFMS</A>].
1088c1261
< This corresponds to the property called the 'subject' in the formal model for RDF
---
> This corresponds to the property called the 'subject' in the formal model for RDF
1090,1094c1263,1266
< specification [<A HREF="#refs">RDFMS</A>]. Its <code>rdfs:domain</code>
< is <code>rdf:Statement</code>
< and <code>rdfs:range</code>
< is <code>rdfs:Resource</code>. This is used to specify the resource described
< by a reified statement.
---
> specification [<A HREF="#refs">RDFMS</A>]. Its <code>rdfs:domain</code>
> is <code>rdf:Statement</code> and <code>rdfs:range</code> is
> <code>rdfs:Resource</code>. This is used to specify the resource
> described by a reified statement.
1099c1271
< This corresponds to the property called the 'predicate' in the formal model for RDF
---
> This corresponds to the property called the 'predicate' in the formal model for RDF
1101,1104c1273,1276
< specification [<A HREF="#refs">RDFMS</A>]. Its <code>rdfs:domain</code>
< is <code>rdf:Statement</code>
< and <code>rdfs:range</code>
< is <code>rdf:Property</code>. This is used to identify the property used in the modeled statement.
---
> specification [<A HREF="#refs">RDFMS</A>]. Its <code>rdfs:domain</code>
> is <code>rdf:Statement</code> and <code>rdfs:range</code> is
> <code>rdf:Property</code>. This is used to identify the property used
> in the modelled statement.
1109,1110c1281,1282
< This corresponds to the property called the 'predicate' in the formal model for RDF
< presented in section 5 of the Model and Syntax
---
> This corresponds to the property called the 'object' in the formal model
> for RDF presented in section 5 of the Model and Syntax
1112c1284
< This is used to identify the property value in the modeled statement.
---
> This is used to identify the property value in the modelled statement.
1116d1287
<
1118c1289
< This class is used to hold the Container classes described in section 3
---
> This class is used to hold the Container classes described in section 3
1125,1128c1296,1301
< This corresponds to the class called the 'Bag' in the formal model for RDF
< presented in section 5 of the Model and Syntax
< specification [<A HREF="#refs">RDFMS</A>]. It is an instance of <code>rdfs:Class</code> and
< <code>rdfs:subtypeOf</code> <code>rdfs:Container</code>.
---
> <P>
> This corresponds to the class called 'Bag' in the formal model for RDF presented
> in section 5 of the Model and Syntax specification [<A HREF="#refs">RDFMS</A>]. It
> is an instance of <code>rdfs:Class</code> and
> <code>rdfs:subClassOf</code> <code>rdfs:Container</code>.
> </P>
1131,1134c1304,1309
< This corresponds to the class called the 'Sequence' in the formal model for RDF
< presented in section 5 of the Model and Syntax
< specification [<A HREF="#refs">RDFMS</A>]. It is an instance of <code>rdfs:Class</code> and
< <code>rdfs:subtypeOf</code> <code>rdfs:Container</code>.
---
> <P>
> This corresponds to the class called 'Sequence' in the formal model for RDF
> presented in section 5 of the Model and Syntax specification [<A
> HREF="#refs">RDFMS</A>]. It is an instance of <code>rdfs:Class</code> and
> <code>rdfs:subClassOf</code> <code>rdfs:Container</code>.
> </P>
1137c1312,1313
< This corresponds to the class called the 'Alternative' in the formal model for RDF
---
> <P>
> This corresponds to the class called 'Alternative' in the formal model for RDF
1140c1316,1317
< <code>rdfs:subtypeOf</code> <code>rdfs:Container</code>.
---
> <code>rdfs:subClassOf</code> <code>rdfs:Container</code>.
> </P>
1143,1145c1320,1323
< This corresponds to the properties <code>_1, _2, _3 ...</code> used to indicate
< container membership, as described in section 3
< of the Model and Syntax specification [<A HREF="#refs">RDFMS</A>]. This is a
---
> <P>
> This class has as members the properties <code>_1, _2, _3 ...</code> used
> to indicate container membership, as described in section 3
> of the Model and Syntax specification [<A HREF="#refs">RDFMS</A>]. This is a
1146a1325
> </P>
1149c1328,1329
< This corresponds to the 'value' property described in section 7.3
---
> <P>
> This corresponds to the 'value' property described in section 2.3
1151c1331
<
---
> </P>
1184,1185c1364
< level decision; such decisions will be aided by the provisions in RDF for
< digital signatures.
---
> level decision.
1193,1195c1372,1374
< <rdf:RDF
< xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs="http://www.w3.org/TR/WD-rdf-schema#">
---
> <rdf:RDF xml:lang="en"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#">
1198,1199c1377
< <rdfs:comment>The class of people. correspond to a single person.
< </rdfs:comment>
---
> <rdfs:comment>The class of people.</rdfs:comment>
1238,1241c1416,1418
< is a declared to be a class. Every SearchQuery can have both a
< <code>queryString</code> whose value is an <code>rdf:Literal</code> and a
< <code>queryService</code> whose value is a <code>SearchService</code>.
<
---
> is declared to be a class. Every SearchQuery can have both a
> <code>queryString</code> whose value is an <code>rdfs:Literal</code> and a
> <code>queryService</code> whose value is a <code>SearchService</code>.
1243c1420
< defined elsewhere). A <code>SearchQuery</code> has some number of <code>result</code>
---
> defined elsewhere). A <code>SearchQuery</code> has some number of <code>result</code>
1267,1269c1444,1446
< <rdf:RDF
< xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs="http://www.w3.org/TR/WD-rdf-schema#">
---
> <rdf:RDF xml:lang="en"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#">
1272c1449,1450
< <rdfs:subClassOf rdf:resource="http://www.w3.org/TR/WD-rdf-schema#Resource"/>
---
> <rdfs:subClassOf
> rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
1276c1454,1455
< <rdfs:subClassOf rdf:resource="http://www.w3.org/TR/WD-rdf-schema#Resource"/>
---
> <rdfs:subClassOf
> rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
1280c1459,1460
< <rdfs:subClassOf rdf:resource="http://www.classtypes.org/useful_classes#Service"/>
---
> <rdfs:subClassOf
> rdf:resource="http://www.classtypes.org/useful_classes#InternetService"/>
1286c1466
< rdf:resource="http://www.w3.org/TR/WD-rdf-schema#Literal"/>
---
> rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Literal"/>
1299a1480
> <rdfs:domain rdf:resource="#SearchResult"/>
1305c1486,1487
< <rdfs:range rdf:resource="http://www.w3.org/TR/WD-rdf-schema#Literal"/>
---
> <rdfs:range
> rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Literal"/>
1330,1331c1512,1513
< <B>Status:</B> this is work-in-progess illustrating how a
< PICS schema would be expressed in RDF.
---
> <B>Status:</B> this is work-in-progess illustrating how a
> PICS schema could be expressed in RDF.
1337c1519
< <LI>Part A covers the vocabulary in the
---
> <LI>Part A covers the vocabulary in the
1341c1523
< <LI>Part B covers the
---
> <LI>Part B covers the
1347c1529
< Part C covers an example PICS rating system from the
---
> Part C covers an example PICS rating system from the
1362c1544
< and <TT>MIC-MD5</TT>) are omitted from this vocabulary.
---
> and <TT>MIC-MD5</TT>) are omitted from this vocabulary.
1363a1546
>
1375c1558
< being rated and the rating statement. As such, it is modeled as a property
---
> being rated and the rating statement. As such, it is modelled as a property
1381c1564
< comment="The last modification date of the
---
> comment="The last modification date of the
1383c1566
< <domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
1396c1579
< has for the <EM>content</EM> of the statements.
---
> has for the <EM>content</EM> of the statements.
1402c1585
< <domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
1412c1595
< <domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
1417c1600
< <domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
1421,1422c1604,1606
< <P>The PICS 'until' label option can also be written as 'exp'. We
< could use <code>subPropertyOf</code> to represent this synonym; instead,
---
> <P>
> The PICS 'until' label option can also be written as 'exp'. We
> could use <code>subPropertyOf</code> to represent this synonym; instead,
1428c1612
< <domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
1438c1622,1623
< <domain rdf:resource="http://www.w3.org/TR/WD-rdf-schema#Container"/>
---
> <domain
> rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Container"/>
1442c1627,1628
< <P>The 'completeLabel' property will appear only on a container that has
---
> <P>
> The 'completeLabel' property will appear only on a container that has
1446c1632,1633
< resource are added.</P>
---
> resource are added.
> </P>
1450c1637,1638
< <domain rdf:resource="http://www.w3.org/TR/WD-rdf-schema#Container"/>
---
> <domain
> rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Container"/>
1467c1655
< comment="A graphic associated with the rating service or with a
---
> comment="A graphic associated with the rating service or with a
1498c1686
< <subClassOf resource="http://www.w3.org/TR/WD-rdf-syntax#Bag"/>
---
> <subClassOf resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag"/>
1503c1691
< <subClassOf resource="http://www.w3.org/TR/WD-rdf-syntax#Seq"/>
---
> <subClassOf resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq"/>
1518c1706,1707
< follows:</P>
---
> follows:
> </P>
1527,1528c1716,1718
< xmlns="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:s="http://www.w3.org/TR/WD-rdf-schema#"
---
> xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:s="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#"
1532c1722
< <p:icon resource="icons/gcf.gif"/>
---
> <p:icon rdf:resource="icons/gcf.gif"/>
1535c1725
< related products. For demonstration purposes only.</p:description>
---
> related products. For demonstration purposes only.</p:description>
1545c1735
< <s:range resource="#DensityValue"/>
---
> <s:range rdf:resource="#DensityValue"/>
1551c1741
< value="0"
---
> rdf:value="0"
1553c1743
< <p:icon resource="icons/none.gif"/>
---
> <p:icon rdf:resource="icons/none.gif"/>
1558c1748
< value="1"
---
> rdf:value="1"
1560c1750
< <p:icon resource="icons/lots.gif"/>
---
> <p:icon rdf:resource="icons/lots.gif"/>
1567c1757
< <s:range resource="#SubjectValue">
---
> <s:range rdf:resource="#SubjectValue">
1573c1763
< value="0"
---
> rdf:value="0"
1578c1768
< value="1"
---
> rdf:value="1"
1583c1773
< value="2"
---
> rdf:value="2"
1597,1598c1787,1788
< <s:domain resource="#ColorValue"/>
< <s:range resource="#HueValue"/>
---
> <s:domain rdf:resource="#ColorValue"/>
> <s:range rdf:resource="#HueValue"/>
1604c1794
< value="0"
---
> rdf:value="0"
1609c1799
< value="1"
---
> rdf:value="1"
1614c1804
< value="2"
---
> rdf:value="2"
1620,1621c1810,1811
< <s:domain resource="#ColorValue"/>
< <s:range resource="http://www.w3.org/TR/WD-pics2.0#Integer"/>
---
> <s:domain rdf:resource="#ColorValue"/>
> <s:range rdf:resource="http://www.w3.org/TR/WD-pics2.0#Integer"/>
1633a1824
> <BR />
1635,1671c1826,1827
< <H2><A NAME="figures"></A>8. Figures</H2>
<
< <B>Figure 1</B> illustrates the concepts of class, sub-class, and
< resource. A class is depicted by a rounded rectangle, a resource is
< depicted by a large dot. In the figure below, arrows are drawn from a
< resource to the class it defines. A sub-class is shown by having a rounded rectangle (the
< sub-class) completely enclosed by another (the super-class). If a resource
< is inside a class, then there exists either an explicit or implicit
< <code>rdf:type</code> property of that resource whose value is the resource defining the
< containing class. (These properties are shown as arcs in the directed labelled
< graph representation in figure 2).
<
< <CENTER>
< <P>
< <IMG SRC="sets.gif" ALT="Figure 1: Classes and Resources as Sets and Elements" />
< <BR /><B>Figure 1</B>: Classes and Resources as Sets and Elements
< </P>
< </CENTER>
<
< <P>
< <B>Figure 2</B> shows the same information about the class hierarchy
< as in figure 1, but does so using a "nodes and arcs" graph representation of
< the RDF data model.
< If a class is a subset of another, then there is an <code>rdfs:subClassOf</code>
< arc from the node
< representing the first class to the node representing the second. Similarly,
< if a Resource was an instance of a Class, then there is an <code>rdf:type</code>
< arc from the resource to the node representing the class. (Not all such arcs are shown.
< We only show the arc to the most tightly encompassing class, and rely on the transitivity
< of the <code>rdfs:subClassOf</code> relation to provide the rest).
< </P>
<
< <CENTER>
< <P>
< <IMG SRC="hierarchy.gif" ALT="Figure 2: Class Hierarchy for the RDF Schema" />
< <BR /><B>Figure 2</B>: Class Hierarchy for the RDF Schema</P>
< </CENTER>
---
> <A NAME="ack"></A>
> <H2>8. Acknowledgements</H2>
1674,1677c1830,1832
< The RDF Schema uses the constraint properties to constrain how its
< own properties can be used. These constraints are shown below in
< <B>figure 3</B>. Nodes with <b>bold</b> outlines are instances of
< rdfs:Class.
---
> Note: This document was prepared and approved for publication by the W3C
> RDF Schema Working Group (WG). WG approval of this document does not necessarily
> imply that all WG members voted for its approval.
1679d1833
< <CENTER>
1682,1683c1836,1839
< <IMG SRC="constraints.gif" ALT="Figure 3: Constraints in the RDF Schema" />
< <BR /><B>Figure 3</B>: Constraints in the RDF Schema
---
> David Singer of IBM is the chair of the group; we thank David for his
> efforts and thank IBM for supporting him and us in this endeavor.
> Particular thanks are also due to Andrew Layman for his editorial work
> on earlier versions of this specification.
1685,1695d1840
< </CENTER>
<
< <BR />
< <A NAME="ack"></A>
< <H2>8. Acknowledgements</H2>
<
< <P>Note: This document was prepared and approved for publication by the W3C
< RDF Schema Working Group (WG). WG approval of this document does not necessarily
< imply that all WG members voted for its approval.</P>
< <P>David Singer of IBM is the chair of the group; we thank David for his
< efforts and thank IBM for supporting him and us in this endeavor.</P>
1697a1843
>
1699c1845
< Walter Chang (Adobe), Sailesh Chutani (Oracle), Ron Daniel (DATAFUSION),
---
> Walter Chang (Adobe), Sailesh Chutani (Oracle), Ron Daniel (DATAFUSION),
1719c1865
< <hr />
---
> <hr />
1737c1883
< RDF below does not tell us that subClassOf arcs should not (to use terminology from the
---
> RDF below does not tell us that subClassOf arcs should not (to use terminology from the
1747,1748c1893,1894
< xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs="http://www.w3.org/TR/WD-rdf-schema#">
---
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#">
1757,1758c1903,1904
< <rdf:Description about="http://www.w3.org/TR/WD-rdf-syntax#type">
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:Description about="http://www.w3.org/1999/02/22-rdf-syntax-ns#type">
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1762c1908
< <rdfs:range resource="#Class"/>
---
> <rdfs:range rdf:resource="#Class"/>
1766c1912
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1769c1915
< <rdfs:domain resource="#Resource"/>
---
> <rdfs:domain rdf:resource="#Resource"/>
1771c1917
< <rdfs:range resource="http://www.w3.org/TR/WD-rdf-schema#Literal"/>
---
> <rdfs:range rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Literal"/>
1775c1921
< <rdf:type resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1781c1927
< rdf:resource="http://www.w3.org/TR/WD-rdf-schema#Literal"/>
---
> rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Literal"/>
1785c1931
< <rdf:type rdf:resource="#Class"/>
---
> <rdf:type resource="#Class"/>
1793c1939
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1802c1948
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1806,1807c1952,1972
< <rdfs:range rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> </rdf:Description>
>
> <rdf:Description ID="seeAlso">
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label xml:lang="en">seeAlso</rdfs:label>
> <rdfs:label xml:lang="fr">voirAussi</rdfs:label>
> <rdfs:comment>Indicates a resource that provides information about the subject resource.</rdfs:comment>
> <rdfs:range rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> <rdfs:domain rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> </rdf:Description>
>
> <rdf:Description ID="isDefinedBy">
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:subPropertyOf rdf:resource="#seeAlso"/>
> <rdfs:label xml:lang="en">isDefinedBy</rdfs:label>
> <rdfs:label xml:lang="fr">esDéfiniPar</rdfs:label>
> <rdfs:comment>Indicates a resource containing and defining the subject resource.</rdfs:comment>
> <rdfs:range rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> <rdfs:domain rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
1813c1978
< <rdf:type rdf:resource="#Class"/>
---
> <rdf:type resource="#Class"/>
1821,1822c1986,1987
< <rdf:type rdf:resource="#Class"/>
< <rdfs:subClassOf rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="#Class"/>
> <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1842c2007
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1850c2015
< <rdf:type rdf:resource="#Class"/>
---
> <rdf:type resource="#Class"/>
1860c2025
< <rdf:Description about="http://www.w3.org/TR/WD-rdf-syntax#Statement">
---
> <rdf:Description about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement">
1864c2029
< <rdfs:subClassOf resource="#Resource"/>
---
> <rdfs:subClassOf rdf:resource="#Resource"/>
1868c2033
< <rdf:Description about="http://www.w3.org/TR/WD-rdf-syntax#subject">
---
> <rdf:Description about="http://www.w3.org/1999/02/22-rdf-syntax-ns#subject">
1871,1872c2036,2037
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
1876c2041
< <rdf:Description about="http://www.w3.org/TR/WD-rdf-syntax#predicate">
---
> <rdf:Description about="http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate">
1879,1881c2044,2046
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
< <rdfs:range rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
> <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1884c2049
< <rdf:Description about="http://www.w3.org/TR/WD-rdf-syntax#object">
---
> <rdf:Description about="http://www.w3.org/1999/02/22-rdf-syntax-ns#object">
1887,1888c2052,2053
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
1895c2060
< <rdfs:subClassOf resource="#Resource"/>
---
> <rdfs:subClassOf rdf:resource="#Resource"/>
1899c2064
< <rdf:Description about="http://www.w3.org/TR/WD-rdf-syntax#Bag">
---
> <rdf:Description about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag">
1902,1903c2067,2068
< <rdf:type rdf:resource="#Class"/>
< <rdfs:subClassOf resource="#Container"/>
---
> <rdf:type resource="#Class"/>
> <rdfs:subClassOf rdf:resource="#Container"/>
1906c2071
< <rdf:Description about="http://www.w3.org/TR/WD-rdf-syntax#Seq">
---
> <rdf:Description about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq">
1909,1910c2074,2075
< <rdf:type rdf:resource="#Class"/>
< <rdfs:subClassOf resource="#Container"/>
---
> <rdf:type resource="#Class"/>
> <rdfs:subClassOf rdf:resource="#Container"/>
1913c2078
< <rdf:Description about="http://www.w3.org/TR/WD-rdf-syntax#Alt">
---
> <rdf:Description about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Alt">
1916,1917c2081,2082
< <rdf:type rdf:resource="#Class"/>
< <rdfs:subClassOf resource="#Container"/>
---
> <rdf:type resource="#Class"/>
> <rdfs:subClassOf rdf:resource="#Container"/>
1922,1923c2087,2088
< <rdf:type rdf:resource="#Class"/>
< <rdfs:subClassOf resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="#Class"/>
> <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1926c2091
< <rdf:Description about="http://www.w3.org/TR/WD-rdf-syntax#value">
---
> <rdf:Description about="http://www.w3.org/1999/02/22-rdf-syntax-ns#value">
1929c2094
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:type resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
1958,1969c2123,2134
< <rdf:RDF
< xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs="http://www.w3.org/TR/WD-rdf-schema#">
<
< <rdfs:Class rdf:ID="Resource"
< rdfs:label="Resource"
< rdfs:comment="The most general class/">
<
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#type"
< rdfs:label="type"
< rdfs:comment="Indicates membership of a class">
< <rdfs:range resource="#Class"/>
---
> <rdf:RDF xml:lang="en"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#">
>
> <rdfs:Class rdf:ID="Resource"
> rdfs:label="Resource"
> rdfs:comment="The most general class/">
>
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
> rdfs:label="type"
> rdfs:comment="Indicates membership of a class">
> <rdfs:range rdf:resource="#Class"/>
1973,1976c2138,2141
< rdfs:comment="Use this for descriptions"
< rdfs:label="comment">
< <rdfs:domain resource="#Resource"/>
< <rdfs:range resource="#Literal"/>
---
> rdfs:comment="Use this for descriptions"
> rdfs:label="comment">
> <rdfs:domain rdf:resource="#Resource"/>
> <rdfs:range rdf:resource="#Literal"/>
1980,1981c2145,2146
< rdfs:Label="label"
< rdfs:comment="Provides a human-readable version of a resource name">
---
> rdfs:Label="label"
> rdfs:comment="Provides a human-readable version of a resource name">
1987,1988c2152,2153
< rdfs:label="Class"
< rdfs:comment="The concept of Class">
---
> rdfs:label="Class"
> rdfs:comment="The concept of Class">
1993,1994c2158,2159
< rdfs:label="subClassOf"
< rdfs:comment="Indicates membership of a class">
---
> rdfs:label="subClassOf"
> rdfs:comment="Indicates membership of a class">
2000,2003c2165,2183
< rdfs:label="subPropertyOf"
< rdfs:comment="Indicates specialization of properties">
< <rdfs:range rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> rdfs:label="subPropertyOf"
> rdfs:comment="Indicates specialization of properties">
> <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> </rdf:Property>
>
> <rdf:Property ID="seeAlso"
> rdfs:label="seeAlso"
> rdfs:comment="Indicates a resource that provides information about the subject resource">
> <rdfs:range rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> <rdfs:domain rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> </rdf:Property>
>
> <rdf:Property ID="isDefinedBy"
> rdfs:label="isDefinedBy"
> rdfs:comment="Indicates a resource containing and defining the subject resource.">
> <rdfs:subPropertyOf rdf:resource="#seeAlso"/>
> <rdfs:range rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> <rdfs:domain rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
2007c2187
< rdfs:label="ConstraintResource"
---
> rdfs:label="ConstraintResource"
2013,2015c2193,2195
< rdfs:label="ConstraintProperty"
< rdfs:comment="Properties used to express RDF Schema constraints.">
< <rdfs:subClassOf rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> rdfs:label="ConstraintProperty"
> rdfs:comment="Properties used to express RDF Schema constraints.">
> <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2020,2021c2200,2201
< rdfs:label="domain"
< rdfs:comment="This is how we associate a class with properties that its instances can have">
---
> rdfs:label="domain"
> rdfs:comment="This is how we associate a class with properties that its instances can have">
2023c2203
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2027c2207
< rdfs:label="range"
---
> rdfs:label="range"
2031c2211
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2035,2036c2215,2216
< rdfs:label="Property"
< rdfs:comment="The concept of a property.">
---
> rdfs:label="Property"
> rdfs:comment="The concept of a property.">
2043c2223
< <rdfs:subClassOf resource="#Resource"/>
---
> <rdfs:subClassOf rdf:resource="#Resource"/>
2046,2049c2226,2229
< <rdfs:Class about="http://www.w3.org/TR/WD-rdf-syntax#Statement"
< rdfs:labe="Statement"
< rdfs:comment="This represents the set of reified statements.">
< <rdfs:subClassOf resource="#Resource"/>
---
> <rdfs:Class about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"
> rdfs:labe="Statement"
> rdfs:comment="This represents the set of reified statements.">
> <rdfs:subClassOf rdf:resource="#Resource"/>
2052,2054c2232,2234
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#subject"
< rdfs:label="subject">
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#subject"
> rdfs:label="subject">
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
2058,2061c2238,2241
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#predicate"
< rdfs:label="predicate">
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
< <rdfs:range rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate"
> rdfs:label="predicate">
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
> <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2064,2066c2244,2246
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#object"
< rdfs:label="object">
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#object"
> rdfs:label="object">
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
2072c2252
< <rdfs:subClassOf resource="#Resource"/>
---
> <rdfs:subClassOf rdf:resource="#Resource"/>
2075,2077c2255,2257
< <rdfs:Class about="http://www.w3.org/TR/WD-rdf-syntax#Bag"
< rdfs:label="Bag">
< <rdfs:subClassOf resource="#Container"/>
---
> <rdfs:Class about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag"
> rdfs:label="Bag">
> <rdfs:subClassOf rdf:resource="#Container"/>
2080,2082c2260,2262
< <rdfs:Class about="http://www.w3.org/TR/WD-rdf-syntax#Seq"
< rdfs:label="Sequence">
< <rdfs:subClassOf resource="#Container"/>
---
> <rdfs:Class about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq"
> rdfs:label="Sequence">
> <rdfs:subClassOf rdf:resource="#Container"/>
2085,2087c2265,2267
< <rdfs:Class about="http://www.w3.org/TR/WD-rdf-syntax#Alt"
< rdfs:label="Alt">
< <rdfs:subClassOf resource="#Container"/>
---
> <rdfs:Class about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Alt"
> rdfs:label="Alt">
> <rdfs:subClassOf rdf:resource="#Container"/>
2091,2092c2271,2272
< comment="This is the class that the properties _1,_2, ... that are used to represent lists and are an instance of">
< <rdfs:subClassOf resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> comment="This is the class that the properties _1,_2, ... that are used to represent lists and are an instance of">
> <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2095c2275
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#value"
---
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#value"
2106,2107c2286,2287
< xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs="http://www.w3.org/TR/WD-rdf-schema#">
---
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#">
2109,2116c2289,2296
< <rdfs:Class rdf:ID="Resource"
< rdfs:label="Resource"
< rdfs:comment="The most general class"/>
<
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#type"
< rdfs:label="type"
< rdfs:comment="Indicates membership of a class">
< <rdfs:range resource="#Class"/>
---
> <rdfs:Class rdf:ID="Resource"
> rdfs:label="Resource"
> rdfs:comment="The most general class"/>
>
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
> rdfs:label="type"
> rdfs:comment="Indicates membership of a class">
> <rdfs:range rdf:resource="#Class"/>
2120,2123c2300,2303
< rdfs:comment="Use this for descriptions"
< rdfs:label="comment">
< <rdfs:domain resource="#Resource"/>
< <rdfs:range resource="#Literal"/>
---
> rdfs:comment="Use this for descriptions"
> rdfs:label="comment">
> <rdfs:domain rdf:resource="#Resource"/>
> <rdfs:range rdf:resource="#Literal"/>
2127,2128c2307,2308
< rdfs:Label="label"
< rdfs:comment="Provides a human-readable version of a resource name">
---
> rdfs:Label="label"
> rdfs:comment="Provides a human-readable version of a resource name">
2134,2135c2314,2315
< rdfs:label="Class"
< rdfs:comment="The concept of Class">
---
> rdfs:label="Class"
> rdfs:comment="The concept of Class">
2140,2141c2320,2321
< rdfs:label="subClassOf"
< rdfs:comment="Indicates membership of a class">
---
> rdfs:label="subClassOf"
> rdfs:comment="Indicates membership of a class">
2147,2150c2327,2330
< rdfs:label="subPropertyOf"
< rdfs:comment="Indicates specialization of properties">
< <rdfs:range rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> rdfs:label="subPropertyOf"
> rdfs:comment="Indicates specialization of properties">
> <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2152a2333,2347
> <rdf:Property ID="seeAlso"
> rdfs:label="seeAlso"
> rdfs:comment="Indicates a resource that provides information about the subject resource">
> <rdfs:range rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> <rdfs:domain rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> </rdf:Property>
>
> <rdf:Property ID="isDefinedBy"
> rdfs:label="isDefinedBy"
> rdfs:comment="Indicates a resource containing and defining the subject resource.">
> <rdfs:subPropertyOf rdf:resource="#seeAlso"/>
> <rdfs:range rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> <rdfs:domain rdf:resource="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#Resource"/>
> </rdf:Property>
>
2154c2349
< rdfs:label="ConstraintResource"
---
> rdfs:label="ConstraintResource"
2160,2162c2355,2357
< rdfs:label="ConstraintProperty"
< rdfs:comment="Properties used to express RDF Schema constraints.">
< <rdfs:subClassOf rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> rdfs:label="ConstraintProperty"
> rdfs:comment="Properties used to express RDF Schema constraints.">
> <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2167,2168c2362,2363
< rdfs:label="domain"
< rdfs:comment="This is how we associate a class with properties that its instances can have">
---
> rdfs:label="domain"
> rdfs:comment="This is how we associate a class with properties that its instances can have">
2170c2365
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2174c2369
< rdfs:label="range"
---
> rdfs:label="range"
2178c2373
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2182,2183c2377,2378
< rdfs:label="Property"
< rdfs:comment="The concept of a property.">
---
> rdfs:label="Property"
> rdfs:comment="The concept of a property.">
2190c2385
< <rdfs:subClassOf resource="#Resource"/>
---
> <rdfs:subClassOf rdf:resource="#Resource"/>
2193,2196c2388,2391
< <rdfs:Class about="http://www.w3.org/TR/WD-rdf-syntax#Statement"
< rdfs:label="Statement"
< rdfs:comment="This represents the set of reified statements.">
< <rdfs:subClassOf resource="#Resource"/>
---
> <rdfs:Class about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"
> rdfs:label="Statement"
> rdfs:comment="This represents the set of reified statements.">
> <rdfs:subClassOf rdf:resource="#Resource"/>
2199,2201c2394,2396
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#subject"
< rdfs:label="subject">
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#subject"
> rdfs:label="subject">
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
2205,2208c2400,2403
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#predicate"
< rdfs:label="predicate">
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
< <rdfs:range rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#predicate"
> rdfs:label="predicate">
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
> <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2211,2213c2406,2408
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#object"
< rdfs:label="object">
< <rdfs:domain rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Statement"/>
---
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#object"
> rdfs:label="object">
> <rdfs:domain rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Statement"/>
2219c2414
< <rdfs:subClassOf resource="#Resource"/>
---
> <rdfs:subClassOf rdf:resource="#Resource"/>
2222,2224c2417,2419
< <rdfs:Class about="http://www.w3.org/TR/WD-rdf-syntax#Bag"
< rdfs:label="Bag">
< <rdfs:subClassOf resource="#Container"/>
---
> <rdfs:Class about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag"
> rdfs:label="Bag">
> <rdfs:subClassOf rdf:resource="#Container"/>
2227,2229c2422,2424
< <rdfs:Class about="http://www.w3.org/TR/WD-rdf-syntax#Seq"
< rdfs:label="Sequence">
< <rdfs:subClassOf resource="#Container"/>
---
> <rdfs:Class about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Seq"
> rdfs:label="Sequence">
> <rdfs:subClassOf rdf:resource="#Container"/>
2232,2234c2427,2429
< <rdfs:Class about="http://www.w3.org/TR/WD-rdf-syntax#Alt"
< rdfs:label="Alt">
< <rdfs:subClassOf resource="#Container"/>
---
> <rdfs:Class about="http://www.w3.org/1999/02/22-rdf-syntax-ns#Alt"
> rdfs:label="Alt">
> <rdfs:subClassOf rdf:resource="#Container"/>
2238,2239c2433,2434
< comment="This is the class that the properties _1,_2, ... that are used to represent lists and are an instance of">
< <rdfs:subClassOf resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
---
> comment="This is the class that the properties _1,_2, ... that are used to represent lists and are an instance of">
> <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
2242c2437
< <rdf:Property about="http://www.w3.org/TR/WD-rdf-syntax#value"
---
> <rdf:Property about="http://www.w3.org/1999/02/22-rdf-syntax-ns#value"
2260c2455
< <a href="http://purl.org/metadata/dublin_core">Dublin Core Initiative</a>.
---
> <a href="http://purl.org/dc/">Dublin Core Initiative</a>.
2276,2439d2470
< <rdf:RDF
< xmlns:rdf="http://www.w3.org/TR/WD-rdf-syntax#"
< xmlns:rdfs="http://www.w3.org/TR/WD-rdf-schema#">
<
< <rdf:Description ID="Title">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Title</rdfs:label>
< <rdfs:comment>The name given to the resource, usually by the Creator
< or Publisher.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Creator">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Author/Creator</rdfs:label>
< <rdfs:comment>The person or organization primarily responsible for
< creating the intellectual content of the resource. For example,
< authors in the case of written documents, artists, photographers, or
< illustrators in the case of visual resources.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Subject">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Subject</rdfs:label>
< <rdfs:comment>The topic of the resource. Typically, subject will be
< expressed as keywords or phrases that describe the subject or
< content of the resource. The use of controlled vocabularies and
< formal classification schemes is encouraged.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Description">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Description</rdfs:label>
< <rdfs:comment> A textual description of the content of the resource,
< including abstracts in the case of document-like objects or content
< descriptions in the case of visual resources.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Publisher">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Publisher</rdfs:label>
< <rdfs:comment>The entity responsible for making the resource
< available in its present form, such as a publishing house, a
< university department, or a corporate entity.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Contributor">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Other Contributors</rdfs:label>
< <rdfs:comment>A person or organization not specified in a Creator
< element who has made significant intellectual contributions to the
< resource but whose contribution is secondary to any person or
< organization specified in a Creator element (for example, editor,
< transcriber, and illustrator).</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Date">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Date</rdfs:label>
< <rdfs:comment>A date associated with the creation or availability of
< the resource. Such a date is not to be confused with one belonging
< in the Coverage element, which would be associated with the resource
< only insofar as the intellectual content is somehow about that
< date. Recommended best practice is defined in a profile of ISO 8601
< [Date and Time Formats (based on ISO8601), W3C Technical Note,
< http://www.w3.org/TR/NOTE-datetime] that includes (among others)
< dates of the forms YYYY and YYYY-MM-DD. In this scheme, for example,
< the date 1994-11-05 corresponds to November 5, 1994.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Type">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Type</rdfs:label>
< <rdfs:comment>The category of the resource, such as home page,
< novel, poem, working paper, technical report, essay, dictionary. For
< the sake of interoperability, Type should be selected from an
< enumerated list that is currently under development in the workshop
< series.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Format">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Format</rdfs:label>
< <rdfs:comment>The data format of the resource, used to identify the
< software and possibly hardware that might be needed to display or
< operate the resource. For the sake of interoperability, Format
< should be selected from an enumerated list that is currently under
< development in the workshop series.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Identifier">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Identifier</rdfs:label>
< <rdfs:comment>A string or number used to uniquely identify the
< resource. Examples for networked resources include URLs and URNs
< (when implemented). Other globally-unique identifiers, such as
< International Standard Book Numbers (ISBN) or other formal names are
< also candidates for this element.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Source">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Source</rdfs:label>
< <rdfs:comment>Information about a second resource from which the
< present resource is derived. While it is generally recommended that
< elements contain information about the present resource only, this
< element may contain a date, creator, format, identifier, or other
< metadata for the second resource when it is considered important for
< discovery of the present resource; recommended best practice is to
< use the Relation element instead. For example, it is possible to
< use a Source date of 1603 in a description of a 1996 film adaptation
< of a Shakespearean play, but it is preferred instead to use Relation
< "IsBasedOn" with a reference to a separate resource whose
< description contains a Date of 1603. Source is not applicable if the
< present resource is in its original form.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Language">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Language</rdfs:label>
< <rdfs:comment>The language of the intellectual content of the
< resource. Where practical, the content of this field should coincide
< with RFC 1766 [Tags for the Identification of Languages,
< http://ds.internic.net/rfc/rfc1766.txt ]; examples include en, de,
< es, fi, fr, ja, th, and zh.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Relation">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Relation</rdfs:label>
< <rdfs:comment>An identifier of a second resource and its
< relationship to the present resource. This element permits links
< between related resources and resource descriptions to be
< indicated. Examples include an edition of a work (IsVersionOf), a
< translation of a work (IsBasedOn), a chapter of a book (IsPartOf),
< and a mechanical transformation of a dataset into an image
< (IsFormatOf). For the sake of interoperability, relationships should
< be selected from an enumerated list that is currently under
< development in the workshop series.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Coverage">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Coverage</rdfs:label>
< <rdfs:comment>The spatial or temporal characteristics of the
< intellectual content of the resource. Spatial coverage refers to a
< physical region (e.g., celestial sector); use coordinates (e.g.,
< longitude and latitude) or place names that are from a controlled
< list or are fully spelled out. Temporal coverage refers to what the
< resource is about rather than when it was created or made available
< (the latter belonging in the Date element); use the same date/time
< format (often a range) [Date and Time Formats (based on ISO8601),
< W3C Technical Note, http://www.w3.org/TR/NOTE-datetime] as
< recommended for the Date element or time periods that are from a
< controlled list or are fully spelled out.</rdfs:comment>
< </rdf:Description>
<
< <rdf:Description ID="Rights">
< <rdf:type rdf:resource="http://www.w3.org/TR/WD-rdf-syntax#Property"/>
< <rdfs:label>Rights</rdfs:label>
< <rdfs:comment>A rights management statement, an identifier that
< links to a rights management statement, or an identifier that links
< to a service providing information about rights management for the
< resource.</rdfs:comment>
< </rdf:Description>
2441c2472,2662
< </rdf:RDF>
---
> <?xml version='1.0'?>
> <rdf:RDF
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdfs="http://www.w3.org/TR/1999/PR-rdf-schema-19990303#"
> xmlns:dc="">
>
> <rdf:Description about = "">
> <dc:Title> The Dublin Core Element Set </dc:Title>
> <dc:Creator> The Dublin Core Metadata Inititative </dc:Creator>
> <dc:Description> The Dublin Core is a simple metadata element
> set intended to facilitate discovery of electronic
> resources. </dc:Description>
> <dc:Date> 1995-03-01 </dc:Date>
> </rdf:Description>
>
> <rdf:Description ID="Title">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Title</rdfs:label>
> <rdfs:comment>The name given to the resource, usually by the Creator
> or Publisher.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Creator">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Author/Creator</rdfs:label>
> <rdfs:comment>The person or organization primarily responsible for
> creating the intellectual content of the resource. For example,
> authors in the case of written documents, artists, photographers, or
> illustrators in the case of visual resources.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Subject">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Subject</rdfs:label>
> <rdfs:comment>The topic of the resource. Typically, subject will be
> expressed as keywords or phrases that describe the subject or
> content of the resource. The use of controlled vocabularies and
> formal classification schemes is encouraged.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Description">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Description</rdfs:label>
> <rdfs:comment> A textual description of the content of the resource,
> including abstracts in the case of document-like objects or content
> descriptions in the case of visual resources.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Publisher">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Publisher</rdfs:label>
> <rdfs:comment>The entity responsible for making the resource
> available in its present form, such as a publishing house, a
> university department, or a corporate entity.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Contributor">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Other Contributors</rdfs:label>
> <rdfs:comment>A person or organization not specified in a Creator
> element who has made significant intellectual contributions to the
> resource but whose contribution is secondary to any person or
> organization specified in a Creator element (for example, editor,
> transcriber, and illustrator).</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Date">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Date</rdfs:label>
> <rdfs:comment>A date associated with the creation or availability of
> the resource. Such a date is not to be confused with one belonging
> in the Coverage element, which would be associated with the resource
> only insofar as the intellectual content is somehow about that
> date. Recommended best practice is defined in a profile of ISO 8601
> [Date and Time Formats (based on ISO8601), W3C Technical Note,
> http://www.w3.org/TR/NOTE-datetime] that includes (among others)
> dates of the forms YYYY and YYYY-MM-DD. In this scheme, for example,
> the date 1994-11-05 corresponds to November 5, 1994.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Type">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Type</rdfs:label>
> <rdfs:comment>The category of the resource, such as home page,
> novel, poem, working paper, technical report, essay, dictionary. For
> the sake of interoperability, Type should be selected from an
> enumerated list that is currently under development in the workshop
> series.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Format">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Format</rdfs:label>
> <rdfs:comment>The data format of the resource, used to identify the
> software and possibly hardware that might be needed to display or
> operate the resource. For the sake of interoperability, Format
> should be selected from an enumerated list that is currently under
> development in the workshop series.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Identifier">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Identifier</rdfs:label>
> <rdfs:comment>A string or number used to uniquely identify the
> resource. Examples for networked resources include URLs and URNs
> (when implemented). Other globally-unique identifiers, such as
> International Standard Book Numbers (ISBN) or other formal names are
> also candidates for this element.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Source">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Source</rdfs:label>
> <rdfs:comment>Information about a second resource from which the
> present resource is derived. While it is generally recommended that
> elements contain information about the present resource only, this
> element may contain a date, creator, format, identifier, or other
> metadata for the second resource when it is considered important for
> discovery of the present resource; recommended best practice is to
> use the Relation element instead. For example, it is possible to
> use a Source date of 1603 in a description of a 1996 film adaptation
> of a Shakespearean play, but it is preferred instead to use Relation
> "IsBasedOn" with a reference to a separate resource whose
> description contains a Date of 1603. Source is not applicable if the
> present resource is in its original form.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Language">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Language</rdfs:label>
> <rdfs:comment>The language of the intellectual content of the
> resource. Where practical, the content of this field should coincide
> with RFC 1766 [Tags for the Identification of Languages,
> http://ds.internic.net/rfc/rfc1766.txt ]; examples include en, de,
> es, fi, fr, ja, th, and zh.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Relation">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Relation</rdfs:label>
> <rdfs:comment>An identifier of a second resource and its
> relationship to the present resource. This element permits links
> between related resources and resource descriptions to be
> indicated. Examples include an edition of a work (IsVersionOf), a
> translation of a work (IsBasedOn), a chapter of a book (IsPartOf),
> and a mechanical transformation of a dataset into an image
> (IsFormatOf). For the sake of interoperability, relationships should
> be selected from an enumerated list that is currently under
> development in the workshop series.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Coverage">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Coverage</rdfs:label>
> <rdfs:comment>The spatial or temporal characteristics of the
> intellectual content of the resource. Spatial coverage refers to a
> physical region (e.g., celestial sector); use coordinates (e.g.,
> longitude and latitude) or place names that are from a controlled
> list or are fully spelled out. Temporal coverage refers to what the
> resource is about rather than when it was created or made available
> (the latter belonging in the Date element); use the same date/time
> format (often a range) [Date and Time Formats (based on ISO8601),
> W3C Technical Note, http://www.w3.org/TR/NOTE-datetime] as
> recommended for the Date element or time periods that are from a
> controlled list or are fully spelled out.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
>
> <rdf:Description ID="Rights">
> <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
> <rdfs:label>Rights</rdfs:label>
> <rdfs:comment>A rights management statement, an identifier that
> links to a rights management statement, or an identifier that links
> to a service providing information about rights management for the
> resource.</rdfs:comment>
> <rdfs:isDefinedBy rdf:resource = ""/>
> </rdf:Description>
> </rdf:RDF>
2458d2678
<
2461c2681,2682
< <A HREF="http://www.w3.org/TR/WD-rdf-syntax/">http://www.w3.org/TR/WD-rdf-syntax/</A></DD>
---
> <A HREF="http://www.w3.org/TR/REC-rdf-syntax/">http://www.w3.org/TR/REC-rdf-syntax/</A></DD>
> </DL>
2462a2684
> <DL>
2515c2737
< <A HREF="http://www.rational.com/uml/resources.html">http://www.rational.com/uml/resources.html</A></DD>
---
> <A HREF="http://www.rational.com/uml/resources">http://www.rational.com/uml/resources</A></DD>
2535,2635d2756
< <H2><A NAME="openissues"></A>Appendix D: Open Issues</H2>
< The following issues are currently under consideration by the RDF Schema
< working group.
<
< <BR />
<
< <A NAME="c1"></A>
<
< <BR />
<
< <H3>C.21. Interactions with External Type Systems</H3>
< <P>
< The RDF Schema mechanism defines a basic type system. It was not developed
< to provide every imaginable capability. Instead, in the interests of simplicity
< and performance, it will be only as expressive as needed to meet the
< requirements of PICS.
< </P>
<
< <P>The RDF Schema mechanism will need to interact with many externally
< developed typing systems. There are two broad categories of such systems.
< The first are externally defined "primitive data types", such as IEEE floating
< point numbers, Integers, Boolean values, Dates and Times, etc. The second
< category are external "type systems", which provide features such as
< inheritance, type inferencing, etc.</P>
<
< <P>
< Several factors make it difficult to decide on the appropriate interactions
< with the first category. RDF models are exchanged as XML document instances.
< The XML Schema Working group will be addressing the problem of data
< typing in XML, to provide the ability to specify that element content
< should be interpreted as an integer, a date, a float, left as a string,
< etc. The interactions between data typing efforts in XML and RDF is currently
< being discussed by the W3C staff, so this document does not provide a
< specification for those interactions that is as detailed as the specification
< for elements such as rdfs:Class, rdfs:subClassOf, etc.
< </P>
<
< <P>However, it is the rough consensus of the RDF Schema WG that it would
< be useful to show that the current schema system can actually accommodate
< externally defined primitive data types. Therefore, figure 1, and the relevant
< portion of the text of the specification, was modified to give a provisional
< indication of how external types might be handled.
< </P>
<
<
< <HR />
< <H2><A NAME="changes"></A>Appendix E: Changes</H2>
<
< <P>The <A HREF="http://www.w3.org/TR/1998/WD-rdf-schema-19980814/">previous
< public version</A> of this specification was published on 1998-08-14.
< The most significant changes since that date are listed below.
< </P>
<
< <H3>subPropertyOf</H3>
<
< A concept similar to <code>subClassOf</code> has been introduced, to enable
< machine-readable statements to be made asserting that one property is a
< specialisation (or 'sub-property') of another.
<
< <H3>ConstraintResource</H3>
<
< A super-class of <code>ConstraintProperty</code> has been added.
<
< <H3>Extensibility Mechanisms</H3>
<
< An <A HREF="#extensibility">extensibility</A> section has been added, discussing the
< use of <code>subClassOf</code> and <code>subPropertyOf</code> for vocabulary evolution,
< and the use of <code>ConstraintResource</code> as a futureproofing mechanism that will
< allow for new forms of schema consistency checking to be introduced at a
< later date.
<
< <H3>PICS</H3>
<
< A prototype PICS/RDF Schema has been included as an example for discussion.
<
< <H3>Examples</H3>
<
< Additional examples have been included in the specification, and integrated with the main
< body of the document.
<
<
< <H3>Scope</H3>
<
< Previous versions of this specification included a longer list of open
< issues under consideration by the RDF Schema Working Group.
< In order to keep the scope and complexity manageable, the Working Group
< confined its focus to developing a minimal set of foundational concepts
< which can be extended later. As a result, we ruled out of scope some
< primitives many schema designers may come to expect and be accustomed to.
< A number of these were previously listed as Open Issues.
< A partial list of such features which have been deferred to future
< activities are:
<
< <UL>
< <LI>Specifying cardinality constraints for properties</LI>
< <LI>Specifying default values for properties</LI>
< <LI>Specifying rules for overriding default values</LI>
< <LI>Class-centric schema specification</LI>
< <LI>Class-specific constraints</LI>
< </UL>
< <HR />
2637c2758
< $Date: 1999/03/02 23:57:48 $
---
> $Date: 1999/03/02 23:57:48 $
2642d2762
<