Re: [asap] Demonstration Scenarios for Interoperability Demo

[John Fuller <jfuller@wernervas.com>]

To clarify then, the customer order is the context data for a createinstancerq
and the customer order confirmation is the result data for a completedrq? 


***

FYI, a discussion in WSRM right now is to replace URIs with WSRefs
so that we know what type of binding we're dealing with:
ex: do we HTTP Post a soap request or SMTP to a reply-to URI.


On May 5, 2004, at 8:21 AM, Justin Brunt wrote:

Please find attached a zip file that contains the text for the proposed scenarios for June's interoperability demonstrations. Following last week's conversations in eth con call I have simplified the scenarios greatly.

There are two document in the zip file:
• One containing just the text for the scenarios (Demo_scenario.doc)
• A modified version of Keith's Observer information sheet with the scenario text pasted in (WfXML_Demo_Scenario_Overview.doc).



I have also include the .XSD file that defines the data to be used in the interchanges plus the corresponding output from XMLSPY.

Please let me have any comments/suggestions for change.

Best regards

Justin
 
<<Simple_demo_p3.zip>>
Justin C Brunt
Research Director
 
staffware.
THE POWER OF PROCESS

>   
> Tel:        +44 (0) 1793 441300 
> Fax:       +44 (0) 1793 441333 
> Mobile:   +44 (0) 7768 924239 
> http://www.staffware.com 
>   
>
> The information in this e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  If you are not the intended recipient, please inform the sender immediately and destroy the e-mail and any attachments.  No liability or responsibility whatsoever is accepted for any review, retransmission, dissemination or other use or any action taken or omitted, in reliance on this e-mail or its contents
> <Simple_demo_p3>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/asap/members/leave_workgroup.php.