If you have difficulty in submitting comments on draft standards you can use a commenting template and email it to admin.start@bsigroup.com. The commenting template can be found here.
Standards Development
This document specifies criteria and provides guidance for the development and assessment of AIready interoperability specifications for data-driven agrifood systems. It addresses the information and interface descriptions needed for AI agents, acting with appropriate authorization, to discover resources, establish connections, interpret data consistently, invoke operations and verify results across organizational and technical boundaries.
The document covers machine-readable resource and capability discovery; interface contracts and versioning; semantic definitions and mappings; identifiers, units and reference systems; provenance and data-quality metadata; machine-actionable access and usage policies; trust and verifiable claims; and conformance-assessment guidance for the specification being drafted. It requires a specification to identify which workflow stages it covers and the external specifications on which it relies. Illustrative agrifood use cases include input recommendations and verification of supply-chain claims.
The document does not define a universal agrifood API, prescribe a particular AI model or agent architecture, replace horizontal standards for AI governance, identity or cybersecurity, or establish legal obligations for data sharing. It is intended for standard developers and may also inform implementers and reviewers.
Provide ISO/TC 347 groups with a common, auditable meaning of “AI-ready” for agrifood interoperability specifications, so AI agents can complete a documented workflow with less ad hoc interpretation while retaining authorization, traceability and human accountability.
Problem to be addressed
Agrifood data needed for a single decision often resides in independently developed systems. A recommendation for nitrogen application, for example, may combine soil observations, field history, weather, legal constraints and a machine-executable plan. A supply-chain verification may combine origin, geospatial, transport and certification records. Inconsistent terms, units, identifiers, access rules and interfaces can make automated decisions wrong or impossible. The manuscript organizes this problem into discover, connect, understand and act, and supplies a practical drafting checklist.
Why a Technical Specification
The field is changing quickly. A TS allows ISO/TC 347 to establish and test a coherent, technically specific approach for its developing portfolio, including normative assessment criteria and informative implementation guidance. Experience from applying the TS can inform a later International Standard or revision. Normative provisions will be restricted to properties of the specifications under assessment; illustrative technologies and examples will be reviewed for maturity and maintained references.
Alignment with ISO/TC 347 strategy
The March 2026 strategic business plan identifies interoperable data, shared semantics, FAIR principles, a reference architecture, responsible innovation, and inclusion of smallholders and their technology providers as committee priorities. A cross-cutting drafting TS can help working groups apply those priorities consistently across work items.
Required form fields are indicated by an asterisk (*) character.
You are now following this standard. Weekly digest emails will be sent to update you on the following activities:
You can manage your follow preferences from your Account. Please check your mailbox junk folder if you don't receive the weekly email.
You have successfully unsubscribed from weekly updates for this standard.
Comment by: