4 RDF Schema declaration for the Dublin Core Element Set 1.1
6 comments, etc. to webteam <dcmi-feedback@dublincore.org>
9 <!-- HELM: OLD URL OF SCHEMAS: VRP gives errors -->
10 <!--<!DOCTYPE rdf:RDF [
11 <!ENTITY rdfns 'http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
12 <!ENTITY rdfsns 'http://www.w3.org/2000/01/rdf-schema#'>
13 <!ENTITY dcns 'http://purl.org/dc/elements/1.1/'>
14 <!ENTITY eorns 'http://dublincore.org/2000/03/13/eor#'>
18 <!ENTITY rdfns 'http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
19 <!ENTITY rdfsns 'http://www.w3.org/2000/01/rdf-schema#'>
20 <!ENTITY dcns 'http://www.cs.unibo.it/~schena/dces#'>
21 <!ENTITY eorns 'http://www.cs.unibo.it/~schena/eor#'>
24 <rdf:RDF xmlns:rdf="&rdfns;"
30 <!-- Description of Schema -->
32 <eor:Schema rdf:about="&dcns;">
33 <rdf:value>The Dublin Core Element Set v1.1</rdf:value>
34 <dc:title>The Dublin Core Element Set v1.1</dc:title>
35 <dc:publisher>The Dublin Core Metadata Initiative</dc:publisher>
36 <dc:description>The Dublin Core metadata vocabulary is a simple vocabulary
37 intended to facilitate discovery of resources. </dc:description>
38 <dc:language>English</dc:language>
39 <dc:relation rdf:resource="http://dublincore.org/documents/dces/"/>
40 <dc:date>2000-07-02</dc:date>
43 <!-- HELM: every declaration has the rdf:ID = "name" instead of
44 rdf:about = "&dctypens;name" -->
46 <!-- Begin: Title Declaration -->
48 <rdf:Property rdf:ID = "title">
49 <rdfs:label>Title</rdfs:label>
50 <rdfs:comment>A name given to the resource.</rdfs:comment>
51 <eor:comment>Typically, a Title will be a name by which the resource
52 is formally known.</eor:comment>
53 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
56 <rdf:Property rdf:ID = "contributor">
57 <rdfs:label>Contributor</rdfs:label>
58 <rdfs:comment>An entity responsible for making contributions to the
59 content of the resource.</rdfs:comment>
60 <eor:comment>Examples of a Contributor include a person, an
61 organisation, or a service. Typically, the name of a Contributor
62 should be used to indicate the entity.</eor:comment>
63 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
66 <rdf:Property rdf:ID = "creator">
67 <rdfs:label>Author/Creator</rdfs:label>
68 <rdfs:comment>An entity primarily responsible for making the content
69 of the resource.</rdfs:comment>
70 <eor:comment> Examples of a Creator include a person, an
71 organisation, or a service. Typically, the name of a Creator should
72 be used to indicate the entity.</eor:comment>
73 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
76 <rdf:Property rdf:ID = "publisher">
77 <rdfs:label>Publisher</rdfs:label>
78 <rdfs:comment>An entity responsible for making the resource
79 available.</rdfs:comment>
80 <eor:comment> Examples of a Publisher include a person, an
81 organisation, or a service. Typically, the name of a Publisher
82 should be used to indicate the entity.</eor:comment>
83 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
86 <rdf:Property rdf:ID = "subject">
87 <rdfs:label>Subject</rdfs:label>
88 <rdfs:comment>The topic of the content of the resource.</rdfs:comment>
89 <eor:comment> Typically, a Subject will be expressed as keywords,
90 key phrases or classification codes that describe a topic of the
91 resource. Recommended best practice is to select a value from a
92 controlled vocabulary or formal classification scheme.</eor:comment>
93 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
96 <rdf:Property rdf:ID = "description">
97 <rdfs:label>Description</rdfs:label>
98 <rdfs:comment>An account of the content of the resource.</rdfs:comment>
99 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
102 <rdf:Property rdf:ID = "date">
103 <rdfs:label>Date</rdfs:label>
104 <rdfs:comment>A date associated with an event in the life cycle of
105 the resource.</rdfs:comment>
106 <eor:comment>Typically, Date will be associated with the creation or
107 availability of the resource. Recommended best practice for
108 encoding the date value is defined in a profile of ISO 8601 [W3CDTF]
109 and follows the YYYY-MM-DD format.</eor:comment>
110 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
113 <rdf:Property rdf:ID = "type">
114 <rdfs:label>Resource Type</rdfs:label>
115 <rdfs:comment>The nature or genre of the content of the
116 resource.</rdfs:comment>
117 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
120 <rdf:Property rdf:ID = "format">
121 <rdfs:label>Format</rdfs:label>
122 <rdfs:comment>The physical or digital manifestation of the
123 resource.</rdfs:comment>
124 <eor:comment> Typically, Format may include the media-type or
125 dimensions of the resource. Format may be used to determine the
126 software, hardware or other equipment needed to display or operate
127 the resource. Examples of dimensions include size and duration.
128 Recommended best practice is to select a value from a controlled
129 vocabulary (for example, the list of Internet Media Types [MIME]
130 defining computer media formats).</eor:comment>
131 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
134 <rdf:Property rdf:ID = "identifier">
135 <rdfs:label>Resource Identifier</rdfs:label>
136 <rdfs:comment>An unambiguous reference to the resource within a
137 given context.</rdfs:comment>
138 <eor:comment>Recommended best practice is to identify the resource
139 by means of a string or number conforming to a formal identification
140 system. Example formal identification systems include the Uniform
141 Resource Identifier (URI) (including the Uniform Resource Locator
142 (URL)), the Digital Object Identifier (DOI) and the International
143 Standard Book Number (ISBN).</eor:comment>
144 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
147 <rdf:Property rdf:ID = "language">
148 <rdfs:label>Language</rdfs:label>
149 <rdfs:comment> A language of the intellectual content of the
150 resource.</rdfs:comment>
151 <eor:comment> Recommended best practice for the values of the
152 Language element is defined by RFC 1766 [RFC1766] which includes a
153 two-letter Language Code (taken from the ISO 639 standard [ISO639]),
154 followed optionally, by a two-letter Country Code (taken from the
155 ISO 3166 standard [ISO3166]). For example, 'en' for English, 'fr'
156 for French, or 'en-uk' for English used in the United
157 Kingdom.</eor:comment>
158 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
161 <rdf:Property rdf:ID = "relation">
162 <rdfs:label>Relation</rdfs:label>
163 <rdfs:comment> A reference to a related resource.</rdfs:comment>
164 <eor:comment> Recommended best practice is to reference the resource
165 by means of a string or number conforming to a formal identification
166 system.</eor:comment>
167 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
170 <rdf:Property rdf:ID = "source">
171 <rdfs:label>Source</rdfs:label>
172 <rdfs:comment>A Reference to a resource from which the present
173 resource is derived.</rdfs:comment>
174 <eor:comment> The present resource may be derived from the Source
175 resource in whole or in part. Recommended best practice is to
176 reference the resource by means of a string or number conforming to
177 a formal identification system.</eor:comment>
178 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
181 <rdf:Property rdf:ID = "coverage">
182 <rdfs:label>Coverage</rdfs:label>
183 <rdfs:comment> The extent or scope of the content of the
184 resource.</rdfs:comment>
185 <eor:comment>Coverage will typically include spatial location (a
186 place name or geographic coordinates), temporal period (a period
187 label, date, or date range) or jurisdiction (such as a named
188 administrative entity). Recommended best practice is to select a
189 value from a controlled vocabulary (for example, the Thesaurus of
190 Geographic Names [TGN]) and that, where appropriate, named places or
191 time periods be used in preference to numeric identifiers such as
192 sets of coordinates or date ranges.</eor:comment>
193 <rdfs:isDefinedBy rdf:resource = "&dcns;" />
196 <rdf:Property rdf:ID = "rights">
197 <rdfs:label>Rights</rdfs:label>
198 <rdfs:comment> Information about rights held in and over the
199 resource.</rdfs:comment>
200 <eor:comment> Typically, a Rights element will contain a rights
201 management statement for the resource, or reference a service
202 providing such information. Rights information often encompasses
203 Intellectual Property Rights (IPR), Copyright, and various Property
204 Rights. If the Rights element is absent, no assumptions can be made
205 about the status of these and other rights with respect to the
206 resource.</eor:comment>
207 <rdfs:isDefinedBy rdf:resource = "&dcns;" />