OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: BPSS updated examples


To be honest I have not studied the content of the drop ship example. I
simply made it compliant with the changes over time. I'll take a close look.
Can I infer that all BinaryCollaborations need a Start state? Likewise do
they all need a Success state? 

I have to admit, I haven't really thought though the MultiParty or
CollaborationActivity stuff. I have been focusing on more atomic things like
the RosettaNet PIPs.

Kurt Kanaskie
Lucent Technologies
(610) 778-1069 Note the new number!

 -----Original Message-----
From: 	Cory Casanave [mailto:cory-c@enterprise-component.com] 
Sent:	Friday, May 04, 2001 3:43 PM
To:	Kanaskie, Kurt A (Kurt); 'ebxml-bp@lists.ebxml.org'
Cc:	'ebXML-PoC'; Eugenio Alvarez
Subject:	RE: BPSS updated examples

Issue with sample models:
We have found the following issue with the drop-ship model which reflects a
more general problem.  The issue is that the initiator of a binary
collaboration is non deterministic without a start state, few have a start
state.  Also the direction of a <CollaborationActivity> is not

Please refer to "DropShipSamples_v1", the "Credit Charge" Binary

1) The roles reference the roles in the other collaboration, the "local"
roles are not referenced.  
2) There is no way to know which side of the collaboration is starting the
3) Note that there is no start state so we don't know the initiator

	a) The initiator be identified in a binary collaboration, either by
requiring a start state or flagging the AuthorizingRoles as requester or
responder (I prefer the flag as it is much easier to parse).  Note that the
old way of doing the roles as attributes did capture this information.
	b) The from/to roles must reference the LOCAL roles (just like a
business transaction activity) - the DTD/Schema does not make this clear so
they would not change, only the examples will change - I will have to look
at the text.

The combination of these two will make all directions deterministic.

For the demo we will be changing the role names as above and making
assumptions about the start state, we may change the sample files to reflect
these assumptions.

Cory Casanave

> -----Original Message-----
> From:	Kanaskie, Kurt A (Kurt) [SMTP:kkanaskie@lucent.com]
> Sent:	Friday, May 04, 2001 2:54 PM
> To:	'ebxml-bp@lists.ebxml.org'
> Cc:	'ebXML-PoC'
> Subject:	BPSS updated examples
> All,
> Attached are slightly updated examples and the latest DTD/Schema. I found
> some copy and paste errors in the OAG and ebXML examples.
> Best Regards,
>  <<BPSS_XML_V1_2001_05_04.zip>> 
> ________________________________________________________________
> Kurt Kanaskie
> Lucent Technologies
> kkanaskie@lucent.com
> (610) 778-1069 Note the new number!
>  << File: BPSS_XML_V1_2001_05_04.zip >> 

To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-bp-request@lists.ebxml.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC