Skip to content

Collaborative Maintenance

Keep a shared knowledge artifact current through an open community working under five documented-and-exercised governance pathways — proposal, review, dispute resolution, deprecation, and attribution — rather than a single custodian.

Core Idea

Collaborative maintenance is the governance arrangement in which a shared knowledge artifact — a controlled vocabulary, ontology, schema, or standards document — is kept current by an open community under publicly documented decision rules, not a lone custodian. The OBO Foundry reference case requires five coordinated, exercised mechanisms: a change-proposal pathway, a review-and-approval pathway, a dispute-resolution pathway, a deprecation policy, and an attribution-and-provenance rule. The arrangement is constitutively ongoing.

Scope of Application

Collaborative maintenance lives across the governance of informational commons — shared, indefinitely-lived knowledge or standards artifacts kept current by distributed stewardship under explicit norms.

  • Open scientific ontologies and vocabularies — the home turf (OBO, Gene Ontology, schema.org).
  • Public-knowledge wikis — Wikipedia and Wikidata editorial governance over an encyclopedic artifact.
  • Open-source projects with stated governance — Linux kernel, Python PEPs, Kubernetes, Apache.
  • Standards bodies — IETF working groups, W3C consortia, ISO technical committees.
  • Open mapping projects — OpenStreetMap edit-and-review norms over a geospatial artifact.
  • Metadata standards and registries — schema projects beyond the biomedical core.

Clarity

The concept separates a property adopters need to assess from the surface features they read it off — recent commits, an active tracker, a named host, none of which establish that the artifact stays current. It reframes "is this maintained?" structurally: which of the five pathways are documented and visible in the contribution trace? That replaces guessing from how busy the repository looks.

Manages Complexity

The landscape an adopter faces — thousands of ontologies, each hosted, paced, and governed differently — compresses to one fixed checklist: are the five pathways present and exercised? Instead of reconstructing "will this stay interpretable?" from commit volume and host reputation for every candidate, you score each against one short governance template, and read predictable brittleness off whichever pathway is missing.

Abstract Reasoning

The concept supports diagnosis (reading the specific failure mode off the absent pathway — a missing deprecation rule predicts silent term-deletion downstream), inversion of the naive activity proxy (a busy tracker over an undocumented rule signals a bus-factor-of-one custodian), interventionist prediction (install a pathway, name the brittleness it removes), boundary-drawing (does the indefinite-lifetime commitment hold?), and comparative scoring of rival candidates against one template.

Knowledge Transfer

Within knowledge-infrastructure governance the concept transfers as mechanism: a curator applies the identical five-pathway checklist to a new schema, wiki, codebase, or standard, and reads the same brittleness off the same missing slot — these are co-instances, not analogies. Beyond that family the transfer becomes metaphor: the artifact-specific cargo (deprecation-with-redirects, version-controlled proposal channels) does not survive extraction, so the honest move carries the parent prime — commons governance / distributed stewardship (Ostrom) — not the named OBO concept.

Relationships to Other Abstractions

Local relationship map for Collaborative MaintenanceParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.CollaborativeMaintenanceDOMAINPrime abstraction: Maintenance — is part ofMaintenancePRIMEPrime abstraction: Provenance — is part ofProvenancePRIMEPrime abstraction: Commons Governance — is a kind ofCommonsGovernancePRIME

Current abstraction Collaborative Maintenance Domain-specific

Parents (3) — more general patterns this builds on

  • Collaborative Maintenance is a kind of Commons Governance Prime

    Collaborative maintenance is commons governance specialized to versioned knowledge and standards artifacts.

  • Collaborative Maintenance is part of Maintenance Prime

    Ongoing maintenance is a defining constituent of collaborative maintenance rather than merely a precondition.

  • Collaborative Maintenance is part of Provenance Prime

    Recoverable contribution and change provenance is one of collaborative maintenance's defining governance pathways.

Hierarchy paths (8) — routes to 7 parentless roots

Neighborhood in Abstraction Space

Collaborative Maintenance sits in a crowded region of the domain-specific corpus (28th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Trust Infrastructure for Shared Knowledge (6 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12