I appreciate Sally's comments.
As long as we're going to talk "reality" (or ignorance of it), I assume that
the types of business communications directly affecting supply-chain are in
the procurement materials management realm. How do I discern what XML is
used for implementation in this
An afterthought.
My comments are not meant to demean or belittle any of the activity
occurring in ebXML. I agree that this is important work that needs to
continue.
-Karen
-- XML/edi Group Discussion List --
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to:
Also, authentication is a security function unrelated to XML. One
authenticates a user on a system with a user-name and password, for example.
I've not read the article yet so I can't comment on its accuracy. From your
comments, it sounds like there were major omissions and glaring errors.
Message text written by "Ken North"
I've not read the article yet so I can't comment on its accuracy. From
your
comments, it sounds like there were major omissions and glaring errors.
However, the writer might have described an authentication and
authorization
scenario, for example, to describe
As long as we're slamming bad reporting, reporting of hype without
countering with factual content may have cause the economic "bubble"
mentioned by some of the posters. Market investors and analysts do read
these publications.
FWIW,
-Karen
-- XML/edi Group Discussion List --
Colleagues,
I very rarely pass comment on these discussions - not because I'm sat in an
ivory tower, nor because none of them warrant augmentation. The primary
reason is time which these days I have very little of. However, in this
instance I really must say something.
There is one thing
Steve,
You are totally on the mark. It is, was, and will be the challenge of
semantic alignment of the business information being exchanged and then the
mapping of that to the backend systems, that is the heartburn of EDI, edi,
XML, or any other flavor of file structure/format. This still
Martin, Steve,
Thank you, thank you, thank you. It's about time we all recognize this myth
and get off this attempt to "standardize" documents. It just ain't going to
happen in anyone's lifetime. I do agree with and support the concept of
certain standardized "core components" that can be reused
Karen,
Not exactly. I think you're close but not quite there. It's not the
variation in internal systems file structures that cause the challenge, it's
the semantic definition of every piece of business information being
exchanged. This is what has to be aligned between business partners. Once
David,
I can't resist! When is a fact not true? Something is either a fact or it's
not a fact. Are there false facts?
On the other hand, I do agree with your comments about the author of the
article in question. It's just more of the hypster-mongering, but at the
other end of the pendulum
Title: RE: The XML/EDI has no Clothes!
Hey
Anthony,
good
point. You're absolutely right and if the Redmond crew misses that target (say
the DOJ breaks them up as the Judge wants them to) I guess IBM can build a
mammoth mainframe for everyone in the universe to use. Maybe we can all use
Title: RE: The XML/EDI has no Clothes!
Hello everyone,
Just a quick heads up - yes, BizTalk is alive,
operational and being actively deployed... ___Mario O. PipkinDirector, Microsoft e*BISElectronic Business Integration ServicesIntranet: http://itgweb/ebisPhone: (425)
Title: RE: The XML/EDI has no Clothes!
I
forgot to add that the real benefit of XML is NOT extensibility,
butreengineering the communication process from a higher level, which now
includes transport.
With
X12 EDI there are alot of variations on how the files are transported, how acks
Title: XML.com: Even More Extensible
All,
Earlier I
posted a URL to xml.com where one could find references for many XML
vocabularies. What I actually had in mind was this article by Alan
Kotok.
If you
follow the links for Frameworks, Functions, and Verticals you see just how many
are
Title: RE: The XML/EDI has no Clothes!
Microsoft's next targets, via .net initiative, will
be SAP, etc -
They will copy the concept of mysap.com
where ERPs are hosted and developed as a service, then participants will all use
Biztalk and there will be no incompatability.
ERP vendors
Over the last year I had the experience of working on both and EDI as well
as an XML functions and I would like to share my experience.
The EDI function involved sending checks for printing at a bank.
The ANSI X12 spec was no walk in the park. The EDI spec was very restrictive
in terms of
Hi all,
One of the complaints of EDI is cost. The way I see it, XML will not be less
costlier. The amount of initiatives moving this XML is costing money, and
they would like to make money from it.
Next time you use XML, you'll pay (probably like pay-per-view tv style). To
parse, you pay for
17 matches
Mail list logo
