Matches in LOV for { <http://www.loc.gov/premis/rdf/v1#SignificantProperties> ?p ?o. }
Showing items 1 to 6 of
6
with 100 items per page.
- SignificantProperties type Class.
- SignificantProperties term_status "stable".
- SignificantProperties definition "Definition: Characteristics of a particular object subjectively determined to be important to maintain through preservation actions.".
- SignificantProperties 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.".
- SignificantProperties 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.".
- SignificantProperties 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.".