Lady’s Gitweb - Vocab/blob - data/named_individuals/_PCDM_

   1 <?xml version="1.0"?>
   2 <!--
   3 SPDX-FileCopyrightText: 2025 Lady <https://www.ladys.computer/about/#lady>
   4 SPDX-License-Identifier: CC0-1.0
   5 -->
   6 <!DOCTYPE NamedIndividual SYSTEM "../../DTD">
   7 <NamedIndividual name="https://github.com/duraspace/pcdm/wiki">
   8         <label xml:lang="en">P·C·D·M</label>
   9         <comment xml:lang="en">
  10                 <p>
  11                         The Portland Common Data Model (P·C·D·M) is a set of vocabularies published by Duraspace and used by certain institutions and communities in the library and cultural heritage sphere for modelling their collections.
  12                         It comprises five parts :⁠—
  13                 </p>
  14                 <list>
  15                         <item>
  16                                 <p>
  17                                         <strong>P·C·D·M Models</strong> builds on top of <ptr target="(OAI-ORE)"/> to provide basic structural modelling for <ref target="pcdm:Collection">Collections</ref>, their <ref target="pcdm:Object">Objects</ref>, and the <ref target="pcdm:File">Files</ref> associated with them.
  18                                         This ontology only omits the term <resource name="pcdm:AlternateOrder"/>, whose meaning and utility is unclear.
  19                                 </p>
  20                         </item>
  21                         <item>
  22                                 <p>
  23                                         <strong>P·C·D·M Use</strong> provides subclasses for <ptr target="pcdm:File"/> which identify its intended <em>use</em>.
  24                                         The choice of modelling this using classes, rather than a relationship like <ptr target="anno:hasPurpose"/>, is a bit suspect, but a conversion from one to the other is not especially difficult.
  25                                 </p>
  26                         </item>
  27                         <item>
  28                                 <p>
  29                                         <strong>P·C·D·M Rights</strong> provides a few terms for specifying temporary, time‐limited overrides to rights statements.
  30                                         As this is use·case is fairly domain‐specific and niche, this ontology does not bother defining its terms.
  31                                 </p>
  32                         </item>
  33                         <item>
  34                                 <p>
  35                                         <strong>P·C·D·M Works</strong> expands P·C·D·M Models to add the concepts of <ref target="pcdmworks:Work">Work</ref> and <ref target="pcdmworks:FileSet">File Set</ref>.
  36                                         It also defines two classes for use with <ptr target="(IIIF)"/>, <resource name="pcdmworks:Range"/> and <resource name="pcdmworks:TopRange"/>, which are more suspect in utility and not included in this ontology.
  37                                 </p>
  38                         </item>
  39                         <item>
  40                                 <p>
  41                                         <strong>P·C·D·M File Formats</strong> provides a set of <ref target="skos:Concept">Concepts</ref> for denoting specific file format genres.
  42                                         These are a bit undocumented, and don¦t have a clear use·case, so they not been encoded into this ontology.
  43                                 </p>
  44                         </item>
  45                 </list>
  46         </comment>
  47         <type>
  48                 <resource name="dcterms:BibliographicResource"/>
  49         </type>
  50 </NamedIndividual>