W3C home > Mailing lists > Public > www-ws-arch@w3.org > July 2002

RE: [hst] harvest list

From: <michael.mahan@nokia.com>
Date: Wed, 10 Jul 2002 15:15:34 -0400
Message-ID: <5C76D29CD0FA3143896D08BB1743296A072D19@bsebe001.NOE.Nokia.com>
To: <Suresh_Damodaran@stercomm.com>
Cc: <www-ws-arch@w3.org>

Thanks for pitching in Suresh! I will put your name aside 
ebXML.

Follow the links I sent Joel. Basically, we want to capture the 
hard architectual elements of connectors and components, along 
with descriptions of their roles and responsiblities. Also, we 
want to try to capture any other architectural feature often 
described in other 'views' of the architecture. From this I mean 
things like MEPS, process models, etc. We/I am open to some 
interpretation here, so grab what seems relevant to the ebXML 
architecture. We will try to normalize after the harvesting is
completed.

Thanks again. 

Mike 

>-----Original Message-----
>From: ext Damodaran, Suresh [mailto:Suresh_Damodaran@stercomm.com]
>Sent: July 10, 2002 11:28 AM
>To: Mahan Michael (NRC/Boston)
>Subject: RE: [hst] harvest list
>
>
>Michael,
>
>As you may know, I have a fairly good understanding of most 
>standards in
>ebXML.
>If you give me a brief idea about what is expected of 
>harvesting, I can help
>with ebXML.
>Please let me know.
>
>Regards,
>
>-Suresh
>Sterling Commerce   
>
>
>
>-----Original Message-----
>From: michael.mahan@nokia.com [mailto:michael.mahan@nokia.com]
>Sent: Wednesday, July 10, 2002 8:46 AM
>To: joel.d.munter@intel.com; distobj@acm.org; Hao.He@thomson.com.au;
>gdaniels@macromedia.com; jones@research.att.com
>Cc: chrisfer@us.ibm.com; w3c-ws-arch@w3.org
>Subject: RE: [hst] harvest list
>
>
>
>Thanks Joel, your help is appreciated. Please have at it with UDDI.
>
>There have been discussions on what harvesting entails[1][2]. For an 
>example, Mark has harvested REST [3]. Our overall approach is at [4], 
>which we are entering step 2.
>
>Hope this helps - we are trying to figure this out as we go, 
>so feel free 
>to chime in with suggestions.
>
>[1] http://lists.w3.org/Archives/Member/w3c-ws-arch/2002Jul/0017.html
>[2] http://lists.w3.org/Archives/Member/w3c-ws-arch/2002Jul/0028.html
>[3] http://lists.w3.org/Archives/Member/w3c-ws-arch/2002Jul/0023.html
>[4] http://lists.w3.org/Archives/Member/w3c-ws-arch/2002Jul/0001.html
>
>>-----Original Message-----
>>From: ext Munter, Joel D [mailto:joel.d.munter@intel.com]
>>Sent: July 09, 2002 02:02 PM
>>To: Mahan Michael (NRC/Boston); distobj@acm.org; 
>Hao.He@thomson.com.au;
>>gdaniels@macromedia.com; jones@research.att.com
>>Cc: chrisfer@us.ibm.com; w3c-ws-arch@w3.org
>>Subject: RE: [hst] harvest list
>>
>>
>>As I am a little unclear of precisely what you are looking 
>>for, I would be
>>happy to help someone "harvest" UDDI.  
>>Joel
>>
>>-----Original Message-----
>>From: michael.mahan@nokia.com [mailto:michael.mahan@nokia.com]
>>Sent: Monday, July 08, 2002 2:20 PM
>>To: distobj@acm.org; Hao.He@thomson.com.au; gdaniels@macromedia.com;
>>jones@research.att.com
>>Cc: chrisfer@us.ibm.com; w3c-ws-arch@w3.org
>>Subject: [hst] harvest list
>>
>>
>>
>>Hi All,
>>
>>It seems like there is a concensus to harvest both types of 
>>architectural
>>entities - 
>>both components/connectors and relevant arch features of the system
>>(processing model,
>>MEPs, etc.)
>>
>>Moving on, the current list to harvest:
>>1. SOAP/XMLP
>>2. WSD
>>3. OMG/Corba
>>4. REST
>>5. Meerkat
>>6. XML-RPC
>>7. UDDI
>>8. ebXML
>>
>>Any others?
>>
>>Mark Jones mentioned that he is going through the SOAP spec. In the
>>democratic 
>>spirit of divide and conquer, are there volunteers for the other
>>systems/specs?
>>
>>Mike
>>
>
Received on Wednesday, 10 July 2002 15:15:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:01 GMT