These data concern the legal systems governing intellectual property (breeders rights, maintainers rights etc), restrictions concerning imports/exports between geographic regions due to considerations regarding health, local biodiversity etc.

Sources
- UPOV: https://www.upov.int/portal/index.html.en
- Relevant authorities in all jurisdictions our system is going to serve
- Norway: The Norwegian Food Safety Authority on imports
- Portals about other countries:
- Global Regulatory Authority Websites (pda.org)
- List of Foreign Countries or Regions and Their Regulatory Authorities for the Application of Subsection C.02.019(5) of the Food and Drug Regulations – Canada.ca
- List of food safety organisations – Wikipedia
- The Essential List of Regulatory Authorities in Asia | RAPS
We’ve only just started looking at this, so any help is most welcome.
Tell us about other sources we should check!
Method
These datasets will be hard to build because of the complexity of the task, and because the field is changing. Both makes access to and maintenance of data difficult.
There are to main groups of data here:
- intellectual property (breeders/maintainers/producers rights etc), which is connected to single cultivars and thus must be broken down to that level in our database
- restrictions on imports/exports between geographical regions due to considerations conserning health, biodiversity etc., which is connected to the species and thus the crops/livestock/microorganism level in our database
A tentative method regarding intellectual property:
- Achieve a data exchange solution with UPOV around this. Our argument to them would be that we are building a system for hobbyist and smb’s, with users who often don’t know much about breeders/maintainers/producers rights and their need for those to be respected. We think our system will educate them, and such would be helpful for the work of UPOV with this respect.
- Build a data exchange system that keep our system up to date with as much automation as possible
A tentative method regarding restrictions on imports/exports between geographical regions:
- Achieve a data exchange solution with autorities in every jurisdiction Culton and CultonX manage to become accessible in
- Build internal procedures to normalize and keep such data up to date, which will be a huge task, because one cannot expect such data to be delivered in a standarized way.
Data
Our first beta version of the checklist service will run from beta.culton.org. Here at culton.org development datasets, mostly in spreadsheet format, are intended for internal discussion among logged in participants of the project. If such data has been posted, there is a link to it below here:
Last Updated on 2023-09-02 by Karl Aakerro