W3C home > Mailing lists > Public > public-ws-chor@w3.org > April 2003

Re: Requirement - Ability to store and retrieve from a registry / repository

From: <Daniel_Austin@grainger.com>
Date: Thu, 17 Apr 2003 09:59:46 -0500
To: tony_fletcher@btopenworld.com
Cc: Daniel_Austin@grainger.com, martin.chapman@oracle.com, public-ws-chor@w3.org, public-ws-chor-request@w3.org, steve@enigmatec.net
Message-ID: <OFC0937955.1327AFE8-ON86256D0B.00524D09@grainger.com>


Hi Folks,

      This sort of mail needs to also be CC'd to the issues mailing list.
Has that been established yet?

Regards,

D-

*************************************************
Dr. Daniel Austin
Sr. Technical Architect / Architecture Team Lead
daniel_austin@notes.grainger.com <----- Note change!
847 793 5044
Visit http://www.grainger.com

"If I get a little money, I buy books. If there is anything left over, I
buy clothing and food."
-Erasmus


                                                                                                                                    
                      "Tony Fletcher"                                                                                               
                      <tony_fletcher@btope        To:       public-ws-chor@w3.org, Daniel_Austin@grainger.com                       
                      nworld.com>                 cc:       "'Martin Chapman'" <martin.chapman@oracle.com>, steve@enigmatec.net     
                      Sent by:                    Subject:  Requirement - Ability to store and retrieve from a registry /           
                      public-ws-chor-reque         repository                                                                       
                      st@w3.org                                                                                                     
                                                                                                                                    
                                                                                                                                    
                      04/17/2003 03:55 AM                                                                                           
                                                                                                                                    
                                                                                                                                    




Dear Daniel et al,

I would like to highlight that if the point that if the gist of what Fred
says below is agreed, then it contains a requirement in the language that
should be in our Requirements document.

That is it shall be possible and practicable to store instances of use of
the WS-Chor language in a Registry / Repository, to be a able to search for
such instances and to retrieve them.

Best Regards     Tony
A M Fletcher

Cohesions 1.0 (TM)

Business transaction management software for application coordination

Choreology Ltd., 13 Austin Friars, London EC2N 2JX     UK
Tel: +44 (0) 20 76701787   Fax: +44 (0) 20 7670 1785  Mobile: +44 (0) 7801
948219
tony.fletcher@choreology.com     (Home: amfletcher@iee.org)
      -----Original Message-----
      From: public-ws-chor-request@w3.org
      [mailto:public-ws-chor-request@w3.org] On Behalf Of Cummins, Fred A
      Sent: 12 April 2003 00:09
      To: Stephen White; Assaf Arkin; Patil, Sanjaykumar
      Cc: Martin Chapman; Burdett, David; Cummins, Fred A; jdart@tibco.com;
      public-ws-chor@w3.org
      Subject: RE: Internal processes and/or external choreographies (was
      RE: Events and States ...

      Steve,

      I believe the choreography language should express the exchange at
      the level of abstraction that is appropriate for business people to
      understand.  This does not mean that the form of expression is
      appropriate for business people.  I beleive we should focus on the
      XML form of expression as that is the form that will be appropriate
      for retrieval from registries and exchanged between potential
      participants in a web services exchange.  A form suitable for
      business users should be deferred since this requires different
      skills and can be done in different ways by different tools without
      adverse impact on the computational web services protocol
      specifications and implementations.

      Fred
Received on Thursday, 17 April 2003 10:59:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:00:58 UTC