RE: POC Demo's One-only, two-in-one, two-separate....?

[Krishna Sankar <ksankar@cisco.com>]

Bob,

	Thanks for pointing this out.

	Yep, you are right. The integration is at the document level and *need* not
be at the demo level. I am sure we will have the demo showing many
scenarios.

	The idea is to have one POC control *document* which contains the scenarios
from the GCI and Automotive proposals.

	For example there might be four (or two or three)  use cases/scenarios -
say two from Automotive and two from GCI. Then folks can decide which ones
they want to implement/participate in. The roles could look like Buyer-AIAG,
Buyer-CGI, etc. That way we will avoid sending cheese orders to GM ! May be
a hub can process both as it is payload agnostic.

	Both processes should be traceable to the top level BP/CC processes,
components. Both examples should use common regrep implementations.

	And if it is possible to combine them or show cross-context, then
excellent. We can show this as a stretch goal.

	Folks, please voice your ideas, opinions et al. We need to pull this
together in the next couple of days.

	cheers

-----Original Message-----
From: Bob Haugen [mailto:linkage@interaccess.com]
Sent: Friday, September 29, 2000 11:00 AM
To: Ebxml-Poc
Subject: RE: POC Demo's One-only, two-in-one, two-separate....?


Krishna Sankar wrote:
>	From what I understand, at the moment, the thought is that there will be
>one eintegrated demo. The starting point of the integrated proposal is
>Mark's document sent on 9/28. I plan to work with Mark, Philippe, Sig et al
>and send the first cut by COB Sunday.

Maybe you meant this in the first place, but demo planners
need to understand that the GCI and automotive content
come from different supply chains and so you can't really
mix and match, e.g. send cheese to the Ford assembly
line when they want gears.
The materials group had a proposal for taking a business
document from one context and adapting it for the other;
that would be cool.

Good luck,
Bob Haugen