Frequently Asked Questions, etc.
What is EDIXMLOnline?
EDIXMLOnline is a SOAP web service that takes an EDI Standard Exchange Format (SEF)
to produce a corresponding XML schema (XSD), and using both, allows the developer
to generate and translate EDI files in a manner most developers are familiar with...
by programming against an object class in their favourite IDE. There is no need
for external mapping tools!
So, if you are a developer familiar with EDI and Web Services you will enjoy working
with EDIXMLOnline. And because EDIXMLOnline is a web service on the internet it
is pretty much platform independent. The tool that you write your application with
just needs to allow you to write webservice client-applications that are compliant
with the WS-I protocol.
Although an understanding of an implementation guideline between trading partners
(developers) would still be required, EDIXMLOnline eliminates or reduces many cumbersome
techniques, that comes with using mapping external tools.
Current Implementation
Planned features
- Support for Attachments through WSE specification
Planned features (long list)
- End-to-end security. (Currently relies on point-to-point over SSL security)
Limitations
- No support for AS2 security. This will be replaced with end-to-end WSE security.
Privacy
- Any data payload incoming to & outgoing from this web service is temporarily stored in a temp folder
for processing operations
only. Upon completion of an operation the data payload is deleted. Also, in case
of an error where the
temporary file is not deleted, the temporary folder is continuously scanned for
"expired" temporary
files and will be deleted.
What are the benefits of EDIXMLOnline?
With this service EDI and/or XML developers can better help themselves to exchange
electronic documents in a manner they are more a customed to... by writing code
against objects. Also,
- EDI developers can create XML payloads and send it to their trading-partner if the
trading-partner is more familiar with XML than EDI.
- XML developers can create EDI payloads for their "EDI familiar" trading-partners.
- Or EDI developers can receive and XML payload and generate an EDI payload from it.
- Or XML developers can receive and EDI payload and translate it to an XML payload.
- XML developers can make use of the more intuitive XML
payloads to easily transform the data into other XML document (structures) via XSL
transformations. This is unlike other EDI/XML solutiions that make heavy use of
generic element names but use (heavily) xml attributes to identify the EDI datasegment
and dataelement, that although still functional, do not lend themselves to easy
XSL transformation syntax; such XML files do not map easily to .NET dataset and
Java EJB's through serialization.
Simply put, EDIXMLOnline can easily convert EDI to XML, and back.
And because EDIXMLOnline is a SOAP WS-I web service it can be used by any development
tool/platform that takes advantage of this standard to create client applications,
easily. e.g. Netbeans/Java and VS.NET.
Going from EDI to XML and back, there has to be some kind of "rules" or "guideline"
mechanism established for both camps of developers which will force document compliance
between them. How is this accomplished using EDIXMLOnline?
Easily. Using the EDI Standard Exchange File (SEF) which is basically a schema definition
for an EDI file to adhere to, the EDIXMLOnline service creates a corresponding XML
Schema (XSD) whose definition is embedded in the WSDL file that is created
by the service. Using a RAD development tool like VS.NET or Netbeans the programmer
would code their document logic against objects based on proxy classes that will
be generated by these IDE's upon importing the WSDL into the application's project.
However, the SEF and XSD (WSDL) only helps in the facilitation of compliance at
the coding level. Developers from both camps still need to understand and agree
to an "implementation guideline".
Can the EDIXMLOnline service create a SEF file from a XML schema file?
No. The service only generates an XML schema file from an EDI SEF file. This only
makes sense since EDI technology and "standards" have already been established and
have been in use for many years. So, the SEF format is reliable and not susceptible
to change. And many fortune 500 companies still rely on EDI for their B2B operations.
This is unlike XML, where - still to this day - the differing standards on the use
of XML in B2B is still evolving, leading to slow adoption. But with EDIXMLOnline
a new generation of companies and developers can easily implement B2B solutions
to communicate/integrate with proven & reliable EDI solutions used by longer-existing
companies.
What does a payload from EDIXMLOnline look like?
For an EDI document payload of...
... the XML equivalent generated by EDXMLOnline looks like this. (Notice the intuitive element
names, and the parallel hierarchy to a SEF file.)
But remember, as the developer, for basic EDI operations you would not be concerned
with how the XML payload looks like. You would just be programming against the proxy
object(s) and the property values.
Where can I obtain SEF files?
You can purchase SEF files from
www.edidev.com
|