Schemas to use for mappings

Link uses the XSD standard to define schema for input and output formats. XSD is a WWW standard and are used by many other integration platforms and standard organizations.

In case you EDI message is not XML, you can still use XSD.

We have support for at number of non-xml formats and also support you building your own disassemblers and assemblers to convert between xml and native format.

Edifact:

We support using Microsoft schemas which are available as open source xsd’s here: https://github.com/microsoft/Integration/tree/master/BizTalk%20Server/Schema/EDIFACT

X12:

We have schema repository available to share with all that has a Link Developer license.

CSV:

We support building you own schemas to convert from and to CSV format. It is descirbed here:

Convert from xml to CSV format using Links CSV Assemble itinerary step: https://bizbrains.atlassian.net/wiki/spaces/L300/pages/2684616788

Convert from CSV to Xml using Links CSV initilaize step: https://bizbrains.atlassian.net/wiki/spaces/L300/pages/2684616765

Tradacom:

Support using Link Tradacom Initialize and assemble itinerary step.

JSON:

Support out of the box with for converting from xml to json using Link JSON Assemble itinerary step: https://bizbrains.atlassian.net/wiki/spaces/L300/pages/2684616811

or from JSON to XML using Links JSON Initilize step.