3 SPDX-FileCopyrightText: 2025 Lady <https://www.ladys.computer/about/#lady>
4 SPDX-License-Identifier: CC0-1.0
6 <!DOCTYPE NamedIndividual SYSTEM "../../DTD">
7 <NamedIndividual name="https://github.com/ewilderj/doap">
8 <label xml:lang="en">D·O·A·P</label>
9 <comment xml:lang="en">
11 Description Of A Project (D·O·A·P) is an early vocabulary aimed at describing software projects, and in particular open‐source ones.
12 In the software distribution world, it has been largely supplanted by <ref target="https://spdx.dev">S·P·D·X</ref>, but S·P·D·X is undesirable for more general metadata purposes for a number of reasons.<note n="1">
14 For one, S·P·D·X name·space I·R·I¦s are namespaced to the specific (patch!) version of S·P·D·X, so that, for example, metadata written under version 3.0.0 of S·P·D·X is not compatible with version 3.0.1.
15 This is, frankly, absurd.
18 Consequently, D·O·A·P still gets a fair bit of use today.
21 This ontology aims to support the core functionality of D·O·A·P, but it ignores some aspects of the model, including :—
26 The subclasses of <ptr target="doap:Repository"/>: <resource name="doap:ArchRepository"/>, <resource name="doap:BazaarBranch"/>, <resource name="doap:BKRepository"/>, <resource name="doap:CVSRepository"/>, <resource name="doap:DarcsRepository"/>, <resource name="doap:GitBranch"/>, <resource name="doap:GitRepository"/>, <resource name="doap:HgRepository"/>, and <resource name="doap:SVNRepository"/>.
27 Using <ptr target="dcterms:format"/> to indicate the format of the repository instead is recommended, in situations where this information is relevant.
32 The properties <resource name="doap:anon-root"/> and <resource name="doap:module"/>, which are only useful for certain kinds of <ref target="doap:Repository">Repository</ref>.
38 <resource name="dcterms:BibliographicResource"/>