GOAT Conventions and Standards Ecosystem Inventory: Initialization (version 0.1)

Standard Name *

Specify the full name of the standard.

Standard Name - Acronym

Standard Type

How would you classify your standard? Select all that apply.

schema - defines the structure and fields of a data object (e.g., model input specification saved as JSON Schema or XML Schema)

Ontology - defines the shared terms and their relationships (e.g., AGROVOC, controleld vocabularies)

Taxonomy / Classification - hierarchical category systems (e.g., NAICS codes, crop classificaiton systems)

Identifier standard - unique ID formats for entities (e.g., GLN, UUID, farm or field identifiers)

Codelist - standardized codes for values (e.g., UCUM for units)

File format - structure of a stored artifact (e.g., GeoJSON)

Message / exchange format — structure of data in transit (e.g., ADAPT Toolkit)

API specification — defines how systems communicate (e.g., OpenAPI/Swagger, FMIS APIs)

Communication protocol — rules governing transmission and security (e.g., MQTT, REST conventions, Signal Protocol, Matrix)

Methodology standard — defines how a process should be conducted; workflows (e.g. sampling protocols)

Measurement / test standard — specifies how to measure or test something (e.g., AOAC soil test methods)

Certification / conformance standard — defines criteria for compliance verification

Data governance framework — rules for ownership, access, and stewardship (e.g., FAIR principles)

Licensing standard — terms for reuse (e.g., Creative Commons)

Privacy / consent standard — rules for data rights

Interoperability profile — a constrained subset of another standard for a specific context

clear value

Lead Contact

Who should people contact if they have questions about the standard?

What domains are this standard relevant to?

List each domain as a short phrase (2–4 words), separated by commas. E.g., "agriculture, farmer data privacy"

Who are the known adopters of the standard? *

Knowing who has adopted the standard helps folks understand how the standard can be applied and opportunities for interoperability.

What is the standard built on top of? What are its ingredients? *

The specs, schemas, and standards this standard is built from.

What development phase is the standard in? *

Describe the target development goal of the standard.

If you have phased goals, you may include those as well.

Is this an actively maintained standard?

Provide a link to the standard's documentation

Should include adoption instructions.

Provide a link to the standard's repository

What is the current geography or region for the standard?

This should reflect existing scope, not target scope.

What is the target geography or region for the standard?

Is your standard specific to North America? A specific bio-region? Or globally relevant?

What is the target audience for the standard?

Who or what is meant to adopt this standard? An organization? A software? A hardware? What motivation should they have to adopt it? E.g., Software wanting to share a common exchange format to reduce the burden to support many APIs.

License

What license is this standard released under?

Governance Model

What is the governance model this standard conforms to?

Competitors/Similar Standards

Names of competitors or similar standards.

Developers and Collaborators

Names of organizations or individuals involved in creation or development of the standard.