• Chapter 1: Getting Started with Stylus Studio®
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
  • Introduction
  • DataDirect XML Converters
  • Custom XML Converters
  • The Custom XML Conversion Definition Editor
  • Parts of an Input File
  • Working with Regions
  • Working with Fields
  • Controlling XML Output
  • Creating a Custom XML Conversion Definition
  • Using Custom XML Conversion Definitions in Stylus Studio
  • Working with EDI Conversions
    • Supported EDI Dialects
    • Creating Custom EDI Message Types
    • Documentation for DataDirect XML Converters
    • XML Schemas for Custom EDI Message Types
    • Validating XML from/to EDI
  • The Converter URL Scheme
  • Custom XML Conversion Definitions Properties Reference
• Chapter 4: Working with XSLT
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Working with WSDL Documents
• Chapter 13: Building XML Pipelines
• Chapter 14: Publishing XML Data
• Chapter 15: Integrating with Third-Party File Systems
• Chapter 16: Extending Stylus Studio
• Chapter 17: The Stylus Studio Java API
• Chapter 18: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > Validating XML from/to EDI

Validating XML from/to EDI

Stylus Studio provides several document wizards that convert various EDI dialects and message types to XML Schema. Such an XML Schema can be useful if you are converting XML to EDI, because it allows you to ensure that the EDI created by the DataDirect XML Converters for EDI conforms to a particular EDI message type standard. There are document wizards for all EDI dialects supported in Stylus Studio: EDIFACT, EANCOM, HL7, IATA, and X12.

You can also use the XML Schema created by the various EDI to XML Schema document wizards to validate data after you have converted EDI to XML, when URL-based error checking is disabled, to determine how well the incoming stream conforms to the EDI standards.

See Creating XML Schema from EDI for more information on using these document wizards.