- From: Christopher B Ferris <chrisfer@us.ibm.com>
- Date: Fri, 15 Jun 2007 09:53:03 -0400
- To: Asir Vedamuthu <asirveda@microsoft.com>
- Cc: Doug Davis <dug@us.ibm.com>, "public-ws-policy@w3.org" <public-ws-policy@w3.org>, "public-ws-policy-interop@w3.org" <public-ws-policy-interop@w3.org>, public-ws-policy-request@w3.org
- Message-ID: <OF8ABC9E6B.6D9AD451-ON852572FB.004B7B42-852572FB.004C2708@us.ibm.com>
Please disregard... I just now noticed that Doug has already done this. Cheers, Christopher Ferris STSM, Software Group Standards Strategy email: chrisfer@us.ibm.com blog: http://www.ibm.com/developerworks/blogs/page/chrisferris phone: +1 508 234 2986 __________________ Attached is an updated version of the optional lax intersection with nested policy test cases that reflect the issues raised by Asir. [attachment "interop.zip" deleted by Christopher B Ferris/Waltham/IBM] Cheers, Christopher Ferris STSM, Software Group Standards Strategy email: chrisfer@us.ibm.com blog: http://www.ibm.com/developerworks/blogs/page/chrisferris phone: +1 508 234 2986 public-ws-policy-request@w3.org wrote on 06/08/2007 08:17:45 PM: > We reviewed these additional optional test cases. They look good. > There are two MINOR issues: > > 1) Expected outcome policy expressions are in a partial normal form > [1]. Thus far, all the expected outcome policy expressions in the > interop directory are in the normal form. If you would like to be > consistent then all the expected policy expressions need to be normalized. > 2) Expected outcome for intersection(lax, policy-35, policy-36) is > labeled as ?-xml? instead of ?.xml?. > > Regards, > > Asir S Vedamuthu > Microsoft Corporation > > > > [1] For instance, there are two assertions in the following policy > expression. Of them, the first assertion is in the normal form and > second assertion is not. > > <wsp:Policy xmlns:wsp="http://www.w3.org/ns/ws-policy"> > <wsp:ExactlyOne> > <wsp:All> > <logging:Logging wsp:Ignorable="true" xmlns:logging="http: > //example.org/policy-test"> > <wsp:Policy> > <wsp:ExactlyOne> > <wsp:All> > <logging:TwentyFourSeven wsp:Ignorable="true"/> > </wsp:All> > </wsp:ExactlyOne> > </wsp:Policy> > </logging:Logging> > <logging:Logging wsp:Ignorable="true" xmlns:logging="http: > //example.org/policy-test"> > <wsp:Policy> > <logging:TwentyFourSeven wsp:Ignorable="true"/> > </wsp:Policy> > </logging:Logging> > </wsp:All> > </wsp:ExactlyOne> > </wsp:Policy> > > > > > From: public-ws-policy-interop-request@w3.org [mailto:public-ws- > policy-interop-request@w3.org] On Behalf Of Doug Davis > Sent: Thursday, May 24, 2007 10:02 AM > To: public-ws-policy@w3.org; public-ws-policy-interop@w3.org > Subject: Additional lax intersection testing > > > *********************** > Warning: Your file, interop.zip, contains more than 32 files after > decompression and cannot be scanned. > *********************** > > > IBM would like to contribue the following tests to the ws-policy wg > for additonal, optional, testing of the lax intersection involving > nested policy. > > > > thanks > -Doug > ______________________________________________________ > STSM | Web Services Architect | IBM Software Group > (919) 254-6905 | IBM T/L 444-6905 | dug@us.ibm.com
Received on Friday, 15 June 2007 13:53:40 UTC