Title: RFA Custom
I welcome this direction of work suggested by Rachel for our work.
 
What I suggest is to recognize, once for all,  that standardised EDI (X12 , EDIFACT etc.) has produced results which are an input of outstanding interest for XML.
Hoping that this is well understood, we can be confident that XML will preserve the heritage. At least this is my assumption. Then the real questions become :
  1. What is the real davantage to use XML assuming that we admit that we have to bring with us all the results gained working on EDI Standards. In other terms :
  2. What is the value added by XML and its complements ?
  3. Shall we start using XML now or shall we wait until it is mature ?
  4. How can we live with systems where there is on the hand side users having established "traditional' EDI systems (if it works don't fix it, as you say in the US) and on the other hand new comers to B2B who would prefer to use XML rather than 'traditional" EDI ? (B2B in the sense of exchange of data between applications/softwares/ERP etc. I give this definition because I think that the concept of e-commerce is too vague, too large) .
  5. What are the others doing ? By "the others", I mean a) software editors, ERP vendors (they announce XML gateways which can be customized by the clients whishing to send orders, get their status etc.., b) user's groups such as Architecture and construction, chartered accountants, reinsurance companies, health care etc..
These are the topics that I would like to hear discussing about, because these are the problems to which I am confronted.
 
R�my Marchand
API*EDI
Suite 284       et                 126 rue du Vallon des Auffes
19 place de l'IRIS               13007 Marseille
92400 Courbevoie              T�l : 04 91 31 63 22
T�l : 01 49 01 00 08
Fax 01 49 00 13 79
Portable : 06 11 02 02 37
email : [EMAIL PROTECTED]
----- Message d'origine -----
Envoy� : dimanche 30 juillet 2000 19:33
Objet : The Value and Use of XML

Now that we've gotten all of the VAN bashing and toilet-bowl humor and comments out of the way for a while (well, we did need a bit of comic relief, didn't we!) I would like to see the discussion on this list move away from X12 vs XML (or EDI vs XML) and VAN bashing to where can XML play a role, how can it do that, and of course, what's required for XML to deliver on all of the expectations. As I've said, XML still has a lot of maturing to do in order to be fully functional and robust for industrial prime-time use. These are the issues that we could be focusing on.
 
Rachel
 
Rachel Foerster
Principal
Rachel Foerster & Associates
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099-3602
Voice: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
 
R�my Marchand
API*EDI
Suite 284       et                 126 rue du Vallon des Auffes
19 place de l'IRIS               13007 Marseille
92400 Courbevoie              T�l : 04 91 31 63 22
T�l : 01 49 01 00 08
Fax 01 49 00 13 79
Portable : 06 11 02 02 37
email : [EMAIL PROTECTED]
----- Message d'origine -----
Envoy� : dimanche 30 juillet 2000 19:33
Objet : The Value and Use of XML

Now that we've gotten all of the VAN bashing and toilet-bowl humor and comments out of the way for a while (well, we did need a bit of comic relief, didn't we!) I would like to see the discussion on this list move away from X12 vs XML (or EDI vs XML) and VAN bashing to where can XML play a role, how can it do that, and of course, what's required for XML to deliver on all of the expectations. As I've said, XML still has a lot of maturing to do in order to be fully functional and robust for industrial prime-time use. These are the issues that we could be focusing on.
 
Rachel
 
Rachel Foerster
Principal
Rachel Foerster & Associates
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099-3602
Voice: 847-872-8070
Fax: 847-872-6860
http://www.rfa-edi.com
 

Reply via email to