Re: Terminology

Per my action item, I checked the definitions in our Requirements 
document[1], and they are consistent with the definitions that I 
proposed[2], though they are for a different purpose and explained at a 
very different level.  I also verified against the current WSDL 1.2 Core 
document[3] and they are pretty consistent there, with one notable 
exception in the intro:

         "WSDL further considers that an interface represents (some of)
         the behavior of a resource on the World-Wide-Web. A service can
         thus be seen as a collection of endpoints bound to the same resource."

Assuming the word "resource" in the above paragraph is refering to the 
thing identified by the wsdl:@targetResource (if we keep it!), then I think 
that last sentence is incorrect or misleading, because the endpoints are 
not (directly) bound to the resource.  A collection of *services* may be 
bound to the same resource.

Aside from that, I think the explanation in the intro is very good, and I 
don't think it needs as much detail as I was proposing[2].  I suggest that 
the additional detail that I proposed be merged in with the detailed 
"Content Model" descriptions of service, interface, operation, etc. in 
section 2.2 of the core draft[5].


References
1. Requirements: 
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/requirements/ws-desc-reqs.html
2. Proposed terms: 
http://lists.w3.org/Archives/Public/www-ws-desc/2003Jul/0018.html
3. Core draft: 
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.html
4. Intro of core draft: 
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.html#intro_ws
5. Content Model descriptions of core draft: 
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.html#component_model


-- 
David Booth
W3C Fellow / Hewlett-Packard
Telephone: +1.617.253.1273

Received on Thursday, 17 July 2003 10:09:47 UTC