- From: Colin Adam <colin.adam@webservices.org>
- Date: Sun, 24 Jun 2001 20:59:10 +0100
- To: <www-ws@w3.org>
hi, I have been trying to put together a webservices stack, mainly using as a template the "stack" (as reported by james snell at IBM developerworks) which came out of the W3C webservices workshop. It reads 1. internet - IPv4 Ipv6 2. transport - http etc 3. messaging - soap, xml protocol 4. routing reliability transactions ??? 5. workflow, discovery, registries - UDDI ebXML registry, WSFL, XLANG 6. service negotiation - trading partner agreements Layers 2-6 - security, process management, QoS I would like to hear any comments anyone has on this, since I want to get it right and have some concerns. One of my concerns is routing and reliability in layer 4. I think these might be generic and not sufficient to be worth mentioning, particularly since they come under management also. This would leave layer 4 for transactional languages such as XAML, and the business transaction protocol. Then in layer 5 you could describe a webservice as "transactional". You can see it in colour at http://www.webservices.org/whatarewebservices.php regards colin
Received on Sunday, 24 June 2001 15:46:52 UTC