CSA TS-105:26

Description

Preface This is the first edition of CSA TS-105, Data sourcing protocol for agri-food performance — Part 3: Protocol for sourcing data . This Technical Specification (referred to as “this Document” from here on) outlines protocols and governance guidelines for sourcing, managing, and sharing agri-food data. It provides a framework that helps organizations establish robust data governance practices and supports them in evaluating and collaborating with trusted data providers. This Document is not a Standard and has not been formally approved by a CSA Technical Committee. CSA Group acknowledges that the development of this Document was made possible, in part, by the financial support of the Standards Council of Canada. This Document was prepared by the Development Subcommittee on Protocol for Sourcing Data, under the jurisdiction of the Data Sourcing Protocol Development Committee, and has been reviewed by the Development Committee. Scope 1.1 General This Document is focused on protocols for data sourcing. It aims to establish comprehensive guidelines for data governance, trust frameworks, ensuring transparency, data quality, data sharing and use, and privacy. Annex A includes a data sourcing protocol template, while this Document covers guidelines for data quality assessment, informed consent, privacy and confidentiality procedures, and documentation processes. This Document provides governance guidelines on how the user can source data, integrate aggregated data, and maintain data transparency and trust. This Document addresses a) transparency of data sourcing decisions and transparency of the data sources and methodologies; b) protocols for disclosure, privacy, and confidentiality of data sourced by the users, and mitigation solutions to privacy risks and business confidentiality issues; and c) processes for how users can document, retain, publish, archive, and dispose of the data they collect or create. 1.2 Terminology In this Document, “shall” is used to express a requirement, i.e., a provision that the user is obliged to satisfy in order to comply with the Document; “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 Document. 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.