"NAGEL Erlend" wrote:

>> No. We are talking about having standardized templates on which to build
>> understandings between trading partners. This is the current big
difference
>> between XML (general XML not XYZ's implementation of it) and the
traditional
>> eCommerce formats (X12/EDIFACT).
>
> Andy, maybe you are willing to explain this. What are these
> standardized templates on which to build understandings between
> trading partners?
>
> I've been thinking that these templates may be semantic elements, like
> the ones in the UNTDED (UN Trade Data Element Directory) or maybe they
> also include rules for building your own messages using these
> elements, like the UN/EDIFACT Message Design Guidelines?
>
> I guess there is more to it and would love to hear, like no doubt
> others on the EDI-L as well, what these templates are.
>
> thanks,
>
> Erlend Nagel.

The templates I'm referring to are, as you surmised, the element, segment
and document dictionaries published somewhat semi-annually by the ANSI X12
and the ISO EDIFACT related committees. Physically, we refer to them as X12
4020 850 or EDIFACT D97B ORDERS.

Why do I call these great works of our times templates? Because each trading
partner is able to choose subsets and interpretations of each document which
best meets their business environment and their application's capabilities.
This gives the flexibility of implementation within a structured
understanding so that you ALWAYS know where the Ordered Date is in a
Purchase Order and how the ship to address will be structured but you and
your trading partner can come to an understanding as to how much information
is sent and the basis for defaulting that which is not.

Well, that's my take on it anyway!!

Andy

=======================================================================
To signoff the EDI-L list,  mailto:[EMAIL PROTECTED]
To subscribe,               mailto:[EMAIL PROTECTED]
To contact the list owner:  mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/

Reply via email to