- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 12 Sep 2007 15:00:43 +0000
- To: public-ws-policy-qa@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5039 Summary: potential issues for primer and guidelines #2 Product: WS-Policy Version: FPWD Platform: All URL: http://lists.w3.org/Archives/Public/public-ws- policy/2007Jul/0047.html OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Primer AssignedTo: fsasaki@w3.org ReportedBy: chrisfer@us.ibm.com QAContact: public-ws-policy-qa@w3.org 2. The specs do not adequately address support for discovery. If anything, they make discovery very difficult because policy attachment is all over the place and the roll up is to the levels of finer granularity rather than the service level where most people would expect to find it. Information expressed as policies will likely form an important set of the search criteria when looking for services (more typically, looking for the business effects that result from the service interaction [2]) and there is no guidance (and seemingly no consideration) on how such information can be effectively used for discovery or any other function besides message level protocols. [2] Are the "business effects", i.e. what happens when you interact with a service, supposed to be expressed as part of "capabilities and requirements" covered by WS-Policy? My initial read was yes, but am I reading too much into it? Again, supporting consumer policies so you have something with which to intersect services policies seems to be important in the current context.
Received on Wednesday, 12 September 2007 15:00:46 UTC