rdf-vocab 0.0.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +17 -0
- data/Gemfile +4 -0
- data/LICENSE +201 -0
- data/README.md +4 -0
- data/Rakefile +1 -0
- data/lib/rdf-vocab.rb +5 -0
- data/lib/rdf-vocab/version.rb +5 -0
- data/lib/rdf-vocab/vocab/marc_relators.rb +544 -0
- data/lib/rdf-vocab/vocab/premis.rb +445 -0
- data/lib/rdf-vocab/vocab/preservation.rb +6 -0
- data/lib/rdf-vocab/vocab/preservation/event_type.rb +24 -0
- data/rdf-vocab.gemspec +24 -0
- metadata +98 -0
@@ -0,0 +1,445 @@
|
|
1
|
+
# This file generated automatically using vocab-loader
|
2
|
+
require 'rdf'
|
3
|
+
|
4
|
+
module RDF
|
5
|
+
class PREMIS < StrictVocabulary("http://www.loc.gov/premis/rdf/v1#")
|
6
|
+
|
7
|
+
# Class definitions
|
8
|
+
property :Agent, :comment =>
|
9
|
+
%(The Agent entity aggregates information about attributes or
|
10
|
+
characteristics of agents \(persons, organizations, or
|
11
|
+
software\) associated with rights management and preservation
|
12
|
+
events in the life of a data object. Agent information serves
|
13
|
+
to identify an agent unambiguously from all other Agent
|
14
|
+
entities.)
|
15
|
+
property :ApplicableDates
|
16
|
+
property :Bitstream
|
17
|
+
property :ContentLocation
|
18
|
+
property :CopyrightInformation
|
19
|
+
property :CreatingApplication
|
20
|
+
property :Dependency
|
21
|
+
property :Environment
|
22
|
+
property :Event, :comment =>
|
23
|
+
%(The Event entity aggregates information about an action that
|
24
|
+
involves one or more Object entities. Metadata about an Event
|
25
|
+
would normally be recorded and stored separately from the
|
26
|
+
digital object. Whether or not a preservation repository
|
27
|
+
records an Event depends upon the importance of the event.
|
28
|
+
Actions that modify objects should always be recorded. Other
|
29
|
+
actions such as copying an object for backup purposes may be
|
30
|
+
recorded in system logs or an audit trail but not necessarily
|
31
|
+
in an Event entity. Mandatory semantic units are:
|
32
|
+
eventIdentifier, eventType, and eventDateTime.)
|
33
|
+
property :EventOutcomeDetail
|
34
|
+
property :EventOutcomeInformation
|
35
|
+
property :File
|
36
|
+
property :Fixity
|
37
|
+
property :Format
|
38
|
+
property :FormatDesignation
|
39
|
+
property :FormatRegistry
|
40
|
+
property :Hardware
|
41
|
+
property :Identifier, :comment =>
|
42
|
+
%(This class is used in PREMIS OWL to describe identifiers if
|
43
|
+
the identifiers are not http URIs.)
|
44
|
+
property :Inhibitors
|
45
|
+
property :IntellectualEntity, :comment =>
|
46
|
+
%(Intellectual entities are described via Descriptive metadata
|
47
|
+
models. These are very domain-specific and are out of scope
|
48
|
+
for PREMIS. Examples: Dublin Core, Mets, MARC)
|
49
|
+
property :LicenseInformation
|
50
|
+
property :Object, :comment =>
|
51
|
+
%(The object class aggregates information about a digital object
|
52
|
+
held by a preservation repository and describes those
|
53
|
+
characteristics relevant to preservation management. The only
|
54
|
+
mandatory property is objectIdentifier. The object class has
|
55
|
+
three subclasses: Representation, File, and Bitstream.)
|
56
|
+
property :ObjectCharacteristics
|
57
|
+
property :PremisEntity
|
58
|
+
property :PreservationLevel
|
59
|
+
property :RelatedObjectIdentification
|
60
|
+
property :Representation
|
61
|
+
property :RightsDocumentation
|
62
|
+
property :RightsGranted
|
63
|
+
property :RightsStatement, :comment =>
|
64
|
+
%(Extensions: In OWL one can define its own subclasses to the
|
65
|
+
the RightsStatement class to denote OtherRightsInformation of
|
66
|
+
the PREMIS data dictionary.)
|
67
|
+
property :Signature
|
68
|
+
property :SignificantProperties
|
69
|
+
property :Software
|
70
|
+
property :StatuteInformation
|
71
|
+
property :Storage
|
72
|
+
property :TermOfGrant
|
73
|
+
property :TermOfRestriction
|
74
|
+
|
75
|
+
# Property definitions
|
76
|
+
property :hasAgentName, :comment =>
|
77
|
+
%(Examples: Erik Owens, Pc)
|
78
|
+
property :hasAgentNote
|
79
|
+
property :hasCompositionLevel, :comment =>
|
80
|
+
%(Examples: 0, 1, 2)
|
81
|
+
property :hasCompositionLevel, :comment =>
|
82
|
+
%(Data Constraints: Non-negative integers.)
|
83
|
+
property :hasContentLocationValue, :comment =>
|
84
|
+
%(Examples:
|
85
|
+
http://wwasearch.loc.gov/107th/200212107035/http://house.gov/langevin/
|
86
|
+
\(file\), c:\apache2\htdocs\index.html \(file\), 64 [offset
|
87
|
+
from start of file c:\apache2\htdocs\image\logo.gif]
|
88
|
+
\(bitstream\))
|
89
|
+
property :hasCopyrightJurisdiction, :comment =>
|
90
|
+
%(Examples: us, de, be)
|
91
|
+
property :hasCopyrightJurisdiction, :comment =>
|
92
|
+
%(Data Constraint: Values should be taken from ISO 3166.)
|
93
|
+
property :hasCopyrightStatusDeterminationDate, :comment =>
|
94
|
+
%(Example: 2001-10-26T19:32:52+00:00)
|
95
|
+
property :hasCopyrightStatusDeterminationDate, :comment =>
|
96
|
+
%(Data Constraint: To aid machine processing, value should use a
|
97
|
+
structured form: xsd:dateTime)
|
98
|
+
property :hasCreatingApplicationName, :comment =>
|
99
|
+
%(Example: MSWord)
|
100
|
+
property :hasCreatingApplicationVersion, :comment =>
|
101
|
+
%(Example: 2000)
|
102
|
+
property :hasDateCreatedByApplication, :comment =>
|
103
|
+
%(Example: 2001-10-26T19:32:52+00:00)
|
104
|
+
property :hasDateCreatedByApplication, :comment =>
|
105
|
+
%(Data Constraint: To aid machine processing, value should use a
|
106
|
+
structured form: xsd:dateTime)
|
107
|
+
property :hasDependencyName, :comment =>
|
108
|
+
%(Example: Additional Element Set for Language Corpora)
|
109
|
+
property :hasEndDate, :comment =>
|
110
|
+
%(Data Constraint: To aid machine processing, value should use a
|
111
|
+
structured form: xsd:dateTime)
|
112
|
+
property :hasEnvironmentNote, :comment =>
|
113
|
+
%(Example: This environment assumes that the PDF will be stored
|
114
|
+
locally and used with a standalone PDF reader.)
|
115
|
+
property :hasEventDateTime, :comment =>
|
116
|
+
%(Example: 2001-10-26T19:32:52+00:00)
|
117
|
+
property :hasEventDateTime, :comment =>
|
118
|
+
%(Data Constraint: To aid machine processing, value should use a
|
119
|
+
structured form: xsd:dateTime)
|
120
|
+
property :hasEventOutcome, :comment =>
|
121
|
+
%(Data Constraint: Value should be taken from a controlled
|
122
|
+
vocabulary.)
|
123
|
+
property :hasEventOutcomeDetailNote, :comment =>
|
124
|
+
%(Examples: LZW compressed file, Non-standard tags found in
|
125
|
+
header)
|
126
|
+
property :hasFormatName, :comment =>
|
127
|
+
%(Data Constraint: Value should be taken from a controlled
|
128
|
+
vocabulary.)
|
129
|
+
property :hasFormatName, :comment =>
|
130
|
+
%(Examples: Text/sgml, image/tiff/geotiff, Adobe PDF, DES, PGP,
|
131
|
+
base64, unknown, LaTex)
|
132
|
+
property :hasFormatNote, :comment =>
|
133
|
+
%(Examples: tentative identification, disjunction, multiple
|
134
|
+
format identifications found)
|
135
|
+
property :hasFormatRegistryKey, :comment =>
|
136
|
+
%(Examples: info:gdfr/fred/f/tiff, TIFF/6.0)
|
137
|
+
property :hasFormatRegistryName, :comment =>
|
138
|
+
%(Examples: PRONOM, www.nationalarchives.gov.uk/pronom,
|
139
|
+
Representation Information Registry Repository, FRED: A format
|
140
|
+
registry demonstration, release 0.07)
|
141
|
+
property :hasFormatVersion, :comment =>
|
142
|
+
%(Examples: 6.0, 2003)
|
143
|
+
property :hasHardwareName, :comment =>
|
144
|
+
%(Examples: Intel Pentium III, 1 GB DRAM, Windows XPcompatible
|
145
|
+
joystick)
|
146
|
+
property :hasHardwareOtherInformation, :comment =>
|
147
|
+
%(Examples: 32MB minimum, Required RAM for Apache is unknown)
|
148
|
+
property :hasIdentifierType, :comment =>
|
149
|
+
%(Data Constraint: Value should be taken from controlled
|
150
|
+
vocabulary.)
|
151
|
+
property :hasIdentifierType, :comment =>
|
152
|
+
%(Examples: DLC, DRS, hdl:4263537)
|
153
|
+
property :hasIdentifierValue, :comment =>
|
154
|
+
%(Examples: 0000000312 \(Representation\), IU2440 \(File\),
|
155
|
+
WAC1943.56 \(File\),
|
156
|
+
http://nrs.harvard.edu/urn-3:FHCL.Loeb:sal \(File\), IU2440-1
|
157
|
+
\(Bitstream\))
|
158
|
+
property :hasIdentifierValue, :comment =>
|
159
|
+
%(Defnition: The value of the Identifier.)
|
160
|
+
property :hasInhibitorKey, :comment =>
|
161
|
+
%(Example: [DES decryption key])
|
162
|
+
property :hasLicenseTerms
|
163
|
+
property :hasMessageDigest, :comment =>
|
164
|
+
%(Example:
|
165
|
+
7c9b35da4f2ebd436f1cf88e5a39b3a257edf4a22be3c955ac49da2e2107b67a1924419563)
|
166
|
+
property :hasMessageDigestOriginator, :comment =>
|
167
|
+
%(Examples: DRS, A0000978)
|
168
|
+
property :hasOriginalName, :comment =>
|
169
|
+
%(Example: N419.pdf)
|
170
|
+
property :hasPreservationLevelDateAssigned, :comment =>
|
171
|
+
%(Data Constraint: To aid machine processing, value should use a
|
172
|
+
structured form: xsd:dateTime)
|
173
|
+
property :hasPreservationLevelDateAssigned, :comment =>
|
174
|
+
%(Examples: 2001-10-26T19:32:52+00:00)
|
175
|
+
property :hasPreservationLevelRationale, :comment =>
|
176
|
+
%(Examples: user pays, legislation, defective file, bit-level
|
177
|
+
preservation only available for this format)
|
178
|
+
property :hasPreservationLevelValue, :comment =>
|
179
|
+
%(Examples: bit-level, full, fully supported with future
|
180
|
+
migrations \(File\), 0)
|
181
|
+
property :hasPreservationLevelValue, :comment =>
|
182
|
+
%(Data Constraint: Value should be taken from a controlled
|
183
|
+
vocabulary.)
|
184
|
+
property :hasRelatedObjectSequence
|
185
|
+
property :hasRestriction, :comment =>
|
186
|
+
%(Examples: No more than three, Allowed only after one year of
|
187
|
+
archival retention has elapsed, Rightsholder must be notified
|
188
|
+
after completion of act)
|
189
|
+
property :hasRightsGrantedNote
|
190
|
+
property :hasRightsStatementNote, :comment =>
|
191
|
+
%(Examples: Copyright expiration expected in 2010 unless
|
192
|
+
renewed. License is embedded in XMP block in file header.)
|
193
|
+
property :hasSignatureProperties
|
194
|
+
property :hasSignatureValidationRules
|
195
|
+
property :hasSignatureValue, :comment =>
|
196
|
+
%(Example:
|
197
|
+
juS5RhJ884qoFR8flVXd/rbrSDVGn40CapgB7qeQiT+rr0NekEQ6BHhUA8dT3+BCTBUQI0dBjlml9lwzENXvS83zRECjzXbMRTUtVZiPZG2pqKPnL2YU3A9645UCjTXU+jgFumv7k78hieAGDzNci+PQ9KRmm//icT7JaYztgt4=)
|
198
|
+
property :hasSignificantPropertiesType, :comment =>
|
199
|
+
%(Examples: content, structure, behavior, page count, page
|
200
|
+
width, typeface, hyperlinks \(representation\), image count
|
201
|
+
\(representation\), color space [for an embedded image]
|
202
|
+
\(bitstream\))
|
203
|
+
property :hasSignificantPropertiesValue, :comment =>
|
204
|
+
%(Examples: [For a Web page containing animation that is not
|
205
|
+
considered essential] Content only, [For detail associated
|
206
|
+
with a significantPropertiesType of "behavior"] Hyperlinks
|
207
|
+
traversable, [For a Word document with embedded links that are
|
208
|
+
not considered essential] Content only, [For detail associated
|
209
|
+
with significantPropertiesType of "behavior"] Editable, [For
|
210
|
+
detail associated with a significantPropertiesType of "page
|
211
|
+
width"] 210 mm, [For a PDF with an embedded graph, where the
|
212
|
+
lines' color determines the lines' meaning] Color, [For detail
|
213
|
+
associated with a significantPropertiesType of "appearance"]
|
214
|
+
Color)
|
215
|
+
property :hasSize, :comment =>
|
216
|
+
%(Example: 2038937)
|
217
|
+
property :hasSoftwareDependency, :comment =>
|
218
|
+
%(Example: GNU gcc >=2.7.2)
|
219
|
+
property :hasSoftwareName, :comment =>
|
220
|
+
%(Examples: Adobe Photoshop, Adobe Acrobat Reader)
|
221
|
+
property :hasSoftwareOtherInformation, :comment =>
|
222
|
+
%(Example: Install Acroread \(Adobe Acrobat\) first; copy
|
223
|
+
nppdf.so \(the plug-in\) to your Mozilla plug-ins directory,
|
224
|
+
and make sure a copy of \(or symlink to\) Acroread is in your
|
225
|
+
PATH.)
|
226
|
+
property :hasSoftwareVersion, :comment =>
|
227
|
+
%(Examples: >=2.2.0, 6.0, 2003)
|
228
|
+
property :hasStartDate, :comment =>
|
229
|
+
%(Data Constraint: To aid machine processing, value should use a
|
230
|
+
structured form: xsd:dateTime)
|
231
|
+
property :hasStatuteInformationDeterminationDate, :comment =>
|
232
|
+
%(Data Constraint: To aid machine processing, value should use a
|
233
|
+
structured form: xsd:dateTime)
|
234
|
+
property :hasStatuteInformationDeterminationDate, :comment =>
|
235
|
+
%(Example: 2001-10-26T19:32:52+00:00)
|
236
|
+
property :hasStatuteJurisdiction, :comment =>
|
237
|
+
%(Examples: us, de, be)
|
238
|
+
property :hasStatuteJurisdiction, :comment =>
|
239
|
+
%(Data Constraint: Values should be taken from a controlled
|
240
|
+
vocabulary.)
|
241
|
+
property :hasAct, :comment =>
|
242
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
243
|
+
this property. The precondition to do this, is to link your
|
244
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
245
|
+
vocabulary.)
|
246
|
+
property :hasAct, :comment =>
|
247
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
248
|
+
http://id.loc.gov/vocabulary/preservation/actionsGranted)
|
249
|
+
property :hasAgent
|
250
|
+
property :hasAgentType, :comment =>
|
251
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
252
|
+
http://id.loc.gov/vocabulary/preservation/agentType)
|
253
|
+
property :hasAgentType, :comment =>
|
254
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
255
|
+
this property. The precondition to do this, is to link your
|
256
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
257
|
+
vocabulary.)
|
258
|
+
property :hasApplicableDates
|
259
|
+
property :hasContentLocation
|
260
|
+
property :hasContentLocationType, :comment =>
|
261
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
262
|
+
this property. The precondition to do this, is to link your
|
263
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
264
|
+
vocabulary.)
|
265
|
+
property :hasContentLocationType, :comment =>
|
266
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
267
|
+
http://id.loc.gov/vocabulary/preservation/contentLocationType)
|
268
|
+
property :hasCopyrightStatus, :comment =>
|
269
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
270
|
+
this property. The precondition to do this, is to link your
|
271
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
272
|
+
vocabulary.)
|
273
|
+
property :hasCopyrightStatus, :comment =>
|
274
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
275
|
+
http://id.loc.gov/vocabulary/preservation/copyrightStatus)
|
276
|
+
property :hasCreatingApplication
|
277
|
+
property :hasDependency
|
278
|
+
property :hasEnvironment
|
279
|
+
property :hasEnvironmentCharacteristic, :comment =>
|
280
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
281
|
+
this property. The precondition to do this, is to link your
|
282
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
283
|
+
vocabulary.)
|
284
|
+
property :hasEnvironmentCharacteristic, :comment =>
|
285
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
286
|
+
http://id.loc.gov/vocabulary/preservation/environmentCharacteristic)
|
287
|
+
property :hasEnvironmentPurpose, :comment =>
|
288
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
289
|
+
http://id.loc.gov/vocabulary/preservation/environmentPurpose)
|
290
|
+
property :hasEnvironmentPurpose, :comment =>
|
291
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
292
|
+
this property. The precondition to do this, is to link your
|
293
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
294
|
+
vocabulary.)
|
295
|
+
property :hasEvent
|
296
|
+
property :hasEventOutcomeDetail
|
297
|
+
property :hasEventOutcomeInformation
|
298
|
+
property :hasEventRelatedAgent, :comment =>
|
299
|
+
%(This propety links a Event instance to an Agent instance. Via
|
300
|
+
this property a distinction can be made in the linkingAgent
|
301
|
+
properties based on the domain.)
|
302
|
+
property :hasEventRelatedAgent, :comment =>
|
303
|
+
%(Extensions: One can extend this property to use more fine
|
304
|
+
grained properties by defining the fine grained properties as
|
305
|
+
subproperties of this property.)
|
306
|
+
property :hasEventRelatedObject, :comment =>
|
307
|
+
%(Extensions: One can extend this property to use more fine
|
308
|
+
grained properties by defining the fine grained properties as
|
309
|
+
subproperties of this property.)
|
310
|
+
property :hasEventType, :comment =>
|
311
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
312
|
+
http://id.loc.gov/vocabulary/preservation/eventType)
|
313
|
+
property :hasEventType, :comment =>
|
314
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
315
|
+
this property. The precondition to do this, is to link your
|
316
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
317
|
+
vocabulary.)
|
318
|
+
property :hasFixity
|
319
|
+
property :hasFormat
|
320
|
+
property :hasFormatDesignation
|
321
|
+
property :hasFormatRegistry
|
322
|
+
property :hasFormatRegistryRole, :comment =>
|
323
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
324
|
+
this property. The precondition to do this, is to link your
|
325
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
326
|
+
vocabulary.)
|
327
|
+
property :hasFormatRegistryRole, :comment =>
|
328
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
329
|
+
http://id.loc.gov/vocabulary/preservation/formatRegistryRole)
|
330
|
+
property :hasHardware
|
331
|
+
property :hasHardwareType, :comment =>
|
332
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
333
|
+
this property. The precondition to do this, is to link your
|
334
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
335
|
+
vocabulary.)
|
336
|
+
property :hasHardwareType, :comment =>
|
337
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
338
|
+
http://id.loc.gov/vocabulary/preservation/hardwareType)
|
339
|
+
property :hasIdentifier
|
340
|
+
property :hasInhibitorTarget, :comment =>
|
341
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
342
|
+
http://id.loc.gov/vocabulary/preservation/inhibitorTarget)
|
343
|
+
property :hasInhibitorTarget, :comment =>
|
344
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
345
|
+
this property. The precondition to do this, is to link your
|
346
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
347
|
+
vocabulary.)
|
348
|
+
property :hasInhibitorType, :comment =>
|
349
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
350
|
+
http://id.loc.gov/vocabulary/preservation/inhibitorType)
|
351
|
+
property :hasInhibitorType, :comment =>
|
352
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
353
|
+
this property. The precondition to do this, is to link your
|
354
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
355
|
+
vocabulary.)
|
356
|
+
property :hasInhibitors
|
357
|
+
property :hasIntellectualEntity
|
358
|
+
property :hasKeyInformation
|
359
|
+
property :hasMessageDigestAlgorithm, :comment =>
|
360
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
361
|
+
http://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions)
|
362
|
+
property :hasMessageDigestAlgorithm, :comment =>
|
363
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
364
|
+
this property. The precondition to do this, is to link your
|
365
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
366
|
+
vocabulary.)
|
367
|
+
property :hasObject, :comment =>
|
368
|
+
%(Extensions: One can extend this property to use more fine
|
369
|
+
grained properties by defining the fine grained properties as
|
370
|
+
subproperties of this property.)
|
371
|
+
property :hasObjectCharacteristics
|
372
|
+
property :hasPreservationLevel
|
373
|
+
property :hasPreservationLevelRole, :comment =>
|
374
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
375
|
+
this property. The precondition to do this, is to link your
|
376
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
377
|
+
vocabulary.)
|
378
|
+
property :hasPreservationLevelRole, :comment =>
|
379
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
380
|
+
http://id.loc.gov/vocabulary/preservation/preservationLevelRole)
|
381
|
+
property :hasRelatedObject
|
382
|
+
property :hasRelatedStatuteInformation
|
383
|
+
property :hasRelationship, :comment =>
|
384
|
+
%(The LOC will provide a SKOS vocabulary, where the concepts can
|
385
|
+
also be used as object properties at http://id.loc.gov/. These
|
386
|
+
relationships will capture the relationship type and subtype.
|
387
|
+
One can define its own relationships, but for interoperability
|
388
|
+
reasons, these should be linked to or made a subproperty of
|
389
|
+
the properties of the LOC vocabulary.)
|
390
|
+
property :hasRelationship, :comment =>
|
391
|
+
%(Extensions: One can extend this property to use more fine
|
392
|
+
grained properties by defining the fine grained properties as
|
393
|
+
subproperties of this property.)
|
394
|
+
property :hasRightsDocumentation
|
395
|
+
property :hasRightsDocumentationRole
|
396
|
+
property :hasRightsGranted
|
397
|
+
property :hasRightsRelatedAgent, :comment =>
|
398
|
+
%(Extensions: One can extend this property to use more fine
|
399
|
+
grained properties by defining the fine grained properties as
|
400
|
+
subproperties of this property.)
|
401
|
+
property :hasRightsRelatedAgent, :comment =>
|
402
|
+
%(This propety links a RightsStatement instance to an Agent
|
403
|
+
instance. Via this property a distinction can be made in the
|
404
|
+
linkingAgent properties based on the domain.)
|
405
|
+
property :hasRightsStatement
|
406
|
+
property :hasSignature
|
407
|
+
property :hasSignatureEncoding, :comment =>
|
408
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
409
|
+
http://id.loc.gov/vocabulary/signatureEncoding)
|
410
|
+
property :hasSignatureEncoding, :comment =>
|
411
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
412
|
+
this property. The precondition to do this, is to link your
|
413
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
414
|
+
vocabulary.)
|
415
|
+
property :hasSignatureMethod, :comment =>
|
416
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
417
|
+
this property. The precondition to do this, is to link your
|
418
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
419
|
+
vocabulary.)
|
420
|
+
property :hasSignatureMethod, :comment =>
|
421
|
+
%(Data Constraint: Values are taken from a SKOS vocabulary)
|
422
|
+
property :hasSignificantProperties
|
423
|
+
property :hasSoftware
|
424
|
+
property :hasSoftwareType, :comment =>
|
425
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
426
|
+
this property. The precondition to do this, is to link your
|
427
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
428
|
+
vocabulary.)
|
429
|
+
property :hasSoftwareType, :comment =>
|
430
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
431
|
+
http://id.loc.gov/vocabulary/preservation/softwareType)
|
432
|
+
property :hasStorage
|
433
|
+
property :hasStorageMedium, :comment =>
|
434
|
+
%(Data Constraint: Values are taken from the SKOS vocabulary:
|
435
|
+
http://id.loc.gov/vocabulary/preservation/storageMedium)
|
436
|
+
property :hasStorageMedium, :comment =>
|
437
|
+
%(Extensions: One can use its own SKOS vocabulary to use for
|
438
|
+
this property. The precondition to do this, is to link your
|
439
|
+
SKOS concepts to the SKOS concepts of the id.loc.gov
|
440
|
+
vocabulary.)
|
441
|
+
property :hasTermOfGrant
|
442
|
+
property :hasTermOfRestriction
|
443
|
+
property :hasSigner
|
444
|
+
end
|
445
|
+
end
|