- From: Dan Brickley <danbri@w3.org>
- Date: Tue, 19 Nov 2002 13:04:22 -0500 (EST)
- To: Jean-Jacques Moreau <moreau@crf.canon.fr>
- cc: <www-ws@w3.org>
On Tue, 19 Nov 2002, Jean-Jacques Moreau wrote: > Dan, > > There are now a couple of examples of SOAP features[1,2,3]. I > don't quite think they would qualify as a Policy as defined by > WS-Arch. However, Glen Daniels recently gave a presentation[4] on > features to WS-Arch. Thanks. Glen's slides were useful. It seems that SOAP features are (to quote Glen) "Arbitrary pieces of semantics / functionality". Some (but not all) features seem to be close to the WS-Arch's notion of a Policy. Policy per http://www.w3.org/TR/2002/WD-ws-arch-20021114/#id2616445 "...may be used by the over-arching concerns: security, quality of service, and management; as well as higher layers of the description stack.". This doesn't use a Policy as a noun, ie. it doesn't talk about URI-identified _policies_. Instead it talks about a "policy description layer" which relates to "the additional description necessary to specify the business context, qualities of service, security requirements and offerings, and management requirements." So the working draft as it stands does not invite us to ask whether there are some things that are Features but that aren't Policies, whether there are _any_ things that are both Features and Policies etc etc. From the description above, the two do seem to be close, but described in different terms... Dan > [1] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part2.html#WebMethodFeature > [2] http://www.w3.org/2000/xp/Group/2/07/SOAP-AF/aftf-soap-af.html > [3] http://www.w3.org/TR/2002/NOTE-soap12-email-20020626#correlation > [4] http://lists.w3.org/Archives/Public/www-ws-arch/2002Nov/0085.html
Received on Tuesday, 19 November 2002 13:04:23 UTC