From the 2021-05-11 Meet Up: 

Web Services, API implementation and CNC connectivity: 

• Some parties are implementing non-CNC XML messages for ShipNotice, others. Where reviewed, business rules appear to be in line with CNC implementation.
• Some parties are interested in implementing a web service approach to message exchange; others, an API implementation.
• No widespread agreement on moving from XML to JSON; some parties still implementing X12 EDI in the segment. 

Questions from June call:

Does an API/RESTful web service offer a similar tool to the technical acknowledgement? Technical acknowledgement is a specialized component of SOAP. 

Are we talking about a refactored SOAP into a RESTful web service?

What about a JSON implementation of the XML?

What about X12 implementations? Is there a crosswalk between formats and toolsets?

• For SAP implementers, PO has an internal tool that can be leveraged for converting JSON to XML; 
• No reason you can't transmit X12 or XML payloads over RESTful service - just becomes a new transport 

Some conversation about using Nexus as a RESTful endpoint - consider pinging Guido on that

Schedule a conversation with Ginger about a demo for the Nutrien service

Invite SSI/AgVance to comment

Finish message harmonization for X12 to XML (Order series)

Nutrien shared an overview of their movement to API implementation of B2B connectivity.

• Shared contributing factors to their decision making
• RESTful API portal approach - Apigee tech from Google as a base
• Reviewed navigation of Supplier Order Management
  • AgGateway v5 messages supported
  • JSON is proprietary format, but appears to share naming convention closely aligned to ag eStandards
  • How would a supplier GET a purchase order? That's an artifact of the presentation layer; human involvement noted, has some challenges with the outbound message
  • Discussion on how to handle long running processes, call backs, and identifiers returned 
  • Question on how to obtain support once registration request is submitted - email address 
  • OAuth2.0 protocol is supported - any intent to support external authentication provider? Design for inbound is scoped to the product. Outbound supports pretty much any standard HTTP authentication protocol. 
  • Question on connection intent - if a partner isn't moving off of X12, is the intent to not connect? Same issue as in other interoperability initiatives; seeing some motion forward. How can connectivity be opened up to the masses instead of a single path? Maintenance, ease of implementation seen as benefits.
  • Recognition that someone will have to build this - success stories shared. 
• API conversation to be scheduled following some agenda building around current implementations, message service guidelines, and defining scope for discussion.

Revisited X12 to XML mapping and crosswalk

• Think the order is complete; ship notice likely; invoice maybe outlier
  • CF observes that they are less interested in participating in EDI
  • Simplot is getting more interest in X12
  • Schedule week of 13 September; shoot for Wednesday 15th

Retail-to-distributor Ship Notice

• Deferred to September/October group call

• Schedule next call
• Issue invitations to identified parties
• Review state of XML message implementation across versions

Next Meetings: 

EDI harmonization scheduled for 15 September at 2:00 pm Chicago time