Who owns the words? The economics of data and the future of landscape architecture

Language locked inside platforms

Every mature design discipline eventually faces the same tension: the words practitioners use to describe their work become embedded in software, templates, and enterprise libraries. At first this feels like convenience — predefined fields, consistent exports, faster documentation. Over time it becomes dependency. The taxonomy in the model is the taxonomy in the contract. Change vendor, and you change the grammar of the project archive.

Landscape architecture is late to this conversation compared with building engineering, but not exempt from it. Nurseries, councils, climate analysts, and asset managers already ask for structured metadata on planting, performance, and maintenance. When those structures live only inside commercial products, practices pay twice: once for the tool, and again in switching costs, retraining, and lost comparability across projects and jurisdictions.

The cost is not only financial. When vocabulary is proprietary, professional debate moves off the public record. Associations cannot align continuing education with citable definitions. Researchers cannot reproduce planting-performance studies across cities. Graduates learn product-specific templates rather than transferable disclosure grammar — a hidden tax on mobility in an already international labour market.

Renting vocabulary versus citing infrastructure

A closed field list is a recurring economic rent on professional memory. Teams cannot cite definitions in procurement, teach them consistently across universities, or challenge them through an open process — because the definitions are tied to a product lifecycle, not a public record. That model fragments international collaboration: a Scandinavian municipal brief, a Gulf state digital-twin mandate, and an Australian green-infrastructure programme may all demand “native planting” evidence, yet each inherits incompatible private schemas.

Multinational practices feel this fragmentation in every internal knowledge-management initiative. Without a public interchange grammar, “lessons learned” stay trapped in local templates. Open definitions do not harmonise every national regulation — but they give teams a stable layer to map against, the same way IFC and buildingSMART profiles function for built form while local codes still differ.

TLA-185 inverts part of that equation. The Foundation stewards structural definitions under an open licence — citable, versioned, independently governed — while vendors compete on implementation quality: datasets, automation, validation tooling, training, and support. The profession keeps the words; the market keeps the services built around them. That split is deliberate. The dictionary is public and revisable; the independent entity and long-term funding model remain in preparation.

What changes for practices and institutions

For practices, open vocabulary lowers the cost of honesty. When disclosure fields are published, teams can align project metadata with client reporting, regulatory templates, and post-occupancy review without rebuilding semantics for every job. Cross-border studios gain a shared interchange layer they can map to local taxonomies rather than maintaining parallel glossaries per office.

For universities, a citable dictionary is curriculum infrastructure — something students can inspect, critique, and extend in studio work tied to real conformance rules. For public bodies, it is procurement language that does not expire when a vendor contract ends. For regulators and climate-disclosure frameworks, it is a path toward comparable project claims without forcing every jurisdiction to invent a bespoke planting schema from scratch.

None of this eliminates commercial software or proprietary datasets. High-fidelity species inventories, trait engines, and automation remain licensed implementation assets — as they should. The economic shift is narrower and more important: the definitions of what a landscape record ought to say should not be a trade secret.

Professional indemnity, climate litigation, and nature-related finance are pushing landscape claims into discoverable records anyway. Teams that already export dictionary-aligned metadata will face lower friction when clients, insurers, or reviewers ask for evidence. Teams that rely on vendor-specific labels alone may need extra work at handover to recover meaning across platforms.

Stewardship as a counterweight to consolidation

The global AEC platform market is consolidating faster than most professional associations can publish guidance. That consolidation is not inherently hostile — until metadata grammars become exclusive moats and project archives become unreadable outside a single ecosystem. An independent Foundation layer is a hedge against that outcome: a place where terms are argued about in public, where version history matters, and where no single vendor decides unilaterally what “sustainable planting” means this quarter.

Stewardship is not free. Hosting, governance preparation, dictionary maintenance, and crosswalk work require sustained support — which is why the Foundation publishes transparent interim arrangements and invites institutional participation while a suitable independent entity is established. The alternative cost is higher: a profession that cannot compare projects across time, place, or platform because it never owned its words in the first place.

Open infrastructure also shifts competitive advantage toward implementation quality rather than definitional capture. Vendors that validate conformance, publish crosswalks, and train practitioners on careful disclosure can differentiate on service — while the profession retains a stable reference it can cite in contracts, journals, and policy submissions worldwide. The future this programme is written for keeps commercial tools competitive while treating the grammar of landscape metadata as shared professional infrastructure.

Next Steps

Open Foundation materials for one studio deliverable are on the adoption guide. A short Archive page for practices is also available.