OASIS Open

Microsoft

No

There is an obvious error in the WS-Policy ns reference. We cancelled our last ballot for errors in the specification that were more minor than an incorrect namespace. Now the Policy CR we are referencing will be out of date by the time RM is up for a member approval ballot. With these two obvious errors I think we risk not passing a member approval ballot for the specifications.

Regretfully I have to change my vote on the current ballot to no.

---
Previous comment regarding my earlier abstention:
---
The late change from referencing WS-Policy 1.2 to WS-Policy 1.5 in RM Policy requires that I abstain.

This change was not technically necessary as the RM Policy assertion does not use any features of WS-Policy 1.5 alone and the assertion is backwards compatible with WS-Policy 1.2. The change does however mean that Microsoft cannot use the revised RM Policy assertion and be compliant to this specification until we also support the final version of WS-Policy 1.5.

I believe that the delay caused by waiting for WS-Policy 1.5 to be completed is going to hurt the market adoption of WS-RM and WS-RM Policy.

It is regretful that the TC made this change at the last minute thinking of the references alone rather than considering the change's impact on market adoption of the specifications.