Open Availability¶
Make a knowledge resource reachable by anyone under explicit, non-restrictive, machine-operative terms so that reuse shifts from negotiate-per-use to consult-the-license, unlocking combinatorial composition across an ecosystem.
Core Idea¶
Open availability is the governance posture in which a knowledge resource — an ontology, dataset, software package, specification, or publication — is made accessible to any user under explicit, non-restrictive terms, converting a gatekept asset into one with known permissive terms supporting downstream reuse without per-use negotiation. Four commitments travel together: findability (public lookup), accessibility (open retrieval), explicit use terms (an operative license), and non-restrictiveness (terms that actually permit reuse). The first three without the fourth yield only nominal openness.
Scope of Application¶
Open availability lives within knowledge-resource governance; its substance is one coordination posture applied to non-rivalrous knowledge resources.
- Biomedical ontologies — the OBO Foundry principle requiring licenses that permit cross-ontology composition.
- Research data — the FAIR principles formalizing three of the four commitments.
- Open-source software — the OSI Open Source Definition codifying the use-terms commitment.
- Open-access publishing — the Budapest, Bethesda, and Berlin declarations.
- Open standards and government data — W3C/IETF/ISO practice and public-data portals.
Commons cases that share the word "open" (a forest, the airwaves) belong to a different prime family (commons, tragedy_of_the_commons), where the resource is rivalrous and the failure mode is overuse, not gated reuse.
Clarity¶
Naming open availability separates availability (the resource exists somewhere reachable) from open availability (reachable by anyone under explicit, non-restrictive terms). It names the failure mode — nominal availability without substantive openness — the resource in a public repository under terms that block the reuse it was meant to enable. It also pulls apart three layers — technical, legal, and social — so a maintainer can localize a breakdown to the layer where the fix actually moves the needle.
Manages Complexity¶
A reuse decision in a closed ecosystem is a thicket of bespoke transactions — for every resource, identify the rights holder, reach them, describe the use, await terms — a per-pair cost growing combinatorially at scale. Open availability collapses that thicket onto the license: explicit permissive terms pre-authorise the whole class of uses, dropping per-use cost to "consult the license." The posture reduces to four readable commitments checked once per resource, plus pairwise license compatibility, which together predict the ecosystem's combinatorial reach.
Abstract Reasoning¶
Reduced to a four-commitment checklist over a three-layer stack, open availability licenses several inferences. A diagnostic move localizes a stalled composition to the failed commitment and layer. An interventionist move fixes the layer that is actually broken and predicts the change in reach — a better server cannot cure a restrictive license. A boundary-drawing move decides whether a resource is composable and whether two are combinable (requiring compatible licenses). A predictive move forecasts combinatorial reach at population scale and the standing enclosure risk of re-closure.
Knowledge Transfer¶
Within knowledge-resource governance open availability transfers as mechanism across substrates sharing the four-part architecture, because the cargo is one coordination move: convert negotiate-per-use into consult-the-license. The transfer is unusually literal and documented — open-source licensing discipline ported into open-access publishing and open data, and Creative Commons was designed to carry the GPL-style architecture into other media. Beyond knowledge resources the substantive content is largely the union of parents already catalogued — transparency, mediator_availability_constraint, and the governance family — plus one sharp move, explicit-license-as-coordination-mechanism, now carried by the parent prime license_as_coordination. That coordination move is the portable core; the posture as named stays home.
Relationships to Other Abstractions¶
Current abstraction Open Availability Domain-specific
Parents (1) — more general patterns this builds on
-
Open Availability is a kind of License as Coordination Prime
Open availability is license-as-coordination specialized to openly reusable knowledge resources.
Hierarchy paths (5) — routes to 4 parentless roots
- Open Availability → License as Coordination → Coordination → Concurrency
- Open Availability → License as Coordination → Coordination → Dependency
- Open Availability → License as Coordination → Coordination → Task Interdependence → Dependency
- Open Availability → License as Coordination → Coordination → Mobilization → Latent Realizable Capacity
- Open Availability → License as Coordination → Coordination → Task Interdependence → Network → Reservoir-Flux Network → Conservation Laws → Invariance
Neighborhood in Abstraction Space¶
Open Availability sits in a moderately populated region (58th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.
Family — Trust Infrastructure for Shared Knowledge (6 abstractions)
Nearest neighbors
- Collaborative Maintenance — 0.85
- Format Relation — 0.85
- Declared Equivalence Mapping — 0.84
- Textual Definition — 0.84
- Robust Accessibility — 0.83
Computed from structural-signature embeddings · 2026-07-12