of how policies may be defined for several existing use cases that have been
part of the WS-Security Interops that have been conducted", where the
previous paragraph defines these to include "WS-Security TC and other
WS-Security based Interops".
As such, this would not include stand-alone WS-SC and WS-Trust. However,
it would include WS-SC and WS-Trust as included in any of the above mentioned
interops, such as the WS-SX Interop.
If someone would like to write up appropriate examples of these for the examples
doc, they would be a welcome addition. I had been considering it while the
WS-SX Interop was in progress, however from that time on resource limitations
prevented me from personally doing it. We could probably add a full section to
describe in a similar level of detail the ws-sx interop examples. In fact, the
unfinished example 2.3.2.5 would be a good place to start with this, as it
relates to an earlier Interop, but may be more appropriate to apply instead
to the more recent Interop.
Thanks,
Rich
Anthony Nadalin wrote:
Discussion is that if we are going to have an examples document it should not be just about WS-SecurityPolicy but about all the specifications in the TC, so I don't agree with what Hal submitted
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
Prateek Mishra ---07/02/2007 04:39:56 PM---Hal,
Prateek Mishra <prateek.mishra@oracle.com>
07/02/2007 04:34 PM
To
Hal Lockhart <hlockhar@bea.com>
cc
Anthony Nadalin/Austin/IBM@IBMUS, Kelvin Lawrence/Austin/IBM@IBMUS, ws-sx@lists.oasis-open.org
Subject
Re: [ws-sx] Proposed Charter Clarification
Hal,
Not sure where we are going with this, as I understood it, the chairs
had requested charter language to support the "SecurityPolicy Examples"
document. I think your proposal speaks to that quite clearly.
Clearly, the SecurityPolicy examples could reference WSS or any of the
WS-SX standards.
So I am not sure what this discussion is about...
- prateek
> Well it already covers SP and SC, so that just leaves Trust.
>
>
>
> Hal
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Anthony Nadalin [mailto:drsecure@us.ibm.com]
> *Sent:* Monday, July 02, 2007 12:45 PM
> *To:* Kelvin Lawrence
> *Cc:* Hal Lockhart; ws-sx@lists.oasis-open.org
> *Subject:* Re: [ws-sx] Proposed Charter Clarification
>
>
>
> >A Committee Specification is scheduled for completion by the end of
> calendar 2007
>
> I don't think that this level (CS) is necessary as we don't do this
> for actual interop (that work) documents or for any of the other
> documents in the TC.
>
> At best I think that if we are going to create a examples document, it
> should cover all specifications in the TC not just WS-SecurityPolicy
>
> Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
> Inactive hide details for Kelvin Lawrence/Austin/IBM@IBMUSKelvin
> Lawrence/Austin/IBM@IBMUS
>
> *Kelvin Lawrence/Austin/IBM@IBMUS*
>
> 07/02/2007 10:39 AM
>
>
>
> To
>
>
>
>
> "Hal Lockhart" <hlockhar@bea.com>
>
> cc
>
>
>
>
> ws-sx@lists.oasis-open.org
>
> Subject
>
>
>
>
> Re: [ws-sx] Proposed Charter Clarification
>
>
>
>
>
>
>
> Thanks Hal for posting the text
>
> Chris and I took an action to setup a vote with the OASIS staff once
> Hal posted his text. Before I do that I'd just like to solicit any
> feedback from TC members on Hal's text (which looks fine to me).
>
> Any comments anyone before we setup the ballot?
>
> I'll probably ask Mary to setup the Ballot on Thursday so that gives
> folks a few days to provide any feedback. I will assume that silence
> == agreement to proceed.
>
> Thanks everyone and for those of you with national holidays this week
> - have a safe and enjoyable one.
>
> Cheers
> Kelvin
>
>
> *"Hal Lockhart" <hlockhar@bea.com>*
>
> 07/02/2007 10:13 AM
>
>
>
> To
>
>
>
> <ws-sx@lists.oasis-open.org>
>
> cc
>
>
>
> Subject
>
>
>
> [ws-sx] Proposed Charter Clarification
>
>
>
>
>
>
>
>
> I took an action to propose text for a clarification of the charter.
>
> Section d of the charter currently reads:
>
> -----
> d. Deliverables
>
> The TC has the following set of deliverables:
>
> * A revised Web Services SecureConversation specification and
> associated Schema. A Committee Specification is scheduled for completion
> within 18 months of the first TC meeting.
>
> * A revised Web Services Trust specification with associated Schema
> and WSDL. A Committee Specification is scheduled for completion within
> 18 months of the first TC meeting.
>
> * A revised Web Services SecurityPolicy specification and associated
> Schema. A Committee Specification is scheduled for completion within 18
> months of the first TC meeting.
>
> These specifications will reflect refinements, corrections or material
> technological improvements with respect to the input documents and in
> accordance with this charter. Ratification of the above specifications
> as OASIS standards. Following this, ratification of updated
> specifications as revised OASIS standards to address any errata to fix
> errors and to replace policy references to the WS-Policy W3C
> Recommendation as soon as that Recommendation is available will mark the
> end of the TCs lifecycle.
> ----
>
> I propose adding the following text below the third bullet.
>
> " * A Web Services Security Policy Examples document containing
> narrative descriptions, example policies and example messages for
> message exchanges which are expected to be widely used. A Committee
> Specification is scheduled for completion by the end of calendar 2007."
>
> Hal
>
