Session 1
Attendees
Stuart Rhea, Hiroyuki Morita, Conny Graumans, Andres Ferreyra, Daoud Urdu, Roberto Garcia, Cale Boriack, Hirko Miura, Clement Jonquet, Rackwoo Kim, Ben Craker, Gaelle Cheruy Pottiau
Reminder TC 347 face to face coming up March 10-13 2025 in Berlin
AHG2 has several deliverables as well as dependencies/coordination with other AHG’s
Need to draft new work item proposals
One on the technological foundation to host crop definition among other controlled vocabularies
One on crop definition model
Check with your national standards body on how to register, all are a little different
Remote participation will only be available for opening and closing plenary, not working meetings
Classification of crops into groups discussion
For example when stating what crop protection chemicals can be used have a group of crops that are allowed instead of naming each crop individually
Also potentially applies to part of vegetable harvested, shape of fruit, ration of mass to surface area at time pesticide is applied, condition and timing of harvest, time from sowing to harvest
Reviewed examples from Japan
In EU the authority has a very detailed data structure on how to manage relationships and different crop types for all the different restrictions for crop protection products there
Believe that the work here will not change how anyone groups products, goal is to create a machine readable/actionable way to express that information consistently around the world
Comment that there is often a very ambiguous differentiation between crop and commodity the group should probably set out to define a little more clearly
Crop: growing something with the intention to harvest it a certain way
Harvested commodity (not the best term): a crop plus the context in which it was harvested
Commodity is a carry over in terminology from an AEF exception to ISO11783, the thing harvested is not necessarily a commodity, ADAPT Standard is now using Harvested Product: https://adaptstandard.org/docs/harvested-product-attributes/
https://www.fao.org/fao-who-codexalimentarius/codex-texts/dbs/pestres/commodities/en/
Minimum Residual Value (MRL) use case could be a property of the harvested commodity, not the crop
Would still want to know MRL for a crop to inform decisions for field operations
When adding support for crop group also need to be able to differentiate between a crop that is a group of plants. A pasture or hay that is comprised of multiple different plants, alfalfa and timothy, and …
Grouping s work in a couple different ways
Common features of the plant/harvested product - root vegetables
Plants that are listed on a label that a product is allowed to be used on
Taxon like EPPO is helpful but does not work universially
There is a one to many relationship between a crop and groups
Trying to drill down through a particular group could be difficult since a crop can be in multiple groups
Crop relationship object supports the one to many hierarchy
Does a group need to be a crop definition object or a crop group (new) object in the model
Groups may or may not be hierarchical
Groups will vary how people use it, how many levels it has, etc.
Is grouping just a need for crop protection labeling use case or are there other use cases
e.g. is there a group of crops used for computational modeling
Believe we will not be able to come up with a list of crop groups, but do need the ability to group crops
Question on if GPCcodes could be used for grouping
Geo Political Context codes are meant to show where a product is used
GPC is also used by GS1 for the Group Product Codes, very commonly used in export of fruits and vegetables
Plan is to spell it out to reduce confusion
Each code will have a unique ID with the ability to include additional ID’s to support multiple groupings/uses
There is likely a TC347 principle that all codes should have a URI
This allows building ontologies by pointing to the URI’s without forcing how the ontology would be built
Try to keep it simple for industry to have drop downs and database while enabling (generally more academic) ontological use cases