rdf-vocab 3.0.3 → 3.0.4

Sign up to get free protection for your applications and to get access to all the features.
@@ -11,26 +11,34 @@ module RDF::Vocab
11
11
 
12
12
  # Ontology definition
13
13
  ontology :"http://www.loc.gov/premis/rdf/v1#",
14
- comment: %(This ontology identifies the classes and properties used to describe preservation metadata in RDF.).freeze,
14
+ comment: %(This ontology identifies the classes and
15
+ properties used to describe preservation metadata in RDF.).freeze,
15
16
  "dc:modified": "2012-09-14T00:00:00Z".freeze,
16
17
  isDefinedBy: "http://www.loc.gov/standards/premis/v2/premis-2-2.pdf".freeze,
17
- label: "Preservation Metadata: Implementation Strategies (PREMIS) Ontology".freeze,
18
+ label: "Preservation Metadata: Implementation\n Strategies (PREMIS) Ontology".freeze,
18
19
  "owl:imports": ["http://id.loc.gov/vocabulary/preservation/actionsGranted".freeze, "http://id.loc.gov/vocabulary/preservation/agentType".freeze, "http://id.loc.gov/vocabulary/preservation/contentLocationType".freeze, "http://id.loc.gov/vocabulary/preservation/copyrightStatus".freeze, "http://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions".freeze, "http://id.loc.gov/vocabulary/preservation/environmentCharacteristic".freeze, "http://id.loc.gov/vocabulary/preservation/environmentPurpose".freeze, "http://id.loc.gov/vocabulary/preservation/eventRelatedAgentRole".freeze, "http://id.loc.gov/vocabulary/preservation/eventRelatedObjectRole".freeze, "http://id.loc.gov/vocabulary/preservation/eventType".freeze, "http://id.loc.gov/vocabulary/preservation/formatRegistryRole".freeze, "http://id.loc.gov/vocabulary/preservation/hardwareType".freeze, "http://id.loc.gov/vocabulary/preservation/inhibitorTarget".freeze, "http://id.loc.gov/vocabulary/preservation/inhibitorType".freeze, "http://id.loc.gov/vocabulary/preservation/objectCategory".freeze, "http://id.loc.gov/vocabulary/preservation/preservationLevelRole".freeze, "http://id.loc.gov/vocabulary/preservation/relationshipSubType".freeze, "http://id.loc.gov/vocabulary/preservation/relationshipType".freeze, "http://id.loc.gov/vocabulary/preservation/rightsBasis".freeze, "http://id.loc.gov/vocabulary/preservation/rightsRelatedAgentRole".freeze, "http://id.loc.gov/vocabulary/preservation/signatureEncoding".freeze, "http://id.loc.gov/vocabulary/preservation/signatureMethod".freeze, "http://id.loc.gov/vocabulary/preservation/softwareType".freeze, "http://id.loc.gov/vocabulary/preservation/storageMedium".freeze],
19
- "owl:versionInfo": "version 2.2.1".freeze,
20
- "rdfs:seeAlso": "http://multimedialab.elis.ugent.be/users/samcoppe/ontologies/Premis/index.html for the OWL Documentation of the ontology.".freeze,
20
+ "owl:versionInfo": "version\n 2.2.1".freeze,
21
+ "rdfs:seeAlso": "http://multimedialab.elis.ugent.be/users/samcoppe/ontologies/Premis/index.html for the OWL\n Documentation of the ontology.".freeze,
21
22
  type: "owl:Ontology".freeze
22
23
 
23
24
  # Class definitions
24
25
  term :Agent,
25
- comment: %(The Agent entity aggregates information about attributes or characteristics of agents \(persons, organizations, or software\) associated with rights management and preservation events in the life of a data object. Agent information serves to identify an agent unambiguously from all other
26
- Agent entities.).freeze,
27
- editorialNote: %(Entity properties: May hold or grant one or more rights. May carry out, authorize, or compel one or more events. May create or act upon one or more objects through an event or with respect to a rights statement.).freeze,
26
+ comment: %(The Agent entity aggregates information
27
+ about attributes or characteristics of agents \(persons, organizations, or software\) associated
28
+ with rights management and preservation events in the life of a data object. Agent information
29
+ serves to identify an agent unambiguously from all other Agent entities.).freeze,
30
+ editorialNote: %(Entity properties: May hold or grant one or
31
+ more rights. May carry out, authorize, or compel one or more events. May create or act upon
32
+ one or more objects through an event or with respect to a rights
33
+ statement.).freeze,
28
34
  subClassOf: ["dc:Agent".freeze, "foaf:Agent".freeze, "premis:PremisEntity".freeze],
29
35
  type: "owl:Class".freeze,
30
36
  "vs:term_status": "stable".freeze
31
37
  term :ApplicableDates,
