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


Title: 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
Greg Whitehead <greg.whitehead@hp.com>


To


<ws-sx@lists.oasis-open.org>

cc


Subject


[ws-sx] WS-Policy and WS-Trust

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






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