- From: Paul Denning <pauld@mitre.org>
- Date: Wed, 23 Aug 2006 11:48:51 -0400
- To: public-ws-policy@w3.org
Lets say my policy subject is an endpoint [e]. Lets assume two different policy files exist, [P1] and [P2]. I may have a WSDL file for endpoint [e] with an attached policy [1] that references [P1]. I may also have a UDDI entry for [e] with an attached policy [2] that references [P2]. So, both [P1] and [P2] are associated with [e]. What if [P1] and [P2] conflict? For example, [P1] = endpoint available only Mon-Fri [P2] = endpoint available only on Sat and Sun [1] http://www.w3.org/Submission/WS-PolicyAttachment/#EndpointPolicySubject [2] http://www.w3.org/Submission/WS-PolicyAttachment/#EndpointPolicySubjectUDDI [3] http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425/#Policy_Inclusion It would be nice to avoid this situation. Perhaps an approach that would work is for the WSDL policy reference to point to a UDDI tModel, then the UDDI tModel points to the actual policy document, say [P1]. However, I don't think [3] allows this extra layer of indirection where WSDL points to UDDI which points to Policy. I think [3] only allows WSDL to point to Policy. Is my reading correct? Do you agree that the specs should support this extra layer of indirection to avoid potential policy conflicts and reduce the burden of synchronizing the WSDL and UDDI policy references? Paul
Received on Wednesday, 23 August 2006 15:49:02 UTC