|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: (Machine readable) Documentation of EDIFACT-s
Edifecs' SpecBuilder guideline authoring tool can assist in this
matter.<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" />
1. Edifecs' SpecBuilder can output EDI transaction sets/ message
structures in XML Schema (XSD) format. SpecBuilder can also output them in
gXML (Guideline XML) format which is the format of choice for major
integration providers for reading in implementation guidelines into their
Mappers. This allows a user to import the guideline into their Mapper as a
half-map (thus eliminating the need to re-key the message structure into
their Mapper). SpecBuilder has integration bridges with over 20+ B2B Mappers
using gXML such as IBM, Mercator, TIBCO, TIE, webMethods, and many others.
SpecBuilder is standards-agnostic so the user can even handle flat file
structures and XML based structures. Thus users can leverage the tool for
EDI, flat files & XML for data structure/ guideline specialization and
document. The structures can then be exported to a Mapper.
So the scenario works something like this - User will use SpecBuilder to
author, edit and customize an implementation guideline/ MIG. They publish
them in RTF/HTML type human readable formats to distribute within their
internal team and to their trading partners. They also then output the
guidelines in gXML type format to import into their Mapper internally as
well as distribution to their trading partners. This leads to tremendous
savings in time & cost as their trading partners do not have to re key the
same structure into their Mapper and you leverage the "build-once but use
many times" concept.
2. SpecBuilder allows the user to customize/ specialize transaction
sets/ guideline/ MIGs from a variety of standards such as X12, UN/ EDIFACT,
RosettaNet etc. These customized guidelines can then be output as gXML or
XSD which can then be imported into the Mapper.
Some of Edifecs partners use SpecBuilder for exactly that reason. They
provide SpecBuilder to their customers to access and customize the standards
and then export them into their mapper. Off course their Mappers are able
to recognize and handle XML based structures.
3. About GXML: Guideline XML (gXML) is an open specification designed
to facilitate the exchange of e-commerce guidelines using eXtensible Markup
Language (XML). Guidelines are used to define business documents such as
purchase orders, catalog requests and invoices. For more information please
visit http://www.edifecs.com/b2b_resources_guideline.jsp
<http://www.edifecs.com/b2b_resources_guideline.jsp> . Integration
software providers download the gXML specification and DTD from this site to
build the integration bridge without a need to get in touch directly with
Edifecs. In other instances we have worked with the providers to build the
integration.
4. SpecBuilder: SpecBuilder is a schema and guideline authoring,
documentation and testing tool. It is not a Mapper but compliments a Mapper
system.
5. If you would like additional information on SpecBuilder Mapper
integrations or availability of XML based machine readable outputs please
email <mailto: or visit www.edifecs.com
<http://www.edifecs.com/> .
Hope this helps.
Grey Warnock
-----Original Message-----
From: Vigneron. Francois [ mailto:
<mailto: ]
Sent: Monday, July 08, 2002 12:06 AM
To: 'EDI-L
Subject: RE: [EDI-L] (Machine readable) Documentation of
EDIFACT-messages
So you plan to write an EDIFACT-guideline and a XML-guideline
(documentation describing the messages used by the market-place).
It is very clever that you choose to propose both to your trading
partners.
As far as the EDIFACT data structures are concerned, it's quite sure
that most EDI-vendors will already have the necessary structures ready
in their librairies and/or that they or your trading partners can
adapt/create them quickly following the guidelines. Most trading
partners are used to that espacially in automotive where you have many
adaptation work for each partner.
I don't know of a tool which can create data structures for several
EDI-tools. It could be that there is one. Some vendors will also admit
that they can take over data strutures from their main competitors - but
it does not help you much.
If you think it's necessary to provide your trading partners with
ready-to-import data-structures, you can check what tools your trading
partners have and go to the vendors. As far as Seeburger's propriatary
data structures are concerned, we are ready to provide you with the
EDIFACT structures at a small cost so that you can hand them on to your
trading partners which have our EDI-softwares. I'm sure that our
collegues would be ready to do that too.
As far as XML data structures are concerned it's even easier as every
"serious" XML-mapping tool is able to import at least DTD and probably
also schemes. So you do not have to care for specificities.
In the end your trading partners will still have to do (or let do) the
mappings from/to their internal IT-systems to the exchange structure
(XML or EDIFACT).
Kind regards,
Francois Vigneron
-----Message d'origine-----
De : Anders Tholén [ mailto:
<mailto: ]
Envoyé : samedi 6 juillet 2002 19:54
À : Vigneron. Francois; 'EDI-L
Objet : Re: [EDI-L] (Machine readable) Documentation of EDIFACT-messages
Yes, the purpose is to offer integration for EDI-enabled trading
partners (buyers and suppliers) to a marketplace, leveraging an industry
standard sub-set. And to do this e.g. by providing them with good
documentation and possibly by letting them import the proposed
EDI-structures.
(The industry standard is defined by the standard organisation for the
industry in question (steel) who are defining both an EDIFACT standard
as well as an XML-standard.)
With best regards
Anders Tholén
[Non-text portions of this message have been removed]
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
<http://groups.yahoo.com/group/EDI-L>
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
<http://docs.yahoo.com/info/terms/>
[Non-text portions of this message have been removed]
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