32
- definition: %(Definition: The date range during which the particular rights statement applies or is applied to the content.).freeze,
33
- editorialNote: %(Rationale Specific dates may apply to the particular rights statement.).freeze,
38
+ definition: %(Definition: The date range during which the
39
+ particular rights statement applies or is applied to the content.).freeze,
40
+ editorialNote: %(Rationale Specific dates
41
+ may apply to the particular rights statement.).freeze,
34
42
  subClassOf: [term(
35
43
  maxCardinality: "1".freeze,
36
44
  onProperty: "premis:hasEndDate".freeze,
@@ -43,7 +51,8 @@ Agent entities.).freeze,
43
51
  type: "owl:Class".freeze,
44
52
  "vs:term_status": "stable".freeze
45
53
  term :Bitstream,
46
- definition: %(Definition: Contiguous or non-contiguous data within a file that has meaningful properties for preservation purposes.).freeze,
54
+ definition: %(Definition: Contiguous or non-contiguous
55
+ data within a file that has meaningful properties for preservation purposes.).freeze,
47
56
  "rdfs:seeAlso": "Object class definition".freeze,
48
57
  subClassOf: ["premis:Object".freeze, term(
49
58
  minCardinality: "1".freeze,
@@ -53,9 +62,10 @@ Agent entities.).freeze,
53
62
  type: "owl:Class".freeze,
54
63
  "vs:term_status": "stable".freeze
55
64
  term :ContentLocation,
56
- definition: %(Definition: Information needed to retrieve a file from the storage system, or to access a bitstream within a file.).freeze,
57
- "skos:historyNote": "Creation / Maintenance Notes: A preservation repository should never refer to content that it does not control. Therefore, the PREMIS working group assumed that the repository will always assign the contentLocation, probably by program.".freeze,
58
- "skos:scopeNote": "Usage Notes: If the preservation repository uses the objectIdentifier as a handle for retrieving data, contentLocation is implicit and does not need to be recorded.".freeze,
65
+ definition: %(Definition: Information needed to retrieve a
66
+ file from the storage system, or to access a bitstream within a file.).freeze,
67
+ "skos:historyNote": "Creation / Maintenance Notes: A preservation\n repository should never refer to content that it does not control. Therefore, the PREMIS\n working group assumed that the repository will always assign the contentLocation, probably by\n program.".freeze,
68
+ "skos:scopeNote": "Usage Notes: If the preservation repository\n uses the objectIdentifier as a handle for retrieving data, contentLocation is implicit and\n does not need to be recorded.".freeze,
59
69
  subClassOf: term(
60
70
  intersectionOf: list(term(
61
71
  cardinality: "1".freeze,
@@ -71,8 +81,9 @@ Agent entities.).freeze,
71
81
  type: "owl:Class".freeze,
72
82
  "vs:term_status": "stable".freeze
73
83
  term :CopyrightInformation,
74
- definition: %(Definition: Information about the copyright status of the object\(s\).).freeze,
75
- "skos:scopeNote": "Usage Notes: When rights basis is a copyright, copyrightInformation should be provided. Repositories may need to extend this with more detailed information. See the California Digital Library's copyrightMD schema (www.cdlib.org/inside/projects/rights/schema/) for an example of a more detailed scheme.".freeze,
84
+ definition: %(Definition: Information about the copyright
85
+ status of the object\(s\).).freeze,
86
+ "skos:scopeNote": "Usage Notes: When rights basis is a\n copyright, copyrightInformation should be provided. Repositories may need to extend this with\n more detailed information. See the California Digital Library's copyrightMD schema\n (www.cdlib.org/inside/projects/rights/schema/) for an example of a more detailed\n scheme.".freeze,
76
87
  subClassOf: ["premis:RightsStatement".freeze, term(
77
88
  intersectionOf: list(term(
78
89
  cardinality: "1".freeze,
@@ -88,10 +99,17 @@ Agent entities.).freeze,
88
99
  type: "owl:Class".freeze,
89
100
  "vs:term_status": "stable".freeze
90
101
  term :CreatingApplication,
91
- definition: %(Definition: Information about the application that created the object.).freeze,
92
- editorialNote: %(Rationale: Information about the creating application, including the version of the application and the date the file was created, can be useful for problem solving purposes. For example, it is not uncommon for certain versions of software to be known for causing conversion errors or introducing artifacts. It is also useful to determine which rendering software is available for the digital object. For example, if you know that the Distiller program created the PDF file, you know it will be renderable with \(among other programs\) Adobe Reader.).freeze,
93
- "skos:historyNote": "Creation / Maintenance Notes: If the object was created by the repository, assignment of creating application information should be straightforward. If the object was created outside the repository, it is possible this information could be supplied by the depositor. It might also be extracted from the file itself; the name of the creating application is often embedded within the file.".freeze,
94
- "skos:scopeNote": "Usage Notes: This semantic unit applies to both objects created external to the repository and subsequently ingested, and to objects created by the repository, for example, through migration events. The creatingApplication container is repeatable if more than one application processed the object in turn. For example, a file could be created by Microsoft Word and later turned into a PDF using Adobe Acrobat. Details of both the Word and Acrobat applications may be recorded. However, if both files are stored in the repository, each file should be completely described as an Object entity and linked by using relationship information with a relationshipType “derivation.” It may also be repeated to record the creating application before the object was ingested as well as the creating application used as part of the ingest process. For example, an HTML file was created pre-ingest using Dreamweaver, and the Web crawler Heritrix then captured a snapshot of the files as part of the ingest. The amount of information needed for creatingApplication given here is minimal. For more granularity, extensibility is provided. Rather than having each repository record this locally, it would be preferable to have a registry of this information similar to format or environment registries.".freeze,
102
+ definition: %(Definition: Information about the
103
+ application that created the object.).freeze,
104
+ editorialNote: %(Rationale: Information about the creating
105
+ application, including the version of the application and the date the file was created, can
106
+ be useful for problem solving purposes. For example, it is not uncommon for certain versions
107
+ of software to be known for causing conversion errors or introducing artifacts. It is also
108
+ useful to determine which rendering software is available for the digital object. For example,
109
+ if you know that the Distiller program created the PDF file, you know it will be renderable
110
+ with \(among other programs\) Adobe Reader.).freeze,
111
+ "skos:historyNote": "Creation / Maintenance Notes: If the object\n was created by the repository, assignment of creating application information should be\n straightforward. If the object was created outside the repository, it is possible this\n information could be supplied by the depositor. It might also be extracted from the file\n itself; the name of the creating application is often embedded within the\n file.".freeze,
112
+ "skos:scopeNote": "Usage Notes: This semantic unit applies to\n both objects created external to the repository and subsequently ingested, and to objects\n created by the repository, for example, through migration events. The creatingApplication\n container is repeatable if more than one application processed the object in turn. For\n example, a file could be created by Microsoft Word and later turned into a PDF using Adobe\n Acrobat. Details of both the Word and Acrobat applications may be recorded. However, if both\n files are stored in the repository, each file should be completely described as an Object\n entity and linked by using relationship information with a relationshipType “derivation.” It\n may also be repeated to record the creating application before the object was ingested as well\n as the creating application used as part of the ingest process. For example, an HTML file was\n created pre-ingest using Dreamweaver, and the Web crawler Heritrix then captured a snapshot of\n the files as part of the ingest. The amount of information needed for creatingApplication\n given here is minimal. For more granularity, extensibility is provided. Rather than having\n each repository record this locally, it would be preferable to have a registry of this\n information similar to format or environment registries.".freeze,
95
113
  subClassOf: term(
96
114
  type: "owl:Class".freeze,
97
115
  unionOf: list(term(
@@ -111,9 +129,11 @@ Agent entities.).freeze,
111
129
  type: "owl:Class".freeze,
112
130
  "vs:term_status": "stable".freeze
113
131
  term :Dependency,
114
- definition: %(Definition: Information about a non-software component or associated file needed in order to use or render the representation or file, for example, a schema, a DTD, or an entity file declaration.).freeze,
115
- "skos:historyNote": "Creation / Maintenance Notes: Recommended practice is for a repository to archive objects on which other objects depend. These may be sent by the submitter of the primary object, or they may in some cases be automatically obtained by the repository. For example, a markup file will often contain links to other objects it requires such as DTDs or XML Schema. If it does, these objects can often be identified by the link and downloaded by the repository.".freeze,
116
- "skos:scopeNote": "Usage Notes: This semantic unit is for additional objects that are necessary to render a file or representation, not for required software or hardware. It may also be used for a non-executable component of the object, such as a font or style sheet. For things that the software requires, see swDependency. This semantic unit does not include objects required by structural relationships, such as child content objects (e.g., figures that are part of an article), which are recorded under relationship with a relationshipType of “structural”. It is up to the repository to determine what constitutes a dependency in the context of the designated community. The objects noted may be internal or external to the preservation repository.".freeze,
132
+ definition: %(Definition: Information about a non-software
133
+ component or associated file needed in order to use or render the representation or file, for
134
+ example, a schema, a DTD, or an entity file declaration.).freeze,
135
+ "skos:historyNote": "Creation / Maintenance Notes: Recommended\n practice is for a repository to archive objects on which other objects depend. These may be\n sent by the submitter of the primary object, or they may in some cases be automatically\n obtained by the repository. For example, a markup file will often contain links to other\n objects it requires such as DTDs or XML Schema. If it does, these objects can often be\n identified by the link and downloaded by the repository.".freeze,
136
+ "skos:scopeNote": "Usage Notes: This semantic unit is for\n additional objects that are necessary to render a file or representation, not for required\n software or hardware. It may also be used for a non-executable component of the object, such\n as a font or style sheet. For things that the software requires, see swDependency. This\n semantic unit does not include objects required by structural relationships, such as child\n content objects (e.g., figures that are part of an article), which are recorded under\n relationship with a relationshipType of “structural”. It is up to the repository to determine\n what constitutes a dependency in the context of the designated community. The objects noted\n may be internal or external to the preservation repository.".freeze,
117
137
  subClassOf: term(
118
138
  type: "owl:Class".freeze,
119
139
  unionOf: list(term(
@@ -129,10 +149,13 @@ Agent entities.).freeze,
129
149
  type: "owl:Class".freeze,
130
150
  "vs:term_status": "stable".freeze
131
151
  term :Environment,
132
- definition: %(Definition: Hardware/software combinations supporting use of the object.).freeze,
133
- editorialNote: %(Rationale: Environment is the means by which the user renders and interacts with content. Separation of digital content from its environmental context can result in the content becoming unusable.).freeze,
134
- "skos:historyNote": "Creation / Maintenance Notes: This information may be omitted when the repository is doing only bit-level preservation on the object. Rather than having each repository record this locally, it would be preferable to have a registry of environment information similar to proposed registries of format information. Repositories may choose to design mechanisms for inheritance, so that if the environment required for each file within a representation is identical to the environment recorded for the representation as a whole, it is not necessary to store this information in each file.".freeze,
135
- "skos:scopeNote": "Usage Notes: All of this semantic units’ subunits are optional. At least one subunit (i.e. environmentNote, dependency, software, hardware, and/or environmentExtension) must be present if this container is included.".freeze,
152
+ definition: %(Definition: Hardware/software combinations
153
+ supporting use of the object.).freeze,
154
+ editorialNote: %(Rationale: Environment is the means by which
155
+ the user renders and interacts with content. Separation of digital content from its
156
+ environmental context can result in the content becoming unusable.).freeze,
157
+ "skos:historyNote": "Creation / Maintenance Notes: This\n information may be omitted when the repository is doing only bit-level preservation on the\n object. Rather than having each repository record this locally, it would be preferable to have\n a registry of environment information similar to proposed registries of format information.\n Repositories may choose to design mechanisms for inheritance, so that if the environment\n required for each file within a representation is identical to the environment recorded for\n the representation as a whole, it is not necessary to store this information in each\n file.".freeze,
158
+ "skos:scopeNote": "Usage Notes: All of this semantic units’\n subunits are optional. At least one subunit (i.e. environmentNote, dependency, software,\n hardware, and/or environmentExtension) must be present if this container is\n included.".freeze,
136
159
  subClassOf: term(
137
160
  maxCardinality: "1".freeze,
138
161
  onProperty: "premis:hasEnvironmentCharacteristic".freeze,
@@ -141,11 +164,17 @@ Agent entities.).freeze,
141
164
  type: "owl:Class".freeze,
142
165
  "vs:term_status": "stable".freeze
143
166
  term :Event,
144
- comment: %(The Event entity aggregates information about an action that involves one or more Object entities. Metadata about an Event would normally be recorded and stored separately from the digital object.
145
- Whether or not a preservation repository records an Event depends upon the importance of the event. Actions that modify objects should always be recorded. Other actions such as copying an object for backup purposes may be recorded in system logs or an audit trail but not necessarily in
146
- an Event entity.
147
- Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).freeze,
148
- editorialNote: %(Entity properties: Must be related to one or more objects. Can be related to one or more agents. Links between entities may be recorded from either direction and need not be bi-directional.).freeze,
167
+ comment: %(The Event entity aggregates information
168
+ about an action that involves one or more Object entities. Metadata about an Event would
169
+ normally be recorded and stored separately from the digital object. Whether or not a
170
+ preservation repository records an Event depends upon the importance of the event. Actions
171
+ that modify objects should always be recorded. Other actions such as copying an object for
172
+ backup purposes may be recorded in system logs or an audit trail but not necessarily in an
173
+ Event entity. Mandatory semantic units are: eventIdentifier, eventType, and
174
+ eventDateTime.).freeze,
175
+ editorialNote: %(Entity properties: Must be related to one or
176
+ more objects. Can be related to one or more agents. Links between entities may be recorded
177
+ from either direction and need not be bi-directional.).freeze,
149
178
  subClassOf: ["premis:PremisEntity".freeze, term(
150
179
  intersectionOf: list(term(
151
180
  cardinality: "1".freeze,
@@ -165,9 +194,12 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
165
194
  type: "owl:Class".freeze,
166
195
  "vs:term_status": "stable".freeze
167
196
  term :EventOutcomeDetail,
168
- definition: %(Definition: A detailed description of the result or product of the event.).freeze,
169
- editorialNote: %(Rationale: An event outcome may be sufficiently complex that a coded description is not adequate to document it.).freeze,
170
- "skos:scopeNote": "Usage Notes: This may be used to record all error and warning messages issued by a program involved in the event or to record a pointer to an error log. If the event was a validity check (e.g., profile conformance) any anomalies or quirks discovered would be recorded here. All subunits of this semantic unit are optional. At least one subunit (i.e. eventOutcomeDetailNote and/or eventOutcomeDetailExtension) must be present if this container is included.".freeze,
197
+ definition: %(Definition: A detailed description of the
198
+ result or product of the event.).freeze,
199
+ editorialNote: %(Rationale: An event outcome may be
200
+ sufficiently complex that a coded description is not adequate to document
201
+ it.).freeze,
202
+ "skos:scopeNote": "Usage Notes: This may be used to record all\n error and warning messages issued by a program involved in the event or to record a pointer to\n an error log. If the event was a validity check (e.g., profile conformance) any anomalies or\n quirks discovered would be recorded here. All subunits of this semantic unit are optional. At\n least one subunit (i.e. eventOutcomeDetailNote and/or eventOutcomeDetailExtension) must be\n present if this container is included.".freeze,
171
203
  subClassOf: term(
172
204
  maxCardinality: "1".freeze,
173
205
  onProperty: "premis:hasEventOutcomeDetailNote".freeze,
@@ -176,8 +208,9 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
176
208
  type: "owl:Class".freeze,
177
209
  "vs:term_status": "stable".freeze
178
210
  term :EventOutcomeInformation,
179
- definition: %(Definition: Information about the outcome of an event.).freeze,
180
- "skos:scopeNote": "Usage Notes: A repository may wish to supplement a coded eventOutcome value with additional information in eventOutcomeDetail. Since events may have more than one outcome, the container is repeatable. All subunits of this semantic unit are optional. At least one subunit (i.e. eventOutcome or eventOutcomeDetail) must be present if this container is included.".freeze,
211
+ definition: %(Definition: Information about the outcome of
212
+ an event.).freeze,
213
+ "skos:scopeNote": "Usage Notes: A repository may wish to\n supplement a coded eventOutcome value with additional information in eventOutcomeDetail. Since\n events may have more than one outcome, the container is repeatable. All subunits of this\n semantic unit are optional. At least one subunit (i.e. eventOutcome or eventOutcomeDetail)\n must be present if this container is included.".freeze,
181
214
  subClassOf: term(
182
215
  maxCardinality: "1".freeze,
183
216
  onProperty: "premis:hasEventOutcome".freeze,
@@ -186,7 +219,8 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
186
219
  type: "owl:Class".freeze,
187
220
  "vs:term_status": "stable".freeze
188
221
  term :File,
189
- definition: %(Definition: A named and ordered sequence of bytes that is known to an operating system.).freeze,
222
+ definition: %(Definition: A named and ordered sequence of
223
+ bytes that is known to an operating system.).freeze,
190
224
  "rdfs:seeAlso": "Object class definition".freeze,
191
225
  subClassOf: ["premis:Object".freeze, term(
192
226
  minCardinality: "1".freeze,
@@ -196,9 +230,10 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
196
230
  type: "owl:Class".freeze,
197
231
  "vs:term_status": "stable".freeze
198
232
  term :Fixity,
199
- definition: %(Definition: Information used to verify whether an object has been altered in an undocumented or unauthorized way.).freeze,
200
- "skos:historyNote": "Creation / Maintenance Notes: Automatically calculated and recorded by repository.".freeze,
201
- "skos:scopeNote": "Usage Notes: To perform a fixity check, a message digest calculated at some earlier time is compared with a message digest calculated at a later time. If the digests are the same, the object was not altered in the interim. Recommended practice is to use two or more message digests calculated by different algorithms. (Note that the terms “message digest” and “checksum” are commonly used interchangeably. However, the term “checksum” is more correctly used for the product of a cyclical redundancy check (CRC), whereas the term “message digest” refers to the result of a cryptographic hash function, which is what is referred to here.) The act of performing a fixity check and the date it occurred would be recorded as an Event. The result of the check would be recorded as the eventOutcome. Therefore, only the messageDigestAlgorithm and messageDigest need to be recorded as objectCharacteristics for future comparison. Representation level: It could be argued that if a representation consists of a single file or if all the files comprised by a representation are combined (e.g., zipped) into a single file, then a fixity check could be performed on the representation. However, in both cases the fixity check is actually being performed on a file, which in this case happens to be coincidental with a representation. Bitstream level: Message digests can be computed for bitstreams although they are not as common as with files. For example, the JPX format, which is a JPEG2000 format, supports the inclusion of MD5 or SHA-1 message digests in internal metadata that was calculated on any range of bytes of the file.".freeze,
233
+ definition: %(Definition: Information used to verify
234
+ whether an object has been altered in an undocumented or unauthorized way.).freeze,
235
+ "skos:historyNote": "Creation / Maintenance Notes: Automatically\n calculated and recorded by repository.".freeze,
236
+ "skos:scopeNote": "Usage Notes: To perform a fixity check, a\n message digest calculated at some earlier time is compared with a message digest calculated at\n a later time. If the digests are the same, the object was not altered in the interim.\n Recommended practice is to use two or more message digests calculated by different algorithms.\n (Note that the terms “message digest” and “checksum” are commonly used interchangeably.\n However, the term “checksum” is more correctly used for the product of a cyclical redundancy\n check (CRC), whereas the term “message digest” refers to the result of a cryptographic hash\n function, which is what is referred to here.) The act of performing a fixity check and the\n date it occurred would be recorded as an Event. The result of the check would be recorded as\n the eventOutcome. Therefore, only the messageDigestAlgorithm and messageDigest need to be\n recorded as objectCharacteristics for future comparison. Representation level: It could be\n argued that if a representation consists of a single file or if all the files comprised by a\n representation are combined (e.g., zipped) into a single file, then a fixity check could be\n performed on the representation. However, in both cases the fixity check is actually being\n performed on a file, which in this case happens to be coincidental with a representation.\n Bitstream level: Message digests can be computed for bitstreams although they are not as\n common as with files. For example, the JPX format, which is a JPEG2000 format, supports the\n inclusion of MD5 or SHA-1 message digests in internal metadata that was calculated on any\n range of bytes of the file.".freeze,
202
237
  subClassOf: term(
203
238
  intersectionOf: list(term(
204
239
  cardinality: "1".freeze,
@@ -214,10 +249,16 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
214
249
  type: "owl:Class".freeze,
215
250
  "vs:term_status": "stable".freeze
216
251
  term :Format,
217
- definition: %(Definition: Identification of the format of a file or bitstream where format is the organization of digital information according to preset specifications.).freeze,
218
- editorialNote: %(Rationale: Many preservation activities depend on detailed knowledge about the format of the digital object. An accurate identification of format is essential. The identification provided, whether by name or pointer into a format registry, should be sufficient to associate the object with more detailed format information.).freeze,
219
- "skos:historyNote": "Creation / Maintenance Notes: The format of a file or bitstream should be ascertained by the repository on ingest. Even if this information is provided by the submitter, directly in metadata or indirectly via the file name extension, recommended practice is to independently identify the format by parsing the file when possible. If the format cannot be identified at the time of ingest, it is valid to record that it is unknown, but the repository should subsequently make an effort to identify the format, even if manual intervention is required.".freeze,
220
- "skos:scopeNote": "Usage Notes: A bitstream embedded within a file may have different characteristics than the larger file. For example, a bitstream in LaTex format could be embedded within an SGML file, or multiple images using different colorspaces could be embedded within a TIFF file. format must be recorded for every object. When the bitstream format can be recognized by the repository and the repository might want to treat the bitstream differently from the embedding file for preservation purposes, format can be recorded for embedded bitstreams. Although this semantic unit is mandatory, both of its subunits are optional. At least one subunit (i.e. either formatDesignation or formatRegistry) must be present if this container is included or both may be used. If the subunit (formatDesignation or formatRegistry) needs to be repeated, the entire format container is repeated. This allows for association of format designation with a particular set of format registry information. For example, if the precise format cannot be determined and two format designations are recorded, each is given within a separate format container. The format container may also be repeated for multiple format registry entries.".freeze,
252
+ definition: %(Definition: Identification of the format of
253
+ a file or bitstream where format is the organization of digital information according to
254
+ preset specifications.).freeze,
255
+ editorialNote: %(Rationale: Many preservation activities
256
+ depend on detailed knowledge about the format of the digital object. An accurate
257
+ identification of format is essential. The identification provided, whether by name or pointer
258
+ into a format registry, should be sufficient to associate the object with more detailed format
259
+ information.).freeze,
260
+ "skos:historyNote": "Creation / Maintenance Notes: The format of\n a file or bitstream should be ascertained by the repository on ingest. Even if this\n information is provided by the submitter, directly in metadata or indirectly via the file name\n extension, recommended practice is to independently identify the format by parsing the file\n when possible. If the format cannot be identified at the time of ingest, it is valid to record\n that it is unknown, but the repository should subsequently make an effort to identify the\n format, even if manual intervention is required.".freeze,
261
+ "skos:scopeNote": "Usage Notes: A bitstream embedded within a\n file may have different characteristics than the larger file. For example, a bitstream in\n LaTex format could be embedded within an SGML file, or multiple images using different\n colorspaces could be embedded within a TIFF file. format must be recorded for every object.\n When the bitstream format can be recognized by the repository and the repository might want to\n treat the bitstream differently from the embedding file for preservation purposes, format can\n be recorded for embedded bitstreams. Although this semantic unit is mandatory, both of its\n subunits are optional. At least one subunit (i.e. either formatDesignation or formatRegistry)\n must be present if this container is included or both may be used. If the subunit\n (formatDesignation or formatRegistry) needs to be repeated, the entire format container is\n repeated. This allows for association of format designation with a particular set of format\n registry information. For example, if the precise format cannot be determined and two format\n designations are recorded, each is given within a separate format container. The format\n container may also be repeated for multiple format registry entries.".freeze,
221
262
  subClassOf: term(
222
263
  type: "owl:Class".freeze,
223
264
  unionOf: list(term(
@@ -233,8 +274,9 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
233
274
  type: "owl:Class".freeze,
234
275
  "vs:term_status": "stable".freeze
235
276
  term :FormatDesignation,
236
- definition: %(Definition: An identification of the format of the object.).freeze,
237
- "skos:scopeNote": "Usage Notes: Either formatDesignation or at least one instance of formatRegistry is required. Both may be included. The most specific format (or format profile) should be recorded. A repository (or formats registry) may wish to use multipart format names (e.g., “TIFF_GeoTIFF” or “WAVE_MPEG_BWF”) to achieve this specificity.".freeze,
277
+ definition: %(Definition: An identification of the format
278
+ of the object.).freeze,
279
+ "skos:scopeNote": "Usage Notes: Either formatDesignation or at\n least one instance of formatRegistry is required. Both may be included. The most specific\n format (or format profile) should be recorded. A repository (or formats registry) may wish to\n use multipart format names (e.g., “TIFF_GeoTIFF” or “WAVE_MPEG_BWF”) to achieve this\n specificity.".freeze,
238
280
  subClassOf: term(
239
281
  cardinality: "1".freeze,
240
282
  onProperty: "premis:hasFormatName".freeze,
@@ -243,9 +285,12 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
243
285
  type: "owl:Class".freeze,
244
286
  "vs:term_status": "stable".freeze
245
287
  term :FormatRegistry,
246
- definition: %(Definition: Identifies and/or gives further information about the format by reference to an entry in a format registry.).freeze,
247
- editorialNote: %(Rationale: If central format registries are available to the preservation repository, they may provide an excellent way of referencing detailed format information.).freeze,
248
- "skos:scopeNote": "Usage Notes: Either formatDesignation or at least one instance of formatRegistry is required. If more than one formatRegistry needs to be recorded the format container should be repeated to include each additional set of formatRegistry information. The PREMIS working group assumed that a number of format registries will be developed and maintained to support digital preservation efforts. The proposal for a Global Digital Format Registry (GDFR) (http://hul.harvard.edu/gdfr/documents.html#data), for example, would create a network-accessible registry designed to store detailed specifications on formats and profiles.".freeze,
288
+ definition: %(Definition: Identifies and/or gives further
289
+ information about the format by reference to an entry in a format registry.).freeze,
290
+ editorialNote: %(Rationale: If central format registries are
291
+ available to the preservation repository, they may provide an excellent way of referencing
292
+ detailed format information.).freeze,
293
+ "skos:scopeNote": "Usage Notes: Either formatDesignation or at\n least one instance of formatRegistry is required. If more than one formatRegistry needs to be\n recorded the format container should be repeated to include each additional set of\n formatRegistry information. The PREMIS working group assumed that a number of format\n registries will be developed and maintained to support digital preservation efforts. The\n proposal for a Global Digital Format Registry (GDFR)\n (http://hul.harvard.edu/gdfr/documents.html#data), for example, would create a\n network-accessible registry designed to store detailed specifications on formats and\n profiles.".freeze,
249
294
  subClassOf: [term(
250
295
  cardinality: "1".freeze,
251
296
  onProperty: "premis:hasFormatRegistryKey".freeze,
@@ -258,8 +303,10 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
258
303
  type: "owl:Class".freeze,
259
304
  "vs:term_status": "stable".freeze
260
305
  term :Hardware,
261
- definition: %(Definition: Hardware components needed by the software referenced in swName or the human user of the referenced software.).freeze,
262
- "skos:historyNote": "Creation / Maintenance Notes: Hardware environment information can be very difficult to provide. Many different hardware environments may apply; there are a huge number of combinations of maker and type of CPU, memory, video drivers, and so on. Although at least one hardware environment should be recorded, it is not necessary to record them all and each repository will have to make its own decisions about which hardware environments to record. Because of the difficulty recording this information comprehensively, it would be optimal if central registries of environment information existed. In many cases the environment of a file object is directly associated with the format, making registry lookup by format feasible. In the absence of a global mechanism, repositories may be forced to develop their own local “registries” relating format to hwEnvironment.".freeze,
306
+ definition: %(Definition: Hardware components needed by
307
+ the software referenced in swName or the human user of the referenced
308
+ software.).freeze,
309
+ "skos:historyNote": "Creation / Maintenance Notes: Hardware\n environment information can be very difficult to provide. Many different hardware environments\n may apply; there are a huge number of combinations of maker and type of CPU, memory, video\n drivers, and so on. Although at least one hardware environment should be recorded, it is not\n necessary to record them all and each repository will have to make its own decisions about\n which hardware environments to record. Because of the difficulty recording this information\n comprehensively, it would be optimal if central registries of environment information existed.\n In many cases the environment of a file object is directly associated with the format, making\n registry lookup by format feasible. In the absence of a global mechanism, repositories may be\n forced to develop their own local “registries” relating format to\n hwEnvironment.".freeze,
263
310
  subClassOf: term(
264
311
  intersectionOf: list(term(
265
312
  cardinality: "1".freeze,
@@ -275,7 +322,8 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
275
322
  type: "owl:Class".freeze,
276
323
  "vs:term_status": "stable".freeze
277
324
  term :Identifier,
278
- comment: %(This class is used in PREMIS OWL to describe identifiers if the identifiers are not http URIs.).freeze,
325
+ comment: %(This class is used in PREMIS OWL to
326
+ describe identifiers if the identifiers are not http URIs.).freeze,
279
327
  subClassOf: [term(
280
328
  cardinality: "1".freeze,
281
329
  onProperty: "premis:hasIdentifierType".freeze,
@@ -288,10 +336,13 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
288
336
  type: "owl:Class".freeze,
289
337
  "vs:term_status": "stable".freeze
290
338
  term :Inhibitors,
291
- definition: %(Definition: Features of the object intended to inhibit access, use, or migration.).freeze,
292
- editorialNote: %(Rationale: Format information may indicate whether a file is encrypted, but the nature of the encryption also must be recorded, as well as the access key.).freeze,
293
- "skos:historyNote": "Creation / Maintenance Notes: Inhibitors are more likely to be present on an object ingested by the repository than applied by the repository itself. It is often not possible to tell that a file has been encrypted by parsing it; the file may appear to be ASCII text. Therefore, information about inhibitors should be supplied as metadata with submitted objects when possible.".freeze,
294
- "skos:scopeNote": "Usage Notes: Some file formats allow encryption for embedded bitstreams. Some file formats such as PDF use passwords to control access to content or specific functions. Although this is actually implemented at the bitstream level, for preservation purposes it is effectively managed at the file level; that is, passwords would not be recorded for individually addressable bitstreams. For certain types of inhibitor keys, more granularity may be required. If the inhibitor key information is identical to key information in digital signatures, use those semantic units.".freeze,
339
+ definition: %(Definition: Features of the object intended
340
+ to inhibit access, use, or migration.).freeze,
341
+ editorialNote: %(Rationale: Format information may indicate
342
+ whether a file is encrypted, but the nature of the encryption also must be recorded, as well
343
+ as the access key.).freeze,
344
+ "skos:historyNote": "Creation / Maintenance Notes: Inhibitors are\n more likely to be present on an object ingested by the repository than applied by the\n repository itself. It is often not possible to tell that a file has been encrypted by parsing\n it; the file may appear to be ASCII text. Therefore, information about inhibitors should be\n supplied as metadata with submitted objects when possible.".freeze,
345
+ "skos:scopeNote": "Usage Notes: Some file formats allow\n encryption for embedded bitstreams. Some file formats such as PDF use passwords to control\n access to content or specific functions. Although this is actually implemented at the\n bitstream level, for preservation purposes it is effectively managed at the file level; that\n is, passwords would not be recorded for individually addressable bitstreams. For certain types\n of inhibitor keys, more granularity may be required. If the inhibitor key information is\n identical to key information in digital signatures, use those semantic units.".freeze,
295
346
  subClassOf: term(
296
347
  cardinality: "1".freeze,
297
348
  onProperty: "premis:hasInhibitorType".freeze,
@@ -300,14 +351,22 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
300
351
  type: "owl:Class".freeze,
301
352
  "vs:term_status": "stable".freeze
302
353
  term :IntellectualEntity,
303
- comment: %(Intellectual entities are described via Descriptive metadata models. These are very domain-specific and are out of scope for PREMIS. Examples: Dublin Core, Mets, MARC).freeze,
304
- definition: %(Definition: a set of content that is considered a single intellectual unit for purposes of management and description: for example, a particular book, map, photograph, or database. An Intellectual Entity can include other Intellectual Entities; for example, a Web site can include a Web page; a Web page can include an image. An Intellectual Entity may have one or more digital representations.).freeze,
354
+ comment: %(Intellectual entities are described via
355
+ Descriptive metadata models. These are very domain-specific and are out of scope for PREMIS.
356
+ Examples: Dublin Core, Mets, MARC).freeze,
357
+ definition: %(Definition: a set of content that is
358
+ considered a single intellectual unit for purposes of management and description: for example,
359
+ a particular book, map, photograph, or database. An Intellectual Entity can include other
360
+ Intellectual Entities; for example, a Web site can include a Web page; a Web page can include
361
+ an image. An Intellectual Entity may have one or more digital
362
+ representations.).freeze,
305
363
  subClassOf: "premis:PremisEntity".freeze,
306
364
  type: "owl:Class".freeze,
307
365
  "vs:term_status": "stable".freeze
308
366
  term :LicenseInformation,
309
- definition: %(Definition: Information about a license or other agreement granting permissions related to an object.).freeze,
310
- "skos:scopeNote": "Usage Note: When rights basis is a license, licenseInformation should be provided.".freeze,
367
+ definition: %(Definition: Information about a license or
368
+ other agreement granting permissions related to an object.).freeze,
369
+ "skos:scopeNote": "Usage Note: When rights basis is a license,\n licenseInformation should be provided.".freeze,
311
370
  subClassOf: ["premis:RightsStatement".freeze, term(
312
371
  maxCardinality: "1".freeze,
313
372
  onProperty: "premis:hasLicenseTerms".freeze,
@@ -316,16 +375,29 @@ Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.).fr
316
375
  type: "owl:Class".freeze,
317
376
  "vs:term_status": "stable".freeze
318
377
  term :Object,
319
- comment: %(The object class aggregates information about a digital object held by a preservation repository and describes those characteristics relevant to preservation management. The only mandatory property is objectIdentifier.
320
- The object class has three subclasses: Representation, File, and Bitstream.).freeze,
321
- editorialNote: [%(Entity properties: Can be associated with one or more rights statements. Can participate in one or more events. Links between entities may be recorded from either direction and need not be bi-directional.).freeze, %(Entity types: Representation: A digital object instantiating or embodying an Intellectual Entity. A representation is the set of stored digital files and structural metadata needed to provide a complete and reasonable rendition of the Intellectual Entity. File: A named and ordered sequence of bytes that is known to an operating system. Bitstream: Contiguous or non-contiguous data within a file that has meaningful properties for preservation purposes.).freeze],
378
+ comment: %(The object class aggregates information
379
+ about a digital object held by a preservation repository and describes those characteristics
380
+ relevant to preservation management. The only mandatory property is objectIdentifier. The
381
+ object class has three subclasses: Representation, File, and Bitstream.).freeze,
382
+ editorialNote: [%(Entity properties: Can be associated with
383
+ one or more rights statements. Can participate in one or more events. Links between entities
384
+ may be recorded from either direction and need not be bi-directional.).freeze, %(Entity types: Representation: A digital
385
+ object instantiating or embodying an Intellectual Entity. A representation is the set of
386
+ stored digital files and structural metadata needed to provide a complete and reasonable
387
+ rendition of the Intellectual Entity. File: A named and ordered sequence of bytes that is
388
+ known to an operating system. Bitstream: Contiguous or non-contiguous data within a file that
389
+ has meaningful properties for preservation purposes.).freeze],
322
390
  subClassOf: "premis:PremisEntity".freeze,
323
391
  type: "owl:Class".freeze,
324
392
  "vs:term_status": "stable".freeze
325
393
  term :ObjectCharacteristics,
326
- definition: %(Definition: Technical properties of a file or bitstream that are applicable to all or most formats.).freeze,
327
- editorialNote: %(Rationale: There are some important technical properties that apply to objects of any format. Detailed definition of format-specific properties is outside the scope of this Data Dictionary, although such properties may be included within objectCharacteristicsExtension.).freeze,
328
- "skos:scopeNote": "Usage Notes: The semantic units included in objectCharacteristics should be treated as a set of information that pertains to a single object at a single compositionLevel. Object characteristics may be repeated when an object was created by applying two or more encodings, such as compression and encryption. In this case each repetition of objectCharacteristics would have an incrementally higher compositionLevel. When encryption is applied, the objectCharacteristics block must include an inhibitors semantic unit. A bitstream embedded within a file may have different object characteristics than the file. Where these characteristics are relevant for preservation, they should be recorded. When a single file is equivalent to a representation, objectCharacteristics may be applied and thus associated with the representation. In these cases, the relationship between the file comprising the representation and other associated files may be expressed using relationshipSubType.".freeze,
394
+ definition: %(Definition: Technical properties of a file
395
+ or bitstream that are applicable to all or most formats.).freeze,
396
+ editorialNote: %(Rationale: There are some important
397
+ technical properties that apply to objects of any format. Detailed definition of
398
+ format-specific properties is outside the scope of this Data Dictionary, although such
399
+ properties may be included within objectCharacteristicsExtension.).freeze,
400
+ "skos:scopeNote": "Usage Notes: The semantic units included in\n objectCharacteristics should be treated as a set of information that pertains to a single\n object at a single compositionLevel. Object characteristics may be repeated when an object was\n created by applying two or more encodings, such as compression and encryption. In this case\n each repetition of objectCharacteristics would have an incrementally higher compositionLevel.\n When encryption is applied, the objectCharacteristics block must include an inhibitors\n semantic unit. A bitstream embedded within a file may have different object characteristics\n than the file. Where these characteristics are relevant for preservation, they should be\n recorded. When a single file is equivalent to a representation, objectCharacteristics may be\n applied and thus associated with the representation. In these cases, the relationship between\n the file comprising the representation and other associated files may be expressed using\n relationshipSubType.".freeze,
329
401
  subClassOf: [term(
330
402
  cardinality: "1".freeze,
331
403
  onProperty: "premis:hasCompositionLevel".freeze,
@@ -338,16 +410,24 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
338
410
  type: "owl:Class".freeze,
339
411
  "vs:term_status": "stable".freeze
340
412
  term :PremisEntity,
341
- definition: %(Definition: Basicly, the preservation information in PREMIS OWL consists of five entities related to each other. The entities are: Agent, Event, IntellectualEntity, Object, and RightsStatement.).freeze,
342
- "owl:versionInfo": "PREMIS 2.2 Owl v2".freeze,
413
+ definition: %(Definition: Basicly, the preservation
414
+ information in PREMIS OWL consists of five entities related to each other. The entities are:
415
+ Agent, Event, IntellectualEntity, Object, and RightsStatement.).freeze,
416
+ "owl:versionInfo": "PREMIS 2.2 Owl\n v2".freeze,
343
417
  subClassOf: "owl:Thing".freeze,
344
418
  type: "owl:Class".freeze,
345
419
  "vs:term_status": "stable".freeze
346
420
  term :PreservationLevel,
347
- definition: %(Definition: Information indicating the decision or policy on the set of preservation functions to be applied to an object and the context in which the decision or policy was made.).freeze,
348
- editorialNote: %(Rationale: Some preservation repositories will offer multiple preservation options depending on factors such as the value or uniqueness of the material, the “preservability” of the format, the amount the customer is willing to pay, etc. The context surrounding the choice of a particular preservation option for an object may also require further explanation.).freeze,
349
- "skos:historyNote": "Creation / Maintenance Notes: The preservation level may be assigned by the repository or requested by the depositor and submitted as metadata. The repository may also choose to record additional metadata indicating the context for the assignment of the preservation level.".freeze,
350
- "skos:scopeNote": "Usage Notes: If the repository offers only a single preservation level, this value does not need to be explicitly recorded within the repository. Application of a particular set of preservationLevel semantic units may only cover a single representation of an object: representations in other technical forms or serving other functions may have a different preservationLevel applied. The container may be repeated if a preservation level value needs to be recorded in additional contexts (see preservationLevelRole).".freeze,
421
+ definition: %(Definition: Information indicating the
422
+ decision or policy on the set of preservation functions to be applied to an object and the
423
+ context in which the decision or policy was made.).freeze,
424
+ editorialNote: %(Rationale: Some preservation repositories
425
+ will offer multiple preservation options depending on factors such as the value or uniqueness
426
+ of the material, the “preservability” of the format, the amount the customer is willing to
427
+ pay, etc. The context surrounding the choice of a particular preservation option for an object
428
+ may also require further explanation.).freeze,
429
+ "skos:historyNote": "Creation / Maintenance Notes: The\n preservation level may be assigned by the repository or requested by the depositor and\n submitted as metadata. The repository may also choose to record additional metadata indicating\n the context for the assignment of the preservation level.".freeze,
430
+ "skos:scopeNote": "Usage Notes: If the repository offers only a\n single preservation level, this value does not need to be explicitly recorded within the\n repository. Application of a particular set of preservationLevel semantic units may only cover\n a single representation of an object: representations in other technical forms or serving\n other functions may have a different preservationLevel applied. The container may be repeated\n if a preservation level value needs to be recorded in additional contexts (see\n preservationLevelRole).".freeze,
351
431
  subClassOf: [term(
352
432
  cardinality: "1".freeze,
353
433
  onProperty: "premis:hasPreservationLevelValue".freeze,
@@ -360,8 +440,9 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
360
440
  type: "owl:Class".freeze,
361
441
  "vs:term_status": "stable".freeze
362
442
  term :RelatedObjectIdentification,
363
- definition: %(Definition: The identifier and sequential context of the related resource).freeze,
364
- "skos:scopeNote": "Usage Notes: The related object may or may not be held within the preservation repository. Recommended practice is that objects reside within the repository unless there is a good reason to reference an object outside. Internal and external references should be clear.".freeze,
443
+ definition: %(Definition: The identifier and sequential
444
+ context of the related resource).freeze,
445
+ "skos:scopeNote": "Usage Notes: The related object may or may\n not be held within the preservation repository. Recommended practice is that objects reside\n within the repository unless there is a good reason to reference an object outside. Internal\n and external references should be clear.".freeze,
365
446
  subClassOf: term(
366
447
  intersectionOf: list(term(
367
448
  cardinality: "1".freeze,
@@ -377,13 +458,18 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
377
458
  type: "owl:Class".freeze,
378
459
  "vs:term_status": "stable".freeze
379
460
  term :Representation,
380
- definition: %(Definition: A digital object instantiating or embodying an Intellectual Entity. A representation is the set of stored digital files and structural metadata needed to provide a complete and reasonable rendition of the Intellectual Entity.).freeze,
461
+ definition: %(Definition: A digital object instantiating
462
+ or embodying an Intellectual Entity. A representation is the set of stored digital files and
463
+ structural metadata needed to provide a complete and reasonable rendition of the Intellectual
464
+ Entity.).freeze,
381
465
  "rdfs:seeAlso": "Object class definition".freeze,
382
466
  subClassOf: "premis:Object".freeze,
383
467
  type: "owl:Class".freeze,
384
468
  "vs:term_status": "stable".freeze
385
469
  term :RightsDocumentation,
386
- definition: %(Definition: A designation used to uniquely identify documentation supporting the specified rights within the repository system.).freeze,
470
+ definition: %(Definition: A designation used to uniquely
471
+ identify documentation supporting the specified rights within the repository
472
+ system.).freeze,
387
473
  subClassOf: term(
388
474
  maxCardinality: "1".freeze,
389
475
  onProperty: "premis:hasRightsDocumentationRole".freeze,
@@ -392,7 +478,8 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
392
478
  type: "owl:Class".freeze,
393
479
  "vs:term_status": "stable".freeze
394
480
  term :RightsGranted,
395
- definition: %(Definition: The action\(s\) that the granting agency has allowed the repository.).freeze,
481
+ definition: %(Definition: The action\(s\) that the granting
482
+ agency has allowed the repository.).freeze,
396
483
  subClassOf: [term(
397
484
  intersectionOf: list(term(
398
485
  cardinality: "1".freeze,
@@ -412,9 +499,12 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
412
499
  type: "owl:Class".freeze,
413
500
  "vs:term_status": "stable".freeze
414
501
  term :RightsStatement,
415
- comment: %(Extensions: In OWL one can define its own subclasses to the the RightsStatement class to denote OtherRightsInformation of the PREMIS data dictionary.).freeze,
416
- definition: %(Definition: Documentation of the repository's right to perform one or more acts.).freeze,
417
- "skos:scopeNote": "Usage Notes: This semantic unit is optional because in some cases rights may be unknown. Institutions are encouraged to record rights information when possible. Either rightsStatement or rightsExtension must be present if the Rights entity is included. The rightsStatement should be repeated when the act(s) described has more than one basis, or when different acts have different bases.".freeze,
502
+ comment: %(Extensions: In OWL one can define its own
503
+ subclasses to the the RightsStatement class to denote OtherRightsInformation of the PREMIS
504
+ data dictionary.).freeze,
505
+ definition: %(Definition: Documentation of the
506
+ repository's right to perform one or more acts.).freeze,
507
+ "skos:scopeNote": "Usage Notes: This semantic unit is optional\n because in some cases rights may be unknown. Institutions are encouraged to record rights\n information when possible. Either rightsStatement or rightsExtension must be present if the\n Rights entity is included. The rightsStatement should be repeated when the act(s) described\n has more than one basis, or when different acts have different bases.".freeze,
418
508
  subClassOf: ["dc:RightsStatement".freeze, "premis:PremisEntity".freeze, term(
419
509
  maxCardinality: "1".freeze,
420
510
  onProperty: "premis:hasApplicableDates".freeze,
@@ -427,9 +517,13 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
427
517
  type: "owl:Class".freeze,
428
518
  "vs:term_status": "stable".freeze
429
519
  term :Signature,
430
- definition: %(Definition: Information needed to use a digital signature to authenticate the signer of an object and/or the information contained in the object.).freeze,
431
- editorialNote: %(Rationale: A repository may have a policy of generating digital signatures for files on ingest, or may have a need to store and later validate incoming digital signatures.).freeze,
432
- "skos:scopeNote": "Usage Notes: Several of the semantic components of signatureInformation are taken from the W3C’s XML-Signature Syntax and Processing; see www.w3.org/TR/2002/REC-xmldsig-core-20020212/ for more information on the structure and application of these semantic units.".freeze,
520
+ definition: %(Definition: Information needed to use a
521
+ digital signature to authenticate the signer of an object and/or the information contained in
522
+ the object.).freeze,
523
+ editorialNote: %(Rationale: A repository may have a policy of
524
+ generating digital signatures for files on ingest, or may have a need to store and later
525
+ validate incoming digital signatures.).freeze,
526
+ "skos:scopeNote": "Usage Notes: Several of the semantic\n components of signatureInformation are taken from the W3C’s XML-Signature Syntax and\n Processing; see www.w3.org/TR/2002/REC-xmldsig-core-20020212/ for more information on the\n structure and application of these semantic units.".freeze,
433
527
  subClassOf: term(
434
528
  intersectionOf: list(term(
435
529
  cardinality: "1".freeze,
@@ -453,15 +547,20 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
453
547
  type: "owl:Class".freeze,
454
548
  "vs:term_status": "stable".freeze
455
549
  term :SignificantProperties,
456
- definition: %(Definition: Characteristics of a particular object subjectively determined to be important to maintain through preservation actions.).freeze,
457
- editorialNote: %(Rationale: Objects that have the same technical properties may still differ as to the properties that should be preserved for future presentation or use.).freeze,
458
- "skos:historyNote": "Creation / Maintenance Notes: Significant properties may pertain to all objects of a certain class; for example, the repository can decide that for all PDF files, only the content need be preserved. In other cases, for example, for media art, the significant properties may be unique to each individual object. Where values are unique, they must be supplied by the submitter or provided by the curatorial staff of the repository.".freeze,
459
- "skos:scopeNote": "Usage Notes: All of this semantic unit’s subunits are optional. At least one of the significantPropertiesValue and significantPropertiesExtension subunits must be present if this container is included or both may be used. Significant properties may be objective technical characteristics subjectively considered important, or subjectively determined characteristics. For example, a PDF may contain links that are not considered important and JavaScript that is considered important. Or future migrations of a TIFF image may require optimization for line clarity or for color; the option chosen would depend upon a curatorial judgment of the significant properties of the image. Listing significant properties implies that the repository plans to preserve these properties across time and requires them to acceptably survive preservation action; for example, to be maintained during emulation or after format migration. It also implies that the repository would note when preservation action results in modification of significant properties. In practice, significant properties might be used as measures of preservation success, as part of quality checking the results of a preservation action or evaluating the efficacy of a preservation method. For example, if the listed significant properties are not maintained after application of a particular preservation method, it may indicate a failure of the process or that the method is not well suited to the type of material. More experience with digital preservation is needed to determine the best ways of representing significant properties in general, and of representing modification of significant properties. The semantic units included in the significantProperties container aim to provide a flexible structure for describing significant properties, allowing general types of aspects, facets or attributes of an object to be declared and to be paired with specific significant details about the object pertaining to that aspect, facet or attribute. For example, some repositories may define significant properties for objects related to facets of content, appearance, structure, behavior, and context. Examples of facet:detail pairs in this case could include: significantPropertiesType = “content” significantPropertiesValue = “all textual content and images” significantPropertiesType = “behavior” significantPropertiesValue = “editable” Other repositories may choose to describe significant properties at a more granular attribute level; for example: significantPropertiesType = “page count” significantPropertiesValue = “7” significantPropertiesType = “page width” significantPropertiesValue = “210 mm” Each facet:detail pair should be contained in a separate, repeated significantProperties container. Further work on determining and describing significant properties may yield more detailed schemes to facilitate general description. Representing modification of significant properties as a result of preservation action also requires further work. One possible way involves the use of Object and Event information: Object A has significant properties volume and timing, which are recorded as significantProperties of A. In migrated version B, the timing is modified, which is noted in the eventOutcome of the migration event. Only volume is listed as a significant property of B.".freeze,
550
+ definition: %(Definition: Characteristics of a particular
551
+ object subjectively determined to be important to maintain through preservation
552
+ actions.).freeze,
553
+ editorialNote: %(Rationale: Objects that have the same
554
+ technical properties may still differ as to the properties that should be preserved for future
555
+ presentation or use.).freeze,
556
+ "skos:historyNote": "Creation / Maintenance Notes: Significant\n properties may pertain to all objects of a certain class; for example, the repository can\n decide that for all PDF files, only the content need be preserved. In other cases, for\n example, for media art, the significant properties may be unique to each individual object.\n Where values are unique, they must be supplied by the submitter or provided by the curatorial\n staff of the repository.".freeze,
557
+ "skos:scopeNote": "Usage Notes: All of this semantic unit’s\n subunits are optional. At least one of the significantPropertiesValue and\n significantPropertiesExtension subunits must be present if this container is included or both\n may be used. Significant properties may be objective technical characteristics subjectively\n considered important, or subjectively determined characteristics. For example, a PDF may\n contain links that are not considered important and JavaScript that is considered important.\n Or future migrations of a TIFF image may require optimization for line clarity or for color;\n the option chosen would depend upon a curatorial judgment of the significant properties of the\n image. Listing significant properties implies that the repository plans to preserve these\n properties across time and requires them to acceptably survive preservation action; for\n example, to be maintained during emulation or after format migration. It also implies that the\n repository would note when preservation action results in modification of significant\n properties. In practice, significant properties might be used as measures of preservation\n success, as part of quality checking the results of a preservation action or evaluating the\n efficacy of a preservation method. For example, if the listed significant properties are not\n maintained after application of a particular preservation method, it may indicate a failure of\n the process or that the method is not well suited to the type of material. More experience\n with digital preservation is needed to determine the best ways of representing significant\n properties in general, and of representing modification of significant properties. The\n semantic units included in the significantProperties container aim to provide a flexible\n structure for describing significant properties, allowing general types of aspects, facets or\n attributes of an object to be declared and to be paired with specific significant details\n about the object pertaining to that aspect, facet or attribute. For example, some repositories\n may define significant properties for objects related to facets of content, appearance,\n structure, behavior, and context. Examples of facet:detail pairs in this case could include:\n significantPropertiesType = “content” significantPropertiesValue = “all textual content and\n images” significantPropertiesType = “behavior” significantPropertiesValue = “editable” Other\n repositories may choose to describe significant properties at a more granular attribute level;\n for example: significantPropertiesType = “page count” significantPropertiesValue = “7”\n significantPropertiesType = “page width” significantPropertiesValue = “210 mm” Each\n facet:detail pair should be contained in a separate, repeated significantProperties container.\n Further work on determining and describing significant properties may yield more detailed\n schemes to facilitate general description. Representing modification of significant properties\n as a result of preservation action also requires further work. One possible way involves the\n use of Object and Event information: Object A has significant properties volume and timing,\n which are recorded as significantProperties of A. In migrated version B, the timing is\n modified, which is noted in the eventOutcome of the migration event. Only volume is listed as\n a significant property of B.".freeze,
460
558
  type: "owl:Class".freeze,
461
559
  "vs:term_status": "stable".freeze
462
560
  term :Software,
463
- definition: %(Definition: Software required to render or use the object.).freeze,
464
- "skos:historyNote": "Creation / Maintenance Notes: If recording this explicitly, many different software environments may apply; for example, a particular object such as a PDF file may be viewable by several versions of several applications running under several operating systems and operating system versions. Although at least one software environment should be recorded, it is not necessary to record them all and each repository will have to make its own decisions about which software environments to record. Also, what appears to the user as a single rendering program can have many dependencies, including system utilities, runtime libraries, and so on, which each might have their own dependencies in turn. As with environment, metadata may be more efficiently managed in conjunction with a format registry either internal or external to a repository. In the absence of a global mechanism, repositories may be forced to develop their own local “registries” relating format to software environment.".freeze,
561
+ definition: %(Definition: Software required to render or
562
+ use the object.).freeze,
563
+ "skos:historyNote": "Creation / Maintenance Notes: If recording\n this explicitly, many different software environments may apply; for example, a particular\n object such as a PDF file may be viewable by several versions of several applications running\n under several operating systems and operating system versions. Although at least one software\n environment should be recorded, it is not necessary to record them all and each repository\n will have to make its own decisions about which software environments to record. Also, what\n appears to the user as a single rendering program can have many dependencies, including system\n utilities, runtime libraries, and so on, which each might have their own dependencies in turn.\n As with environment, metadata may be more efficiently managed in conjunction with a format\n registry either internal or external to a repository. In the absence of a global mechanism,\n repositories may be forced to develop their own local “registries” relating format to software\n environment.".freeze,
465
564
  subClassOf: term(
466
565
  intersectionOf: list(term(
467
566
  cardinality: "1".freeze,
@@ -477,8 +576,9 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
477
576
  type: "owl:Class".freeze,
478
577
  "vs:term_status": "stable".freeze
479
578
  term :StatuteInformation,
480
- definition: %(Definition: Information about the statute allowing use of the object.).freeze,
481
- "skos:scopeNote": "Usage Notes: When rights basis is a statute, statuteInformation should be provided.".freeze,
579
+ definition: %(Definition: Information about the statute
580
+ allowing use of the object.).freeze,
581
+ "skos:scopeNote": "Usage Notes: When rights basis is a statute,\n statuteInformation should be provided.".freeze,
482
582
  subClassOf: ["premis:RightsStatement".freeze, term(
483
583
  intersectionOf: list(term(
484
584
  cardinality: "1".freeze,
@@ -494,9 +594,11 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
494
594
  type: "owl:Class".freeze,
495
595
  "vs:term_status": "stable".freeze
496
596
  term :Storage,
497
- definition: %(Definition: Information about how and where a file is stored in the storage system.).freeze,
498
- editorialNote: %(Rationale: It is necessary for a repository to associate the contentLocation with the storageMedium.).freeze,
499
- "skos:scopeNote": "Usage Notes: Normally there would be a single storage location and medium for an object, because an object in another location would be considered a different object. The storage composite should be repeated if there are two or more copies that are identical bit-wise and managed as a unit except for the medium on which they are stored. They must have a single objectIdentifier and be managed as a single object by the repository. Although this semantic unit is mandatory, both of its subunits are optional. At least one subunit (i.e. either contentLocation or storageMedium) must be present or both may be used.".freeze,
597
+ definition: %(Definition: Information about how and where
598
+ a file is stored in the storage system.).freeze,
599
+ editorialNote: %(Rationale: It is necessary for a repository
600
+ to associate the contentLocation with the storageMedium.).freeze,
601
+ "skos:scopeNote": "Usage Notes: Normally there would be a\n single storage location and medium for an object, because an object in another location would\n be considered a different object. The storage composite should be repeated if there are two or\n more copies that are identical bit-wise and managed as a unit except for the medium on which\n they are stored. They must have a single objectIdentifier and be managed as a single object by\n the repository. Although this semantic unit is mandatory, both of its subunits are optional.\n At least one subunit (i.e. either contentLocation or storageMedium) must be present or both\n may be used.".freeze,
500
602
  subClassOf: term(
501
603
  type: "owl:Class".freeze,
502
604
  unionOf: list(term(
@@ -512,8 +614,10 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
512
614
  type: "owl:Class".freeze,
513
615
  "vs:term_status": "stable".freeze
514
616
  term :TermOfGrant,
515
- definition: %(Definition: The time period for the permissions granted.).freeze,
516
- editorialNote: %(Rationale: The permission to preserve may be time bounded.).freeze,
617
+ definition: %(Definition: The time period for the
618
+ permissions granted.).freeze,
619
+ editorialNote: %(Rationale: The permission to preserve may be
620
+ time bounded.).freeze,
517
621
  subClassOf: ["premis:ApplicableDates".freeze, term(
518
622
  cardinality: "1".freeze,
519
623
  onProperty: "premis:hasStartDate".freeze,
@@ -522,8 +626,13 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
522
626
  type: "owl:Class".freeze,
523
627
  "vs:term_status": "stable".freeze
524
628
  term :TermOfRestriction,
525
- definition: %(Definition: The time period for the restriction granted.).freeze,
526
- editorialNote: %(Rationale: The current definition of termOfGrant is "time period for the permissions granted." This allows for expressing information about the rights granted, but some repositories may need to express timebounded restrictions like embargoes. If this is applicable startDate for the beginning of the embargo and endDate for the end of the embargo should be recorded.).freeze,
629
+ definition: %(Definition: The time period for the
630
+ restriction granted.).freeze,
631
+ editorialNote: %(Rationale: The current definition of
632
+ termOfGrant is "time period for the permissions granted." This allows for expressing
633
+ information about the rights granted, but some repositories may need to express timebounded
634
+ restrictions like embargoes. If this is applicable startDate for the beginning of the embargo
635
+ and endDate for the end of the embargo should be recorded.).freeze,
527
636
  subClassOf: ["premis:ApplicableDates".freeze, term(
528
637
  cardinality: "1".freeze,
529
638
  onProperty: "premis:hasStartDate".freeze,
@@ -534,8 +643,12 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
534
643
 
535
644
  # Property definitions
536
645
  property :hasAct,
537
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/actionsGranted ).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
538
- definition: %(Definition: The action the preservation repository is allowed to take.).freeze,
646
+ comment: [%(Data Constraint: Values are taken from the
647
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/actionsGranted ).freeze, %(Extensions: One can use its own SKOS
648
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
649
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
650
+ definition: %(Definition: The action the preservation
651
+ repository is allowed to take.).freeze,
539
652
  domain: "premis:RightsGranted".freeze,
540
653
  range: term(
541
654
  onProperty: "skos:inScheme".freeze,
@@ -545,35 +658,50 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
545
658
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
546
659
  "vs:term_status": "stable".freeze
547
660
  property :hasAgent,
548
- definition: %(Definition: link to the associated Agent.).freeze,
661
+ definition: %(Definition: link to the associated
662
+ Agent.).freeze,
549
663
  domain: term(
550
664
  type: "owl:Class".freeze,
551
665
  unionOf: list("premis:Event".freeze, "premis:RightsStatement".freeze)
552
666
  ),
553
- editorialNote: %(Rationale: Digital provenance requires often that relationships between agents and events are documented. The role of the associated agent may need to be documented. For this, a SKOS vocabulary can be used. The LOC will publish a vocabulary at http://id.loc.gov/, denoting the agent's role. These vocabulary will publish the concepts also as subproperties to the linkingAgent property, for denoting the role of the agent in the event or rightsstatement.).freeze,
667
+ editorialNote: %(Rationale: Digital provenance requires often
668
+ that relationships between agents and events are documented. The role of the associated agent
669
+ may need to be documented. For this, a SKOS vocabulary can be used. The LOC will publish a
670
+ vocabulary at http://id.loc.gov/, denoting the agent's role. These vocabulary will publish the
671
+ concepts also as subproperties to the linkingAgent property, for denoting the role of the
672
+ agent in the event or rightsstatement.).freeze,
554
673
  range: "premis:Agent".freeze,
555
674
  "rdfs:seeAlso": "Agent class definition".freeze,
556
675
  type: "owl:ObjectProperty".freeze,
557
676
  "vs:term_status": "testing".freeze
558
677
  property :hasAgentName,
559
678
  comment: %(Examples: Erik Owens, Pc).freeze,
560
- definition: %(Definition: A text string which could be used in addition to agentIdentifier to identify an agent.).freeze,
679
+ definition: %(Definition: A text string which could be
680
+ used in addition to agentIdentifier to identify an agent.).freeze,
561
681
  domain: "premis:Agent".freeze,
562
- editorialNote: %(Rationale: This semantic unit provides a more reader-friendly version of the agent identified by the agentIdentifier.).freeze,
682
+ editorialNote: %(Rationale: This semantic unit provides a
683
+ more reader-friendly version of the agent identified by the
684
+ agentIdentifier.).freeze,
563
685
  range: "xsd:string".freeze,
564
- "skos:scopeNote": "Usage Note: The value is not necessarily unique.".freeze,
686
+ "skos:scopeNote": "Usage Note: The value is not necessarily\n unique.".freeze,
565
687
  type: "owl:DatatypeProperty".freeze,
566
688
  "vs:term_status": "stable".freeze
567
689
  property :hasAgentNote,
568
- definition: %(Definition: Additional information about the agent.).freeze,
690
+ definition: %(Definition: Additional information about the
691
+ agent.).freeze,
569
692
  domain: "premis:Agent".freeze,
570
- editorialNote: %(Rationale: Additional information may be needed to describe or disambiguate the agent.).freeze,
693
+ editorialNote: %(Rationale: Additional information may be
694
+ needed to describe or disambiguate the agent.).freeze,
571
695
  range: "xsd:string".freeze,
572
696
  type: "owl:DatatypeProperty".freeze,
573
697
  "vs:term_status": "stable".freeze
574
698
  property :hasAgentType,
575
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/agentType ).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
576
- definition: %(Definition: A high-level characterization of the type of agent.).freeze,
699
+ comment: [%(Data Constraint: Values are taken from the
700
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/agentType ).freeze, %(Extensions: One can use its own SKOS
701
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
702
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
703
+ definition: %(Definition: A high-level characterization of
704
+ the type of agent.).freeze,
577
705
  domain: "premis:Agent".freeze,
578
706
  range: term(
579
707
  onProperty: "skos:inScheme".freeze,
@@ -585,30 +713,40 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
585
713
  property :hasApplicableDates,
586
714
  domain: "premis:RightsStatement".freeze,
587
715
  range: "premis:ApplicableDates".freeze,
588
- "rdfs:seeAlso": "ApplicableDates class definition".freeze,
716
+ "rdfs:seeAlso": "ApplicableDates class\n definition".freeze,
589
717
  type: "owl:ObjectProperty".freeze,
590
718
  "vs:term_status": "stable".freeze
591
719
  property :hasCompositionLevel,
592
- comment: [%(Data Constraints: Non-negative integers.).freeze, %(Examples: 0, 1, 2).freeze],
593
- definition: %(Definition: An indication of whether the object is subject to one or more processes of decoding or unbundling.).freeze,
720
+ comment: [%(Data Constraints: Non-negative
721
+ integers.).freeze, %(Examples: 0, 1, 2).freeze],
722
+ definition: %(Definition: An indication of whether the
723
+ object is subject to one or more processes of decoding or unbundling.).freeze,
594
724
  domain: "premis:ObjectCharacteristics".freeze,
595
- editorialNote: %(Rationale: A file or bitstream can be encoded with compression, encryption, etc., or bundled with other files or bitstreams into larger packages. Knowing the order in which these actions are taken is important if the original object or objects must be recovered.).freeze,
725
+ editorialNote: %(Rationale: A file or bitstream can be
726
+ encoded with compression, encryption, etc., or bundled with other files or bitstreams into
727
+ larger packages. Knowing the order in which these actions are taken is important if the
728
+ original object or objects must be recovered.).freeze,
596
729
  range: "xsd:int".freeze,
597
- "skos:historyNote": "Creation / Maintenance Notes: Composition level will generally be supplied by the repository, which should attempt to supply this value automatically. If the object was created by the repository, the creating routine knows the composition level and can supply this metadata. If the object is being ingested by the repository, repository programs will have to attempt to identify the composition level from the object itself or from externally supplied metadata.".freeze,
598
- "skos:scopeNote": "Usage Notes: A file or bitstream can be subject to multiple encodings that must be decoded in reverse order (highest to lowest). For example, file A may be compressed to create file B, which is encrypted to create file C. To recreate a copy of the base file A, one would have to unencrypt file C to create file B and then uncompress file B to create file A. A compositionLevel of zero indicates that the object is a base object and not subject to further decoding, while a level of 1 or higher indicates that one or more decodings must be applied. Numbering goes lowest to highest (first encoded = 0). 0 is base object; 1-n are subsequent encodings. Use 0 as the default if there is only one compositionLevel. When multiple file objects are bundled together as filestreams within a package file object (e.g., a ZIP file), the individual filestream objects are not composition levels of the package file object. They should be considered separate objects, each with their own composition levels. For example, two encrypted files zipped together and stored in an archive as one file object would be described as three separate objects, each with its own associated metadata. The storage location of the two inner objects would point to the ZIP file, but the ZIP file itself would have only a single composition level (of zero) whose format would be “zip.”".freeze,
730
+ "skos:historyNote": "Creation / Maintenance Notes: Composition\n level will generally be supplied by the repository, which should attempt to supply this value\n automatically. If the object was created by the repository, the creating routine knows the\n composition level and can supply this metadata. If the object is being ingested by the\n repository, repository programs will have to attempt to identify the composition level from\n the object itself or from externally supplied metadata.".freeze,
731
+ "skos:scopeNote": "Usage Notes: A file or bitstream can be\n subject to multiple encodings that must be decoded in reverse order (highest to lowest). For\n example, file A may be compressed to create file B, which is encrypted to create file C. To\n recreate a copy of the base file A, one would have to unencrypt file C to create file B and\n then uncompress file B to create file A. A compositionLevel of zero indicates that the object\n is a base object and not subject to further decoding, while a level of 1 or higher indicates\n that one or more decodings must be applied. Numbering goes lowest to highest (first encoded =\n 0). 0 is base object; 1-n are subsequent encodings. Use 0 as the default if there is only one\n compositionLevel. When multiple file objects are bundled together as filestreams within a\n package file object (e.g., a ZIP file), the individual filestream objects are not composition\n levels of the package file object. They should be considered separate objects, each with their\n own composition levels. For example, two encrypted files zipped together and stored in an\n archive as one file object would be described as three separate objects, each with its own\n associated metadata. The storage location of the two inner objects would point to the ZIP\n file, but the ZIP file itself would have only a single composition level (of zero) whose\n format would be “zip.”".freeze,
599
732
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
600
733
  "vs:term_status": "stable".freeze
601
734
  property :hasContentLocation,
602
735
  domain: "premis:Storage".freeze,
603
736
  range: "premis:ContentLocation".freeze,
604
- "rdfs:seeAlso": "Storage class definition and ContentLocation class definition".freeze,
737
+ "rdfs:seeAlso": "Storage class definition and\n ContentLocation class definition".freeze,
605
738
  type: ["owl:FunctionalProperty".freeze, "owl:InverseFunctionalProperty".freeze, "owl:ObjectProperty".freeze],
606
739
  "vs:term_status": "stable".freeze
607
740
  property :hasContentLocationType,
608
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/contentLocationType).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
609
- definition: %(Definition: The means of referencing the location of the content.).freeze,
741
+ comment: [%(Data Constraint: Values are taken from the
742
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/contentLocationType).freeze, %(Extensions: One can use its own SKOS
743
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
744
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
745
+ definition: %(Definition: The means of referencing the
746
+ location of the content.).freeze,
610
747
  domain: "premis:ContentLocation".freeze,
611
- editorialNote: %(Rationale: To understand the meaning of the value it is necessary to know what location scheme is used.).freeze,
748
+ editorialNote: %(Rationale: To understand the meaning of the
749
+ value it is necessary to know what location scheme is used.).freeze,
612
750
  range: term(
613
751
  onProperty: "skos:inScheme".freeze,
614
752
  "owl:hasValue": "http://id.loc.gov/vocabulary/preservation/contentLocationType".freeze,
@@ -617,24 +755,35 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
617
755
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
618
756
  "vs:term_status": "stable".freeze
619
757
  property :hasContentLocationValue,
620
- comment: %(Examples: http://wwasearch.loc.gov/107th/200212107035/http://house.gov/langevin/ \(file\), c:\apache2\htdocs\index.html \(file\), 64 [offset from start of file c:\apache2\htdocs\image\logo.gif] \(bitstream\)).freeze,
621
- definition: %(Definition: The reference to the location of the content used by the storage system.).freeze,
758
+ comment: %(Examples:
759
+ http://wwasearch.loc.gov/107th/200212107035/http://house.gov/langevin/ \(file\),
760
+ c:\apache2\htdocs\index.html \(file\), 64 [offset from start of file
761
+ c:\apache2\htdocs\image\logo.gif] \(bitstream\)).freeze,
762
+ definition: %(Definition: The reference to the location of
763
+ the content used by the storage system.).freeze,
622
764
  domain: "premis:ContentLocation".freeze,
623
765
  range: "xsd:string".freeze,
624
- "skos:scopeNote": "Usage Notes: This could be a fully qualified path and filename, or the information used by a resolution system (e.g., a handle) or the native information used by a storage management system. For a bitstream or filestream, this would probably be the reference point and offset of the starting position of the bitstream. It is up to the repository to determine the level of granularity that should be recorded.".freeze,
766
+ "skos:scopeNote": "Usage Notes: This could be a fully qualified\n path and filename, or the information used by a resolution system (e.g., a handle) or the\n native information used by a storage management system. For a bitstream or filestream, this\n would probably be the reference point and offset of the starting position of the bitstream. It\n is up to the repository to determine the level of granularity that should be\n recorded.".freeze,
625
767
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
626
768
  "vs:term_status": "stable".freeze
627
769
  property :hasCopyrightJurisdiction,
628
- comment: [%(Data Constraint: Values should be taken from ISO 3166.).freeze, %(Examples: us, de, be).freeze],
629
- definition: %(Definition: The country whose copyright laws apply.).freeze,
770
+ comment: [%(Data Constraint: Values should be taken
771
+ from ISO 3166.).freeze, %(Examples: us, de, be).freeze],
772
+ definition: %(Definition: The country whose copyright laws
773
+ apply.).freeze,
630
774
  domain: "premis:CopyrightInformation".freeze,
631
- editorialNote: %(Rationale: Copyright law can vary from country to country.).freeze,
775
+ editorialNote: %(Rationale: Copyright law can vary from
776
+ country to country.).freeze,
632
777
  range: "xsd:string".freeze,
633
778
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
634
779
  "vs:term_status": "stable".freeze
635
780
  property :hasCopyrightStatus,
636
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/copyrightStatus).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
637
- definition: %(Definition: A coded designation for the copyright status of the object at the time the rights statement is recorded.).freeze,
781
+ comment: [%(Data Constraint: Values are taken from the
782
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/copyrightStatus).freeze, %(Extensions: One can use its own SKOS
783
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
784
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
785
+ definition: %(Definition: A coded designation for the
786
+ copyright status of the object at the time the rights statement is recorded.).freeze,
638
787
  domain: "premis:CopyrightInformation".freeze,
639
788
  range: term(
640
789
  onProperty: "skos:inScheme".freeze,
@@ -644,8 +793,11 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
644
793
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
645
794
  "vs:term_status": "stable".freeze
646
795
  property :hasCopyrightStatusDeterminationDate,
647
- comment: [%(Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime).freeze, %(Example: 2001-10-26T19:32:52+00:00).freeze],
648
- definition: %(Definition: The date that the copyright status recorded in copyrightStatus was determined.).freeze,
796
+ comment: [%(Data Constraint: To aid machine processing,
797
+ value should use a structured form: xsd:dateTime).freeze, %(Example:
798
+ 2001-10-26T19:32:52+00:00).freeze],
799
+ definition: %(Definition: The date that the copyright
800
+ status recorded in copyrightStatus was determined.).freeze,
649
801
  domain: "premis:CopyrightInformation".freeze,
650
802
  range: "xsd:dateTime".freeze,
651
803
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
@@ -653,65 +805,81 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
653
805
  property :hasCreatingApplication,
654
806
  domain: "premis:ObjectCharacteristics".freeze,
655
807
  range: "premis:CreatingApplication".freeze,
656
- "rdfs:seeAlso": "ObjectCharacteristics class definition and CreatingApplication class definition".freeze,
808
+ "rdfs:seeAlso": "ObjectCharacteristics class definition and\n CreatingApplication class definition".freeze,
657
809
  type: "owl:ObjectProperty".freeze,
658
810
  "vs:term_status": "stable".freeze
659
811
  property :hasCreatingApplicationName,
660
812
  comment: %(Example: MSWord).freeze,
661
- definition: %(Definition: A designation for the name of the software program that created the object.).freeze,
813
+ definition: %(Definition: A designation for the name of
814
+ the software program that created the object.).freeze,
662
815
  domain: "premis:CreatingApplication".freeze,
663
816
  range: "xsd:string".freeze,
664
- "skos:scopeNote": "Usage Notes: The creatingApplication is the application that created the object in its current format, not the application that created the copy written to storage. For example, if a document is created by Microsoft Word and subsequently copied to archive storage by a repository’s Ingest program, the creatingApplication is Word, not the Ingest program.".freeze,
817
+ "skos:scopeNote": "Usage Notes: The creatingApplication is the\n application that created the object in its current format, not the application that created\n the copy written to storage. For example, if a document is created by Microsoft Word and\n subsequently copied to archive storage by a repository’s Ingest program, the\n creatingApplication is Word, not the Ingest program.".freeze,
665
818
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
666
819
  "vs:term_status": "stable".freeze
667
820
  property :hasCreatingApplicationVersion,
668
821
  comment: %(Example: 2000).freeze,
669
- definition: %(Definition: The version of the software program that created the object.).freeze,
822
+ definition: %(Definition: The version of the software
823
+ program that created the object.).freeze,
670
824
  domain: "premis:CreatingApplication".freeze,
671
825
  range: "xsd:string".freeze,
672
826
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
673
827
  "vs:term_status": "stable".freeze
674
828
  property :hasDateCreatedByApplication,
675
- comment: [%(Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime).freeze, %(Example: 2001-10-26T19:32:52+00:00).freeze],
676
- definition: %(Definition: The actual or approximate date and time the object was created.).freeze,
829
+ comment: [%(Data Constraint: To aid machine processing,
830
+ value should use a structured form: xsd:dateTime).freeze, %(Example:
831
+ 2001-10-26T19:32:52+00:00).freeze],
832
+ definition: %(Definition: The actual or approximate date
833
+ and time the object was created.).freeze,
677
834
  domain: "premis:CreatingApplication".freeze,
678
835
  range: "xsd:dateTime".freeze,
679
- "skos:scopeNote": "Usage Notes: Use the most precise date available. This is the date the object was created by the creating application, not the date any copy was made externally or by the repository. For example, if a file is created by Microsoft Word in 2001 and two copies are made in 2003, the dateCreatedByApplication of all three files is 2001. The date a file is written to storage can be recorded as an Event. If the object itself contains internal creation and modification dates, the modification date should be used as dateCreatedByApplication. If the application is a Web harvester capturing an object at a point of time, use for date captured.".freeze,
836
+ "skos:scopeNote": "Usage Notes: Use the most precise date\n available. This is the date the object was created by the creating application, not the date\n any copy was made externally or by the repository. For example, if a file is created by\n Microsoft Word in 2001 and two copies are made in 2003, the dateCreatedByApplication of all\n three files is 2001. The date a file is written to storage can be recorded as an Event. If the\n object itself contains internal creation and modification dates, the modification date should\n be used as dateCreatedByApplication. If the application is a Web harvester capturing an object\n at a point of time, use for date captured.".freeze,
680
837
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
681
838
  "vs:term_status": "stable".freeze
682
839
  property :hasDependency,
683
840
  domain: "premis:Environment".freeze,
684
841
  range: "premis:Dependency".freeze,
685
- "rdfs:seeAlso": "Environment class definition and Dependency class definition".freeze,
842
+ "rdfs:seeAlso": "Environment class definition and Dependency\n class definition".freeze,
686
843
  type: "owl:ObjectProperty".freeze,
687
844
  "vs:term_status": "stable".freeze
688
845
  property :hasDependencyName,
689
- comment: %(Example: Additional Element Set for Language Corpora).freeze,
690
- definition: %(Definition: A designation for a component or associated file needed by the representation or file.).freeze,
846
+ comment: %(Example: Additional Element Set for
847
+ Language Corpora).freeze,
848
+ definition: %(Definition: A designation for a component or
849
+ associated file needed by the representation or file.).freeze,
691
850
  domain: "premis:Dependency".freeze,
692
- editorialNote: %(Rationale: It may not be self-evident from the dependencyIdentifier what the name of the object actually is.).freeze,
851
+ editorialNote: %(Rationale: It may not be self-evident from
852
+ the dependencyIdentifier what the name of the object actually is.).freeze,
693
853
  range: "xsd:string".freeze,
694
854
  type: "owl:DatatypeProperty".freeze,
695
855
  "vs:term_status": "stable".freeze
696
856
  property :hasEndDate,
697
- comment: %(Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime).freeze,
698
- definition: %(Definition: The ending date of the permission granted.).freeze,
857
+ comment: %(Data Constraint: To aid machine processing,
858
+ value should use a structured form: xsd:dateTime).freeze,
859
+ definition: %(Definition: The ending date of the
860
+ permission granted.).freeze,
699
861
  domain: "premis:ApplicableDates".freeze,
700
862
  range: "xsd:dateTime".freeze,
701
- "skos:scopeNote": "Usage Notes: Use “0000-00-00T00:00:00+00:00for an open ended term of grant. Omit endDate if the ending date is unknown or the permission statement applies to many objects with different end dates.".freeze,
863
+ "skos:scopeNote": "Usage Notes: Use “0000-00-00T00:00:00+00:00”\n for an open ended term of grant. Omit endDate if the ending date is unknown or the permission\n statement applies to many objects with different end dates.".freeze,
702
864
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
703
865
  "vs:term_status": "stable".freeze
704
866
  property :hasEnvironment,
705
867
  domain: "premis:Object".freeze,
706
868
  range: "premis:Environment".freeze,
707
- "rdfs:seeAlso": "Object class definition and Environment class definition".freeze,
869
+ "rdfs:seeAlso": "Object class definition and Environment\n class definition".freeze,
708
870
  type: "owl:ObjectProperty".freeze,
709
871
  "vs:term_status": "stable".freeze
710
872
  property :hasEnvironmentCharacteristic,
711
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/environmentCharacteristic).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
712
- definition: %(Definition: An assessment of the extent to which the described environment supports its purpose.).freeze,
873
+ comment: [%(Data Constraint: Values are taken from the
874
+ SKOS vocabulary:
875
+ http://id.loc.gov/vocabulary/preservation/environmentCharacteristic).freeze, %(Extensions: One can use its own SKOS
876
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
877
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
878
+ definition: %(Definition: An assessment of the extent to
879
+ which the described environment supports its purpose.).freeze,
713
880
  domain: "premis:Environment".freeze,
714
- editorialNote: %(Rationale: If multiple environments are described, this element can help to distinguish among them.).freeze,
881
+ editorialNote: %(Rationale: If multiple environments are
882
+ described, this element can help to distinguish among them.).freeze,
715
883
  range: term(
716
884
  onProperty: "skos:inScheme".freeze,
717
885
  "owl:hasValue": "http://id.loc.gov/vocabulary/preservation/environmentCharacteristic".freeze,
@@ -720,20 +888,28 @@ The object class has three subclasses: Representation, File, and Bitstream.).fre
720
888
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
721
889
  "vs:term_status": "stable".freeze
722
890
  property :hasEnvironmentNote,
723
- comment: %(Example: This environment assumes that the PDF will be stored locally
724
- and used with a standalone PDF reader.).freeze,
725
- definition: %(Definition: Additional information about the environment.).freeze,
891
+ comment: %(Example: This environment assumes that the
892
+ PDF will be stored locally and used with a standalone PDF reader.).freeze,
893
+ definition: %(Definition: Additional information about the
894
+ environment.).freeze,
726
895
  domain: "premis:Environment".freeze,
727
- editorialNote: %(Rationale: There may be a need to give a textual description of the environment for additional explanation.).freeze,
896
+ editorialNote: %(Rationale: There may be a need to give a
897
+ textual description of the environment for additional explanation.).freeze,
728
898
  range: "xsd:string".freeze,
729
- "skos:scopeNote": "Usage Notes: This note could be used to record the context of the environment information. For example, if a file can be rendered through a PC client application or through a browser with a plug-in, this note could be used to identify which situation applies. The note should not be used for a textual description of environment information recorded more rigorously elsewhere.".freeze,
899
+ "skos:scopeNote": "Usage Notes: This note could be used to\n record the context of the environment information. For example, if a file can be rendered\n through a PC client application or through a browser with a plug-in, this note could be used\n to identify which situation applies. The note should not be used for a textual description of\n environment information recorded more rigorously elsewhere.".freeze,
730
900
  type: "owl:DatatypeProperty".freeze,
731
901
  "vs:term_status": "stable".freeze
732
902
  property :hasEnvironmentPurpose,
733
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/environmentPurpose).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
734
- definition: %(Definition: The use\(s\) supported by the specified environment.).freeze,
903
+ comment: [%(Data Constraint: Values are taken from the
904
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/environmentPurpose).freeze, %(Extensions: One can use its own SKOS
905
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
906
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
907
+ definition: %(Definition: The use\(s\) supported by the
908
+ specified environment.).freeze,
735
909
  domain: "premis:Environment".freeze,
736
- editorialNote: %(Rationale: Different environments can support different uses of objects. For example, the environment needed to edit and modify a file can be quite different than the environment needed to render it.).freeze,
910
+ editorialNote: %(Rationale: Different environments can
911
+ support different uses of objects. For example, the environment needed to edit and modify a
912
+ file can be quite different than the environment needed to render it.).freeze,
737
913
  range: term(
738
914
  onProperty: "skos:inScheme".freeze,
739
915
  "owl:hasValue": "http://id.loc.gov/vocabulary/preservation/environmentPurpose".freeze,
@@ -742,64 +918,82 @@ and used with a standalone PDF reader.).freeze,
742
918
  type: "owl:ObjectProperty".freeze,
743
919
  "vs:term_status": "stable".freeze
744
920
  property :hasEvent,
745
- definition: %(Definition: The event associated with the object or an agent.).freeze,
921
+ definition: %(Definition: The event associated with the
922
+ object or an agent.).freeze,
746
923
  domain: term(
747
924
  type: "owl:Class".freeze,
748
925
  unionOf: list("premis:Agent".freeze, "premis:Object".freeze)
749
926
  ),
750
927
  range: "premis:Event".freeze,
751
- "rdfs:seeAlso": "Object class definition, the Agent class Definition and Event class definition".freeze,
752
- "skos:scopeNote": "Usage Notes: Use to link to events that are not associated with relationships between objects, such as format validation, virus checking, etc.".freeze,
928
+ "rdfs:seeAlso": "Object class definition, the Agent class\n Definition and Event class definition".freeze,
929
+ "skos:scopeNote": "Usage Notes: Use to link to events that are\n not associated with relationships between objects, such as format validation, virus checking,\n etc.".freeze,
753
930
  type: "owl:ObjectProperty".freeze,
754
931
  "vs:term_status": "stable".freeze
755
932
  property :hasEventDateTime,
756
- comment: [%(Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime).freeze, %(Example: 2001-10-26T19:32:52+00:00).freeze],
757
- definition: %(Definition: The single date and time, or date and time range, at or during which the event occurred.).freeze,
933
+ comment: [%(Data Constraint: To aid machine processing,
934
+ value should use a structured form: xsd:dateTime).freeze, %(Example:
935
+ 2001-10-26T19:32:52+00:00).freeze],
936
+ definition: %(Definition: The single date and time, or
937
+ date and time range, at or during which the event occurred.).freeze,
758
938
  domain: "premis:Event".freeze,
759
939
  range: "xsd:dateTime".freeze,
760
- "skos:scopeNote": "Usage Notes: Recommended practice is to record the most specific time possible and to designate the time zone.".freeze,
940
+ "skos:scopeNote": "Usage Notes: Recommended practice is to\n record the most specific time possible and to designate the time zone.".freeze,
761
941
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
762
942
  "vs:term_status": "stable".freeze
763
943
  property :hasEventDetail,
764
- comment: %(Examples: Object permanently withdrawn by request of Caroline Hunt,
765
- Program=“MIGJP2JP2K”; version=“2.2”).freeze,
766
- definition: %(Definition: Additional information about the event.).freeze,
944
+ comment: %(Examples: Object permanently withdrawn by
945
+ request of Caroline Hunt, Program=“MIGJP2JP2K”; version=“2.2”).freeze,
946
+ definition: %(Definition: Additional information about the
947
+ event.).freeze,
767
948
  domain: "premis:Event".freeze,
768
949
  range: "xsd:string".freeze,
769
- "skos:scopeNote": "Usage Notes: eventDetail is not intended to be processed by machine. It may record any information about an event and/or point to information stored elsewhere.".freeze,
950
+ "skos:scopeNote": "Usage Notes: eventDetail is not intended to\n be processed by machine. It may record any information about an event and/or point to\n information stored elsewhere.".freeze,
770
951
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
771
952
  "vs:term_status": "stable".freeze
772
953
  property :hasEventOutcome,
773
- comment: [%(Data Constraint: Value should be taken from a controlled vocabulary.).freeze, %(Examples: 00 [a code meaning “action successfully completed”], CV-01 [a code meaning “checksum validated”]).freeze],
774
- definition: %(Definition: A categorization of the overall result of the event in terms of success, partial success, or failure.).freeze,
954
+ comment: [%(Data Constraint: Value should be taken from
955
+ a controlled vocabulary.).freeze, %(Examples: 00 [a code meaning “action
956
+ successfully completed”], CV-01 [a code meaning “checksum validated”]).freeze],
957
+ definition: %(Definition: A categorization of the overall
958
+ result of the event in terms of success, partial success, or failure.).freeze,
775
959
  domain: "premis:EventOutcomeInformation".freeze,
776
- editorialNote: %(Rationale: A coded way of representing the outcome of an event may be useful for machine processing and reporting. If, for example, a fixity check fails, the event record provides both an actionable and a permanent record.).freeze,
960
+ editorialNote: %(Rationale: A coded way of representing the
961
+ outcome of an event may be useful for machine processing and reporting. If, for example, a
962
+ fixity check fails, the event record provides both an actionable and a permanent
963
+ record.).freeze,
777
964
  range: "xsd:string".freeze,
778
- "skos:scopeNote": "Usage Notes: Recommended practice is to use a controlled vocabulary that a system can act upon automatically. More detail about the outcome may be recorded in eventOutcomeDetail. Recommended practice is to define events with sufficient granularity that each event has a single outcome.".freeze,
965
+ "skos:scopeNote": "Usage Notes: Recommended practice is to use\n a controlled vocabulary that a system can act upon automatically. More detail about the\n outcome may be recorded in eventOutcomeDetail. Recommended practice is to define events with\n sufficient granularity that each event has a single outcome.".freeze,
779
966
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
780
967
  "vs:term_status": "stable".freeze
781
968
  property :hasEventOutcomeDetail,
782
969
  domain: "premis:EventOutcomeInformation".freeze,
783
970
  range: "premis:EventOutcomeDetail".freeze,
784
- "rdfs:seeAlso": "EventOutcomeInformation class definition and EventOutcomeDetail class definition".freeze,
971
+ "rdfs:seeAlso": "EventOutcomeInformation class definition\n and EventOutcomeDetail class definition".freeze,
785
972
  type: "owl:ObjectProperty".freeze,
786
973
  "vs:term_status": "stable".freeze
787
974
  property :hasEventOutcomeDetailNote,
788
- comment: %(Examples: LZW compressed file, Non-standard tags found in header).freeze,
789
- definition: %(Definition: A detailed description of the result or product of the event in textual form.).freeze,
975
+ comment: %(Examples: LZW compressed file, Non-standard
976
+ tags found in header).freeze,
977
+ definition: %(Definition: A detailed description of the
978
+ result or product of the event in textual form.).freeze,
790
979
  domain: "premis:EventOutcomeDetail".freeze,
791
- editorialNote: %(Rationale: Additional information in textual form may be needed about the outcome of the event.).freeze,
980
+ editorialNote: %(Rationale: Additional information in textual
981
+ form may be needed about the outcome of the event.).freeze,
792
982
  range: "xsd:string".freeze,
793
983
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
794
984
  "vs:term_status": "stable".freeze
795
985
  property :hasEventOutcomeInformation,
796
986
  domain: "premis:Event".freeze,
797
987
  range: "premis:EventOutcomeInformation".freeze,
798
- "rdfs:seeAlso": "Event class definition and EventOutcomeInformation class definition".freeze,
988
+ "rdfs:seeAlso": "Event class definition and\n EventOutcomeInformation class definition".freeze,
799
989
  type: "owl:ObjectProperty".freeze,
800
990
  "vs:term_status": "stable".freeze
801
991
  property :hasEventRelatedAgent,
802
- comment: [%(Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.).freeze, %(This propety links a Event instance to an Agent instance. Via this property a distinction can be made in the linkingAgent properties based on the domain.).freeze],
992
+ comment: [%(Extensions: One can extend this
993
+ property to use more fine grained properties by defining the fine grained properties as
994
+ subproperties of this property.).freeze, %(This propety links a Event
995
+ instance to an Agent instance. Via this property a distinction can be made in the linkingAgent
996
+ properties based on the domain.).freeze],
803
997
  domain: "premis:Event".freeze,
804
998
  range: "premis:Agent".freeze,
805
999
  "rdfs:seeAlso": "http://id.loc.gov/vocabulary/preservation/eventRelatedAgentRole".freeze,
@@ -807,20 +1001,30 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
807
1001
  type: "owl:ObjectProperty".freeze,
808
1002
  "vs:term_status": "unstable".freeze
809
1003
  property :hasEventRelatedObject,
810
- comment: %(Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.).freeze,
811
- definition: %(Definition: Information about an object associated with an event.).freeze,
1004
+ comment: %(Extensions: One can extend this
1005
+ property to use more fine grained properties by defining the fine grained properties as
1006
+ subproperties of this property.).freeze,
1007
+ definition: %(Definition: Information about an object
1008
+ associated with an event.).freeze,
812
1009
  domain: "premis:Event".freeze,
813
- editorialNote: %(Rationale: Digital provenance often requires that relationships between objects and events are documented.).freeze,
1010
+ editorialNote: %(Rationale: Digital provenance often requires
1011
+ that relationships between objects and events are documented.).freeze,
814
1012
  range: "premis:Object".freeze,
815
- "rdfs:seeAlso": ["Event class definition and Object class definition".freeze, "http://id.loc.gov/vocabulary/preservation/eventRelatedObjectRole".freeze],
1013
+ "rdfs:seeAlso": ["Event class definition and Object class\n definition".freeze, "http://id.loc.gov/vocabulary/preservation/eventRelatedObjectRole".freeze],
816
1014
  subPropertyOf: "premis:hasObject".freeze,
817
1015
  type: "owl:ObjectProperty".freeze,
818
1016
  "vs:term_status": "stable".freeze
819
1017
  property :hasEventType,
820
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/eventType).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
821
- definition: %(Definition: A categorization of the nature of the event.).freeze,
1018
+ comment: [%(Data Constraint: Values are taken from the
1019
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/eventType).freeze, %(Extensions: One can use its own SKOS
1020
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1021
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1022
+ definition: %(Definition: A categorization of the nature
1023
+ of the event.).freeze,
822
1024
  domain: "premis:Event".freeze,
823
- editorialNote: %(Rationale: Categorizing events will aid the preservation repository in machine processing of event information, particularly in reporting.).freeze,
1025
+ editorialNote: %(Rationale: Categorizing events will aid the
1026
+ preservation repository in machine processing of event information, particularly in
1027
+ reporting.).freeze,
824
1028
  range: term(
825
1029
  onProperty: "skos:inScheme".freeze,
826
1030
  "owl:hasValue": "http://id.loc.gov/vocabulary/preservation/eventType".freeze,
@@ -831,7 +1035,7 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
831
1035
  property :hasFixity,
832
1036
  domain: "premis:ObjectCharacteristics".freeze,
833
1037
  range: "premis:Fixity".freeze,
834
- "rdfs:seeAlso": "ObjectCharacteristics class definition and Fixity class definition".freeze,
1038
+ "rdfs:seeAlso": "ObjectCharacteristics class definition and\n Fixity class definition".freeze,
835
1039
  type: ["owl:InverseFunctionalProperty".freeze, "owl:ObjectProperty".freeze],
836
1040
  "vs:term_status": "stable".freeze
837
1041
  property :hasFormat,
@@ -840,57 +1044,76 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
840
1044
  type: "owl:Class".freeze,
841
1045
  unionOf: list("premis:Format".freeze, "http://reference.data.gov.uk/technical-registry/file-format".freeze, "http://www.udfr.org/onto#AbstractFormat".freeze)
842
1046
  ),
843
- "rdfs:seeAlso": "ObjectCharacteristics class definition and Format class definition. Next to the premis:Format class this property can also link to a pronom:file-format or udfr:AbstractFormat .".freeze,
1047
+ "rdfs:seeAlso": "ObjectCharacteristics class definition and\n Format class definition. Next to the premis:Format class this property can also link to a\n pronom:file-format or udfr:AbstractFormat .".freeze,
844
1048
  type: "owl:ObjectProperty".freeze,
845
1049
  "vs:term_status": "stable".freeze
846
1050
  property :hasFormatDesignation,
847
1051
  domain: "premis:Format".freeze,
848
1052
  range: "premis:FormatDesignation".freeze,
849
- "rdfs:seeAlso": "Format class definition and FormatDesignation class definition".freeze,
1053
+ "rdfs:seeAlso": "Format class definition and\n FormatDesignation class definition".freeze,
850
1054
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
851
1055
  "vs:term_status": "stable".freeze
852
1056
  property :hasFormatName,
853
- comment: [%(Data Constraint: Value should be taken from a controlled vocabulary.).freeze, %(Examples: Text/sgml, image/tiff/geotiff, Adobe PDF, DES, PGP, base64, unknown, LaTex).freeze],
854
- definition: %(Definition: A designation of the format of the file or bitstream.).freeze,
1057
+ comment: [%(Data Constraint: Value should be taken from
1058
+ a controlled vocabulary.).freeze, %(Examples: Text/sgml, image/tiff/geotiff,
1059
+ Adobe PDF, DES, PGP, base64, unknown, LaTex).freeze],
1060
+ definition: %(Definition: A designation of the format of
1061
+ the file or bitstream.).freeze,
855
1062
  domain: "premis:FormatDesignation".freeze,
856
1063
  range: "xsd:string".freeze,
857
- "skos:scopeNote": "Usage Notes: For unidentified formats, formatName may be recorded as “unknown”.".freeze,
1064
+ "skos:scopeNote": "Usage Notes: For unidentified formats,\n formatName may be recorded as “unknown”.".freeze,
858
1065
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
859
1066
  "vs:term_status": "stable".freeze
860
1067
  property :hasFormatNote,
861
- comment: %(Examples: tentative identification, disjunction, multiple format identifications found).freeze,
862
- definition: %(Definition: Additional information about format.).freeze,
1068
+ comment: %(Examples: tentative identification,
1069
+ disjunction, multiple format identifications found).freeze,
1070
+ definition: %(Definition: Additional information about
1071
+ format.).freeze,
863
1072
  domain: "premis:Format".freeze,
864
- editorialNote: %(Rationale: Qualifying information may be needed to supplement format designation and registry information or record a status for identification.).freeze,
1073
+ editorialNote: %(Rationale: Qualifying information may be
1074
+ needed to supplement format designation and registry information or record a status for
1075
+ identification.).freeze,
865
1076
  range: "xsd:string".freeze,
866
- "skos:scopeNote": "Usage Notes: The formatNote may contain free text, a reference pointer, or a value from a controlled list.".freeze,
1077
+ "skos:scopeNote": "Usage Notes: The formatNote may contain free\n text, a reference pointer, or a value from a controlled list.".freeze,
867
1078
  type: "owl:DatatypeProperty".freeze,
868
1079
  "vs:term_status": "stable".freeze
869
1080
  property :hasFormatRegistry,
870
1081
  domain: "premis:Format".freeze,
871
1082
  range: "premis:FormatRegistry".freeze,
872
- "rdfs:seeAlso": "Format class definition and FormatRegistry class definition".freeze,
1083
+ "rdfs:seeAlso": "Format class definition and FormatRegistry\n class definition".freeze,
873
1084
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
874
1085
  "vs:term_status": "stable".freeze
875
1086
  property :hasFormatRegistryKey,
876
- comment: %(Examples: info:gdfr/fred/f/tiff, TIFF/6.0).freeze,
877
- definition: %(Definition: The unique key used to reference an entry for this format in a format registry.).freeze,
1087
+ comment: %(Examples: info:gdfr/fred/f/tiff,
1088
+ TIFF/6.0).freeze,
1089
+ definition: %(Definition: The unique key used to reference
1090
+ an entry for this format in a format registry.).freeze,
878
1091
  domain: "premis:FormatRegistry".freeze,
879
1092
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
880
1093
  "vs:term_status": "stable".freeze
881
1094
  property :hasFormatRegistryName,
882
- comment: %(Examples: PRONOM, www.nationalarchives.gov.uk/pronom, Representation Information Registry Repository, FRED: A format registry demonstration, release 0.07).freeze,
883
- definition: %(Definition: A designation identifying the referenced format registry.).freeze,
1095
+ comment: %(Examples: PRONOM,
1096
+ www.nationalarchives.gov.uk/pronom, Representation Information Registry Repository, FRED: A
1097
+ format registry demonstration, release 0.07).freeze,
1098
+ definition: %(Definition: A designation identifying the
1099
+ referenced format registry.).freeze,
884
1100
  domain: "premis:FormatRegistry".freeze,
885
1101
  range: "xsd:string".freeze,
886
- "skos:scopeNote": "Usage Notes: This can be a formal name, internally used name, or URI.".freeze,
1102
+ "skos:scopeNote": "Usage Notes: This can be a formal name,\n internally used name, or URI.".freeze,
887
1103
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
888
1104
  "vs:term_status": "stable".freeze
889
1105
  property :hasFormatRegistryRole,
890
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/formatRegistryRole).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
891
- definition: %(Definition: The purpose or expected use of the registry.).freeze,
1106
+ comment: [%(Data Constraint: Values are taken from the
1107
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/formatRegistryRole).freeze, %(Extensions: One can use its own SKOS
1108
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1109
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1110
+ definition: %(Definition: The purpose or expected use of
1111
+ the registry.).freeze,
892
1112
  domain: "premis:FormatRegistry".freeze,
893
- editorialNote: %(Rationale: The same format may be defined in different registries for different purposes. For example, one registry may give detailed format specifications while another has profile information. If multiple registries are recorded, this semantic unit can be used to distinguish among them.).freeze,
1113
+ editorialNote: %(Rationale: The same format may be defined in
1114
+ different registries for different purposes. For example, one registry may give detailed
1115
+ format specifications while another has profile information. If multiple registries are
1116
+ recorded, this semantic unit can be used to distinguish among them.).freeze,
894
1117
  range: term(
895
1118
  onProperty: "skos:inScheme".freeze,
896
1119
  "owl:hasValue": "http://id.loc.gov/vocabulary/preservation/formatRegistryRole".freeze,
@@ -900,39 +1123,53 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
900
1123
  "vs:term_status": "stable".freeze
901
1124
  property :hasFormatVersion,
902
1125
  comment: %(Examples: 6.0, 2003).freeze,
903
- definition: %(Definition: The version of the format named in formatName.).freeze,
1126
+ definition: %(Definition: The version of the format named
1127
+ in formatName.).freeze,
904
1128
  domain: "premis:FormatDesignation".freeze,
905
- editorialNote: %(Rationale: Many authority lists of format names are not granular enough to indicate version, for example, MIME Media types.).freeze,
1129
+ editorialNote: %(Rationale: Many authority lists of format
1130
+ names are not granular enough to indicate version, for example, MIME Media
1131
+ types.).freeze,
906
1132
  range: "xsd:string".freeze,
907
- "skos:scopeNote": "Usage Notes: If the format is versioned, formatVersion should be recorded. It can be either a numeric or chronological designation.".freeze,
1133
+ "skos:scopeNote": "Usage Notes: If the format is versioned,\n formatVersion should be recorded. It can be either a numeric or chronological\n designation.".freeze,
908
1134
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
909
1135
  "vs:term_status": "stable".freeze
910
1136
  property :hasHardware,
911
1137
  domain: "premis:Environment".freeze,
912
1138
  range: "premis:Hardware".freeze,
913
- "rdfs:seeAlso": "Environment class definition and Hardware class definition".freeze,
1139
+ "rdfs:seeAlso": "Environment class definition and Hardware\n class definition".freeze,
914
1140
  type: "owl:ObjectProperty".freeze,
915
1141
  "vs:term_status": "stable".freeze
916
1142
  property :hasHardwareName,
917
- comment: %(Examples: Intel Pentium III, 1 GB DRAM, Windows XPcompatible joystick).freeze,
918
- definition: %(Definition: Manufacturer, model, and version \(if applicable\) of the hardware.).freeze,
1143
+ comment: %(Examples: Intel Pentium III, 1 GB DRAM,
1144
+ Windows XPcompatible joystick).freeze,
1145
+ definition: %(Definition: Manufacturer, model, and version
1146
+ \(if applicable\) of the hardware.).freeze,
919
1147
  domain: "premis:Hardware".freeze,
920
1148
  range: "xsd:string".freeze,
921
- "skos:scopeNote": "Usage Notes: Include manufacturer when this helps to identify or disambiguate the product. Include version for firmware or other components where that information is pertinent.".freeze,
1149
+ "skos:scopeNote": "Usage Notes: Include manufacturer when this\n helps to identify or disambiguate the product. Include version for firmware or other\n components where that information is pertinent.".freeze,
922
1150
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
923
1151
  "vs:term_status": "stable".freeze
924
1152
  property :hasHardwareOtherInformation,
925
- comment: %(Examples: 32MB minimum, Required RAM for Apache is unknown).freeze,
926
- definition: %(Definition: Additional requirements or instructions related to the hardware referenced in hwName.).freeze,
1153
+ comment: %(Examples: 32MB minimum, Required RAM for
1154
+ Apache is unknown).freeze,
1155
+ definition: %(Definition: Additional requirements or
1156
+ instructions related to the hardware referenced in hwName.).freeze,
927
1157
  domain: "premis:Hardware".freeze,
928
- editorialNote: %(Rationale: For hardware, the amount of computing resource needed \(such as memory, storage, processor speed, etc.\) may need to be documented. In addition, more detailed instructions may be needed to install and/or operate the hardware.).freeze,
1158
+ editorialNote: %(Rationale: For hardware, the amount of
1159
+ computing resource needed \(such as memory, storage, processor speed, etc.\) may need to be
1160
+ documented. In addition, more detailed instructions may be needed to install and/or operate
1161
+ the hardware.).freeze,
929
1162
  range: "xsd:string".freeze,
930
- "skos:scopeNote": "Usage Notes: This could be an identifier or URI used to point to hardware documentation.".freeze,
1163
+ "skos:scopeNote": "Usage Notes: This could be an identifier or\n URI used to point to hardware documentation.".freeze,
931
1164
  type: "owl:DatatypeProperty".freeze,
932
1165
  "vs:term_status": "stable".freeze
933
1166
  property :hasHardwareType,
934
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/hardwareType).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
935
- definition: %(Definition: Class or category of the hardware.).freeze,
1167
+ comment: [%(Data Constraint: Values are taken from the
1168
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/hardwareType).freeze, %(Extensions: One can use its own SKOS
1169
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1170
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1171
+ definition: %(Definition: Class or category of the
1172
+ hardware.).freeze,
936
1173
  domain: "premis:Hardware".freeze,
937
1174
  range: term(
938
1175
  onProperty: "skos:inScheme".freeze,
@@ -946,35 +1183,49 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
946
1183
  type: "owl:Class".freeze,
947
1184
  unionOf: list("premis:Agent".freeze, "premis:Dependency".freeze, "premis:Event".freeze, "premis:LicenseInformation".freeze, "premis:Object".freeze, "premis:RightsDocumentation".freeze, "premis:RightsStatement".freeze)
948
1185
  ),
949
- "rdfs:seeAlso": "Identifier class definition".freeze,
1186
+ "rdfs:seeAlso": "Identifier class\n definition".freeze,
950
1187
  type: ["owl:InverseFunctionalProperty".freeze, "owl:ObjectProperty".freeze],
951
1188
  "vs:term_status": "stable".freeze
952
1189
  property :hasIdentifierType,
953
- comment: [%(Data Constraint: Value should be taken from controlled vocabulary.).freeze, %(Examples: DLC, DRS, hdl:4263537).freeze],
954
- definition: %(Definition: A designation of the domain within which the identifier is unique.).freeze,
1190
+ comment: [%(Data Constraint: Value should be taken from
1191
+ controlled vocabulary.).freeze, %(Examples: DLC, DRS,
1192
+ hdl:4263537).freeze],
1193
+ definition: %(Definition: A designation of the domain
1194
+ within which the identifier is unique.).freeze,
955
1195
  domain: "premis:Identifier".freeze,
956
- editorialNote: %(Rationale: Identifier values cannot be assumed to be unique across domains. The combination of identifierType and identifierValue should ensure uniqueness.).freeze,
1196
+ editorialNote: %(Rationale: Identifier values cannot be
1197
+ assumed to be unique across domains. The combination of identifierType and identifierValue
1198
+ should ensure uniqueness.).freeze,
957
1199
  range: "xsd:string".freeze,
958
- "skos:scopeNote": "Usage Notes: The type of the identifier may be implicit within the repository as long it can be explicitly communicated when the item is disseminated outside of it.".freeze,
1200
+ "skos:scopeNote": "Usage Notes: The type of the identifier may\n be implicit within the repository as long it can be explicitly communicated when the item is\n disseminated outside of it.".freeze,
959
1201
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
960
1202
  "vs:term_status": "stable".freeze
961
1203
  property :hasIdentifierValue,
962
- comment: [%(Defnition: The value of the Identifier.).freeze, %(Examples: 0000000312 \(Representation\), IU2440 \(File\), WAC1943.56 \(File\), http://nrs.harvard.edu/urn-3:FHCL.Loeb:sal \(File\), IU2440-1 \(Bitstream\)).freeze],
1204
+ comment: [%(Defnition: The value of the
1205
+ Identifier.).freeze, %(Examples: 0000000312 \(Representation\),
1206
+ IU2440 \(File\), WAC1943.56 \(File\), http://nrs.harvard.edu/urn-3:FHCL.Loeb:sal \(File\), IU2440-1
1207
+ \(Bitstream\)).freeze],
963
1208
  domain: "premis:Identifier".freeze,
964
1209
  range: "xsd:string".freeze,
965
1210
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
966
1211
  "vs:term_status": "stable".freeze
967
1212
  property :hasInhibitorKey,
968
- comment: %(Example: [DES decryption key]).freeze,
969
- definition: %(Definition: The decryption key or password.).freeze,
1213
+ comment: %(Example: [DES decryption
1214
+ key]).freeze,
1215
+ definition: %(Definition: The decryption key or
1216
+ password.).freeze,
970
1217
  domain: "premis:Inhibitors".freeze,
971
1218
  range: "xsd:string".freeze,
972
- "skos:scopeNote": "Usage Notes: The key should be provided if known. However, it is not advisable to actually store the inhibitorKey in plain text in an unsecure database.".freeze,
1219
+ "skos:scopeNote": "Usage Notes: The key should be provided if\n known. However, it is not advisable to actually store the inhibitorKey in plain text in an\n unsecure database.".freeze,
973
1220
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
974
1221
  "vs:term_status": "stable".freeze
975
1222
  property :hasInhibitorTarget,
976
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/inhibitorTarget).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
977
- definition: %(Definition: The content or function protected by the inhibitor.).freeze,
1223
+ comment: [%(Data Constraint: Values are taken from the
1224
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/inhibitorTarget).freeze, %(Extensions: One can use its own SKOS
1225
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1226
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1227
+ definition: %(Definition: The content or function
1228
+ protected by the inhibitor.).freeze,
978
1229
  domain: "premis:Inhibitors".freeze,
979
1230
  range: term(
980
1231
  onProperty: "skos:inScheme".freeze,
@@ -984,8 +1235,12 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
984
1235
  type: "owl:ObjectProperty".freeze,
985
1236
  "vs:term_status": "stable".freeze
986
1237
  property :hasInhibitorType,
987
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/inhibitorType).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
988
- definition: %(Definition: The inhibitor method employed.).freeze,
1238
+ comment: [%(Data Constraint: Values are taken from the
1239
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/inhibitorType).freeze, %(Extensions: One can use its own SKOS
1240
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1241
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1242
+ definition: %(Definition: The inhibitor method
1243
+ employed.).freeze,
989
1244
  domain: "premis:Inhibitors".freeze,
990
1245
  range: term(
991
1246
  onProperty: "skos:inScheme".freeze,
@@ -997,39 +1252,49 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
997
1252
  property :hasInhibitors,
998
1253
  domain: "premis:ObjectCharacteristics".freeze,
999
1254
  range: "premis:Inhibitors".freeze,
1000
- "rdfs:seeAlso": "ObjectCharacteristics class definition and Inhibitors class definition".freeze,
1255
+ "rdfs:seeAlso": "ObjectCharacteristics class definition and\n Inhibitors class definition".freeze,
1001
1256
  type: "owl:ObjectProperty".freeze,
1002
1257
  "vs:term_status": "stable".freeze
1003
1258
  property :hasIntellectualEntity,
1004
- definition: %(Definition: An intellectual entity associated with the object.).freeze,
1259
+ definition: %(Definition: An intellectual entity
1260
+ associated with the object.).freeze,
1005
1261
  domain: "premis:Object".freeze,
1006
1262
  range: "premis:IntellectualEntity".freeze,
1007
- "skos:scopeNote": "Usage Notes: Use to link to an intellectual entity that is related to the object. This may be a link to descriptive metadata that describes the intellectual entity or some other surrogate for it that can be referenced. This link will likely be to an identifier of an object that is at a higher conceptual level than the object for which the metadata is provided, for example, to a collection or parent object.".freeze,
1263
+ "skos:scopeNote": "Usage Notes: Use to link to an intellectual\n entity that is related to the object. This may be a link to descriptive metadata that\n describes the intellectual entity or some other surrogate for it that can be referenced. This\n link will likely be to an identifier of an object that is at a higher conceptual level than\n the object for which the metadata is provided, for example, to a collection or parent\n object.".freeze,
1008
1264
  type: "owl:ObjectProperty".freeze,
1009
1265
  "vs:term_status": "stable".freeze
1010
1266
  property :hasKeyInformation,
1011
1267
  domain: "premis:Signature".freeze,
1012
- "rdfs:seeAlso": "Signature class definition and KeyInformation class definition".freeze,
1268
+ "rdfs:seeAlso": "Signature class definition and\n KeyInformation class definition".freeze,
1013
1269
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
1014
1270
  "vs:term_status": "unstable".freeze
1015
1271
  property :hasLicenseTerms,
1016
- definition: %(Definition: Text describing the license or agreement by which permission was granted.).freeze,
1272
+ definition: %(Definition: Text describing the license or
1273
+ agreement by which permission was granted.).freeze,
1017
1274
  domain: "premis:LicenseInformation".freeze,
1018
1275
  range: "xsd:string".freeze,
1019
- "skos:scopeNote": "Usage Notes: This could contain the actual text of the license or agreement or a paraphrase or summary.".freeze,
1276
+ "skos:scopeNote": "Usage Notes: This could contain the actual\n text of the license or agreement or a paraphrase or summary.".freeze,
1020
1277
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1021
1278
  "vs:term_status": "stable".freeze
1022
1279
  property :hasMessageDigest,
1023
- comment: %(Example: 7c9b35da4f2ebd436f1cf88e5a39b3a257edf4a22be3c955ac49da2e2107b67a1924419563).freeze,
1024
- definition: %(Definition: The output of the message digest algorithm.).freeze,
1280
+ comment: %(Example:
1281
+ 7c9b35da4f2ebd436f1cf88e5a39b3a257edf4a22be3c955ac49da2e2107b67a1924419563).freeze,
1282
+ definition: %(Definition: The output of the message digest
1283
+ algorithm.).freeze,
1025
1284
  domain: "premis:Fixity".freeze,
1026
- editorialNote: %(Rationale: This must be stored so that it can be compared in future fixity checks.).freeze,
1285
+ editorialNote: %(Rationale: This must be stored so that it
1286
+ can be compared in future fixity checks.).freeze,
1027
1287
  range: "xsd:string".freeze,
1028
1288
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1029
1289
  "vs:term_status": "stable".freeze
1030
1290
  property :hasMessageDigestAlgorithm,
1031
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1032
- definition: %(Definition: The specific algorithm used to construct the message digest for the digital object.).freeze,
1291
+ comment: [%(Data Constraint: Values are taken from the
1292
+ SKOS vocabulary:
1293
+ http://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions).freeze, %(Extensions: One can use its own SKOS
1294
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1295
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1296
+ definition: %(Definition: The specific algorithm used to
1297
+ construct the message digest for the digital object.).freeze,
1033
1298
  domain: "premis:Fixity".freeze,
1034
1299
  range: term(
1035
1300
  onProperty: "skos:inScheme".freeze,
@@ -1040,24 +1305,40 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
1040
1305
  "vs:term_status": "stable".freeze
1041
1306
  property :hasMessageDigestOriginator,
1042
1307
  comment: %(Examples: DRS, A0000978).freeze,
1043
- definition: %(Definition: The agent that created the original message digest that is compared in a fixity check.).freeze,
1308
+ definition: %(Definition: The agent that created the
1309
+ original message digest that is compared in a fixity check.).freeze,
1044
1310
  domain: "premis:Fixity".freeze,
1045
- editorialNote: %(Rationale: A preservation repository may ingest files that have had message digests calculated by the submitter; checking these ensures that the file as received is the same as the file as sent. The repository may also ingest files that do not have message digests, and so must calculate the initial value upon ingest. It can be useful to know who calculated the initial value of the message digest.).freeze,
1311
+ editorialNote: %(Rationale: A preservation repository may
1312
+ ingest files that have had message digests calculated by the submitter; checking these ensures
1313
+ that the file as received is the same as the file as sent. The repository may also ingest
1314
+ files that do not have message digests, and so must calculate the initial value upon ingest.
1315
+ It can be useful to know who calculated the initial value of the message
1316
+ digest.).freeze,
1046
1317
  range: "xsd:string".freeze,
1047
- "skos:historyNote": "Creation / Maintenance Notes: If the calculation of the initial message digest is treated by the repository as an Event, this information could be obtained from an Event record.".freeze,
1048
- "skos:scopeNote": "Usage Notes: The originator of the message digest could be represented by a string representing the agent (e.g., “NRS” referring to the archive itself) or a pointer to an agent description (e.g., “A0000987” taken here to be an agentIdentifierValue).".freeze,
1318
+ "skos:historyNote": "Creation / Maintenance Notes: If the\n calculation of the initial message digest is treated by the repository as an Event, this\n information could be obtained from an Event record.".freeze,
1319
+ "skos:scopeNote": "Usage Notes: The originator of the message\n digest could be represented by a string representing the agent (e.g., “NRS” referring to the\n archive itself) or a pointer to an agent description (e.g., “A0000987” taken here to be an\n agentIdentifierValue).".freeze,
1049
1320
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1050
1321
  "vs:term_status": "stable".freeze
1051
1322
  property :hasObject,
1052
- comment: %(Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.).freeze,
1053
- definition: %(Definition: Information about an object associated with an event or rightsstatement.).freeze,
1323
+ comment: %(Extensions: One can extend this
1324
+ property to use more fine grained properties by defining the fine grained properties as
1325
+ subproperties of this property.).freeze,
1326
+ definition: %(Definition: Information about an object
1327
+ associated with an event or rightsstatement.).freeze,
1054
1328
  domain: term(
1055
1329
  type: "owl:Class".freeze,
1056
1330
  unionOf: list("premis:Event".freeze, "premis:RightsStatement".freeze)
1057
1331
  ),
1058
- editorialNote: %(Rationale: Digital provenance often requires that relationships between objects and events are documented. / Rights statements must be associated with the objects to which they pertain, either by linking from the rights statement to the object\(s\) or by linking from the object\(s\) to the rights statement. This provides the mechanism for the link from the rights statement to an object. For denoting the role of the object, when related to an event,one can extend this ontology be defining your own subproperties, such as those given by http://id.loc.gov/vocabulary/preservation/eventRelatedObjectRole.).freeze,
1332
+ editorialNote: %(Rationale: Digital provenance often requires
1333
+ that relationships between objects and events are documented. / Rights statements must be
1334
+ associated with the objects to which they pertain, either by linking from the rights statement
1335
+ to the object\(s\) or by linking from the object\(s\) to the rights statement. This provides the
1336
+ mechanism for the link from the rights statement to an object. For denoting the role of the
1337
+ object, when related to an event,one can extend this ontology be defining your own
1338
+ subproperties, such as those given by
1339
+ http://id.loc.gov/vocabulary/preservation/eventRelatedObjectRole.).freeze,
1059
1340
  range: "premis:Object".freeze,
1060
- "rdfs:seeAlso": ["Event and RightsStatement class definition and Object class definition".freeze, "http://id.loc.gov/vocabulary/preservation/eventRelatedObjectRole".freeze],
1341
+ "rdfs:seeAlso": ["Event and RightsStatement class definition\n and Object class definition".freeze, "http://id.loc.gov/vocabulary/preservation/eventRelatedObjectRole".freeze],
1061
1342
  type: "owl:ObjectProperty".freeze,
1062
1343
  "vs:term_status": "stable".freeze
1063
1344
  property :hasObjectCharacteristics,
@@ -1066,20 +1347,25 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
1066
1347
  unionOf: list("premis:Bitstream".freeze, "premis:File".freeze)
1067
1348
  ),
1068
1349
  range: "premis:ObjectCharacteristics".freeze,
1069
- "rdfs:seeAlso": "Object class definition and ObjectCharacteristics class definition".freeze,
1350
+ "rdfs:seeAlso": "Object class definition and\n ObjectCharacteristics class definition".freeze,
1070
1351
  type: ["owl:InverseFunctionalProperty".freeze, "owl:ObjectProperty".freeze],
1071
1352
  "vs:term_status": "stable".freeze
1072
1353
  property :hasOriginalName,
1073
1354
  comment: %(Example: N419.pdf).freeze,
1074
- definition: %(Definition: The name of the object as submitted to or harvested by the repository, before any renaming by the repository.).freeze,
1355
+ definition: %(Definition: The name of the object as
1356
+ submitted to or harvested by the repository, before any renaming by the
1357
+ repository.).freeze,
1075
1358
  domain: term(
1076
1359
  type: "owl:Class".freeze,
1077
1360
  unionOf: list("premis:File".freeze, "premis:Representation".freeze)
1078
1361
  ),
1079
- editorialNote: %(Rationale: The name used within the preservation repository may not be known outside of the repository. A depositor might need to request a file by its original name. Also, the repository may need to reconstruct internal links for dissemination.).freeze,
1362
+ editorialNote: %(Rationale: The name used within the
1363
+ preservation repository may not be known outside of the repository. A depositor might need to
1364
+ request a file by its original name. Also, the repository may need to reconstruct internal
1365
+ links for dissemination.).freeze,
1080
1366
  range: "xsd:string".freeze,
1081
- "skos:historyNote": "Creation / Maintenance Notes: This value would always be supplied to the repository by the submitter or harvesting application. How much of the file path to preserve would be up to the repository.".freeze,
1082
- "skos:scopeNote": "Usage Notes: This is the name of the object as designated in the Submission Information Package (SIP). The object may have other names in different contexts. When two repositories are exchanging content, it would be important for the receiving repository to know and record the name of the representation at the originating repository. In the case of representations, this may be a directory name.".freeze,
1367
+ "skos:historyNote": "Creation / Maintenance Notes: This value\n would always be supplied to the repository by the submitter or harvesting application. How\n much of the file path to preserve would be up to the repository.".freeze,
1368
+ "skos:scopeNote": "Usage Notes: This is the name of the object\n as designated in the Submission Information Package (SIP). The object may have other names in\n different contexts. When two repositories are exchanging content, it would be important for\n the receiving repository to know and record the name of the representation at the originating\n repository. In the case of representations, this may be a directory name.".freeze,
1083
1369
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1084
1370
  "vs:term_status": "stable".freeze
1085
1371
  property :hasPreservationLevel,
@@ -1088,31 +1374,49 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
1088
1374
  unionOf: list("premis:File".freeze, "premis:Representation".freeze)
1089
1375
  ),
1090
1376
  range: "premis:PreservationLevel".freeze,
1091
- "rdfs:seeAlso": "Object class definition and PreservationLevel class definition".freeze,
1377
+ "rdfs:seeAlso": "Object class definition and\n PreservationLevel class definition".freeze,
1092
1378
  type: "owl:ObjectProperty".freeze,
1093
1379
  "vs:term_status": "stable".freeze
1094
1380
  property :hasPreservationLevelDateAssigned,
1095
- comment: [%(Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime).freeze, %(Examples: 2001-10-26T19:32:52+00:00).freeze],
1096
- definition: %(Definition: The date, or date and time, when a particular preservationLevelValue was assigned to the object.).freeze,
1381
+ comment: [%(Data Constraint: To aid machine processing,
1382
+ value should use a structured form: xsd:dateTime).freeze, %(Examples:
1383
+ 2001-10-26T19:32:52+00:00).freeze],
1384
+ definition: %(Definition: The date, or date and time, when
1385
+ a particular preservationLevelValue was assigned to the object.).freeze,
1097
1386
  domain: "premis:PreservationLevel".freeze,
1098
- editorialNote: %(Rationale: The preservationLevel applicable to an object is expected to be reviewed and changed over time, in response to changes in repository preservation requirements, policies, or capabilities relevant to the object. The date that the current preservationLevelValue was assigned aids review of decisions.).freeze,
1387
+ editorialNote: %(Rationale: The preservationLevel applicable
1388
+ to an object is expected to be reviewed and changed over time, in response to changes in
1389
+ repository preservation requirements, policies, or capabilities relevant to the object. The
1390
+ date that the current preservationLevelValue was assigned aids review of
1391
+ decisions.).freeze,
1099
1392
  range: "xsd:dateTime".freeze,
1100
1393
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1101
1394
  "vs:term_status": "stable".freeze
1102
1395
  property :hasPreservationLevelRationale,
1103
- comment: %(Examples: user pays, legislation, defective file, bit-level preservation only available for this format).freeze,
1104
- definition: %(Definition: The reason a particular preservationLevelValue was applied to the object.).freeze,
1396
+ comment: %(Examples: user pays, legislation, defective
1397
+ file, bit-level preservation only available for this format).freeze,
1398
+ definition: %(Definition: The reason a particular
1399
+ preservationLevelValue was applied to the object.).freeze,
1105
1400
  domain: "premis:PreservationLevel".freeze,
1106
- editorialNote: %(Rationale: Application of a particular preservationLevelValue may require justification, especially if it differs from that usually applied according to repository policy.).freeze,
1401
+ editorialNote: %(Rationale: Application of a particular
1402
+ preservationLevelValue may require justification, especially if it differs from that usually
1403
+ applied according to repository policy.).freeze,
1107
1404
  range: "xsd:string".freeze,
1108
- "skos:scopeNote": "Usage Notes: This optional semantic unit records the reason for applying the preservationLevelValue. This information can be particularly important when the assigned preservationLevelValue differs from usual repository policy. For example, a repository may normally assign a preservationLevelValue of “full preservation” for JPEG2000 files, but detects that a particular file is defective. This may mean that the repository’s preservation strategy for JPEG2000 may not be effective for this particular file, so the repository may assign a preservationLevelValue of “bit-level preservation” to this file, recording “defective file” as the rationale. Similarly, legislative requirements or contractual agreements may require a higher level of preservation to be assigned to a particular object than would be assigned to that class of object according to usual policy. In this case, the rationale for the assignment may be recorded as “legislation” or “user pays”, for example. preservationLevelRationale may be repeated if more than one reason needs to be recorded.".freeze,
1405
+ "skos:scopeNote": "Usage Notes: This optional semantic unit\n records the reason for applying the preservationLevelValue. This information can be\n particularly important when the assigned preservationLevelValue differs from usual repository\n policy. For example, a repository may normally assign a preservationLevelValue of “full\n preservation” for JPEG2000 files, but detects that a particular file is defective. This may\n mean that the repository’s preservation strategy for JPEG2000 may not be effective for this\n particular file, so the repository may assign a preservationLevelValue of “bit-level\n preservation” to this file, recording “defective file” as the rationale. Similarly,\n legislative requirements or contractual agreements may require a higher level of preservation\n to be assigned to a particular object than would be assigned to that class of object according\n to usual policy. In this case, the rationale for the assignment may be recorded as\n “legislation” or “user pays”, for example. preservationLevelRationale may be repeated if more\n than one reason needs to be recorded.".freeze,
1109
1406
  type: "owl:DatatypeProperty".freeze,
1110
1407
  "vs:term_status": "stable".freeze
1111
1408
  property :hasPreservationLevelRole,
1112
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/preservationLevelRole).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1113
- definition: %(Definition: A value indicating the context in which a set of preservation options is applicable.).freeze,
1409
+ comment: [%(Data Constraint: Values are taken from the
1410
+ SKOS vocabulary:
1411
+ http://id.loc.gov/vocabulary/preservation/preservationLevelRole).freeze, %(Extensions: One can use its own SKOS
1412
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1413
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1414
+ definition: %(Definition: A value indicating the context
1415
+ in which a set of preservation options is applicable.).freeze,
1114
1416
  domain: "premis:PreservationLevel".freeze,
1115
- editorialNote: %(Rationale: Repositories may assign preservationLevelValues in different contexts which must be differentiated, and may need to record more than one context.).freeze,
1417
+ editorialNote: %(Rationale: Repositories may assign
1418
+ preservationLevelValues in different contexts which must be differentiated, and may need to
1419
+ record more than one context.).freeze,
1116
1420
  range: term(
1117
1421
  onProperty: "skos:inScheme".freeze,
1118
1422
  "owl:hasValue": "http://id.loc.gov/vocabulary/preservation/preservationLevelRole".freeze,
@@ -1121,37 +1425,62 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
1121
1425
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
1122
1426
  "vs:term_status": "stable".freeze
1123
1427
  property :hasPreservationLevelValue,
1124
- comment: [%(Data Constraint: Value should be taken from a controlled vocabulary.).freeze, %(Examples: bit-level, full, fully supported with future migrations \(File\), 0).freeze],
1125
- definition: %(Definition: A value indicating the set of preservation functions expected to be applied to the object.).freeze,
1428
+ comment: [%(Data Constraint: Value should be taken from
1429
+ a controlled vocabulary.).freeze, %(Examples: bit-level, full, fully supported
1430
+ with future migrations \(File\), 0).freeze],
1431
+ definition: %(Definition: A value indicating the set of
1432
+ preservation functions expected to be applied to the object.).freeze,
1126
1433
  domain: "premis:PreservationLevel".freeze,
1127
- editorialNote: %(Rationale: Some preservation repositories will offer multiple preservation options depending on factors such as the value or uniqueness of the material, the “preservability” of the format, the amount the customer is willing to pay, etc.).freeze,
1434
+ editorialNote: %(Rationale: Some preservation repositories
1435
+ will offer multiple preservation options depending on factors such as the value or uniqueness
1436
+ of the material, the “preservability” of the format, the amount the customer is willing to
1437
+ pay, etc.).freeze,
1128
1438
  range: "xsd:string".freeze,
1129
- "skos:historyNote": "Creation / Maintenance Notes: The preservation level may be assigned by the repository or requested by the depositor and submitted as metadata.".freeze,
1130
- "skos:scopeNote": "Usage Notes: Only one preservationLevelValue may be recorded per preservationLevel container. If a further preservationLevelValue applies to the object in a different context, a separate preservationLevel container should be repeated.".freeze,
1439
+ "skos:historyNote": "Creation / Maintenance Notes: The\n preservation level may be assigned by the repository or requested by the depositor and\n submitted as metadata.".freeze,
1440
+ "skos:scopeNote": "Usage Notes: Only one preservationLevelValue\n may be recorded per preservationLevel container. If a further preservationLevelValue applies\n to the object in a different context, a separate preservationLevel container should be\n repeated.".freeze,
1131
1441
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1132
1442
  "vs:term_status": "stable".freeze
1133
1443
  property :hasRelatedObject,
1134
- definition: %(Definition: This property related to all object belonging to a RelatedObjectIdentification to describe the related objects as an aggregation.).freeze,
1444
+ definition: %(Definition: This property related to all
1445
+ object belonging to a RelatedObjectIdentification to describe the related objects as an
1446
+ aggregation.).freeze,
1135
1447
  domain: "premis:RelatedObjectIdentification".freeze,
1136
1448
  range: "premis:Object".freeze,
1137
1449
  type: "owl:ObjectProperty".freeze,
1138
1450
  "vs:term_status": "stable".freeze
1139
1451
  property :hasRelatedObjectSequence,
1140
- definition: %(Definition: The order of the related object relative to other objects with the same type of relationship.).freeze,
1452
+ definition: %(Definition: The order of the related object
1453
+ relative to other objects with the same type of relationship.).freeze,
1141
1454
  domain: "premis:RelatedObjectIdentification".freeze,
1142
- editorialNote: %(Rationale: This semantic unit is particularly useful for structural relationships. In order to reconstruct a representation, it may be necessary to know the order of components with sibling or part-whole relationships. For example, to render a page-image book, it is necessary to know the order of files representing pages.).freeze,
1455
+ editorialNote: %(Rationale: This semantic unit is
1456
+ particularly useful for structural relationships. In order to reconstruct a representation, it
1457
+ may be necessary to know the order of components with sibling or part-whole relationships. For
1458
+ example, to render a page-image book, it is necessary to know the order of files representing
1459
+ pages.).freeze,
1143
1460
  range: "xsd:string".freeze,
1144
1461
  type: "owl:DatatypeProperty".freeze,
1145
1462
  "vs:term_status": "stable".freeze
1146
1463
  property :hasRelatedStatuteInformation,
1147
- definition: %(Definition: This property is used to relate certain StatuteInformation instances. The rationale for this is that in the PREMIS data dictionary, a RightsStatement instance can consist of several StatuteInformation instances. In the PREMIS OWL ontology, the StatuteInformation class is subclassed to RightsStatement. The restore the relation between the grouped StatuteInformation instances of a RightsStatement of the PREMIS data dictionary, this property is used is PREMIS OWL.).freeze,
1464
+ definition: %(Definition: This property is used to relate
1465
+ certain StatuteInformation instances. The rationale for this is that in the PREMIS data
1466
+ dictionary, a RightsStatement instance can consist of several StatuteInformation instances. In
1467
+ the PREMIS OWL ontology, the StatuteInformation class is subclassed to RightsStatement. The
1468
+ restore the relation between the grouped StatuteInformation instances of a RightsStatement of
1469
+ the PREMIS data dictionary, this property is used is PREMIS OWL.).freeze,
1148
1470
  domain: "premis:StatuteInformation".freeze,
1149
1471
  range: "premis:StatuteInformation".freeze,
1150
1472
  type: "owl:ObjectProperty".freeze,
1151
1473
  "vs:term_status": "stable".freeze
1152
1474
  property :hasRelationship,
1153
- comment: [%(Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.).freeze, %(The LOC will provide a SKOS vocabulary, where the concepts can also be used as object properties at http://id.loc.gov/. These relationships will capture the relationship type and subtype. One can define its own relationships, but for interoperability reasons, these should be linked to or made a subproperty of the properties of the LOC vocabulary.).freeze],
1154
- definition: %(Definition: This property links one object to one or more other objects.).freeze,
1475
+ comment: [%(Extensions: One can extend this
1476
+ property to use more fine grained properties by defining the fine grained properties as
1477
+ subproperties of this property.).freeze, %(The LOC will provide a SKOS
1478
+ vocabulary, where the concepts can also be used as object properties at http://id.loc.gov/.
1479
+ These relationships will capture the relationship type and subtype. One can define its own
1480
+ relationships, but for interoperability reasons, these should be linked to or made a
1481
+ subproperty of the properties of the LOC vocabulary.).freeze],
1482
+ definition: %(Definition: This property
1483
+ links one object to one or more other objects.).freeze,
1155
1484
  domain: "premis:Object".freeze,
1156
1485
  range: term(
1157
1486
  type: "owl:Class".freeze,
@@ -1161,8 +1490,11 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
1161
1490
  type: "owl:ObjectProperty".freeze,
1162
1491
  "vs:term_status": "testing".freeze
1163
1492
  property :hasRestriction,
1164
- comment: %(Examples: No more than three, Allowed only after one year of archival retention has elapsed, Rightsholder must be notified after completion of act).freeze,
1165
- definition: %(Definition: A condition or limitation on the act.).freeze,
1493
+ comment: %(Examples: No more than three, Allowed only
1494
+ after one year of archival retention has elapsed, Rightsholder must be notified after
1495
+ completion of act).freeze,
1496
+ definition: %(Definition: A condition or limitation on the
1497
+ act.).freeze,
1166
1498
  domain: "premis:RightsGranted".freeze,
1167
1499
  range: "xsd:string".freeze,
1168
1500
  type: "owl:DatatypeProperty".freeze,
@@ -1170,32 +1502,43 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
1170
1502
  property :hasRightsDocumentation,
1171
1503
  domain: "premis:RightsStatement".freeze,
1172
1504
  range: "premis:RightsDocumentation".freeze,
1173
- "rdfs:seeAlso": "RiightsDocumentation class definition".freeze,
1505
+ "rdfs:seeAlso": "RiightsDocumentation class\n definition".freeze,
1174
1506
  type: "owl:ObjectProperty".freeze,
1175
1507
  "vs:term_status": "stable".freeze
1176
1508
  property :hasRightsDocumentationRole,
1177
- definition: %(Definition: This property denotes the role of the related documentation. The value must be taken from a skos vocabulary. A value indicating the purpose or expected use of the documentation being identified.).freeze,
1509
+ definition: %(Definition: This property denotes the role
1510
+ of the related documentation. The value must be taken from a skos vocabulary. A value
1511
+ indicating the purpose or expected use of the documentation being
1512
+ identified.).freeze,
1178
1513
  domain: "premis:RightsDocumentation".freeze,
1179
- editorialNote: %(Rationale: This information distinguishes the purpose of the supporting documentation especially when there are multiple documentation identifiers.).freeze,
1514
+ editorialNote: %(Rationale: This
1515
+ information distinguishes the purpose of the supporting documentation especially when there
1516
+ are multiple documentation identifiers.).freeze,
1180
1517
  range: "skos:Concept".freeze,
1181
1518
  type: "owl:ObjectProperty".freeze,
1182
1519
  "vs:term_status": "stable".freeze
1183
1520
  property :hasRightsGranted,
1184
1521
  domain: "premis:RightsStatement".freeze,
1185
1522
  range: "premis:RightsGranted".freeze,
1186
- "rdfs:seeAlso": "RightsStatement class definition and RightsGranted class definition".freeze,
1523
+ "rdfs:seeAlso": "RightsStatement class definition and\n RightsGranted class definition".freeze,
1187
1524
  type: "owl:ObjectProperty".freeze,
1188
1525
  "vs:term_status": "stable".freeze
1189
1526
  property :hasRightsGrantedNote,
1190
- definition: %(Definition: Additional information about the rights granted.).freeze,
1527
+ definition: %(Definition: Additional information about the
1528
+ rights granted.).freeze,
1191
1529
  domain: "premis:RightsGranted".freeze,
1192
- editorialNote: %(Rationale: A textual description of the rights granted may be needed for additional explanation.).freeze,
1530
+ editorialNote: %(Rationale: A textual description of the
1531
+ rights granted may be needed for additional explanation.).freeze,
1193
1532
  range: "xsd:string".freeze,
1194
- "skos:scopeNote": "Usage Notes: This semantic unit may include a statement about risk assessment, for example, when a repository is not certain about what permissions have been granted.".freeze,
1533
+ "skos:scopeNote": "Usage Notes: This semantic unit may include\n a statement about risk assessment, for example, when a repository is not certain about what\n permissions have been granted.".freeze,
1195
1534
  type: "owl:DatatypeProperty".freeze,
1196
1535
  "vs:term_status": "stable".freeze
1197
1536
  property :hasRightsRelatedAgent,
1198
- comment: [%(Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.).freeze, %(This propety links a RightsStatement instance to an Agent instance. Via this property a distinction can be made in the linkingAgent properties based on the domain.).freeze],
1537
+ comment: [%(Extensions: One can extend this
1538
+ property to use more fine grained properties by defining the fine grained properties as
1539
+ subproperties of this property.).freeze, %(This propety links a
1540
+ RightsStatement instance to an Agent instance. Via this property a distinction can be made in
1541
+ the linkingAgent properties based on the domain.).freeze],
1199
1542
  domain: "premis:RightsStatement".freeze,
1200
1543
  range: "premis:Agent".freeze,
1201
1544
  "rdfs:seeAlso": "http://id.loc.gov/vocabulary/preservation/rightsRelatedAgentRole".freeze,
@@ -1203,20 +1546,24 @@ Program=“MIGJP2JP2K”; version=“2.2”).freeze,
1203
1546
  type: "owl:ObjectProperty".freeze,
1204
1547
  "vs:term_status": "unstable".freeze
1205
1548
  property :hasRightsStatement,
1206
- definition: %(Definition: A rights statement associated with the object.).freeze,
1549
+ definition: %(Definition: A rights statement associated
1550
+ with the object.).freeze,
1207
1551
  domain: term(
1208
1552
  type: "owl:Class".freeze,
1209
1553
  unionOf: list("premis:Agent".freeze, "premis:Object".freeze)
1210
1554
  ),
1211
- editorialNote: %(Rationale: A repository may choose to link from a rights statement to an object or from an object to a rights statement or both.).freeze,
1555
+ editorialNote: %(Rationale: A repository may choose to link
1556
+ from a rights statement to an object or from an object to a rights statement or
1557
+ both.).freeze,
1212
1558
  range: "premis:RightsStatement".freeze,
1213
- "rdfs:seeAlso": "RightsStatement class definition".freeze,
1559
+ "rdfs:seeAlso": "RightsStatement class\n definition".freeze,
1214
1560
  type: "owl:ObjectProperty".freeze,
1215
1561
  "vs:term_status": "stable".freeze
1216
1562
  property :hasRightsStatementNote,
1217
- comment: %(Examples: Copyright expiration expected in 2010 unless renewed.
1218
- License is embedded in XMP block in file header.).freeze,
1219
- definition: %(Definition: Additional information about the RightsStatement of an object.).freeze,
1563
+ comment: %(Examples: Copyright expiration expected in
1564
+ 2010 unless renewed. License is embedded in XMP block in file header.).freeze,
1565
+ definition: %(Definition: Additional information about the
1566
+ RightsStatement of an object.).freeze,
1220
1567
  domain: "premis:RightsStatement".freeze,
1221
1568
  range: "xsd:string".freeze,
1222
1569
  type: "owl:DatatypeProperty".freeze,
@@ -1231,10 +1578,15 @@ License is embedded in XMP block in file header.).freeze,
1231
1578
  type: "owl:ObjectProperty".freeze,
1232
1579
  "vs:term_status": "stable".freeze
1233
1580
  property :hasSignatureEncoding,
1234
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/signatureEncoding).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1235
- definition: %(Definition: The encoding used for the values of signatureValue, keyInformation.).freeze,
1581
+ comment: [%(Data Constraint: Values are taken from the
1582
+ SKOS vocabulary: http://id.loc.gov/vocabulary/signatureEncoding).freeze, %(Extensions: One can use its own SKOS
1583
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1584
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1585
+ definition: %(Definition: The encoding used for the values
1586
+ of signatureValue, keyInformation.).freeze,
1236
1587
  domain: "premis:Signature".freeze,
1237
- editorialNote: %(Rationale: These values cannot be interpreted correctly if the encoding is unknown.).freeze,
1588
+ editorialNote: %(Rationale: These values cannot be
1589
+ interpreted correctly if the encoding is unknown.).freeze,
1238
1590
  range: term(
1239
1591
  onProperty: "skos:inScheme".freeze,
1240
1592
  "owl:hasValue": "http://id.loc.gov/vocabulary/preservation/signatureEncoding".freeze,
@@ -1243,112 +1595,158 @@ License is embedded in XMP block in file header.).freeze,
1243
1595
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
1244
1596
  "vs:term_status": "stable".freeze
1245
1597
  property :hasSignatureMethod,
1246
- comment: [%(Data Constraint: Values are taken from a SKOS vocabulary).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1247
- definition: %(Definition: A designation for the encryption and hash algorithms used for signature generation.).freeze,
1598
+ comment: [%(Data Constraint: Values are taken from a
1599
+ SKOS vocabulary).freeze, %(Extensions: One can use its own
1600
+ SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS
1601
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1602
+ definition: %(Definition: A designation for the encryption
1603
+ and hash algorithms used for signature generation.).freeze,
1248
1604
  domain: "premis:Signature".freeze,
1249
- editorialNote: %(Rationale: The same algorithms must be used for signature validation.).freeze,
1605
+ editorialNote: %(Rationale: The same algorithms must be used
1606
+ for signature validation.).freeze,
1250
1607
  range: "skos:Concept".freeze,
1251
1608
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
1252
1609
  "vs:term_status": "stable".freeze
1253
1610
  property :hasSignatureProperties,
1254
- definition: %(Definition: Additional information about the generation of the signature.).freeze,
1611
+ definition: %(Definition: Additional information about the
1612
+ generation of the signature.).freeze,
1255
1613
  domain: "premis:Signature".freeze,
1256
1614
  range: "xsd:string".freeze,
1257
- "skos:scopeNote": "Usage Notes: This may include the date/time of signature generation, the serial number of the cryptographic hardware used, or other information related to the generation of the signature. Repositories will likely want to define a suitably granular structure to signatureProperties.".freeze,
1615
+ "skos:scopeNote": "Usage Notes: This may include the date/time\n of signature generation, the serial number of the cryptographic hardware used, or other\n information related to the generation of the signature. Repositories will likely want to\n define a suitably granular structure to signatureProperties.".freeze,
1258
1616
  type: "owl:DatatypeProperty".freeze,
1259
1617
  "vs:term_status": "stable".freeze
1260
1618
  property :hasSignatureValidationRules,
1261
- definition: %(Definition: The operations to be performed in order to validate the digital signature.).freeze,
1619
+ definition: %(Definition: The operations to be performed
1620
+ in order to validate the digital signature.).freeze,
1262
1621
  domain: "premis:Signature".freeze,
1263
- editorialNote: %(Rationale: The repository should not assume that the procedure for validating any particular signature will be known many years in the future without documentation.).freeze,
1622
+ editorialNote: %(Rationale: The repository should not assume
1623
+ that the procedure for validating any particular signature will be known many years in the
1624
+ future without documentation.).freeze,
1264
1625
  range: "xsd:string".freeze,
1265
- "skos:scopeNote": "Usage Notes: This may include the canonicalization method used before calculating the message digest, if the object was normalized before signing. This value could also be a pointer to archive documentation.".freeze,
1626
+ "skos:scopeNote": "Usage Notes: This may include the\n canonicalization method used before calculating the message digest, if the object was\n normalized before signing. This value could also be a pointer to archive\n documentation.".freeze,
1266
1627
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1267
1628
  "vs:term_status": "stable".freeze
1268
1629
  property :hasSignatureValue,
1269
- comment: %(Example: juS5RhJ884qoFR8flVXd/rbrSDVGn40CapgB7qeQiT+rr0NekEQ6BHhUA8dT3+BCTBUQI0dBjlml9lwzENXvS83zRECjzXbMRTUtVZiPZG2pqKPnL2YU3A9645UCjTXU+jgFumv7k78hieAGDzNci+PQ9KRmm//icT7JaYztgt4=).freeze,
1270
- definition: %(Definition: The digital signature; a value generated from the application of a private key to a message digest.).freeze,
1630
+ comment: %(Example:
1631
+ juS5RhJ884qoFR8flVXd/rbrSDVGn40CapgB7qeQiT+rr0NekEQ6BHhUA8dT3+BCTBUQI0dBjlml9lwzENXvS83zRECjzXbMRTUtVZiPZG2pqKPnL2YU3A9645UCjTXU+jgFumv7k78hieAGDzNci+PQ9KRmm//icT7JaYztgt4=).freeze,
1632
+ definition: %(Definition: The digital signature; a value
1633
+ generated from the application of a private key to a message digest.).freeze,
1271
1634
  domain: "premis:Signature".freeze,
1272
1635
  range: "xsd:string".freeze,
1273
1636
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1274
1637
  "vs:term_status": "stable".freeze
1275
1638
  property :hasSigner,
1276
- definition: %(Definition: The individual, institution, or authority responsible for generating the signature.).freeze,
1639
+ definition: %(Definition: The individual, institution, or
1640
+ authority responsible for generating the signature.).freeze,
1277
1641
  domain: "premis:Signature".freeze,
1278
- editorialNote: %(Rationale: The signer might also be carried in the keyInformation, but it can be accessed more conveniently if recorded here.).freeze,
1642
+ editorialNote: %(Rationale: The signer might also be carried
1643
+ in the keyInformation, but it can be accessed more conveniently if recorded
1644
+ here.).freeze,
1279
1645
  range: ["premis:Agent".freeze, "xsd:string".freeze],
1280
- "skos:scopeNote": "Usage Notes: If the signer is an Agent known to the repository, this property can directly link to this agent. The consequence is punning: a datatype property and object property with the same name, i.e., :signer".freeze,
1646
+ "skos:scopeNote": "Usage Notes: If the signer is an Agent known\n to the repository, this property can directly link to this agent. The consequence is punning:\n a datatype property and object property with the same name, i.e., :signer".freeze,
1281
1647
  type: "owl:AnnotationProperty".freeze,
1282
1648
  "vs:term_status": "stable".freeze
1283
1649
  property :hasSignificantProperties,
1284
1650
  domain: "premis:Object".freeze,
1285
1651
  range: "premis:SignificantProperties".freeze,
1286
- "rdfs:seeAlso": "Object class definition and SignificantProperties class definition".freeze,
1652
+ "rdfs:seeAlso": "Object class definition and\n SignificantProperties class definition".freeze,
1287
1653
  type: "owl:ObjectProperty".freeze,
1288
1654
  "vs:term_status": "stable".freeze
1289
1655
  property :hasSignificantPropertiesType,
1290
- comment: %(Examples: content, structure, behavior, page count, page width, typeface, hyperlinks \(representation\), image count \(representation\), color space [for an embedded image] \(bitstream\)).freeze,
1291
- definition: %(Definition: The aspect, facet, or attribute of an object about which significant properties are being described.).freeze,
1656
+ comment: %(Examples: content, structure, behavior,
1657
+ page count, page width, typeface, hyperlinks \(representation\), image count \(representation\),
1658
+ color space [for an embedded image] \(bitstream\)).freeze,
1659
+ definition: %(Definition: The aspect, facet, or attribute
1660
+ of an object about which significant properties are being described.).freeze,
1292
1661
  domain: "premis:SignificantProperties".freeze,
1293
- editorialNote: %(Rationale: Repositories may choose to describe significant properties based on a particular aspect or attribute of an object.).freeze,
1662
+ editorialNote: %(Rationale: Repositories may choose to
1663
+ describe significant properties based on a particular aspect or attribute of an
1664
+ object.).freeze,
1294
1665
  range: "xsd:string".freeze,
1295
- "skos:scopeNote": "Usage Notes: This semantic unit is optional and may be used as part of a facet:detail pair with significantPropertiesValue.".freeze,
1666
+ "skos:scopeNote": "Usage Notes: This semantic unit is optional\n and may be used as part of a facet:detail pair with\n significantPropertiesValue.".freeze,
1296
1667
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1297
1668
  "vs:term_status": "stable".freeze
1298
1669
  property :hasSignificantPropertiesValue,
1299
- comment: %(Examples: [For a Web page containing animation that is not considered essential] Content only, [For detail associated with a significantPropertiesType of "behavior"] Hyperlinks traversable, [For a Word document with embedded links that are not considered essential] Content only, [For detail associated with significantPropertiesType of "behavior"] Editable, [For detail associated with a significantPropertiesType of "page width"] 210 mm, [For a PDF with an embedded graph, where the lines' color determines the lines' meaning] Color, [For detail associated with a significantPropertiesType of "appearance"] Color).freeze,
1300
- definition: %(Definition: Description of the characteristics of a particular object subjectively determined to be important to maintain through preservation actions.).freeze,
1670
+ comment: %(Examples: [For a Web page containing
1671
+ animation that is not considered essential] Content only, [For detail associated with a
1672
+ significantPropertiesType of "behavior"] Hyperlinks traversable, [For a Word document with
1673
+ embedded links that are not considered essential] Content only, [For detail associated with
1674
+ significantPropertiesType of "behavior"] Editable, [For detail associated with a
1675
+ significantPropertiesType of "page width"] 210 mm, [For a PDF with an embedded graph, where
1676
+ the lines' color determines the lines' meaning] Color, [For detail associated with a
1677
+ significantPropertiesType of "appearance"] Color).freeze,
1678
+ definition: %(Definition: Description of the
1679
+ characteristics of a particular object subjectively determined to be important to maintain
1680
+ through preservation actions.).freeze,
1301
1681
  domain: "premis:SignificantProperties".freeze,
1302
- editorialNote: %(Rationale: Repositories may choose to describe significant properties based on a particular aspect or attribute of an object.).freeze,
1682
+ editorialNote: %(Rationale: Repositories may choose to
1683
+ describe significant properties based on a particular aspect or attribute of an
1684
+ object.).freeze,
1303
1685
  range: "xsd:string".freeze,
1304
- "skos:scopeNote": "Usage Notes: If facet:detail pairs are used, the content of significantPropertiesValue should describe the significant properties of object relevant to the aspect, facet, or attribute declared in the significantPropertiesType with which it is paired. If facet:detail pairs are not used, significantPropertiesValue may be used to freely describe any characteristic of an object. significantPropertiesValue is not repeatable. Multiple significant properties should be described in separate, repeated significantProperties container units.".freeze,
1686
+ "skos:scopeNote": "Usage Notes: If facet:detail pairs are used,\n the content of significantPropertiesValue should describe the significant properties of object\n relevant to the aspect, facet, or attribute declared in the significantPropertiesType with\n which it is paired. If facet:detail pairs are not used, significantPropertiesValue may be used\n to freely describe any characteristic of an object. significantPropertiesValue is not\n repeatable. Multiple significant properties should be described in separate, repeated\n significantProperties container units.".freeze,
1305
1687
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1306
1688
  "vs:term_status": "stable".freeze
1307
1689
  property :hasSize,
1308
1690
  comment: %(Example: 2038937).freeze,
1309
- definition: %(Definition: The size in bytes of the file or bitstream stored in the repository.).freeze,
1691
+ definition: %(Definition: The size in bytes of the file or
1692
+ bitstream stored in the repository.).freeze,
1310
1693
  domain: "premis:ObjectCharacteristics".freeze,
1311
- editorialNote: %(Rationale: Size is useful for ensuring the correct number of bytes from storage have been retrieved and that an application has enough room to move or process files. It might also be used when billing for storage.).freeze,
1694
+ editorialNote: %(Rationale: Size is useful for ensuring the
1695
+ correct number of bytes from storage have been retrieved and that an application has enough
1696
+ room to move or process files. It might also be used when billing for
1697
+ storage.).freeze,
1312
1698
  range: "xsd:long".freeze,
1313
- "skos:historyNote": "Creation / Maintenance Notes: Automatically obtained by the repository.".freeze,
1314
- "skos:scopeNote": "Usage Notes: Defining this semantic unit as size in bytes makes it unnecessary to record a unit of measurement. However, for the purpose of data exchange the unit of measurement should be stated or understood by both partners.".freeze,
1699
+ "skos:historyNote": "Creation / Maintenance Notes: Automatically\n obtained by the repository.".freeze,
1700
+ "skos:scopeNote": "Usage Notes: Defining this semantic unit as\n size in bytes makes it unnecessary to record a unit of measurement. However, for the purpose\n of data exchange the unit of measurement should be stated or understood by both\n partners.".freeze,
1315
1701
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1316
1702
  "vs:term_status": "stable".freeze
1317
1703
  property :hasSoftware,
1318
1704
  domain: "premis:Environment".freeze,
1319
1705
  range: "premis:Software".freeze,
1320
- "rdfs:seeAlso": "Environment class definition and Software class definition".freeze,
1706
+ "rdfs:seeAlso": "Environment class definition and Software\n class definition".freeze,
1321
1707
  type: "owl:ObjectProperty".freeze,
1322
1708
  "vs:term_status": "stable".freeze
1323
1709
  property :hasSoftwareDependency,
1324
1710
  comment: %(Example: GNU gcc >=2.7.2).freeze,
1325
- definition: %(Definition: The name and, if applicable, version of any software component needed by the software referenced in swName in the context of using this object.).freeze,
1711
+ definition: %(Definition: The name and, if applicable,
1712
+ version of any software component needed by the software referenced in swName in the context
1713
+ of using this object.).freeze,
1326
1714
  domain: "premis:Software".freeze,
1327
1715
  range: "xsd:string".freeze,
1328
- "skos:scopeNote": "Usage Notes: The value should be constructed in a way that is consistent with the construction of swName and swVersion. This semantic unit identifies the software that is needed by what is recorded in swName, for example, a Perl script that depends on a Perl module. In this case the Perl script is listed in swName, with the module in swDependency within a software container.".freeze,
1716
+ "skos:scopeNote": "Usage Notes: The value should be constructed\n in a way that is consistent with the construction of swName and swVersion. This semantic unit\n identifies the software that is needed by what is recorded in swName, for example, a Perl\n script that depends on a Perl module. In this case the Perl script is listed in swName, with\n the module in swDependency within a software container.".freeze,
1329
1717
  type: "owl:DatatypeProperty".freeze,
1330
1718
  "vs:term_status": "stable".freeze
1331
1719
  property :hasSoftwareName,
1332
- comment: %(Examples: Adobe Photoshop, Adobe Acrobat Reader).freeze,
1333
- definition: %(Definition: Manufacturer and title of the software application.).freeze,
1720
+ comment: %(Examples: Adobe Photoshop, Adobe Acrobat
1721
+ Reader).freeze,
1722
+ definition: %(Definition: Manufacturer and title of the
1723
+ software application.).freeze,
1334
1724
  domain: "premis:Software".freeze,
1335
1725
  range: "xsd:string".freeze,
1336
- "skos:scopeNote": "Usage Notes: Include manufacturer when this helps to identify or disambiguate the product, for example, use “Adobe Photoshop” rather than “Photoshop.”".freeze,
1726
+ "skos:scopeNote": "Usage Notes: Include manufacturer when this\n helps to identify or disambiguate the product, for example, use “Adobe Photoshop” rather than\n “Photoshop.”".freeze,
1337
1727
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1338
1728
  "vs:term_status": "stable".freeze
1339
1729
  property :hasSoftwareOtherInformation,
1340
- comment: %(Example: Install Acroread \(Adobe Acrobat\) first; copy nppdf.so \(the plug-in\) to your Mozilla plug-ins directory, and make sure a copy of \(or symlink to\) Acroread is in your PATH.).freeze,
1341
- definition: %(Definition: Additional requirements or instructions related to the software referenced in swName.).freeze,
1730
+ comment: %(Example: Install Acroread \(Adobe Acrobat\)
1731
+ first; copy nppdf.so \(the plug-in\) to your Mozilla plug-ins directory, and make sure a copy of
1732
+ \(or symlink to\) Acroread is in your PATH.).freeze,
1733
+ definition: %(Definition: Additional requirements or
1734
+ instructions related to the software referenced in swName.).freeze,
1342
1735
  domain: "premis:Software".freeze,
1343
1736
  range: "xsd:string".freeze,
1344
- "skos:scopeNote": "Usage Notes: This could be a reliable persistent identifier or URI pointing to software documentation within or outside the repository.".freeze,
1737
+ "skos:scopeNote": "Usage Notes: This could be a reliable\n persistent identifier or URI pointing to software documentation within or outside the\n repository.".freeze,
1345
1738
  type: "owl:DatatypeProperty".freeze,
1346
1739
  "vs:term_status": "stable".freeze
1347
1740
  property :hasSoftwareType,
1348
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/softwareType).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1349
- definition: %(Definition: Class or category of software.).freeze,
1741
+ comment: [%(Data Constraint: Values are taken from the
1742
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/softwareType).freeze, %(Extensions: One can use its own SKOS
1743
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1744
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1745
+ definition: %(Definition: Class or category of
1746
+ software.).freeze,
1350
1747
  domain: "premis:Software".freeze,
1351
- editorialNote: %(Rationale: Several different layers of software can be required to support an object.).freeze,
1748
+ editorialNote: %(Rationale: Several different layers of
1749
+ software can be required to support an object.).freeze,
1352
1750
  range: term(
1353
1751
  onProperty: "skos:inScheme".freeze,
1354
1752
  "owl:hasValue": "http://id.loc.gov/vocabulary/preservation/softwareType".freeze,
@@ -1357,41 +1755,57 @@ License is embedded in XMP block in file header.).freeze,
1357
1755
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
1358
1756
  "vs:term_status": "stable".freeze
1359
1757
  property :hasSoftwareVersion,
1360
- comment: %(Examples: >=2.2.0, 6.0, 2003).freeze,
1361
- definition: %(Definition: The version or versions of the software referenced in swName.).freeze,
1758
+ comment: %(Examples: >=2.2.0, 6.0,
1759
+ 2003).freeze,
1760
+ definition: %(Definition: The version or versions of the
1761
+ software referenced in swName.).freeze,
1362
1762
  domain: "premis:Software".freeze,
1363
1763
  range: "xsd:string".freeze,
1364
- "skos:scopeNote": "Usage Notes: If there is no formal version, the date of issuance can be used.".freeze,
1764
+ "skos:scopeNote": "Usage Notes: If there is no formal version,\n the date of issuance can be used.".freeze,
1365
1765
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1366
1766
  "vs:term_status": "stable".freeze
1367
1767
  property :hasStartDate,
1368
- comment: %(Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime).freeze,
1369
- definition: %(Definition: The beginning date of the permission granted.).freeze,
1768
+ comment: %(Data Constraint: To aid machine processing,
1769
+ value should use a structured form: xsd:dateTime).freeze,
1770
+ definition: %(Definition: The beginning date of the
1771
+ permission granted.).freeze,
1370
1772
  domain: "premis:ApplicableDates".freeze,
1371
1773
  range: "xsd:dateTime".freeze,
1372
1774
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1373
1775
  "vs:term_status": "stable".freeze
1374
1776
  property :hasStatuteCitation,
1375
- comment: %(Examples: Legal Deposit \(Jersey\) Law 200, National Library of New Zealand \(Te Puna Mātauranga o Aotearoa\) Act 2003 no 19 part 4 s 34).freeze,
1376
- definition: %(Definition: An identifying designation for the statute.).freeze,
1777
+ comment: %(Examples: Legal Deposit \(Jersey\) Law 200,
1778
+ National Library of New Zealand \(Te Puna Mātauranga o Aotearoa\) Act 2003 no 19 part 4 s
1779
+ 34).freeze,
1780
+ definition: %(Definition: An identifying designation for
1781
+ the statute.).freeze,
1377
1782
  domain: "premis:StatuteInformation".freeze,
1378
1783
  range: "xsd:string".freeze,
1379
- "skos:scopeNote": "Usage Notes: Use standard citation form when applicable.".freeze,
1784
+ "skos:scopeNote": "Usage Notes: Use standard citation form when\n applicable.".freeze,
1380
1785
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1381
1786
  "vs:term_status": "stable".freeze
1382
1787
  property :hasStatuteInformationDeterminationDate,
1383
- comment: [%(Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime).freeze, %(Example: 2001-10-26T19:32:52+00:00).freeze],
1384
- definition: %(Definition: The date that the determination was made that the statute authorized the permission\(s\) noted.).freeze,
1788
+ comment: [%(Data Constraint: To aid machine processing,
1789
+ value should use a structured form: xsd:dateTime).freeze, %(Example:
1790
+ 2001-10-26T19:32:52+00:00).freeze],
1791
+ definition: %(Definition: The date that the determination
1792
+ was made that the statute authorized the permission\(s\) noted.).freeze,
1385
1793
  domain: "premis:StatuteInformation".freeze,
1386
- editorialNote: %(Rationale: The permission in question may be the subject of some interpretation. These assessments are made within a specific context and at a specific time. At another time the context, and therefore the assessment, could change. For this reason it can be important to record the date of the decision.).freeze,
1794
+ editorialNote: %(Rationale: The permission in question may be
1795
+ the subject of some interpretation. These assessments are made within a specific context and
1796
+ at a specific time. At another time the context, and therefore the assessment, could change.
1797
+ For this reason it can be important to record the date of the decision.).freeze,
1387
1798
  range: "xsd:dateTime".freeze,
1388
1799
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1389
1800
  "vs:term_status": "stable".freeze
1390
1801
  property :hasStatuteJurisdiction,
1391
- comment: [%(Data Constraint: Values should be taken from a controlled vocabulary.).freeze, %(Examples: us, de, be).freeze],
1392
- definition: %(Definition: The country or other political body enacting the statute.).freeze,
1802
+ comment: [%(Data Constraint: Values should be taken
1803
+ from a controlled vocabulary.).freeze, %(Examples: us, de, be).freeze],
1804
+ definition: %(Definition: The country or other political
1805
+ body enacting the statute.).freeze,
1393
1806
  domain: "premis:StatuteInformation".freeze,
1394
- editorialNote: %(Rationale: The connection between the object and the rights granted is based on jurisdiction.).freeze,
1807
+ editorialNote: %(Rationale: The connection between the object
1808
+ and the rights granted is based on jurisdiction.).freeze,
1395
1809
  range: "xsd:string".freeze,
1396
1810
  type: ["owl:DatatypeProperty".freeze, "owl:FunctionalProperty".freeze],
1397
1811
  "vs:term_status": "stable".freeze
@@ -1401,14 +1815,20 @@ License is embedded in XMP block in file header.).freeze,
1401
1815
  unionOf: list("premis:Bitstream".freeze, "premis:File".freeze)
1402
1816
  ),
1403
1817
  range: "premis:Storage".freeze,
1404
- "rdfs:seeAlso": "Object class definition and Storage class definition".freeze,
1818
+ "rdfs:seeAlso": "Object class definition and Storage class\n definition".freeze,
1405
1819
  type: "owl:ObjectProperty".freeze,
1406
1820
  "vs:term_status": "stable".freeze
1407
1821
  property :hasStorageMedium,
1408
- comment: [%(Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/storageMedium).freeze, %(Extensions: One can use its own SKOS vocabulary to use for this property. The precondition to do this, is to link your SKOS concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1409
- definition: %(Definition: The physical medium on which the object is stored \(e.g., magnetic tape, hard disk, CD-ROM, DVD\).).freeze,
1822
+ comment: [%(Data Constraint: Values are taken from the
1823
+ SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/storageMedium).freeze, %(Extensions: One can use its own SKOS
1824
+ vocabulary to use for this property. The precondition to do this, is to link your SKOS
1825
+ concepts to the SKOS concepts of the id.loc.gov vocabulary.).freeze],
1826
+ definition: %(Definition: The physical medium on which the
1827
+ object is stored \(e.g., magnetic tape, hard disk, CD-ROM, DVD\).).freeze,
1410
1828
  domain: "premis:Storage".freeze,
1411
- editorialNote: %(Rationale: The repository needs to know the medium on which an object is stored in order to know how and when to do media refreshment and media migration.).freeze,
1829
+ editorialNote: %(Rationale: The repository needs to know the
1830
+ medium on which an object is stored in order to know how and when to do media refreshment and
1831
+ media migration.).freeze,
1412
1832
  range: term(
1413
1833
  onProperty: "skos:inScheme".freeze,
1414
1834
  "owl:hasValue": "http://id.loc.gov/vocabulary/preservation/storageMedium".freeze,
@@ -1419,13 +1839,13 @@ License is embedded in XMP block in file header.).freeze,
1419
1839
  property :hasTermOfGrant,
1420
1840
  domain: "premis:RightsGranted".freeze,
1421
1841
  range: "premis:TermOfGrant".freeze,
1422
- "rdfs:seeAlso": "RightsGranted class definition and TermOfGrant class definition".freeze,
1842
+ "rdfs:seeAlso": "RightsGranted class definition and\n TermOfGrant class definition".freeze,
1423
1843
  type: ["owl:FunctionalProperty".freeze, "owl:ObjectProperty".freeze],
1424
1844
  "vs:term_status": "stable".freeze
1425
1845
  property :hasTermOfRestriction,
1426
1846
  domain: "premis:RightsGranted".freeze,
1427
1847
  range: "premis:TermOfRestriction".freeze,
1428
- "rdfs:seeAlso": "RightsGranted and TermOfRestriction class definitions".freeze,
1848
+ "rdfs:seeAlso": "RightsGranted and TermOfRestriction class\n definitions".freeze,
1429
1849
  type: "owl:ObjectProperty".freeze,
1430
1850
  "vs:term_status": "stable".freeze
1431
1851
  end