RE: Proposed BP PT comments on Requirements

[khwaja.shaik@us.pwcglobal.com]

Moreover It gives single foundation for EAI+IAI+B2B and also reduces cost, easy
manageability, Single System View etc. for the ebxml users.

 Definitely It is good idea to look for a strong XML-based foundation that takes
care of Enterprise Application Integration, Internet Application Integration and
B2B.

Thanks,
Khwaja




"Miller, Robert (GEIS)" <Robert.Miller@geis.ge.com> on 03/23/2000 10:07:09 AM
To:   ebXML-BP@lists.oasis-open.org
cc:
Subject:  RE: Proposed BP PT comments on Requirements



I for one have no problem with expanding the scope to include app-to-app
within an enterprise.  ebXML is not about providing specific solutions, it
is about providing an XML-based foundation upon which such solutions can be
built.  By my reckoning, that foundation is as applicable to the internal
app-to-app problem as it is to the external app-to-app problem we call B2B.

Cheers,
       Bob Miller

-----Original Message-----
From: Bob Haugen [mailto:linkage@interaccess.com]
Sent: Thursday, March 23, 2000 7:28 AM
To: ebXML-BP@lists.oasis-open.org
Subject: RE: Proposed BP PT comments on Requirements


Paul Levine wrote:
>I have taken the opportunity to propose a few other
>revisions that specifically include within the ebXML scope app-to-app
>applications of XML within an enterprise.  This is very important for large
>enterprises that have networks of operations support systems that have to
>interoperate.

Why duplicate what the OAG is doing in this space?
Is there anything wrong with their efforts?
Is there any real confusion about the generally-accepted
app-to-app standards org?  (Anything like the obvious confusion
about B2B standards?)
What do you think this will do to the scope of ebXML?
Won't it require expanding to include everything in the
OAG standards and then some?

As you can tell, I am resistant to an expansion of scope,
but do not want to misunderstand your proposal.
Can you explain more about why you are proposing it?
And maybe more of the scope of your intention?
(For example, if all you mean is party-to-party dealings within
an enterprise, where "parties" are different business units, and
the same ebXML B2B standards can be used, then my objections
do not hold.  But if you mean any and all internal apps, and
all their integration requirements, I suspect it's a big expansion.)

Respectfully,
Bob Haugen



----------------------------------------------------------------
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material.  Any
review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited.   If you received this in error, please
contact the sender and delete the material from any computer.