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

RE: Features at Risk

From: Prasad Yendluri <prasad.yendluri@webmethods.com>
Date: Wed, 7 Feb 2007 11:28:46 -0500
Message-ID: <BDD4EF3331E8FB4EA19B677CDAD63020FC36E2@ca-exbe1.webm.webmethods.com>
To: Asir Vedamuthu <asirveda@microsoft.com>, public-ws-policy@w3.org
Cc: Rajesh Koilpillai <Rajesh.Koilpillai@webmethods.com>, "Snow, Skip [CCC-OT_IT]" <skip.snow@citigroup.com>

Hi,

> c) Attaching Policies Using UDDI

webMethods expects to have a UDDI server implementation that supports
attaching policy to UDDI entities as defined in the specification. 
We would be opposed to marking this as a feature at risk.

I have copied Skip Snow from Citigroup, that has shown an interest in this
space.

Regards,
Prasad

-----Original Message-----
From: public-ws-policy-request@w3.org
[mailto:public-ws-policy-request@w3.org] On Behalf Of Asir Vedamuthu
Sent: Wednesday, February 07, 2007 8:18 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 Wednesday, 7 February 2007 16:29:00 GMT

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