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

RE: Features at Risk: Attaching Policies Using UDDI

From: Snow, Skip [CCC-OT_IT] <skip.snow@citigroup.com>
Date: Wed, 7 Feb 2007 17:37:07 -0500
Message-ID: <526F87F9F4FB3E4D8710C7F5DC00C5A1036E95A1@EXNJMB28.nam.nsroot.net>
To: <public-ws-policy@w3.org>

Members:

In a separate set of threads I have brought to the attention of the
chairs at least two additional product implementations that are live
today with support for the feature under debate. I have introduced the
chairs to representatives from both firms witch have allowed me to do
so.

While Citigroup is not and can not, be in the business of presenting
technology vendors to public forums like this, we are confident that the
chairs will follow up with these vendors. 

We trust that the public implantations of these features, which we have
brought to the chair's attention, and our own concern with these
important matters will help put this matter into its proper perspective.

If not we are ready to help in any way resolve this issue.

Thank you.

Skip Snow  

-----Original Message-----
From: Snow, Skip [CCC-OT_IT] [mailto:skip.snow@citigroup.com]
Sent: Wednesday, February 07, 2007 8:36 AM
To: Prasad Yendluri; Asir Vedamuthu; public-ws-policy@w3.org
Cc: Rajesh Koilpillai
Subject: RE: Features at Risk

Prasad:

Thank you for this notice.

It is important to insure that policies and their attachments are
discoverable in a standards based way.

It is not sufficient that various meta data resource transfer mechanisms
be available if an actor happens to know the bindings to the actors that
contain information about policies and their attachments are.

It is required that a registry, using a standards based registry
protocol be available for this purpose. The charter stipulates that this
registry be UDDI. We are satisfied with the charter's stipulation. We
would be dismayed if this stipulation was not met.

Skip Snow
Citigroup.

 

-----Original Message-----
From: Prasad Yendluri [mailto:prasad.yendluri@webmethods.com]
Sent: Wednesday, February 07, 2007 11:29 AM
To: Asir Vedamuthu; public-ws-policy@w3.org
Cc: Rajesh Koilpillai; Snow, Skip [CCC-OT_IT]
Subject: RE: Features at Risk

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 22:37:30 GMT

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