From the Ag Retail community: 

JSON message implementation of CN connectivity. 

• General consensus of interest, but concerns about bandwidth since many are already working in the Energy group. Noted that an initial conversation within the CN group is also needed.
• Statement of support around moving to an easier to implement, RESTful API with JSON as message format as opposed to continuing multiple versions of the same messages in ebXML implementations. 

Brent presented an overview of where Crop Nutrition is at. (Include PP slides?)

• Tonnage Reporting: Challenge working with state government as changes in staffs happen with administrations. Migration to web-based portals.
• Mix Ticket (2018-19): JSON-based implementation. 
• Responsible Ag: Auditing & certification of safe and best practices for fertilizer safe handling. Datalink with AGIIS and Responsible Ag.

AgGateway's had interest from members on: 

1. API implementation
   1. EWA interested in using RESTful API transport; requests from existing customers. We concluded that it's not what we were looking for. That implementation will work for other partners and that there is a standard to do it. New CIO from Fall 2020. Using CNC standards, when we integrate with new customers still asking for X12 and new customers have different requests. Need some flexibility. Interest in WG participation. 
      1. API specs are JSON and XML. Preference to XML
      2. If there is a JSON standard, we will follow it to be flexible between the two.
      3. EDI harmonization? Contract message must use X12. TKI was also working on contract.
   2. Mike Kuhn live with some partners on API of order create and order invoice.
2. JSON options
3. EDI harmonization

Natasha - interested in how contracted and grouped together. The alignment would help. Limited products at our company. Using the last quick connect, all of our partners we needed were there.

Anne - Love to have more participants with all supplies. Have begun the process with one. Accepting orders and ship notices. It's seed and chemical ship notice and it's an adaption of that. Looked at business rules available. Had most of what we needed to get up and rolling. If we have more discussion on mix ticket bring in Eric Hoefing. 

Sounds like there is implementation on crop nutrition; harmonization is of interest; and an opportunity to have additional conversations about web services and APIs. 

Ewa - We've implemented INCO terms from the CNC project. Did not know about INCOTerms2020. Need to have a review of INCOTerms2020 v. the previous INCO.

Greg -  Not using. Could see the option available as beneficial. 

Mike - Not using yet.

1. Conversation on X12/XML Harmonization Call.
   1. Ewa to find and send to Brent preparation materials for next meet-up.
2. Standards and implementation of APIs and RESTful web services.
   1. Sharing the approaches of these are steps being taken, areas of concern, etc
   2. Webservice transport is using CNC messaging. Not XML as being the transport mechanism.
   3. Look at establishing a standard around web service
      1. Ask to be involved: Mike from IRN; Nutrien Ag; other members active in this space.
3. Email blast linked to article/review of INCOTerms 2020 delta work to be completed before next meet-up.
4. Brent to reach out to Mark Carabine and TKI.

Next Meetings: a cadence of a regular meet-up would be helpful. Maybe not every month but at least twice a year outside of mid-year and annual meetings. 

Scheduled for XX  at XX:XX a/pm Chicago time

Email blast linked to article/review of INCOTerms 2020 delta work to be completed before next meet-up.