W3C home > Mailing lists > Public > public-ws-policy@w3.org > November 2006

RE: RE: WSDL 1.1 element identifiers extensions, not defined

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Wed, 29 Nov 2006 11:15:32 -0800
To: David Orchard <dorchard@bea.com>, "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Message-ID: <4D66CCFC0B64BA4BBD79D55F6EBC22571FD0E5D30C@NA-EXMSG-C103.redmond.corp.microsoft.com>

> The refresh is at
>http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/wsdl11elementidentifiers.html?content-type=text/html;%20charset=utf-8

WG members should review this Editor's before our next meeting on Dec 6 so that we can determine if we have consensus to publish an initial WD of this document.

You can raise technical issues against the document using Bugzilla since there is a component for it named "WSDL1.1-Element-Identifiers"

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (613) 225-5445 Fax: (425) 936-7329
mailto:Paul.Cotton@microsoft.com





> -----Original Message-----
> From: public-ws-policy-request@w3.org [mailto:public-ws-policy-
> request@w3.org] On Behalf Of David Orchard
> Sent: November 24, 2006 7:11 PM
> To: David Orchard; public-ws-policy@w3.org
> Subject: RE: WSDL 1.1 element identifiers extensions, not defined
>
>
> I was kind of right... And kind of wrong...
>
> WSDL 2.0 defines 3 extensions, but for the majority of their components
> they don't because they are attributes.  So I took what they did for the
> 3 elements and in a similar style defined that for the soap binding
> only.  The refresh is at
> http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/wsdl11elementidentifi
> ers.html?content-type=text/html;%20charset=utf-8
>
> Note, I'm not sure if we can get away with the element decls on the
> soap:header.
>
> Cheers,
> Dave
>
> > -----Original Message-----
> > From: public-ws-policy-request@w3.org
> > [mailto:public-ws-policy-request@w3.org] On Behalf Of David Orchard
> > Sent: Friday, November 24, 2006 2:05 PM
> > To: public-ws-policy@w3.org
> > Subject: WSDL 1.1 element identifiers extensions, not defined
> >
> >
> > Hi all,
> >
> > Chris asked for an extension in wsdl 1.1, and Asir suggested
> > using the SOAP binding.  At this point, I don't believe there
> > is a WSDL 1.1 or WSDL 2.0 identifier for HTTP, SOAP or MIME
> > bindings.  That's because their Xpointer schemes are not defined.
> >
> > I've asked the WSDL 2.0 group about this, whether I'm missing
> > something or not.  Assuming I'm right, that leaves us a few choices:
> > 1. Do nothing, that is do not support identifers for the
> > HTTP, SOAP or MIME bindings.
> > 2. Create identifers for a subset of the elements defined.  One fairly
> > reasonable set seems to be the SOAP bindings.   This is fairly
> > straightforward to do.  Call this option #2 (soap only) 3.
> > Create identifers for all the elements defined.
> >
> > I can live with either #1 or #2 (soap only) but I think that
> > the http and mime bindings in wsdl 1.1 are almost never used
> > and so is well outside an 80/20 point.
> >
> > Cheers,
> > Dave
> >
> >
Received on Wednesday, 29 November 2006 19:16:08 GMT

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