This file is indexed.

/usr/share/Yap/semweb/dc.rdfs is in yap 6.2.2-2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
<?xml version="1.0"?>

<!-- 
  RDF Schema declaration for the Dublin Core Element Set 1.1
  2001/08/14
  comments, etc. to webteam <dcmi-feedback@dublincore.org>
-->

<!DOCTYPE rdf:RDF [
        <!ENTITY rdfns 'http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
        <!ENTITY rdfsns 'http://www.w3.org/2000/01/rdf-schema#'>
        <!ENTITY dcns 'http://purl.org/dc/elements/1.1/'>
        <!ENTITY eorns 'http://dublincore.org/2000/03/13/eor#'>
   ]>

<rdf:RDF xmlns:rdf="&rdfns;"
         xmlns:rdfs="&rdfsns;"
         xmlns:dc="&dcns;"
         xmlns:eor="&eorns;">

<!-- Description of Schema -->	

<eor:Schema rdf:about="&dcns;">
  <rdf:value>The Dublin Core Element Set v1.1</rdf:value>
  <dc:title>The Dublin Core Element Set v1.1</dc:title>
  <dc:publisher>The Dublin Core Metadata Initiative</dc:publisher>
  <dc:description>The Dublin Core metadata vocabulary is a simple vocabulary
      intended to facilitate discovery of resources. </dc:description>
  <dc:language>English</dc:language>
  <dc:relation rdf:resource="http://dublincore.org/documents/dces/"/>
  <dc:date>2000-07-02</dc:date>
</eor:Schema>

<!-- Begin: Title Declaration -->

<rdf:Property rdf:about = "&dcns;title">
  <rdfs:label>Title</rdfs:label>
  <rdfs:comment>A name given to the resource.</rdfs:comment>
  <eor:comment>Typically, a Title will be a name by which the resource
  is formally known.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;contributor">
  <rdfs:label>Contributor</rdfs:label>
  <rdfs:comment>An entity responsible for making contributions to the
  content of the resource.</rdfs:comment>
  <eor:comment>Examples of a Contributor include a person, an
  organisation, or a service.  Typically, the name of a Contributor
  should be used to indicate the entity.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>
 
<rdf:Property rdf:about = "&dcns;creator">
  <rdfs:label>Author/Creator</rdfs:label>
  <rdfs:comment>An entity primarily responsible for making the content
  of the resource.</rdfs:comment>
  <eor:comment> Examples of a Creator include a person, an
  organisation, or a service. Typically, the name of a Creator should
  be used to indicate the entity.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;publisher">
  <rdfs:label>Publisher</rdfs:label>
  <rdfs:comment>An entity responsible for making the resource
  available.</rdfs:comment>
  <eor:comment> Examples of a Publisher include a person, an
  organisation, or a service.  Typically, the name of a Publisher
  should be used to indicate the entity.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;subject">
  <rdfs:label>Subject</rdfs:label>
  <rdfs:comment>The topic of the content of the resource.</rdfs:comment>
  <eor:comment> Typically, a Subject will be expressed as keywords,
  key phrases or classification codes that describe a topic of the
  resource.  Recommended best practice is to select a value from a
  controlled vocabulary or formal classification scheme.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;description">
  <rdfs:label>Description</rdfs:label>
  <rdfs:comment>An account of the content of the resource.</rdfs:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;date">
  <rdfs:label>Date</rdfs:label>
  <rdfs:comment>A date associated with an event in the life cycle of
  the resource.</rdfs:comment>
  <eor:comment>Typically, Date will be associated with the creation or
  availability of the resource.  Recommended best practice for
  encoding the date value is defined in a profile of ISO 8601 [W3CDTF]
  and follows the YYYY-MM-DD format.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;type">
  <rdfs:label>Resource Type</rdfs:label>
  <rdfs:comment>The nature or genre of the content of the
  resource.</rdfs:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;format">
  <rdfs:label>Format</rdfs:label>
  <rdfs:comment>The physical or digital manifestation of the
  resource.</rdfs:comment>
  <eor:comment> Typically, Format may include the media-type or
  dimensions of the resource. Format may be used to determine the
  software, hardware or other equipment needed to display or operate
  the resource. Examples of dimensions include size and duration.
  Recommended best practice is to select a value from a controlled
  vocabulary (for example, the list of Internet Media Types [MIME]
  defining computer media formats).</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;identifier">
  <rdfs:label>Resource Identifier</rdfs:label>
  <rdfs:comment>An unambiguous reference to the resource within a
  given context.</rdfs:comment>
  <eor:comment>Recommended best practice is to identify the resource
  by means of a string or number conforming to a formal identification
  system.  Example formal identification systems include the Uniform
  Resource Identifier (URI) (including the Uniform Resource Locator
  (URL)), the Digital Object Identifier (DOI) and the International
  Standard Book Number (ISBN).</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;language">
  <rdfs:label>Language</rdfs:label>
  <rdfs:comment> A language of the intellectual content of the
  resource.</rdfs:comment>
  <eor:comment> Recommended best practice for the values of the
  Language element is defined by RFC 1766 [RFC1766] which includes a
  two-letter Language Code (taken from the ISO 639 standard [ISO639]),
  followed optionally, by a two-letter Country Code (taken from the
  ISO 3166 standard [ISO3166]).  For example, 'en' for English, 'fr'
  for French, or 'en-uk' for English used in the United
  Kingdom.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;relation">
  <rdfs:label>Relation</rdfs:label>
  <rdfs:comment> A reference to a related resource.</rdfs:comment>
  <eor:comment> Recommended best practice is to reference the resource
  by means of a string or number conforming to a formal identification
  system.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;source">
  <rdfs:label>Source</rdfs:label>
  <rdfs:comment>A Reference to a resource from which the present
  resource is derived.</rdfs:comment>
  <eor:comment> The present resource may be derived from the Source
  resource in whole or in part.  Recommended best practice is to
  reference the resource by means of a string or number conforming to
  a formal identification system.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;coverage">
  <rdfs:label>Coverage</rdfs:label>
  <rdfs:comment> The extent or scope of the content of the
  resource.</rdfs:comment>
  <eor:comment>Coverage will typically include spatial location (a
  place name or geographic coordinates), temporal period (a period
  label, date, or date range) or jurisdiction (such as a named
  administrative entity).  Recommended best practice is to select a
  value from a controlled vocabulary (for example, the Thesaurus of
  Geographic Names [TGN]) and that, where appropriate, named places or
  time periods be used in preference to numeric identifiers such as
  sets of coordinates or date ranges.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

<rdf:Property rdf:about = "&dcns;rights">
  <rdfs:label>Rights</rdfs:label>
  <rdfs:comment> Information about rights held in and over the
  resource.</rdfs:comment>
  <eor:comment> Typically, a Rights element will contain a rights
  management statement for the resource, or reference a service
  providing such information. Rights information often encompasses
  Intellectual Property Rights (IPR), Copyright, and various Property
  Rights.  If the Rights element is absent, no assumptions can be made
  about the status of these and other rights with respect to the
  resource.</eor:comment>
  <rdfs:isDefinedBy rdf:resource = "&dcns;" />
</rdf:Property>

</rdf:RDF>