The Core Insight
A specification is a non-rival, re-expressible artifact: sharing it doesn't diminish it, and anyone can re-implement it. Attempting to fund and coordinate such artifacts primarily by selling exclusive copies is structurally misaligned — it produces lock-in, underinvestment in maintenance, and transaction-cost thickets.
Classic public-goods theory, club-goods theory, network-effects economics, and commons governance research all point to the same conclusion: the most robust model for digital standards is commons-first ownership of the artifact, paired with market and nonmarket capture of rival complements — and explicit institutions for maintenance, security, and coordination.
For venue media standards specifically, this means the specification should be freely available, while certification, integration, training, hosting, and assurance services provide the economic engine.
This Isn't New — It's Proven
The open-commons approach to technical standards has a history stretching back to the earliest days of computing. The PVC builds on institutional patterns that have repeatedly outperformed proprietary alternatives.
The Circulating Technique Culture (1970s)
Before software was routinely sold as a product, communities like the People's Computer Company and the Homebrew Computer Club circulated programs, techniques, and specifications through newsletters and meetings. Dennis Allison's Tiny BASIC (1975) was published as a portable, implementable specification — explicitly inviting reimplementation across different hardware. It was a design choice optimized for diffusion and recombination, not exclusion.
This "shared technique" path wasn't hypothetical — it was implemented, scaled across machines via reimplementation, and supported by publication institutions.
The RFC Series and Internet Standards (1969–present)
The Internet's foundational protocols were developed through the RFC series — open working notes shared for communal review and implementation. The IETF institutionalized this as "rough consensus and running code," emphasizing implementability and interoperability over centralized ownership.
This model produced TCP/IP, HTTP, DNS, and the infrastructure the entire digital economy runs on — not through exclusion, but through open publication and competitive implementation.
Foundation-Governed Open Source (2000s–present)
Organizations like the Apache Software Foundation, the W3C, and the Linux Foundation demonstrated that governance credibility — neutrality, transparency, earned authority — is itself a competitive advantage. Apache's "community over code" philosophy and the W3C's royalty-free patent policy are institutional innovations that keep standards implementable at scale.
The PVC's governance model draws directly from these proven templates.
The Proprietary Pivot — A Contested Choice
The shift to proprietary software wasn't inevitable — it was argued for. Bill Gates's 1976 "Open Letter to Hobbyists" explicitly framed copying as a problem and proposed that software should be sold as exclusive copies. This moment clarified competing design options: one path treats software as a commodity sold by excluding copies; another treats it as shared technique funded through complements and structured community support.
For venue media standards — where compatibility, network effects, and ecosystem health matter more than copy-exclusion — the shared-technique path is structurally superior.
The Economic Logic
Several bodies of economic theory converge on the same conclusion: open commons + competitive complements is the native model for standards like the PVC.
The PVC specification is non-rival (sharing doesn't diminish it) but governance capacity is congestible (maintainer attention, review bandwidth). This makes it a hybrid between a public good and a club good — requiring structured membership and governance around the scarce complements, not artificial scarcity of the artifact.
The PVC standard becomes more valuable as more venues, integrators, and platforms adopt it. Proprietary control fragments the ecosystem and reduces these network effects. Open standards maximize the size of the compatible network — which is where value comes from.
Returns often accrue not to the artifact itself, but to owners of complementary assets: hosting, integration, training, certification, and warranties. The PVC makes this explicit: the standard is free; the complements are the business model.
Maintaining a shared standard is a classic collective action challenge: as the beneficiary set grows, free-riding temptations increase. The PVC addresses this with structured funding (membership dues, certification revenue) and governance that ties rights to contributions.
How Proprietary Approaches Distort
When venue media standards are controlled by a single vendor or behind proprietary licensing, predictable distortions emerge. Understanding these failure modes explains why the PVC is designed the way it is.
Vendor Lock-in
Proprietary standards make switching costly. Once a venue's media infrastructure is built on a closed system, changing vendors means rebuilding from scratch. The open standard eliminates this by ensuring any conformant implementation can be substituted.
Underinvestment in Maintenance
Proprietary vendors optimize for new features that drive sales, not ongoing maintenance of shared infrastructure. Open-source research consistently shows that critical-but-boring maintenance is chronically underfunded under proprietary models. The PVC's funding portfolio addresses this directly.
Patent Thickets and Hold-up
Without explicit IPR governance, overlapping patent claims can create "thickets" that raise barriers to implementation. The PVC's royalty-free patent commitment — modeled on W3C and IETF practices — prevents this dynamic from fragmenting the ecosystem.
Contractual Scarcity and Rent Extraction
SaaS and API models can reintroduce excludability through contractual terms and access control — even when the underlying technology is not inherently scarce. This can block portability and third-party innovation, particularly when strong network effects create platform lock-in.
How Models Compare
No single model solves every challenge. The PVC deliberately combines the strengths of proven models while mitigating their failure modes. Here's how common approaches perform across key dimensions:
| Model | Creation | Maintenance | Funding | Scaling | Typical Failure Mode |
|---|---|---|---|---|---|
| Community Open Source | High | Med-Low | Low-Med | Very High | Maintainer burnout |
| Foundation-Governed OSS | High | Med-High | Medium | High | Governance capture; slow decisions |
| Proprietary SaaS | High | High | High | High | Ecosystem enclosure; weak portability |
| Open Core | Med-High | Medium | High | High | Community distrust; fork risk |
| Patronage / Crowdfunding | Medium | Medium | Low-Med | Medium | Popularity bias; critical work underfunded |
| PVC Model (Foundation + Complements) | High | High | High | High | Mitigated by explicit governance design |
Adapted from comparative analysis of model archetypes across creation incentives, maintenance incentives, funding capacity, quality control, liability capacity, and scaling dynamics.
The Assurance Pool
A native funding mechanism that prices stewardship effort, not scarce copies
The PVC is developing an assurance pool model: a mutualized fund where organizations contribute in proportion to their use of and dependence on the standard. The pool funds maintenance, conformance testing, security hardening, and incident response. Optionally, it can offer insurance-like services — prioritized fixes, audits, and compliance support.
Usage-Indexed Contribution
Organizations contribute based on how deeply they depend on the standard — measured through certification tier, number of venues, and integration depth.
Collective Risk Reduction
The pool converts diffuse benefit into structured financing, addressing the collective action problem that causes underfunding of shared infrastructure.
Transparent Allocation
All contributions and allocations are published. Funding decisions are governed by the same transparent processes as specification changes.
This model is "native" because it doesn't attempt to price scarce copies — it prices risk reduction and stewardship effort, which are genuinely scarce complements to the non-rival standard.
Who Benefits — and How
A native model must make "who pays" and "who benefits" legible and defensible. The PVC is designed so that every stakeholder both contributes and receives.
Venue Operators
What they want:
Reliability, portability, and no lock-in
What they contribute:
Certification dues, feedback, use cases
What they receive:
Open standard, certified partner network, assurance options
Risk without design:
Free-riding on the standard without contributing to its maintenance
Integrators & Service Providers
What they want:
Revenue and differentiation on a level playing field
What they contribute:
Implementation expertise, bug reports, spec contributions
What they receive:
Partner certification, referral network, standard to build on
Risk without design:
Race to bottom on price; enclosure temptations
Platform Vendors
What they want:
Ecosystem adoption and compatibility
What they contribute:
Conformant implementations, tooling, hosting services
What they receive:
Larger addressable market through standard compatibility
Risk without design:
Platform dominance eroding ecosystem diversity
Standards Stewards
What they want:
Implementability and ecosystem growth
What they contribute:
Spec process, IPR governance, conformance testing
What they receive:
Ecosystem legitimacy and growth
Risk without design:
Patent hold-up or governance fragmentation
Transition Paths
Most venues today operate on proprietary media systems. The path to PVC certification doesn't require ripping out existing infrastructure — it starts with transparency and builds toward full conformance.
Assess Against the Four Pillars
Review the open specification and map your current venue media systems against the four pillars. Many venues already meet some criteria without realizing it.
Adopt Transparency Practices
Start publishing venue media transparency metadata — what systems run, what triggers them, how data flows. This is the venue-media equivalent of software supply-chain transparency, and it builds trust with patrons and partners.
Engage Certified Partners
Work with PVC-certified integrators and service providers who compete on a level playing field created by the open standard. You're not locked to a single vendor — the standard ensures portability.
Apply for Certification
When your venue meets all four pillars, submit for certification review. Certified venues join the commons and gain access to the full partner ecosystem, governance participation, and assurance services.