Matches in LOV for { <http://www.loc.gov/premis/rdf/v1#hasCompositionLevel> ?p ?o. }
Showing items 1 to 11 of
11
with 100 items per page.
- hasCompositionLevel type DatatypeProperty.
- hasCompositionLevel type FunctionalProperty.
- hasCompositionLevel comment "Data Constraints: Non-negative integers.".
- hasCompositionLevel comment "Examples: 0, 1, 2".
- hasCompositionLevel domain ObjectCharacteristics.
- hasCompositionLevel range int.
- hasCompositionLevel term_status "stable".
- hasCompositionLevel definition "Definition: An indication of whether the object is subject to one or more processes of decoding or unbundling.".
- hasCompositionLevel 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.".
- hasCompositionLevel 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.".
- hasCompositionLevel 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.\"".