Home >Online Product Documentation >Table of Contents >Generate XML Schema from EDI Standards
Generate XML Schema from EDI Standards
You use the Generate XML Schema from EDI Standards dialog box to specify the settings you want Stylus Studio to use to generate XML Schema from an EDI message.
Fields
Message
You use the fields in the Message group box to specify information about the EDI standard for which you want to generate an XML Schema.
- Dialect - Drop-down list that lets you specify the EDI dialect for which you want to generate an XML Schema.
- Version - Drop-down list that lets you specify the version for the EDI dialect you selected.
- Mode - Certain EDI messages have alternate batch and interactive forms, depending upon whether they are used between systems that have real-time connections. The Interactive setting causes the interactive form to be used, if available. For example, in EDIFACT, this would cause the normal envelope of UNB/UNH/UNT/UNZ to be replaced by UIB/UIH/UIT/UIZ. Valid for EANCOM, EDIFACT, and IATA only.
- Message/Description - The specific EDI message for which you want to generate XML Schema.
XML Structure
You use the fields of the XML Structure group box to specify the structure of the XML
- Use long element names - Whether or not you want to use the long element name as part of the XML tag -
UNB01-SyntaxIdentifier versus UNB01, for example. - Wrap "GROUP" element around message groups - Whether you want to wrap a
<GROUP> element around transaction messages. This can make message groupings easier to handle with XPath for EDI document with multiple message groups. - Prefix GROUP_N tags with the message name - Adds the message name to the
GROUP_n prefix in the XML element tag. For example, <TS_831_GROUP_1>. - Put the data value in value= attributes - Places code list data values in an
value= string in the element tag. For example, <BGN01 value="00"><!--353: Transaction Set Purpose Code--></BGN01>. By default, the data value is output to XML as text (<BGN01><!--353: Transaction Set Purpose Code-->00</BGN01>). - Put decoded data values in decode= attributes - Places decoded code list data values in a
decode= string in the element tag. For example, <ISA15 decode="Production Data">. By default, the decoded value is not output to XML.
XML Schema Options
The fields in this group box allow you to specify the settings that are used to generate the XML Schema for the selected EDI message.
- Write annotations describing each element - Whether or not you want the generated XML Schema to include annotations that are part of the EDI message.
- Enumerations for elements that have codelists - Whether or not you want the generated XML Schema to include enumerations for fields that have lists of values.
- Use "unbounded" for maxOccurs when loop value is 99 or higher) - Replaces
maxOccurs values of 100 or greater with "unbounded". This option ensures that the generated XML Schema can be successfully validated by most processors.
SEF File - The URI of the Standard Exchange Format (SEF) file, if any, you want to use when generating XML Schema. The SEF file can augment information that Stylus Studio uses to generate XML Schema - customized EDI definitions are stored in the SEF file, for example. If the same setting is specified by both the document wizard and the SEF file, the SEF file value is used.
For More Information
The SEF File
Customizing an EDI Standard
Creating XML Schema from EDI
Working with XML Schema in Stylus Studio
Cart
