W3C home > Mailing lists > Public > public-ws-policy@w3.org > February 2007

RE: Features at Risk

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Thu, 8 Feb 2007 11:14:51 -0800
To: "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Message-ID: <4D66CCFC0B64BA4BBD79D55F6EBC2257279D7A3A70@NA-EXMSG-C103.redmond.corp.microsoft.com>

This is a reminder that we discussed this proposal at the Feb 7 meeting and held off making a decision about the proposed three "at risk" features until next week's meeting.

We also agreed to have some email discussion which I am trying to encourage by bringing this back to your attention.

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (613) 225-5445 Fax: (425) 936-7329
mailto:Paul.Cotton@microsoft.com





> -----Original Message-----
> From: public-ws-policy-request@w3.org [mailto:public-ws-policy-
> request@w3.org] On Behalf Of Asir Vedamuthu
> Sent: February 7, 2007 11:16 AM
> To: public-ws-policy@w3.org
> Subject: Features at Risk
>
>
> To advance WS-Policy to Proposed Recommendation, the Working Group needs
> to show that each feature in the Framework and Attachment drafts has been
> implemented. Thus far, there aren't any publicly visible implementations
> for the following features:
>
> a) Ignorable Policy Assertions
> b) External Policy Attachment
> c) Attaching Policies Using UDDI
>
> For a successful Candidate Recommendation phase, we request the WG to
> consider marking features a)-c) as being at risk (the history is that most
> of the features marked as being at risk were implemented by multiple
> vendors).
>
> Also, in Nov, W3C requested the Working Group to consider marking feature
> a) as being at risk [1].
>
> [1] http://lists.w3.org/Archives/Public/public-ws-policy/2006Nov/0077.html
>
> Regards,
>
> Asir S Vedamuthu
> Microsoft Corporation
>
Received on Thursday, 8 February 2007 19:15:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:47 GMT