Re: issue 6401/6661: combined proposal

Hi Li,
  My thinking on this resolves around how the eventing spec has been very 
explicit about the use of the term Notification vs Event.  A Notification 
is the thing that is transmitted - not an Event.  So, therefore WSDL 
describes the Notifications.  The use of the word MAY in there implies 
something pretty strong.  When you say "Events MAY be described in WSDL" - 
that to me it similar to saying that "someone might use WSDL to describe 
Events or they might use something else".  Well, that's not really 
accurate, they never use WSDL to describe Events, they use WSDL to 
describe Notifications.  It worth noting that this was part of the 
proposal that was originally sent in - I didn't change this sentence.

As for the name.... that's too funny.  When I go to: 
http://www.w3.org/TR/wsdl
the HTML title says "Definition" but the title in the doc says 
"Description".  Which wins????
To add more fun, when I scan the doc for "language" to see if it ever uses 
one of those two words before it, only "definition" is used.
Plus, the XML element uses the term "definition".  I'd almost want to say 
that the typo is in the doc title. 
However, bring WSDL 2.0 into the picture and it clearly uses "Description" 
instead - but still uses "definition" in the XML.
But I think you're correct in asking for this change.  I've attached a v4 
version that fixes this.



thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.



"Li, Li (Li)" <lli5@avaya.com> 
Sent by: public-ws-resource-access-request@w3.org
08/27/2009 10:30 AM

To
<public-ws-resource-access@w3.org>
cc

Subject
Re: issue 6401/6661: combined proposal







- Li's edit: "These <add>Events and</add>Notifications MAY be described 
via a Web Services Definition Language..."  is not quite correct.  WSDL 
describes the messages that flow over the wire.  In this case the
messages 
are Notifications not Events. While its true that Events are usually 
someplace in the message, the WSDL may or may not describe them.  For 
example, in a wrapped notification the WSDL has nothing that describes
the 
Events at all - its just an xs:any in a wrapper.  We can discuss this
more 
during the next call.

Doug:

1) It seems to me that your statement "While its true that Events are
usually 
someplace in the message, the WSDL may or may not describe them" is
equivalent to "These Events and Notifications MAY be described 
via a Web Services Definition Language...".

2) I think "Web Services Definition Language" should be "Web Services
Description Language" to match the official WSDL 1.1 spec title.

Thanks.

Li