Yes, see 1st paragraph of last post. It will have value to devs Since there are now a number of tools that will consume WSDL And generate code prototypes. -----Original Message----- From: Shivaram Mysore [mailto:Shivaram.Mysore@Sun.COM] Sent: Thursday, November 07, 2002 9:59 AM To: www-xkms@w3.org; Blair Dillaway > WSDL is a useful tool for describing the message bindings a WebService > supports. I'd suggest we do a WSDL as the mechanism for specifying > the SOAP binding for an XKMS service. This should be straigthforward > based on code Phill already has and available WSDL generation tools. > > I don't see any particular value in creating a WSDL that specifies the > XKMS messages without incorporating the protocols binding sections. > This adds no value beyond the message schemas we already have. > So, is it appropriate to have a WSDL definition in the protocol bindings document for SOAP - may be as an example as to how a WSDL would like - may be useful info for developers. > As to the IP issue. The orginal WSDL Note was submitted by a number > of companies, some who made royalty free declarations and some who > made RAND declarations. (I am not however, aware of any of these > companies declaring any actual IP requiring licensing and royalty > payments.) WSDL > 1.2 is being developed under the W3C Web Services Activity. That > activity was chartered with a royalty free IP policy. Basically, we > have the same situation as with IP declarations related to SOAP. Use > of SOAP 1.2 and WSDL 1.2 for our SOAP binding requirements provides > reasonable assurance we're not requiring use of IP encumbered > technology. > > Blair > > -----Original Message----- > From: Shivaram Mysore [mailto:Shivaram.Mysore@Sun.COM] > Sent: Thursday, November 07, 2002 7:25 AM > To: www-xkms@w3.org > > > Hi, > > Phill had certain expectations from WSDL for XKMS [1]. Are we or > should someone write a WSDL for XKMS schema or has someone already done that. > If yes, should we put it in the spec or as an additional note? > > There is currently only a reference to WSDL, but, nothing more than > that in our spec. Also, are there any IP releated issues w.r.t. WSDL? > > [1] http://lists.w3.org/Archives/Public/www-xkms/2002Mar/0089.html > [2] http://lists.w3.org/Archives/Public/www-xkms/2002Jul/0024.html > > /Shivaram > ______________________________________________________________________ > __ > ___ > Shivaram H. Mysore <shivaram.mysore@sun.com> > > Software Engineer Co-Chair, W3C's XKMS WG > Java Card Engineering > http://www.w3.org/2001/XKMS > JavaSoft, Sun Microsystems Inc. > > Direct: (408)276-7524 > Fax: (408)276-7608 > > http://java.sun.com/people/shivaram (Internal: http://mysore.sfbay/) > ______________________________________________________________________ > __ > ___ > > > ________________________________________________________________________ ___ Shivaram H. Mysore <shivaram.mysore@sun.com> Software Engineer Co-Chair, W3C's XKMS WG Java Card Engineering http://www.w3.org/2001/XKMS JavaSoft, Sun Microsystems Inc. Direct: (408)276-7524 Fax: (408)276-7608 http://java.sun.com/people/shivaram (Internal: http://mysore.sfbay/) ________________________________________________________________________ ___Received on Thursday, 7 November 2002 13:01:45 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 September 2007 14:30:54 GMT