There's nothing to "start," Martin. I didn't say OAG BODs, RosettaNet or
EAN.UCC messages are better than X12. I just read between the lines in
Matt Pierce's posting and inferred that his company doesn't bother with
traditional EDI (X12 or EDIFACT syntax) now. Why bother doing so in the
future? Apparently no customer is breaking down his door asking for X12
832 support. If Matt doesn't use X12 now, and he does any kind of
messaging at all, it must undoubtedly be some kind of XML. So, why not
stick with XML?
All I'm suggesting is that Matt look at XML based e-business standards
that could "loosely" be considered "standard" - rather than inventing
his own. OAG, RosettaNet and EAN.UCC were the first ones that came to
mind that probably include quote or price request messages. If OASIS
UBL, an ebXML core-component based standard, already had such a message
in its kit bag, I would have moved it to the top of my list.
The transport method is probably irrelevant, as each of OAG, RosettaNet
and EAN.UCC - and even X12 - are framework independent. But Matt said he
"is expanding our real-time pricing transaction." I can only assume he
uses Web Services now, where SOAP immediately comes to mind. ebXML
messaging services is just a short hop, skip and jump away from SOAP,
and I mentioned it only because I could swear that ebXML MS has been
warmly endorsed by both RosettaNet (to replace the RNIF) and GS1 n�e
EAN.
ebXML MS and SOAP are at higher levels of abstraction than the
underlying HTTP protocol, which itself (as S-HTTP) sits atop SSL. The
analog for X12 might be real-time EDIINT AS2 - is that what you meant by
"X12 using say, SSL"?
The future is here, Martin. Get used to it and let's "move on." Like
smoking, rotary phones and leisure suits, traditional X12 syntax is
marginalized on the fringes. Even X12 (the standards committee)
recognizes the inevitable march of history and is moving forward with
CICA XML-based core-componentized messaging. Basically, the only X12
syntax based work remaining within X12 itself is implementation guide
("TR3") maintenance on HIPAA transactions - and only because use of X12
syntax is codified (and ossified) by law.
William J. Kammerer
Novannet
Columbus, OH 43221-3859 . USA
+1 (614) 487-0320
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[email protected]>
Sent: Friday, 11 February, 2005 05:49 PM
Subject: RE: [EDI-L] edi pricing transactions
</LURK>
Not trying to start anything, here William...
But how are those methods any better, really, than X12 using say, SSL?
-----Original Message-----
From: William J. Kammerer [mailto:[EMAIL PROTECTED]
Sent: Friday, February 11, 2005 2:33 PM
To: EDI-L Mailing List
Subject: Re: [EDI-L] edi pricing transactions
There's nothing inherently "un-real-time" about traditional X12 or
EDIFACT EDI, and I suppose any of those transaction sets would do for
pricing. But why not skip the X12 altogether if no customers are
calling for it specifically? Why not look at RosettaNet, EAN.UCC XML
or OAGIS messages instead? Then you'll have "real" XML-based EDI which
can be used with a modern real-time transport protocol like SOAP or
ebXML messaging services.
William J. Kammerer
Novannet
Columbus, OH 43221-3859 . USA
+1 (614) 487-0320
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, 11 February, 2005 11:42 AM
Subject: [EDI-L] edi pricing transactions
My company is expanding our real-time pricing transaction and we are
considering whether or not to try to include EDI in our offering. I
would like to know whether or not anyone knows of EDI being used this
way (the 503, 832, and 879 seem likely candidates). If so, how common is
its usage? Is the ability to create one of these as common as the
ability to create an 850 among businesses? I'd appreciate any insight
you might have.
Thanks,
Matt Pierce
.
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
