OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-sx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [ws-sx] WS-Policy and WS-Trust


+1. 

It is a big deal. In WS-Policy 1.5, all other namespaces will be treated
as assertions. It will be interoperability problems when policies from
different sources and have different namespaces.  


Symon Chang 
 

-----Original Message-----
From: Marc Goodner [mailto:mgoodner@microsoft.com] 
Sent: Wednesday, March 07, 2007 4:57 PM
To: Ashok Malhotra; Michael McIntosh; Greg Whitehead
Cc: Anthony Nadalin; ws-sx
Subject: RE: [ws-sx] WS-Policy and WS-Trust

Mike already addressed your point.

> It is also clear that,  for any hope of interoperability, message
producer
> and message consumer must use/expect same namespace.

So yes, it is a big deal.

-----Original Message-----
From: Ashok Malhotra [mailto:ashok.malhotra@oracle.com]
Sent: Wednesday, March 07, 2007 4:37 PM
To: Michael McIntosh; Greg Whitehead
Cc: Anthony Nadalin; ws-sx
Subject: RE: [ws-sx] WS-Policy and WS-Trust


Michael, you said:

> We cannot change to a new namespace and in good faith claim to have
> demonstrated interoperability.

This is true if you follow the letter of the law but, if the contents of
the
policies are the same and only the namespace is different, is it really
a big deal?

All the best, Ashok

> -----Original Message-----
> From: Michael McIntosh [mailto:mikemci@us.ibm.com]
> Sent: Wednesday, March 07, 2007 4:23 PM
> To: Greg Whitehead
> Cc: Anthony Nadalin; ws-sx
> Subject: Re: [ws-sx] WS-Policy and WS-Trust
>
> I think its clear that the intended effect of the commented out part
of
> the WS-Trust schema is to match with what the specification describes
in
> text.
> It was commented to avoid an overly strict interpretation of ordering
of
> elements.
> It is also clear that,  for any hope of interoperability, message
producer
> and message consumer must use/expect same namespace.
> We cannot include a vague reference to an undefined WS-Policy
namespace -
> or implementions will not be interoperable.
> We cannot change to a new namespace and in good faith claim to have
> demonstrated interoperability.
> If we decide to change now to the latest WS-Policy draft - what do we
do
> when by the time we get around to last day of next member vote
WS-Policy's
> latest draft has changed again?
> We cannot continue this cycle until WS-Policy completes its work - we
> should put stake in ground now with what we have proven works now and
> revise later when WS-Policy reaches closure.
> Members of this TC were aware of or should have been aware of this
issue
> all along, one no vote by non-participant member on issue that was
> discussed and addressed in the TC should not cause TC dramatically
change
> its plans and schedule for delivery.
>
> Regards,
> Mike
>
> Greg Whitehead <greg.whitehead@hp.com> wrote on 03/07/2007 06:00:32
PM:
>
> > If you look more carefully you?ll notice that the wsp namespace
> > declaration is not used (outside of comments), so it has no impact
> > on the schema.
> >
> > -Greg
> >
> > On 3/7/07 4:39 PM, "Anthony Nadalin" <drsecure@us.ibm.com> wrote:
>
> > I just looked at the schema on the web site and I show it there
> > -----------------
> > Sent from my BlackBerry Handheld.
> >
> >  ----- Original Message -----
> >  From: Greg Whitehead [greg.whitehead@hp.com]
> >  Sent: 03/07/2007 03:36 PM
> >  To: Anthony Nadalin
> >  Cc: ws-sx <ws-sx@lists.oasis-open.org>
> >  Subject: Re: [ws-sx] WS-Policy and WS-Trust
> >
> > As I said before, there is no wsp:Policy element declared in the WS-
> > Trust schema file (the only mention of wsp:Policy is in a comment).
> > The content model of RST and RSTR is xs:any.
> >
> > -Greg
> >
> >
> > On 3/7/07 4:32 PM, "Anthony Nadalin" <drsecure@us.ibm.com> wrote:
>
> > In the namespace declaration to resolve the wsp:Policy element
> > -----------------
> > Sent from my BlackBerry Handheld.
> >
> >  ----- Original Message -----
> >  From: Greg Whitehead [greg.whitehead@hp.com]
> >  Sent: 03/07/2007 03:24 PM
> >  To: Anthony Nadalin
> >  Cc: ws-sx <ws-sx@lists.oasis-open.org>
> >  Subject: Re: [ws-sx] WS-Policy and WS-Trust
> >
> > Perhaps you can point to where it is expressed in the schema. I
> > certainly don?t see it.
> >
> > -Greg
> >
> >
> > On 3/7/07 4:22 PM, "Anthony Nadalin" <drsecure@us.ibm.com> wrote:
>
> > They are expressed in the schema so I'm not following your claim as
> > it has to resolve the scheama use of wsp:Policy
> > -----------------
> > Sent from my BlackBerry Handheld.
> >
> >  ----- Original Message -----
> >  From: Greg Whitehead [greg.whitehead@hp.com]
> >  Sent: 03/07/2007 03:13 PM
> >  To: Anthony Nadalin
> >  Cc: <ws-sx@lists.oasis-open.org>
> >  Subject: Re: [ws-sx] WS-Policy and WS-Trust
> >
> > I?m just saying that the only normative reference to the WS-Policy
> > namespace, or even that wsp:Policy is legal content in an RST, is in
> > the text of the spec.
> >
> > On the call today it was claimed that these dependencies were
> > expressed in the WS-Trust schema and that doesn?t seem to be the
case.
> >
> > -Greg
> >
> > On 3/7/07 1:55 PM, "Anthony Nadalin" <drsecure@us.ibm.com> wrote:
>
> > I don't think that is quite the case, we need a normative reference
> > to resolve wsp:Policy, so where are we to find this, so the binding
> > is normative now as an explicit namespace is used
> >
> > Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
> > [image removed] Greg Whitehead <greg.whitehead@hp.com>
> >
>
> > Greg Whitehead <greg.whitehead@hp.com> 03/07/2007 12:01 PM
> > [image removed]
> > To
> > [image removed]
> > <ws-sx@lists.oasis-open.org>
> > [image removed]
> > cc
> > [image removed]
> > [image removed]
> > Subject
> > [image removed]
> > [ws-sx] WS-Policy and WS-Trust
> > [image removed] [image removed]
> > I just took a look at ws-trust-1.3.xsd and the content model for RST
and
> > RSTR is already <xs:any> (the wsp namespace is declared in the xsd
file,
> but
> > it is ONLY used in comments).
> >
> > So, for what it's worth, the only binding to a particular version of
> > WS-Policy is in the normative text of the spec.
> >
> > -Greg
> >
> >
>
> >
>
> >
>
> >
>

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]