Practitioner guide · Reference adoption
Adopt the open standard
Pick one door. Institutes use the Institution Join Kit. Studios use the Studio Pilot Kit. Plant modelling and AU Library fill stay on the Australian Hub. Citing the grammar still means one mandated deliverable — a dictionary URL, a procurement sentence, or a documented gap.
Which door
Four jobs. Four doors. One international dictionary.
Citing the grammar is free. Commercial Library, Hub, and Archive Seal stay on the Australian Hub.
- Institute — Institution Join Kit, then TLA Institute on the desktop. Cite one dictionary; bind a jurisdiction pack.
- Studio / practice — Studio Pilot Kit. Cite the dictionary or procurement sentence in one brief.
- Model plants — on the Australian Hub.
- Buy AU fill — Professional Membership on landscapearchive.com.au for commercial documentation rights and AU Library depth. Citing the grammar stays free.
Why open specifications remain unused
Open metadata specifications often stall when teams lack a mandated first use case, accessible validation tooling, and procurement-ready citation language. Governance documentation alone rarely changes day-to-day export workflows when BIM, GIS, and spreadsheet tools already define their own field vocabularies.
Practical adoption requires one concrete deliverable per pilot: cite the registry in a studio brief or procurement clause, paste the published procurement sentence, and document any mapping gap for draft consultation. Public validator and Evidence Checker inspect files locally — they are not Archive Seal or Foundation Approved.
- Tooling gap — no clear download, worked example, or citation path in the first session
- No mandate — nothing in the brief, rubric, or handover checklist requires structured metadata
- Vendor default — teams ship native Revit/IFC fields instead of a shared interchange grammar
- Abstract documentation — governance copy without a published adoption sequence
Landscape-native software initiative
The future of landscape practice also needs software and coding literacy shaped for the discipline. The Foundation explores innovative in-studio coding knowledge and landscape architectural native software — so published metadata fields, living-systems claims, and authorship can travel in tools built for this work.
This consultation sits with the Foundation’s digital twin potential. Practices can still adopt the open grammar today by citing it in one deliverable while studio tooling matures.
Reference adoption path
Follow three steps to reference the open specification. No account is required. Academic citation, studio briefs, and public-procurement reference language are free — the Foundation does not charge for the grammar. The Foundation operates under interim stewardship pending incorporation. Draft dictionary, registry, and schema documentation are available for citation. Public validator and Evidence Checker inspect files locally — they are not Archive Seal or Foundation Approved.
- 1 · Open the draft dictionary
- Cite the free public grammar — https://schema.landscapearchive.org/dictionary
- 2 · Review the draft pack
- Schema manifest and JSON modules (draft) — https://schema.landscapearchive.org/schema/manifest.json
- 3 · Cite in one deliverable
- Add the procurement reference language below to a studio brief, RFQ, or methods section — one mandated deliverable per pilot.
Studio Pilot Kit
Studio / practice door. A copy-paste brief for one pilot deliverable against the open specification. Institutes use the Institution Join Kit. Full education path lives on Industry & practice.
Open reference (draft). Empty or draft schema modules are acceptable for a pilot — document gaps and use published registry keys only. Public validator and Evidence Checker inspect files locally. New to the vocabulary? Start with dictionary & schema in plain language.
- Practice citation loop: cite dictionary → one procurement sentence in a deliverable → draft consultation for gaps
- Gaps in mapping or missing fields → draft consultation / review pack (prefer public feedback over private forks)
- Optional teaching fixtures: messy schedule → TLA-185 remap and LOD 100 + TLA-SYN — empty fields stay empty; generated massing stays synthetic
- In plain language
- Short Foundation explainer for practices and studios — what a term, the dictionary, and the schema pack are — https://landscapearchive.org/industry-practice#in-plain-language
- Open field dictionary
- Start with the free public grammar — https://schema.landscapearchive.org/dictionary — published registry keys only
- Schema manifest (draft)
- Download the draft schema manifest — https://schema.landscapearchive.org/schema/manifest.json
- Self-serve tools
- Public validator and Evidence Checker inspect files locally — not Archive Seal or Foundation Approved
- Procurement sentence
- Cite the published procurement reference language in one brief, RFQ, or methods section
STUDIO PILOT KIT — open TLA-185 reference
The Landscape Archive Foundation (interim stewardship pending incorporation)
PURPOSE
Use the published open landscape metadata specification as a reference in one
studio or practice deliverable. This is open reference infrastructure available
for citation and conformance checking without purchase of a commercial product.
MANDATED DELIVERABLE (choose one)
1. Cite the open field dictionary URL in a studio brief, methods section, or RFQ.
2. Cite the procurement reference language in a studio brief, methods section, or RFQ.
3. Document one mapping gap against the draft registry (send to draft consultation).
NOTE
Public validator and Evidence Checker inspect files locally. They are not Archive Seal,
Foundation Approved, or government approval. Draft dictionary and registry remain available for citation.
CORE LINKS
• Open field dictionary (free grammar): https://schema.landscapearchive.org/dictionary
• Schema manifest (draft): https://schema.landscapearchive.org/schema/manifest.json
• Evidence Checker: https://landscapearchive.org/evidence-checker
• Public validator: https://schema.landscapearchive.org/validate
• Licence & scope: https://landscapearchive.org/licence
• Procurement sentence: https://landscapearchive.org/adopt#procurement-sentence
• Syllabus / methods line: https://landscapearchive.org/adopt#syllabus-methods
• Tender micro-clause: https://landscapearchive.org/adopt#tender-appendix
• Teaching pack: https://landscapearchive.org/industry-practice#teaching-pack
• Industry & practice path: https://landscapearchive.org/industry-practice
• Dictionary & schema in plain language: https://landscapearchive.org/industry-practice#in-plain-language
• Procurement / RFQ checklist: https://landscapearchive.org/industry-practice#rfq-checklist
PRACTICE CITATION LOOP
Cite the open field dictionary → paste one procurement sentence into a deliverable
→ document any mapping gap for draft consultation. Do not invent registry field keys.
Optional: run a local structural check in the public validator or Evidence Checker.
PROCUREMENT REFERENCE LANGUAGE (verbatim or adapt)
Landscape metadata interchange shall use the open TLA-185 field registry and JSON Schema modules published at schema.landscapearchive.org. Vendor implementations may declare scope via published capability grant manifests. This is a non-commercial reference specification under CC BY-NC-ND 4.0 and does not require purchase of a specific commercial product. Where the brief requires Landscape Archive–attested deliverables, submit a licensed Landscape Archive package from an authorised organisation (see landscapearchive.com.au/authorised); Archive Seal marks may be required for pack attestation. Commercial Library, Hub, Studio+™, populated datasets, and software remain separately licensed.
PILOT NOTES
• Empty or draft JSON Schema modules are acceptable for a pilot — document gaps;
do not invent registry field keys.
• Mapping gaps → draft consultation / review pack (prefer public feedback over private forks).
• Optional teaching artefacts (messy schedule remap + LOD 100 synthetic provenance):
https://landscapearchive.org/examples/before-after-conformance/
https://landscapearchive.org/examples/lod100-synthetic-provenance/
Teaching loops only (not Field Notes essays; not Archive Seal).
Studio Pilot Kit page: https://landscapearchive.org/adopt#studio-pilot
Studio Pilot outreach pack
Founder / director pack for inviting 3–5 named studios (and optionally one university teaching contact) to run one mandated Studio Pilot deliverable. Reuses the live Kit brief.
Focus: open reference and citation. Keep commercial product conversations on a separate thread after the pilot artefact exists.
- Prefer practices already teaching planting schedules / disclosure appendices
- One uni contact is enough for the first teaching cohort — focus on the mandated deliverable
- Keep Archive commercial follow-ups on a separate thread after the pilot artefact exists
- Cohort size
- Name 3–5 practices locally in the tracker (not stored on this site) — measurable citation without commercial soft-sell
- Invite email
- Copy-paste template below; link the Studio Pilot Kit and dictionary; ask for one deliverable only
- Success signal
- Cited procurement sentence or registry URL in a real deliverable — then gaps → draft consultation
STUDIO PILOT OUTREACH PACK — Foundation (interim stewardship pending incorporation)
HOW TO USE
1. Name 3–5 studios / one uni contact in the cohort tracker below.
2. Paste the invite email (edit [brackets]). Attach or link the Studio Pilot Kit brief.
3. Ask for one mandated deliverable only. Keep commercial product follow-ups for a later thread.
COHORT TRACKER (fill locally — not stored by this page)
☐ 1. Studio / practice: ____________________ Contact: ____________________ Status: invited / brief sent / deliverable done / declined
☐ 2. Studio / practice: ____________________ Contact: ____________________ Status: …
☐ 3. Studio / practice: ____________________ Contact: ____________________ Status: …
☐ 4. Studio / practice: ____________________ Contact: ____________________ Status: …
☐ 5. University / teaching studio: __________ Contact: ____________________ Status: …
--- INVITE EMAIL (copy below this line) ---
Subject: Open landscape metadata pilot — one deliverable (TLA-185 reference)
Hello [Name],
I am writing from The Landscape Archive Foundation (interim stewardship pending
incorporation). We publish an open field dictionary for landscape metadata interchange
(TLA-185). This is free public grammar for citation — available without purchase of a
commercial product. Public validator and Evidence Checker inspect files locally.
Would [Studio / University] run a single Studio Pilot deliverable this term?
Choose one:
(1) Cite the open field dictionary URL in a brief / methods section / RFQ, or
(2) Cite the published procurement reference language in a brief / methods section / RFQ, or
(3) Document one mapping gap against the draft registry (draft consultation).
Starter pack:
• Studio Pilot Kit: https://landscapearchive.org/adopt#studio-pilot
• Open field dictionary: https://schema.landscapearchive.org/dictionary
• Licence & scope: https://landscapearchive.org/licence
• Industry & practice path: https://landscapearchive.org/industry-practice
• RFQ checklist: https://landscapearchive.org/industry-practice#rfq-checklist
Empty or draft schema modules are fine for a pilot — document gaps; please do not invent
registry field keys. Happy to answer mapping questions via draft consultation.
Thank you,
[Your name]
--- end invite ---
Outreach pack page: https://landscapearchive.org/adopt#studio-pilot-outreach
Full brief: https://landscapearchive.org/adopt#studio-pilot
Institution Join Kit
Institute door. See which door. The institution cites one international dictionary and binds local flora, climate products, and procurement rules to published field IDs.
Australia is origin and live commercial fill. TLA Institute is the desktop workstation (Join, Dictionary, Evidence, Procurement, Teaching). Institute standing stays with the institute.
- Mandated deliverable: cite the dictionary URL, or the procurement sentence, or document one mapping / pack-binding gap
- Remap rule: empty stays empty; claims occupy published slots — the rule applies in every jurisdiction
- Citing TLA-185 is free. Commercial Library, Hub, and Archive Seal remain AU Hub licences
- Layer 3 (ISO, buildingSMART, OGC) remains future work for an incorporated Foundation
- Cite the one dictionary
- Published keys only — https://schema.landscapearchive.org/dictionary — CC BY-NC-ND 4.0
- Bind a jurisdiction pack
- Same field IDs; local country codes, climate products, and disclosure crosswalk. AU is the reference pack; others are starters
- Keep the profession
- Nursery lists, municipal standing, cultural protocol, and professional sign-off stay with the local institute
- Four-way line
- Local inspect ≠ Archive Seal ≠ Foundation Approved ≠ government approval
- Missing term
- Propose the term into the one dictionary
INSTITUTION JOIN KIT — open TLA-185 reference
The Landscape Archive Foundation (interim stewardship pending incorporation)
PURPOSE
A national institute, university standards office, or municipal landscape unit
cites one international dictionary and binds local flora, climate products, and
procurement rules to published field IDs. One dictionary; local binding.
Australia is origin and live commercial fill.
WHICH DOOR
1. Institute — this kit, then TLA Institute (desktop).
2. Studio / practice — Studio Pilot Kit (cite one brief).
3. Model plants — on the Australian Hub.
4. Buy AU fill — Membership / Library on landscapearchive.com.au.
Map: https://landscapearchive.org/adopt#start-here
WHAT THE INSTITUTION HOLDS
1. Cite TLA-185 as published (schema.landscapearchive.org/dictionary, CC BY-NC-ND 4.0).
2. Use published keys only: species key, taxon ID, quantity, climate claim slots,
LOD, cultural sensitivity, and the rest of TLA-185 / TLA-169.
3. Bind a Layer-2 jurisdiction pack (country / subnational codes, dataset pointers,
disclosure crosswalk). AU is the reference pack; others are starters.
4. Nursery lists, municipal standing, cultural protocol, and professional
sign-off stay with the local profession.
5. Teach the four-way line: local inspect ≠ Archive Seal ≠ Foundation Approved
≠ government approval.
6. If a term is missing, propose it into the one dictionary.
MANDATED DELIVERABLE (choose one)
1. Cite the open field dictionary URL in an institute brief, policy note, or RFQ.
2. Cite the published procurement sentence in an institute brief or tender appendix.
3. Document one mapping gap, or a proposed pack binding, for draft consultation.
REMAP RULE
Empty stays empty. Claims occupy published slots. Teaching examples that use
Australian taxa illustrate fill. The remap rule applies in every jurisdiction.
SCOPE
• Commercial Library and overseas Hubs remain AU Hub licences.
• Institute standing stays with the institute.
• ISO / buildingSMART / OGC remain Layer 3 — future work for an incorporated Foundation.
• Nursery lists, cultural authority, and professional sign-off stay local.
OPTIONAL AND SEPARATE
Citing TLA-185 is free. Commercial Library, Hub, Studio+™, and Archive Seal stay
on the Australian Hub (landscapearchive.com.au) as separately licensed products.
CORE LINKS
• Which door: https://landscapearchive.org/adopt#start-here
• Institution Join Kit: https://landscapearchive.org/adopt#institution-join
• One international dictionary: https://landscapearchive.org/governance#one-dictionary
• Open field dictionary: https://schema.landscapearchive.org/dictionary
• Jurisdiction packs: https://landscapearchive.org/jurisdiction-packs
• Propose a dictionary term: https://landscapearchive.org/propose-term
• Licence & scope: https://landscapearchive.org/licence
• Procurement sentence: https://landscapearchive.org/adopt#procurement-sentence
• Studio Pilot Kit (practices): https://landscapearchive.org/adopt#studio-pilot
Desktop (optional, offline): TLA Institute, TLA Dictionary, TLA Procurement,
TLA Evidence, TLA Teaching. Local inspect remains a local file check.
Institution Join Kit page: https://landscapearchive.org/adopt#institution-join
Procurement reference language (RFQ / brief)
Use verbatim or adapt for your jurisdiction. Full RFQ / studio-brief paste block — same honesty as the syllabus and tender micro-clauses below. Public validator and Evidence Checker inspect files locally; citation does not require them.
- Landscape metadata interchange shall use the open TLA-185 field registry and JSON Schema modules published at schema.landscapearchive.org. Vendor implementations may declare scope via published capability grant manifests. This is a non-commercial reference specification under CC BY-NC-ND 4.0 and does not require purchase of a specific commercial product. Where the brief requires Landscape Archive–attested deliverables, submit a licensed Landscape Archive package from an authorised organisation (see landscapearchive.com.au/authorised); Archive Seal marks may be required for pack attestation. Commercial Library, Hub, Studio+™, populated datasets, and software remain separately licensed.
Landscape metadata interchange shall use the open TLA-185 field registry and JSON Schema modules published at schema.landscapearchive.org. Vendor implementations may declare scope via published capability grant manifests. This is a non-commercial reference specification under CC BY-NC-ND 4.0 and does not require purchase of a specific commercial product. Where the brief requires Landscape Archive–attested deliverables, submit a licensed Landscape Archive package from an authorised organisation (see landscapearchive.com.au/authorised); Archive Seal marks may be required for pack attestation. Commercial Library, Hub, Studio+™, populated datasets, and software remain separately licensed.
Syllabus / methods citation
Short paste for university week-1 handouts, studio methods sections, and assessment rubrics. Mandates citing the open dictionary — not purchase of commercial Archive products.
- Planting and landscape metadata in this studio must cite the open TLA-185 field dictionary and JSON Schema modules at schema.landscapearchive.org (CC BY-NC-ND 4.0). Use published registry keys only; do not invent field names. Citing the open grammar does not require purchase of a commercial product. Where a brief separately requires Landscape Archive–attested deliverables, follow that brief’s licensed-package instructions.
- Teaching pack
- Pair with Studio Pilot Kit + RFQ checklist on Industry & practice — one mandated citation deliverable per cohort
- Honesty
- Local inspect is not Foundation Approved; Archive Seal is separate commercial attestation
Planting and landscape metadata in this studio must cite the open TLA-185 field dictionary and JSON Schema modules at schema.landscapearchive.org (CC BY-NC-ND 4.0). Use published registry keys only; do not invent field names. Citing the open grammar does not require purchase of a commercial product. Where a brief separately requires Landscape Archive–attested deliverables, follow that brief’s licensed-package instructions.
Tender appendix micro-clause
Compact insert for municipal tenders, council RFQs, and delivery appendices when the full procurement sentence is too long. Same open-vs-commercial boundary.
- Landscape metadata interchange shall reference the open TLA-185 registry at schema.landscapearchive.org (CC BY-NC-ND 4.0). Commercial Library, Hub, Studio+™, and Archive Seal remain separately licensed where the tender requires Archive-attested packages from an authorised organisation.
Landscape metadata interchange shall reference the open TLA-185 registry at schema.landscapearchive.org (CC BY-NC-ND 4.0). Commercial Library, Hub, Studio+™, and Archive Seal remain separately licensed where the tender requires Archive-attested packages from an authorised organisation.
Adoption ladder
Move one rung at a time. Each step should yield a durable artefact — a cited brief, dictionary URL, or documented mapping gap — suitable for methods sections, studio assessment, or procurement files. Public validator and Evidence Checker inspect files locally.
- Read
- Skim the field registry and one crosswalk relevant to your disclosure or procurement context
- Cite dictionary
- Include the open field dictionary URL in one brief or methods note
- Cite in one deliverable
- Studio brief, methods chapter, RFQ clause, or climate appendix — one sentence plus registry URL
- Pilot
- One project documents interchange metadata for handover or disclosure; note what mapped cleanly and what did not
- Platform conversation
- Where you build or teach landscape-native digital methods, point colleagues to the Foundation’s landscape-native software initiative
- Founding member
- After a pilot, review the draft constitution and nominate an organisational representative — consultation only until incorporation
Year-one reference support
The Foundation publishes free, low-friction reference materials focused on specification citation rather than commercial licensing. Commercial Archive products remain optional implementation layers and are not under Creative Commons.
- Draft schema portal dictionary, field registry, and example bundles — no login
- Public validator and Evidence Checker — local inspect; not Archive Seal or Foundation Approved
- Jurisdiction crosswalks (Australia AASB S2, UK IFRS S2, EU CSRD, US SEC climate) mapping disclosure concepts to field slots
- Briefing call for university studios and public procurement teams — clear status on draft governance
- Pilot feedback channel into RFC comment periods — mapping gaps become specification issues for public review
- Landscape-native software initiative — in-studio coding knowledge and native tools for the discipline
Founding alliance — outreach summary
Plain-language context for charter consultation — problem framing, published reference infrastructure, consultation ask, and conflict rules. Draft only; no alliance exists today and the Foundation is not yet incorporated.
FOUNDING ALLIANCE — OUTREACH SUMMARY (DRAFT / NOT INCORPORATED) CONTEXT Landscape projects often ship with implicit claims — "native planting," "climate resilient," "sustainable" — while BIM and GIS tools export incompatible vocabularies. Open metadata specifications stall when teams lack a mandated first use case, accessible validation tooling, and procurement-ready citation language. Governance documentation alone rarely changes day-to-day export workflows. OFFER The Foundation publishes TLA-185 as open reference infrastructure: field registry, JSON Schema modules, worked examples, and jurisdiction crosswalks (UK, EU, US, Australia) at https://schema.landscapearchive.org. Year-one materials are free to cite — paste a procurement sentence / cite the registry in one brief. Public validator and Evidence Checker inspect files locally (not a certificate). Capability grant manifests let vendors declare integration scope without implying Council membership. CONSULTATION ASK Organisations interested in the founding alliance model may review the draft constitution (consultation only — the Foundation is not yet incorporated) and nominate one organisational representative if they wish to be listed as a founding supporter when the standard launches publicly. Optional: commit to one pilot — cite the registry and add the procurement sentence to an upcoming studio brief or tender. Charter consultation: https://landscapearchive.com.au/contact?topic=foundation-support&intent=founding-alliance WHAT THE CONSULTATION DOES NOT REQUEST • Binding membership in an entity that does not yet exist • Adoption of commercial Archive products or subscriptions • Transfer of proprietary project IP or client data • Joint liability with other participants • Endorsement that TLA-185 is an ISO or government standard • Logo placement without a documented citation pilot CONFLICT RULES • The Landscape Archive Pty Ltd is a founding implementation partner — no default Council vote • The Landscape Vault Pty Ltd holds specification copyright until assignment to the incorporated Foundation • Affiliate partner programme (commercial referrals) is unrelated to founding alliance consultation • Cultural-context field rules require Indigenous advisory sign-off before adoption — not overrideable by majority vote • RFC changes are public; vendor roadmaps do not control the field dictionary LINKS • Adoption quickstart: https://landscapearchive.org/adopt • Draft constitution: https://landscapearchive.org/founding-charter • Schema portal: https://schema.landscapearchive.org • Charter consultation: https://landscapearchive.com.au/contact?topic=foundation-support&intent=founding-alliance PROCUREMENT REFERENCE LANGUAGE Landscape metadata interchange shall use the open TLA-185 field registry and JSON Schema modules published at schema.landscapearchive.org. Vendor implementations may declare scope via published capability grant manifests. This is a non-commercial reference specification under CC BY-NC-ND 4.0 and does not require purchase of a specific commercial product. Where the brief requires Landscape Archive–attested deliverables, submit a licensed Landscape Archive package from an authorised organisation (see landscapearchive.com.au/authorised); Archive Seal marks may be required for pack attestation. Commercial Library, Hub, Studio+™, populated datasets, and software remain separately licensed.