2024-06-12 Agrisemantics Committee Meeting

Owned by Ben Craker, created
2024-06-12
3 min read

Participants

@Names here

Meeting Logistics

Insert meeting info here or use:

See time and GoToMeeting details on the AgGateway Calendar.

Agenda and Minutes

Antitrust Reminder

  1. Leader: Chair

    1. In all of AgGateway's operations and activities, it must avoid discussions or conduct that might violate applicable antitrust laws, or even appear to do so. To that end, AgGateway has established Antitrust Guidelines, which it has provided to each participant in this meeting. While it is your ultimate responsibility to ensure that your actions comply with applicable antitrust laws, your participation in this meeting is affirmation that you will abide by AgGateway's guidelines.

    2. Antitrust Guidelines

  1. Minutes taker

    1. Leader: Chair

    2. The desired outcome is that a minutes taker is selected.

    3. Minutes:

  2. Quorum

    1. Leader: Chair

    2. The desired outcome is that the chair has reminded the meeting participants what the quorum requirements are and has determined whether a quorum has been achieved.

    3. Pre-meeting notes / references: Quorum Requirements Table

    4. Minutes:

  3. Agenda

    1. Leader: Chair

    2. The desired outcome is that the meeting participants agree to the agenda, adjusting first as required.

    3. Minutes:

  4. Prior unapproved meeting minutes

    1. Leader: Chair

    2. The desired outcome is that the working group has approved all unapproved meeting minutes.

    3. Pre-meeting notes / references:

      1. Link to previous minutes

    4. Minutes:

      1. Moved:

      2. Seconded:

      3. Discussion:

      4. Outcome:

  5. Outstanding Tasks

    1. Leader: Chair

    2. The desired outcome is that the meeting participants understand the status of all tasks outstanding as of the end of the previous meeting.

    3. Pre-meeting notes / references:

    4. Minutes:

Main Topics

Use decide tag for any decisions taken

  1. Background & History

    1. Topic Leader:

    2. The desired outcome is that …

    3. Pre-meeting notes and references:

    4. Minutes:

      1.  

  2. Infrastructure

    1. Topic Leader:

    2. The desired outcome is that …

    3. Pre-meeting notes and references:

    4. Minutes:

      1. Idea that JSON file contains simple lists like ADAPT UoM, when a pull request is made a GitHub action sends that new file to update a database

        1. Need for the database use cases:

          1. Once lists get big, getting only changes since last download

          2. Being able to search a code/API call for a specific code with out having to download and search the whole JSON

          3. Having ability to map relationships likely works better in a database/via API than a file on GitHub

        2. Need for grain codes the more complex list of quality tests done for dockage compared to what is documented in GIPSA

      2. Question on if there is a business model for charging for asserting/using relationships as a way to fund maintenance of the infrastructure

      3. How does this fit in ADAPT

        1. Could Modus codes be in the same data type definitions

        2. How do the observation codes are kind of a superset of data type definition objects

        3. Could have a generic data type definition object

        4. Need to do some more work on the crisp delineations between concepts in the crop definition

          1. e.g. is a different variety a different sub crop zinfandel vs Merlot grape are likely different than corn hybrid 1402 planted in a field

        5. Many vocabularies will likely fit in the general observation model, however there will be some that require a different model like Crop Definition

          1. If it model is too generic it becomes quite difficult to implement

          2. Potential to have a very abstracted database, then create “schema on the query”

          3. Might be best to get through a couple worked through to see what patterns emerge

          4. Tech stack likely has implications on how things work best as well

        6. DMN - Data Modeling and Notation standard

          1. Has the ability to define anything but keep it structured so it makes sense

          2. Object Management Group

            1. Have made data type definitions its own standard

            2. Has an active community that is good to work with and seems it might work well for what we might need

            3. Controlled vocabularies we really need and support today are key value pairs where the value is a simple type

            4. Do not want to start creating abstract, complex data types

            5. Some concern that using DMN in ADAPT may be an extra intermediate step that is not needed

          3. Within the infrastructure the codes are complex types

        7. Need to start talking about observation code definitions, data type definitions, and context items all together - possibility to have one

  3. Process submissions

    1. Topic Leader:

    2. The desired outcome is that …

    3. Pre-meeting notes and references:

    4. Minutes:

Closing Topics

Matters arising

  • Minutes:

Tasks assigned during meeting

  • Minutes:

Meeting schedule

  • Minutes: Next meeting on [use “//” shortcut to get date picker]

Adjournment

  • Minutes: Meeting adjourned at HH:MM UTC