Library of Congress

Authorities & Vocabularies

The Library of Congress > Linked Data Service >

Search




**Please Note: LC Classification entries are not included in general search results. You must explicitly select LC Classification in order to search the scheme. This is temporary while the impact of adding LCC to the current system is better understood.

    


Preservation Metadata: Implementation Strategies (PREMIS) Ontology


  • This ontology identifies the classes and properties used to describe preservation metadata in RDF.

  • URI(s)

  • Instance Of

  • Imports


  • Class List

    Agent      ApplicableDates      Bitstream      ContentLocation      CopyrightInformation      CreatingApplication      Dependency      Environment      Event      EventOutcomeDetail      EventOutcomeInformation      File      Fixity      Format      FormatDesignation      FormatRegistry      Hardware      Identifier      Inhibitors      IntellectualEntity      LicenseInformation      Object      ObjectCharacteristics      PremisEntity      PreservationLevel      RelatedObjectIdentification      Representation      RightsDocumentation      RightsGranted      RightsStatement      Signature      SignificantProperties      Software      StatuteInformation      Storage      TermOfGrant      TermOfRestriction     

    Property List

    hasAct      hasAgent      hasAgentName      hasAgentNote      hasAgentType      hasApplicableDates      hasCompositionLevel      hasContentLocation      hasContentLocationType      hasContentLocationValue      hasCopyrightJurisdiction      hasCopyrightStatus      hasCopyrightStatusDeterminationDate      hasCreatingApplication      hasCreatingApplicationName      hasCreatingApplicationVersion      hasDateCreatedByApplication      hasDependency      hasDependencyName      hasEndDate      hasEnvironment      hasEnvironmentCharacteristic      hasEnvironmentNote      hasEnvironmentPurpose      hasEvent      hasEventDateTime      hasEventDetail      hasEventOutcome      hasEventOutcomeDetail      hasEventOutcomeDetailNote      hasEventOutcomeInformation      hasEventRelatedAgent      hasEventRelatedObject      hasEventType      hasFixity      hasFormat      hasFormatDesignation      hasFormatName      hasFormatNote      hasFormatRegistry      hasFormatRegistryKey      hasFormatRegistryName      hasFormatRegistryRole      hasFormatVersion      hasHardware      hasHardwareName      hasHardwareOtherInformation      hasHardwareType      hasIdentifier      hasIdentifierType      hasIdentifierValue      hasInhibitorKey      hasInhibitors      hasInhibitorTarget      hasInhibitorType      hasIntellectualEntity      hasKeyInformation      hasLicenseTerms      hasMessageDigest      hasMessageDigestAlgorithm      hasMessageDigestOriginator      hasObject      hasObjectCharacteristics      hasOriginalName      hasPreservationLevel      hasPreservationLevelDateAssigned      hasPreservationLevelRationale      hasPreservationLevelRole      hasPreservationLevelValue      hasRelatedObject      hasRelatedObjectSequence      hasRelatedStatuteInformation      hasRelationship      hasRestriction      hasRightsDocumentation      hasRightsDocumentationRole      hasRightsGranted      hasRightsGrantedNote      hasRightsRelatedAgent      hasRightsStatement      hasRightsStatementNote      hasSignature      hasSignatureEncoding      hasSignatureMethod      hasSignatureProperties      hasSignatureValidationRules      hasSignatureValue      hasSigner      hasSignificantProperties      hasSignificantPropertiesType      hasSignificantPropertiesValue      hasSize      hasSoftware      hasSoftwareDependency      hasSoftwareName      hasSoftwareOtherInformation      hasSoftwareType      hasSoftwareVersion      hasStartDate      hasStatuteCitation      hasStatuteInformationDeterminationDate      hasStatuteJurisdiction      hasStorage      hasStorageMedium      hasTermOfGrant      hasTermOfRestriction     

    Classes

    Class: premis:Agent
    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 Agent entities.

    Editorial Note: 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.

    SubClass Of: premis:PremisEntity
    dcterms:Agent Offsite link
    foaf:Agent Offsite link

    Used with: premis:hasEventRelatedAgent
    premis:hasAgent
    premis:hasRightsRelatedAgent

    Properties include: premis:hasAgentType

    [back to class list] [back to top]
    Class: premis:ApplicableDates
    Definition: Definition: The date range during which the particular rights statement applies or is applied to the content.

    Editorial Note: Rationale Specific dates may apply to the particular rights statement.

    SubClass Of: [Restriction] max 1 owl:Thing Offsite link
    [Restriction] premis:hasEndDate max 1 owl:Thing Offsite link

    Used with: premis:hasApplicableDates

    [back to class list] [back to top]
    Class: premis:Bitstream
    Definition: Definition: Contiguous or non-contiguous data within a file that has meaningful properties for preservation purposes.

    SubClass Of: [Restriction] min 1 owl:Thing Offsite link
    premis:Object

    [back to class list] [back to top]
    Class: premis:ContentLocation
    Definition: Definition: Information needed to retrieve a file from the storage system, or to access a bitstream within a file.

    Scope Note: 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.

    History Note: 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.

    SubClass Of: ( [Restriction] exactly 1 owl:Thing Offsite link ∩ [Restriction] premis:hasContentLocationValue exactly 1 owl:Thing Offsite link )

    [back to class list] [back to top]
    Class: premis:CopyrightInformation
    Definition: Definition: Information about the copyright status of the object(s).

    Scope Note: 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.

    SubClass Of: ( [Restriction] exactly 1 owl:Thing Offsite link ∩ [Restriction] exactly 1 owl:Thing Offsite link )
    premis:RightsStatement

    [back to class list] [back to top]
    Class: premis:CreatingApplication
    Definition: Definition: Information about the application that created the object.

    Scope Note: 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.

    Editorial Note: 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.

    History Note: 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.

    SubClass Of: ( [Restriction] exactly 1 owl:Thing Offsite link ∪ [Restriction] max 1 owl:Thing Offsite link ∪ [Restriction] max 1 owl:Thing Offsite link )

    Used with: premis:hasCreatingApplication

    [back to class list] [back to top]
    Class: premis:Dependency
    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.

    Scope Note: 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.

    History Note: 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.

    SubClass Of: ( [Restriction] premis:hasIdentifier max 1 owl:Thing Offsite link ∪ [Restriction] premis:hasDependencyName min 1 owl:Thing Offsite link )

    Used with: premis:hasDependency

    [back to class list] [back to top]
    Class: premis:Environment
    Definition: Definition: Hardware/software combinations supporting use of the object.

    Scope Note: 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.

    Editorial Note: 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.

    History Note: 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.

    SubClass Of: [Restriction] premis:hasEnvironmentCharacteristic max 1 owl:Thing Offsite link

    Used with: premis:hasEnvironment

    Properties include: premis:hasDependency
    premis:hasEnvironmentPurpose
    premis:hasEnvironmentCharacteristic
    premis:hasSoftware
    premis:hasHardware

    [back to class list] [back to top]
    Class: premis:Event
    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. 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 an Event entity. Mandatory semantic units are: eventIdentifier, eventType, and eventDateTime.

    Editorial Note: 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.

    SubClass Of: premis:PremisEntity
    ( [Restriction] premis:hasEventType exactly 1 owl:Thing Offsite link ∩ [Restriction] premis:hasIdentifier max 1 owl:Thing Offsite link ∩ [Restriction] exactly 1 owl:Thing Offsite link )

    Used with: premis:hasEvent

    Properties include: premis:hasEventRelatedAgent
    premis:hasEventRelatedObject
    premis:hasEventOutcomeInformation
    premis:hasEventType

    [back to class list] [back to top]
    Class: premis:EventOutcomeDetail
    Definition: Definition: A detailed description of the result or product of the event.

    Scope Note: 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.

    Editorial Note: Rationale: An event outcome may be sufficiently complex that a coded description is not adequate to document it.

    SubClass Of: [Restriction] max 1 owl:Thing Offsite link

    Used with: premis:hasEventOutcomeDetail

    [back to class list] [back to top]
    Class: premis:EventOutcomeInformation
    Definition: Definition: Information about the outcome of an event.

    Scope Note: 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.

    SubClass Of: [Restriction] max 1 owl:Thing Offsite link

    Used with: premis:hasEventOutcomeInformation

    Properties include: premis:hasEventOutcomeDetail

    [back to class list] [back to top]
    Class: premis:File
    Definition: Definition: A named and ordered sequence of bytes that is known to an operating system.

    SubClass Of: [Restriction] min 1 owl:Thing Offsite link
    premis:Object

    [back to class list] [back to top]
    Class: premis:Fixity
    Definition: Definition: Information used to verify whether an object has been altered in an undocumented or unauthorized way.

    Scope Note: 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.

    History Note: Creation / Maintenance Notes: Automatically calculated and recorded by repository.

    SubClass Of: ( [Restriction] exactly 1 owl:Thing Offsite link ∩ [Restriction] exactly 1 owl:Thing Offsite link )

    [back to class list] [back to top]
    Class: premis:Format
    Definition: Definition: Identification of the format of a file or bitstream where format is the organization of digital information according to preset specifications.

    Scope Note: 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.

    Editorial Note: 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.

    History Note: 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.

    SubClass Of: ( [Restriction] premis:hasFormatDesignation max 1 owl:Thing Offsite link ∪ [Restriction] max 1 owl:Thing Offsite link )

    Properties include: premis:hasFormatDesignation

    [back to class list] [back to top]
    Class: premis:FormatDesignation
    Definition: Definition: An identification of the format of the object.

    Scope Note: 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.

    SubClass Of: [Restriction] premis:hasFormatName exactly 1 owl:Thing Offsite link

    Used with: premis:hasFormatDesignation

    [back to class list] [back to top]
    Class: premis:FormatRegistry
    Definition: Definition: Identifies and/or gives further information about the format by reference to an entry in a format registry.

    Scope Note: 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.

    Editorial Note: Rationale: If central format registries are available to the preservation repository, they may provide an excellent way of referencing detailed format information.

    SubClass Of: [Restriction] exactly 1 owl:Thing Offsite link
    [Restriction] premis:hasFormatRegistryName exactly 1 owl:Thing Offsite link

    [back to class list] [back to top]
    Class: premis:Hardware
    Definition: Definition: Hardware components needed by the software referenced in swName or the human user of the referenced software.

    History Note: 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.

    SubClass Of: ( [Restriction] exactly 1 owl:Thing Offsite link ∩ [Restriction] exactly 1 owl:Thing Offsite link )

    Used with: premis:hasHardware

    [back to class list] [back to top]
    Class: premis:Identifier
    Comment: This class is used in PREMIS OWL to describe identifiers if the identifiers are not http URIs.

    SubClass Of: [Restriction] exactly 1 owl:Thing Offsite link
    [Restriction] exactly 1 owl:Thing Offsite link

    [back to class list] [back to top]
    Class: premis:Inhibitors
    Definition: Definition: Features of the object intended to inhibit access, use, or migration.

    Scope Note: 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.

    Editorial Note: 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.

    History Note: 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.

    SubClass Of: [Restriction] exactly 1 owl:Thing Offsite link

    Used with: premis:hasInhibitors

    Properties include: premis:hasInhibitorTarget

    [back to class list] [back to top]
    Class: premis:IntellectualEntity
    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.

    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

    SubClass Of: premis:PremisEntity

    Used with: premis:hasIntellectualEntity

    [back to class list] [back to top]
    Class: premis:LicenseInformation
    Definition: Definition: Information about a license or other agreement granting permissions related to an object.

    Scope Note: Usage Note: When rights basis is a license, licenseInformation should be provided.

    SubClass Of: premis:RightsStatement
    [Restriction] max 1 owl:Thing Offsite link

    [back to class list] [back to top]
    Class: premis:Object
    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. The object class has three subclasses: Representation, File, and Bitstream.

    Editorial Note: 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.
    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.

    SubClass Of: premis:PremisEntity

    Used with: premis:hasObject
    premis:hasEventRelatedObject
    premis:hasRelatedObject

    Properties include: premis:hasSignificantProperties
    premis:hasEnvironment
    premis:hasRelationship
    premis:hasIntellectualEntity

    [back to class list] [back to top]
    Class: premis:ObjectCharacteristics
    Definition: Definition: Technical properties of a file or bitstream that are applicable to all or most formats.

    Scope Note: 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.

    Editorial Note: 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.

    SubClass Of: [Restriction] premis:hasFormat min 1 owl:Thing Offsite link
    [Restriction] exactly 1 owl:Thing Offsite link

    Properties include: premis:hasFormat
    premis:hasInhibitors
    premis:hasCreatingApplication

    [back to class list] [back to top]
    Class: premis:PremisEntity
    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.

    SubClass Of: owl:Thing Offsite link

    [back to class list] [back to top]
    Class: premis:PreservationLevel
    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.

    Scope Note: 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).

    Editorial Note: 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.

    History Note: 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.

    SubClass Of: [Restriction] max 1 owl:Thing Offsite link
    [Restriction] premis:hasPreservationLevelValue exactly 1 owl:Thing Offsite link

    Used with: premis:hasPreservationLevel

    [back to class list] [back to top]
    Class: premis:RelatedObjectIdentification
    Definition: Definition: The identifier and sequential context of the related resource

    Scope Note: 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.

    SubClass Of: ( [Restriction] premis:hasRelatedObject exactly 1 owl:Thing Offsite link ∩ [Restriction] premis:hasRelatedObjectSequence exactly 1 owl:Thing Offsite link )

    Properties include: premis:hasRelatedObject

    [back to class list] [back to top]
    Class: premis:Representation
    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.

    SubClass Of: premis:Object

    [back to class list] [back to top]
    Class: premis:RightsDocumentation
    Definition: Definition: A designation used to uniquely identify documentation supporting the specified rights within the repository system.

    SubClass Of: [Restriction] premis:hasRightsDocumentationRole max 1 owl:Thing Offsite link

    Used with: premis:hasRightsDocumentation

    Properties include: premis:hasRightsDocumentationRole

    [back to class list] [back to top]
    Class: premis:RightsGranted
    Definition: Definition: The action(s) that the granting agency has allowed the repository.

    SubClass Of: ( [Restriction] exactly 1 owl:Thing Offsite link ∩ [Restriction] max 1 owl:Thing Offsite link )
    [Restriction] premis:hasTermOfRestriction max 1 owl:Thing Offsite link

    Used with: premis:hasRightsGranted

    Properties include: premis:hasTermOfRestriction

    [back to class list] [back to top]
    Class: premis:RightsStatement
    Definition: Definition: Documentation of the repository's right to perform one or more acts.

    Comment: Extensions: In OWL one can define its own subclasses to the the RightsStatement class to denote OtherRightsInformation of the PREMIS data dictionary.

    Scope Note: 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.

    SubClass Of: premis:PremisEntity
    dcterms:RightsStatement Offsite link
    [Restriction] premis:hasApplicableDates max 1 owl:Thing Offsite link
    [Restriction] premis:hasIdentifier max 1 owl:Thing Offsite link

    Used with: premis:hasRightsStatement

    Properties include: premis:hasRightsDocumentation
    premis:hasRightsRelatedAgent
    premis:hasApplicableDates
    premis:hasRightsGranted

    [back to class list] [back to top]
    Class: premis:Signature
    Definition: Definition: Information needed to use a digital signature to authenticate the signer of an object and/or the information contained in the object.

    Scope Note: 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.

    Editorial Note: 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.

    SubClass Of: ( [Restriction] premis:hasSignatureEncoding exactly 1 owl:Thing Offsite link ∩ [Restriction] exactly 1 owl:Thing Offsite link ∩ [Restriction] premis:hasSignatureValidationRules exactly 1 owl:Thing Offsite link ∩ [Restriction] exactly 1 owl:Thing Offsite link )

    Used with: premis:hasSignature

    Properties include: premis:hasKeyInformation
    premis:hasSignatureEncoding

    [back to class list] [back to top]
    Class: premis:SignificantProperties
    Definition: Definition: Characteristics of a particular object subjectively determined to be important to maintain through preservation actions.

    Scope Note: 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.

    Editorial Note: Rationale: Objects that have the same technical properties may still differ as to the properties that should be preserved for future presentation or use.

    History Note: 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.

    Used with: premis:hasSignificantProperties

    [back to class list] [back to top]
    Class: premis:Software
    Definition: Definition: Software required to render or use the object.

    History Note: 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.

    SubClass Of: ( [Restriction] exactly 1 owl:Thing Offsite link ∩ [Restriction] exactly 1 owl:Thing Offsite link )

    Used with: premis:hasSoftware

    [back to class list] [back to top]
    Class: premis:StatuteInformation
    Definition: Definition: Information about the statute allowing use of the object.

    Scope Note: Usage Notes: When rights basis is a statute, statuteInformation should be provided.

    SubClass Of: premis:RightsStatement
    ( [Restriction] exactly 1 owl:Thing Offsite link ∩ [Restriction] exactly 1 owl:Thing Offsite link )

    Used with: premis:hasRelatedStatuteInformation

    Properties include: premis:hasRelatedStatuteInformation

    [back to class list] [back to top]
    Class: premis:Storage
    Definition: Definition: Information about how and where a file is stored in the storage system.

    Scope Note: 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.

    Editorial Note: Rationale: It is necessary for a repository to associate the contentLocation with the storageMedium.

    SubClass Of: ( [Restriction] max 1 owl:Thing Offsite link ∪ [Restriction] premis:hasStorageMedium max 1 owl:Thing Offsite link )

    Used with: premis:hasStorage

    Properties include: premis:hasStorageMedium

    [back to class list] [back to top]
    Class: premis:TermOfGrant
    Definition: Definition: The time period for the permissions granted.

    Editorial Note: Rationale: The permission to preserve may be time bounded.

    SubClass Of: premis:ApplicableDates
    [Restriction] exactly 1 owl:Thing Offsite link

    [back to class list] [back to top]
    Class: premis:TermOfRestriction
    Definition: Definition: The time period for the restriction granted.

    Editorial Note: 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.

    SubClass Of: [Restriction] exactly 1 owl:Thing Offsite link
    premis:ApplicableDates

    Used with: premis:hasTermOfRestriction

    [back to class list] [back to top]

    Properties

    Property: premis:hasAct
    Definition: Definition: The action the preservation repository is allowed to take.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/actionsGranted
    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.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:RightsGranted

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/actionsGranted

    [back to property list] [back to top]
    Property: premis:hasAgent
    Definition: Definition: link to the associated Agent.

    Editorial Note: 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.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:Eventpremis:RightsStatement

    Range: premis:Agent

    [back to property list] [back to top]
    Property: premis:hasAgentName
    Definition: Definition: A text string which could be used in addition to agentIdentifier to identify an agent.

    Comment: Examples: Erik Owens, Pc

    Scope Note: Usage Note: The value is not necessarily unique.

    Editorial Note: Rationale: This semantic unit provides a more reader-friendly version of the agent identified by the agentIdentifier.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:Agent

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasAgentNote
    Definition: Definition: Additional information about the agent.

    Editorial Note: Rationale: Additional information may be needed to describe or disambiguate the agent.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:Agent

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasAgentType
    Definition: Definition: A high-level characterization of the type of agent.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/agentType
    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.

    Type: owl:ObjectProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Agent

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/agentType

    [back to property list] [back to top]
    Property: premis:hasApplicableDates
    Type: owl:ObjectProperty Offsite link

    Domain: premis:RightsStatement

    Range: premis:ApplicableDates

    [back to property list] [back to top]
    Property: premis:hasCompositionLevel
    Definition: Definition: An indication of whether the object is subject to one or more processes of decoding or unbundling.

    Comment: Examples: 0, 1, 2
    Data Constraints: Non-negative integers.

    Scope Note: 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.”

    Editorial Note: 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.

    History Note: 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.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:ObjectCharacteristics

    Range: xsd:int Offsite link

    [back to property list] [back to top]
    Property: premis:hasContentLocation
    Type: owl:FunctionalProperty Offsite link
    owl:InverseFunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:Storage

    Range: premis:ContentLocation

    [back to property list] [back to top]
    Property: premis:hasContentLocationType
    Definition: Definition: The means of referencing the location of the content.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/contentLocationType
    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.

    Editorial Note: Rationale: To understand the meaning of the value it is necessary to know what location scheme is used.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:ContentLocation

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/contentLocationType

    [back to property list] [back to top]
    Property: premis:hasContentLocationValue
    Definition: Definition: The reference to the location of the content used by the storage system.

    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)

    Scope Note: 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.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:ContentLocation

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasCopyrightJurisdiction
    Definition: Definition: The country whose copyright laws apply.

    Comment: Data Constraint: Values should be taken from ISO 3166.
    Examples: us, de, be

    Editorial Note: Rationale: Copyright law can vary from country to country.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:CopyrightInformation

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasCopyrightStatus
    Definition: Definition: A coded designation for the copyright status of the object at the time the rights statement is recorded.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/copyrightStatus
    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.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:CopyrightInformation

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/copyrightStatus

    [back to property list] [back to top]
    Property: premis:hasCopyrightStatusDeterminationDate
    Definition: Definition: The date that the copyright status recorded in copyrightStatus was determined.

    Comment: Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime
    Example: 2001-10-26T19:32:52+00:00

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:CopyrightInformation

    Range: xsd:dateTime Offsite link

    [back to property list] [back to top]
    Property: premis:hasCreatingApplication
    Type: owl:ObjectProperty Offsite link

    Domain: premis:ObjectCharacteristics

    Range: premis:CreatingApplication

    [back to property list] [back to top]
    Property: premis:hasCreatingApplicationName
    Definition: Definition: A designation for the name of the software program that created the object.

    Comment: Example: MSWord

    Scope Note: 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.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:CreatingApplication

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasCreatingApplicationVersion
    Definition: Definition: The version of the software program that created the object.

    Comment: Example: 2000

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:CreatingApplication

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasDateCreatedByApplication
    Definition: Definition: The actual or approximate date and time the object was created.

    Comment: Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime
    Example: 2001-10-26T19:32:52+00:00

    Scope Note: 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.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:CreatingApplication

    Range: xsd:dateTime Offsite link

    [back to property list] [back to top]
    Property: premis:hasDependency
    Type: owl:ObjectProperty Offsite link

    Domain: premis:Environment

    Range: premis:Dependency

    [back to property list] [back to top]
    Property: premis:hasDependencyName
    Definition: Definition: A designation for a component or associated file needed by the representation or file.

    Comment: Example: Additional Element Set for Language Corpora

    Editorial Note: Rationale: It may not be self-evident from the dependencyIdentifier what the name of the object actually is.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:Dependency

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasEndDate
    Definition: Definition: The ending date of the permission granted.

    Comment: Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime

    Scope Note: Usage Notes: Use “0000-00-00T00:00:00+00:00” for 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.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:ApplicableDates

    Range: xsd:dateTime Offsite link

    [back to property list] [back to top]
    Property: premis:hasEnvironment
    Type: owl:ObjectProperty Offsite link

    Domain: premis:Object

    Range: premis:Environment

    [back to property list] [back to top]
    Property: premis:hasEnvironmentCharacteristic
    Definition: Definition: An assessment of the extent to which the described environment supports its purpose.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/environmentCharacteristic
    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.

    Editorial Note: Rationale: If multiple environments are described, this element can help to distinguish among them.

    Type: owl:ObjectProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Environment

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/environmentCharacteristic

    [back to property list] [back to top]
    Property: premis:hasEnvironmentNote
    Definition: Definition: Additional information about the environment.

    Comment: Example: This environment assumes that the PDF will be stored locally and used with a standalone PDF reader.

    Scope Note: 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.

    Editorial Note: Rationale: There may be a need to give a textual description of the environment for additional explanation.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:Environment

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasEnvironmentPurpose
    Definition: Definition: The use(s) supported by the specified environment.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/environmentPurpose
    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.

    Editorial Note: 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.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:Environment

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/environmentPurpose

    [back to property list] [back to top]
    Property: premis:hasEvent
    Definition: Definition: The event associated with the object or an agent.

    Scope Note: Usage Notes: Use to link to events that are not associated with relationships between objects, such as format validation, virus checking, etc.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:Agentpremis:Object

    Range: premis:Event

    [back to property list] [back to top]
    Property: premis:hasEventDateTime
    Definition: Definition: The single date and time, or date and time range, at or during which the event occurred.

    Comment: Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime
    Example: 2001-10-26T19:32:52+00:00

    Scope Note: Usage Notes: Recommended practice is to record the most specific time possible and to designate the time zone.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Event

    Range: xsd:dateTime Offsite link

    [back to property list] [back to top]
    Property: premis:hasEventDetail
    Definition: Definition: Additional information about the event.

    Comment: Examples: Object permanently withdrawn by request of Caroline Hunt, Program=“MIGJP2JP2K”; version=“2.2”

    Scope Note: 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.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Event

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasEventOutcome
    Definition: Definition: A categorization of the overall result of the event in terms of success, partial success, or failure.

    Comment: Data Constraint: Value should be taken from a controlled vocabulary.
    Examples: 00 [a code meaning “action successfully completed”], CV-01 [a code meaning “checksum validated”]

    Scope Note: 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.

    Editorial Note: 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.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:EventOutcomeInformation

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasEventOutcomeDetail
    Type: owl:ObjectProperty Offsite link

    Domain: premis:EventOutcomeInformation

    Range: premis:EventOutcomeDetail

    [back to property list] [back to top]
    Property: premis:hasEventOutcomeDetailNote
    Definition: Definition: A detailed description of the result or product of the event in textual form.

    Comment: Examples: LZW compressed file, Non-standard tags found in header

    Editorial Note: Rationale: Additional information in textual form may be needed about the outcome of the event.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:EventOutcomeDetail

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasEventOutcomeInformation
    Type: owl:ObjectProperty Offsite link

    Domain: premis:Event

    Range: premis:EventOutcomeInformation

    [back to property list] [back to top]
    Property: premis:hasEventRelatedAgent
    Comment: 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.
    Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.

    Type: owl:ObjectProperty Offsite link

    SubProperty Of: premis:hasAgent

    Domain: premis:Event

    Range: premis:Agent

    [back to property list] [back to top]
    Property: premis:hasEventRelatedObject
    Definition: Definition: Information about an object associated with an event.

    Comment: Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.

    Editorial Note: Rationale: Digital provenance often requires that relationships between objects and events are documented.

    Type: owl:ObjectProperty Offsite link

    SubProperty Of: premis:hasObject

    Domain: premis:Event

    Range: premis:Object

    [back to property list] [back to top]
    Property: premis:hasEventType
    Definition: Definition: A categorization of the nature of the event.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/eventType
    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.

    Editorial Note: Rationale: Categorizing events will aid the preservation repository in machine processing of event information, particularly in reporting.

    Type: owl:ObjectProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Event

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/eventType

    [back to property list] [back to top]
    Property: premis:hasFixity
    Type: owl:InverseFunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:ObjectCharacteristics

    Range: premis:Fixity

    [back to property list] [back to top]
    Property: premis:hasFormat
    Type: owl:ObjectProperty Offsite link

    Domain: premis:ObjectCharacteristics

    Range: premis:Format

    [back to property list] [back to top]
    Property: premis:hasFormatDesignation
    Type: owl:ObjectProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Format

    Range: premis:FormatDesignation

    [back to property list] [back to top]
    Property: premis:hasFormatName
    Definition: Definition: A designation of the format of the file or bitstream.

    Comment: Data Constraint: Value should be taken from a controlled vocabulary.
    Examples: Text/sgml, image/tiff/geotiff, Adobe PDF, DES, PGP, base64, unknown, LaTex

    Scope Note: Usage Notes: For unidentified formats, formatName may be recorded as “unknown”.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:FormatDesignation

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasFormatNote
    Definition: Definition: Additional information about format.

    Comment: Examples: tentative identification, disjunction, multiple format identifications found

    Scope Note: Usage Notes: The formatNote may contain free text, a reference pointer, or a value from a controlled list.

    Editorial Note: Rationale: Qualifying information may be needed to supplement format designation and registry information or record a status for identification.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:Format

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasFormatRegistry
    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:Format

    Range: premis:FormatRegistry

    [back to property list] [back to top]
    Property: premis:hasFormatRegistryKey
    Definition: Definition: The unique key used to reference an entry for this format in a format registry.

    Comment: Examples: info:gdfr/fred/f/tiff, TIFF/6.0

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:FormatRegistry

    [back to property list] [back to top]
    Property: premis:hasFormatRegistryName
    Definition: Definition: A designation identifying the referenced format registry.

    Comment: Examples: PRONOM, www.nationalarchives.gov.uk/pronom, Representation Information Registry Repository, FRED: A format registry demonstration, release 0.07

    Scope Note: Usage Notes: This can be a formal name, internally used name, or URI.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:FormatRegistry

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasFormatRegistryRole
    Definition: Definition: The purpose or expected use of the registry.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/formatRegistryRole
    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.

    Editorial Note: 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.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:FormatRegistry

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/formatRegistryRole

    [back to property list] [back to top]
    Property: premis:hasFormatVersion
    Definition: Definition: The version of the format named in formatName.

    Comment: Examples: 6.0, 2003

    Scope Note: Usage Notes: If the format is versioned, formatVersion should be recorded. It can be either a numeric or chronological designation.

    Editorial Note: Rationale: Many authority lists of format names are not granular enough to indicate version, for example, MIME Media types.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:FormatDesignation

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasHardware
    Type: owl:ObjectProperty Offsite link

    Domain: premis:Environment

    Range: premis:Hardware

    [back to property list] [back to top]
    Property: premis:hasHardwareName
    Definition: Definition: Manufacturer, model, and version (if applicable) of the hardware.

    Comment: Examples: Intel Pentium III, 1 GB DRAM, Windows XPcompatible joystick

    Scope Note: 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.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Hardware

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasHardwareOtherInformation
    Definition: Definition: Additional requirements or instructions related to the hardware referenced in hwName.

    Comment: Examples: 32MB minimum, Required RAM for Apache is unknown

    Scope Note: Usage Notes: This could be an identifier or URI used to point to hardware documentation.

    Editorial Note: 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.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:Hardware

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasHardwareType
    Definition: Definition: Class or category of the hardware.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/hardwareType
    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.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:Hardware

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/hardwareType

    [back to property list] [back to top]
    Property: premis:hasIdentifier
    Type: owl:ObjectProperty Offsite link
    owl:InverseFunctionalProperty Offsite link

    Domain: premis:Agentpremis:Dependencypremis:Eventpremis:LicenseInformationpremis:Objectpremis:RightsDocumentationpremis:RightsStatement

    [back to property list] [back to top]
    Property: premis:hasIdentifierType
    Definition: Definition: A designation of the domain within which the identifier is unique.

    Comment: Examples: DLC, DRS, hdl:4263537
    Data Constraint: Value should be taken from controlled vocabulary.

    Scope Note: 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.

    Editorial Note: Rationale: Identifier values cannot be assumed to be unique across domains. The combination of identifierType and identifierValue should ensure uniqueness.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Identifier

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasIdentifierValue
    Comment: Defnition: The value of the Identifier.
    Examples: 0000000312 (Representation), IU2440 (File), WAC1943.56 (File), http://nrs.harvard.edu/urn-3:FHCL.Loeb:sal (File), IU2440-1 (Bitstream)

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Identifier

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasInhibitorKey
    Definition: Definition: The decryption key or password.

    Comment: Example: [DES decryption key]

    Scope Note: 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.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Inhibitors

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasInhibitors
    Type: owl:ObjectProperty Offsite link

    Domain: premis:ObjectCharacteristics

    Range: premis:Inhibitors

    [back to property list] [back to top]
    Property: premis:hasInhibitorTarget
    Definition: Definition: The content or function protected by the inhibitor.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/inhibitorTarget
    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.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:Inhibitors

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/inhibitorTarget

    [back to property list] [back to top]
    Property: premis:hasInhibitorType
    Definition: Definition: The inhibitor method employed.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/inhibitorType
    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.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:Inhibitors

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/inhibitorType

    [back to property list] [back to top]
    Property: premis:hasIntellectualEntity
    Definition: Definition: An intellectual entity associated with the object.

    Scope Note: 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.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:Object

    Range: premis:IntellectualEntity

    [back to property list] [back to top]
    Property: premis:hasKeyInformation
    Type: owl:ObjectProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Signature

    [back to property list] [back to top]
    Property: premis:hasLicenseTerms
    Definition: Definition: Text describing the license or agreement by which permission was granted.

    Scope Note: Usage Notes: This could contain the actual text of the license or agreement or a paraphrase or summary.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:LicenseInformation

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasMessageDigest
    Definition: Definition: The output of the message digest algorithm.

    Comment: Example: 7c9b35da4f2ebd436f1cf88e5a39b3a257edf4a22be3c955ac49da2e2107b67a1924419563

    Editorial Note: Rationale: This must be stored so that it can be compared in future fixity checks.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Fixity

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasMessageDigestAlgorithm
    Definition: Definition: The specific algorithm used to construct the message digest for the digital object.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions
    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.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:Fixity

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions

    [back to property list] [back to top]
    Property: premis:hasMessageDigestOriginator
    Definition: Definition: The agent that created the original message digest that is compared in a fixity check.

    Comment: Examples: DRS, A0000978

    Scope Note: 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).

    Editorial Note: 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.

    History Note: 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.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Fixity

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasObject
    Definition: Definition: Information about an object associated with an event or rightsstatement.

    Comment: Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.

    Editorial Note: 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.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:Eventpremis:RightsStatement

    Range: premis:Object

    [back to property list] [back to top]
    Property: premis:hasObjectCharacteristics
    Type: owl:InverseFunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:Bitstreampremis:File

    Range: premis:ObjectCharacteristics

    [back to property list] [back to top]
    Property: premis:hasOriginalName
    Definition: Definition: The name of the object as submitted to or harvested by the repository, before any renaming by the repository.

    Comment: Example: N419.pdf

    Scope Note: 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.

    Editorial Note: 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.

    History Note: 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.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Filepremis:Representation

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasPreservationLevel
    Type: owl:ObjectProperty Offsite link

    Domain: premis:Filepremis:Representation

    Range: premis:PreservationLevel

    [back to property list] [back to top]
    Property: premis:hasPreservationLevelDateAssigned
    Definition: Definition: The date, or date and time, when a particular preservationLevelValue was assigned to the object.

    Comment: Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime
    Examples: 2001-10-26T19:32:52+00:00

    Editorial Note: 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.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:PreservationLevel

    Range: xsd:dateTime Offsite link

    [back to property list] [back to top]
    Property: premis:hasPreservationLevelRationale
    Definition: Definition: The reason a particular preservationLevelValue was applied to the object.

    Comment: Examples: user pays, legislation, defective file, bit-level preservation only available for this format

    Scope Note: 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.

    Editorial Note: Rationale: Application of a particular preservationLevelValue may require justification, especially if it differs from that usually applied according to repository policy.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:PreservationLevel

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasPreservationLevelRole
    Definition: Definition: A value indicating the context in which a set of preservation options is applicable.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/preservationLevelRole
    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.

    Editorial Note: Rationale: Repositories may assign preservationLevelValues in different contexts which must be differentiated, and may need to record more than one context.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:PreservationLevel

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/preservationLevelRole

    [back to property list] [back to top]
    Property: premis:hasPreservationLevelValue
    Definition: Definition: A value indicating the set of preservation functions expected to be applied to the object.

    Comment: Examples: bit-level, full, fully supported with future migrations (File), 0
    Data Constraint: Value should be taken from a controlled vocabulary.

    Scope Note: 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.

    Editorial Note: 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.

    History Note: Creation / Maintenance Notes: The preservation level may be assigned by the repository or requested by the depositor and submitted as metadata.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:PreservationLevel

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasRelatedObject
    Definition: Definition: This property related to all object belonging to a RelatedObjectIdentification to describe the related objects as an aggregation.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:RelatedObjectIdentification

    Range: premis:Object

    [back to property list] [back to top]
    Property: premis:hasRelatedObjectSequence
    Definition: Definition: The order of the related object relative to other objects with the same type of relationship.

    Editorial Note: 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.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:RelatedObjectIdentification

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasRelatedStatuteInformation
    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.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:StatuteInformation

    Range: premis:StatuteInformation

    [back to property list] [back to top]
    Property: premis:hasRelationship
    Definition: Definition: This property links one object to one or more other objects.

    Comment: 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.
    Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:Object

    Range: premis:Objectpremis:RelatedObjectIdentification

    [back to property list] [back to top]
    Property: premis:hasRestriction
    Definition: Definition: A condition or limitation on the act.

    Comment: Examples: No more than three, Allowed only after one year of archival retention has elapsed, Rightsholder must be notified after completion of act

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:RightsGranted

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasRightsDocumentation
    Type: owl:ObjectProperty Offsite link

    Domain: premis:RightsStatement

    Range: premis:RightsDocumentation

    [back to property list] [back to top]
    Property: premis:hasRightsDocumentationRole
    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.

    Editorial Note: Rationale: This information distinguishes the purpose of the supporting documentation especially when there are multiple documentation identifiers.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:RightsDocumentation

    Range: skos:Concept Offsite link

    [back to property list] [back to top]
    Property: premis:hasRightsGranted
    Type: owl:ObjectProperty Offsite link

    Domain: premis:RightsStatement

    Range: premis:RightsGranted

    [back to property list] [back to top]
    Property: premis:hasRightsGrantedNote
    Definition: Definition: Additional information about the rights granted.

    Scope Note: 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.

    Editorial Note: Rationale: A textual description of the rights granted may be needed for additional explanation.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:RightsGranted

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasRightsRelatedAgent
    Comment: Extensions: One can extend this property to use more fine grained properties by defining the fine grained properties as subproperties of this property.
    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.

    Type: owl:ObjectProperty Offsite link

    SubProperty Of: premis:hasAgent

    Domain: premis:RightsStatement

    Range: premis:Agent

    [back to property list] [back to top]
    Property: premis:hasRightsStatement
    Definition: Definition: A rights statement associated with the object.

    Editorial Note: Rationale: A repository may choose to link from a rights statement to an object or from an object to a rights statement or both.

    Type: owl:ObjectProperty Offsite link

    Domain: premis:Agentpremis:Object

    Range: premis:RightsStatement

    [back to property list] [back to top]
    Property: premis:hasRightsStatementNote
    Definition: Definition: Additional information about the RightsStatement of an object.

    Comment: Examples: Copyright expiration expected in 2010 unless renewed. License is embedded in XMP block in file header.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:RightsStatement

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSignature
    Type: owl:ObjectProperty Offsite link

    Domain: premis:Bitstreampremis:File

    Range: premis:Signature

    [back to property list] [back to top]
    Property: premis:hasSignatureEncoding
    Definition: Definition: The encoding used for the values of signatureValue, keyInformation.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/signatureEncoding
    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.

    Editorial Note: Rationale: These values cannot be interpreted correctly if the encoding is unknown.

    Type: owl:ObjectProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Signature

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/signatureEncoding

    [back to property list] [back to top]
    Property: premis:hasSignatureMethod
    Definition: Definition: A designation for the encryption and hash algorithms used for signature generation.

    Comment: Data Constraint: Values are taken from a SKOS vocabulary
    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.

    Editorial Note: Rationale: The same algorithms must be used for signature validation.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:Signature

    Range: skos:Concept Offsite link

    [back to property list] [back to top]
    Property: premis:hasSignatureProperties
    Definition: Definition: Additional information about the generation of the signature.

    Scope Note: 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.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:Signature

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSignatureValidationRules
    Definition: Definition: The operations to be performed in order to validate the digital signature.

    Scope Note: 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.

    Editorial Note: Rationale: The repository should not assume that the procedure for validating any particular signature will be known many years in the future without documentation.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Signature

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSignatureValue
    Definition: Definition: The digital signature; a value generated from the application of a private key to a message digest.

    Comment: Example: juS5RhJ884qoFR8flVXd/rbrSDVGn40CapgB7qeQiT+rr0NekEQ6BHhUA8dT3+BCTBUQI0dBjlml9lwzENXvS83zRECjzXbMRTUtVZiPZG2pqKPnL2YU3A9645UCjTXU+jgFumv7k78hieAGDzNci+PQ9KRmm//icT7JaYztgt4=

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Signature

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSigner
    Definition: Definition: The individual, institution, or authority responsible for generating the signature.

    Scope Note: 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

    Editorial Note: Rationale: The signer might also be carried in the keyInformation, but it can be accessed more conveniently if recorded here.

    Type: owl:AnnotationProperty Offsite link

    Domain: premis:Signature

    Range: premis:Agent
    xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSignificantProperties
    Type: owl:ObjectProperty Offsite link

    Domain: premis:Object

    Range: premis:SignificantProperties

    [back to property list] [back to top]
    Property: premis:hasSignificantPropertiesType
    Definition: Definition: The aspect, facet, or attribute of an object about which significant properties are being described.

    Comment: Examples: content, structure, behavior, page count, page width, typeface, hyperlinks (representation), image count (representation), color space [for an embedded image] (bitstream)

    Scope Note: Usage Notes: This semantic unit is optional and may be used as part of a facet:detail pair with significantPropertiesValue.

    Editorial Note: Rationale: Repositories may choose to describe significant properties based on a particular aspect or attribute of an object.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:SignificantProperties

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSignificantPropertiesValue
    Definition: Definition: Description of the characteristics of a particular object subjectively determined to be important to maintain through preservation actions.

    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

    Scope Note: 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.

    Editorial Note: Rationale: Repositories may choose to describe significant properties based on a particular aspect or attribute of an object.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:SignificantProperties

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSize
    Definition: Definition: The size in bytes of the file or bitstream stored in the repository.

    Comment: Example: 2038937

    Scope Note: 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.

    Editorial Note: 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.

    History Note: Creation / Maintenance Notes: Automatically obtained by the repository.

    Type: owl:DatatypeProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:ObjectCharacteristics

    Range: xsd:long Offsite link

    [back to property list] [back to top]
    Property: premis:hasSoftware
    Type: owl:ObjectProperty Offsite link

    Domain: premis:Environment

    Range: premis:Software

    [back to property list] [back to top]
    Property: premis:hasSoftwareDependency
    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.

    Comment: Example: GNU gcc >=2.7.2

    Scope Note: 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.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:Software

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSoftwareName
    Definition: Definition: Manufacturer and title of the software application.

    Comment: Examples: Adobe Photoshop, Adobe Acrobat Reader

    Scope Note: Usage Notes: Include manufacturer when this helps to identify or disambiguate the product, for example, use “Adobe Photoshop” rather than “Photoshop.”

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Software

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSoftwareOtherInformation
    Definition: Definition: Additional requirements or instructions related to the software referenced in swName.

    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.

    Scope Note: Usage Notes: This could be a reliable persistent identifier or URI pointing to software documentation within or outside the repository.

    Type: owl:DatatypeProperty Offsite link

    Domain: premis:Software

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasSoftwareType
    Definition: Definition: Class or category of software.

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/softwareType
    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.

    Editorial Note: Rationale: Several different layers of software can be required to support an object.

    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:Software

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/softwareType

    [back to property list] [back to top]
    Property: premis:hasSoftwareVersion
    Definition: Definition: The version or versions of the software referenced in swName.

    Comment: Examples: >=2.2.0, 6.0, 2003

    Scope Note: Usage Notes: If there is no formal version, the date of issuance can be used.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:Software

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasStartDate
    Definition: Definition: The beginning date of the permission granted.

    Comment: Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:ApplicableDates

    Range: xsd:dateTime Offsite link

    [back to property list] [back to top]
    Property: premis:hasStatuteCitation
    Definition: Definition: An identifying designation for the statute.

    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

    Scope Note: Usage Notes: Use standard citation form when applicable.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:StatuteInformation

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasStatuteInformationDeterminationDate
    Definition: Definition: The date that the determination was made that the statute authorized the permission(s) noted.

    Comment: Data Constraint: To aid machine processing, value should use a structured form: xsd:dateTime
    Example: 2001-10-26T19:32:52+00:00

    Editorial Note: 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.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:StatuteInformation

    Range: xsd:dateTime Offsite link

    [back to property list] [back to top]
    Property: premis:hasStatuteJurisdiction
    Definition: Definition: The country or other political body enacting the statute.

    Comment: Data Constraint: Values should be taken from a controlled vocabulary.
    Examples: us, de, be

    Editorial Note: Rationale: The connection between the object and the rights granted is based on jurisdiction.

    Type: owl:FunctionalProperty Offsite link
    owl:DatatypeProperty Offsite link

    Domain: premis:StatuteInformation

    Range: xsd:string Offsite link

    [back to property list] [back to top]
    Property: premis:hasStorage
    Type: owl:ObjectProperty Offsite link

    Domain: premis:Bitstreampremis:File

    Range: premis:Storage

    [back to property list] [back to top]
    Property: premis:hasStorageMedium
    Definition: Definition: The physical medium on which the object is stored (e.g., magnetic tape, hard disk, CD-ROM, DVD).

    Comment: Data Constraint: Values are taken from the SKOS vocabulary: http://id.loc.gov/vocabulary/preservation/storageMedium
    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.

    Editorial Note: 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.

    Type: owl:ObjectProperty Offsite link
    owl:FunctionalProperty Offsite link

    Domain: premis:Storage

    Range: [Restriction] On property skos:inScheme Offsite link with value http://id.loc.gov/vocabulary/preservation/storageMedium

    [back to property list] [back to top]
    Property: premis:hasTermOfGrant
    Type: owl:FunctionalProperty Offsite link
    owl:ObjectProperty Offsite link

    Domain: premis:RightsGranted

    Range: premis:TermOfGrant

    [back to property list] [back to top]
    Property: premis:hasTermOfRestriction
    Type: owl:ObjectProperty Offsite link

    Domain: premis:RightsGranted

    Range: premis:TermOfRestriction

    [back to property list] [back to top]
  • Alternate Formats