<?xml version="1.0"?>
<!--
SPDX-FileCopyrightText: 2025 Lady <https://www.ladys.computer/about/#lady>
SPDX-License-Identifier: CC0-1.0
-->
<!DOCTYPE NamedIndividual SYSTEM "../../DTD">
<NamedIndividual name="https://github.com/duraspace/pcdm/wiki">
	<label xml:lang="en">P·C·D·M</label>
	<comment xml:lang="en">
		<p>
			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.
			It comprises five parts :⁠—
		</p>
		<list>
			<item>
				<p>
					<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.
					This ontology only omits the term <resource name="pcdm:AlternateOrder"/>, whose meaning and utility is unclear.
				</p>
			</item>
			<item>
				<p>
					<strong>P·C·D·M Use</strong> provides subclasses for <ptr target="pcdm:File"/> which identify its intended <em>use</em>.
					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.
				</p>
			</item>
			<item>
				<p>
					<strong>P·C·D·M Rights</strong> provides a few terms for specifying temporary, time‐limited overrides to rights statements.
					As this is use·case is fairly domain‐specific and niche, this ontology does not bother defining its terms.
				</p>
			</item>
			<item>
				<p>
					<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>.
					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.
				</p>
			</item>
			<item>
				<p>
					<strong>P·C·D·M File Formats</strong> provides a set of <ref target="skos:Concept">Concepts</ref> for denoting specific file format genres.
					These are a bit undocumented, and don¦t have a clear use·case, so they not been encoded into this ontology.
				</p>
			</item>
		</list>
	</comment>
	<type>
		<resource name="dcterms:BibliographicResource"/>
	</type>
</NamedIndividual>