Agriculture and Agri-food

This Technical Specification supports best practices for collecting metadata for the National Index on Agri-Food Performance.

This Technical Specification provides standardized descriptions for the collection and aggregation of agri-food data from trusted data providers, including normative terms and definitions of data, categorizations, and sourcing information that specifies the required and desirable metadata for data considered for the Index and included in the Index.

This Technical Specification also establishes a framework for a metadata self-declaration form for trusted data providers, detailing the necessary information for data sourcing and categorization for inclusion in the Index. This includes guidance on self-declaration management.

This Technical Specification benefits interested parties by enhancing the reliability, transparency, and usability of the data included in the National Index on Agri-Food Performance, and facilitates better decision-making and fosters trust in the agri-food data and metadata provided.

1.1         Inclusions

This Technical Specification applies to the National Index on Agri-Food Performance and any interested party that has been identified as a trusted data provider by the National Index on Agri-Food Performance.

1.2         Exclusions

Other users could benefit from using this Technical Specification, as described in Clause 1.1 above, but are excluded from mandatory requirements.

1.3         Terminology

In this Technical Specification, “shall” is used to express a requirement, i.e., a provision that the user is obliged to satisfy in order to comply with the standard; “should” is used to express a recommendation or that which is advised but not required; and “may” is used to express an option or that which is permissible within the limits of the Standard.

Notes accompanying clauses do not include requirements or alternative requirements; the purpose of a note accompanying a clause is to separate from the text explanatory or informative material.

Notes to tables and figures are considered part of the table or figure and may be written as requirements.

This Technical Specification establishes a set of criteria to inform evaluation of the quality and suitability of datasets for the intended users. The purpose is to provide a transparent methodology to assess the quality of datasets in relation to the intended purposes of the user.

The methodology serves as a tool for the user to:

a)    Assess data suitability — Existence of data alone does not guarantee that data is a suitable candidate for what the user needs data for. In this way, the user drives the data, not the other way around.

b)    Apply structured criteria — Use a consistent approach to vet submitted data and evaluate its quality for inclusion.

c)    Recognize sector diversity — Acknowledge and assess the varied data management practices across the agri-food sector, supporting ongoing improvements in data governance and use.

1.1 Inclusions

This standard applies to the Centre for Agri-Food Benchmarking while identifying datasets for the Users and any stakeholder recognized as a trusted data provider. It covers data related to the entire agriculture and agri-food system, encompassing the full food supply chain, from primary agricultural production (including livestock, aquaculture, and agroforestry) through processing, distribution, and retail sectors.

1.2 Exclusions

Other users could benefit from using these data quality rating criteria, as described in clause 0.3 Users above, but are excluded from mandatory requirements. This technical specification also does not apply to data on consumers of agri-food products.

1.3 Terminology

In this Technical Specification, “shall” is used to express a requirement, i.e., a provision that the user is obliged to satisfy in order to comply with the standard; “should” is used to express a recommendation or that which is advised but not required; and “may” is used to express an option or that which is permissible within the limits of the Standard.

Notes accompanying clauses do not include requirements or alternative requirements; the purpose of a note accompanying a clause is to separate from the text explanatory or informative material.

Notes to tables and figures are considered part of the table or figure and may be written as requirements.

Annexes are designated normative (mandatory) or informative (non-mandatory) to define their application.

1.1   General

This technical specification is focused on protocols for data sourcing. This Technical Specification aims to establish comprehensive guidelines for data governance, trust frameworks, ensuring transparency, data quality, data sharing and use, and privacy. The Annex includes a data sourcing protocol template, while the Technical Specification covers guidelines for data quality assessment, informed consent, privacy and confidentiality procedures, and documentation processes. This Technical Specification provides governance guidelines on how the user can source data, integrate aggregated data, and maintain data transparency and trust. This Technical Specification addresses:

·    Transparency of data sourcing decisions and transparency of the data sources and methodologies.

·    Protocols for disclosure, privacy and confidentiality of data sourced by the users. Mitigations solutions to privacy risks and business confidentiality issues.

·    Processes on how the users document, retain, publish, archive and dispose of the data they collect or create.

1.2     Terminology

In this Standard, “shall” is used to express a requirement, i.e., a provision that the user is obliged to satisfy in order to comply with the standard; “should” is used to express a recommendation or that which is advised but not required; and “may” is used to express an option or that which is permissible within the limits of the Standard.

Notes accompanying clauses do not include requirements or alternative requirements; the purpose of a note accompanying a clause is to separate from the text explanatory or informative material.

Notes to tables and figures are considered part of the table or figure and may be written as requirements.

Annexes are designated normative (mandatory) or informative (non-mandatory) to define their application.