David,
While your proposed solution to Doug's query is workable, your assumption
that the prod/test flag in the EDI headers was caused by VANs is TOTALLY
WRONG. The need to know about whether an interchange contains test or
production data is important for the intended receiver's processing and
makes no difference whatsoever to any VAN. Thus, the same "business
requirement" will hold true for XML-formatted documents as well.
Furthermore, I can see where it would be very useful for the intended
receiver to know early on (in the transport message header area for example)
whether the enclosed documents contain test or production data.
Rachel
-----Original Message-----
From: David RR Webber [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 19, 2000 10:35 AM
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]';
[EMAIL PROTECTED]
Subject: re: Test vs. Production
Message text written by Doug Anderson
>
Good Afternoon:
Today in EDI we have a test/production indicator in the header (ISA in ASC
X12, UNB in UN/EDIFACT) that allows someone to route the data to the
correct
system. Is there something similar in XML either in use today or on the
drawing board? We don't want to create something if this has already been
solved. We have a customer that will be moving some of their trading
partners into production and would prefer not to have to change receiver
ID's in order to differentiate between those trading partners in test vs.
those in production.
Thanks in advance.
Doug
<<<<<<<<<<<<<<<<<<<
I hate to say this but this is nothing to do with transactions - but
everything to
do with the goofy way VAN's worked in the past.
A local look-up table:
Cust ID, Trans ID, Status (Test / Prod )
is all you need to fix this! Then locally you can choose what type of
processing
you are doing. This also helps when some TP's are in test, others already
in
prod' - they can locally determine their own actions.
Notice you can also use this to switch dynamically
on the fly -regardless of what the actual transaction says!
The VAN's just never wanted to maintain this for you.
DW.
------ XML/edi Group Discussion List ------
Homepage =http://www.XMLedi-Group.org
Unsubscribe =send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
