- From: Jean-Jacques Moreau <jean-jacques.moreau@crf.canon.fr>
- Date: Fri, 14 Feb 2003 11:44:16 +0100
- To: Hugo Haas <hugo@w3.org>
- CC: www-ws-arch@w3.org
Hugo, Great work. Some comments. "binding" ========= I think you need to differentiate between: a) the binding of SOAP to HTTP, i.e. how one uses HTTP for transferring a SOAP envelope over the wire (see SOAP Part 2, section 7, SOAP HTTP Binding [1]). b) the WSDL SOAP binding, i.e. how an abstract WSDL message is mapped to SOAP (see WSDL Part 2, section 2, SOAP Binding [2]). Currently, b) is not covered by the glossary. "binding, 1." describes an abstract (WSDL) binding. I suggest you add "binding, 1'." to describe a concrete (WSDL) binding. "endpoint" ========== The word "binding" is ambiguous. I suggest you refer specifically to a "concrete binding" (definition 1'. above). "safe" and/or "idempotent" ========================== I suggest you point to add a link to SOAP 1.2 Part 2, section 4.1.2 Distinguishing Resource Retrievals from other RPCs [3]. "state" ======= Shouldn't there be a definition for a state machine, as used, for example, to describe SOAP bindings? "intermediary" ============== Any reason not to refer to the SOAP definition? "node" ====== Ibid. "requester" =========== Ibid. Why use a term different than "sender"? The same comment probably applies to "provider". "role" ====== Ibid. References ========== The bibref entry for WSD Reqs points to SOAP 1.2 Part 1 (and actually an old version). Jean-Jacques. [1] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part2.html#soapinhttp [2] http://dev.w3.org/cvsweb/~checkout~//2002/ws/desc/wsdl12/wsdl12-bindings.html?content-type=text/html#_soap-b [3] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part2.html#RPCResourceRetrieval Hugo Haas wrote: > All, > > Here is the URL of a new snapshot of the glossary: > > http://dev.w3.org/cvsweb/~checkout~/2002/ws/arch/glossary/wsa-glossary.html?rev=1.32&content-type=text/html&only_with_tag=edcopy_2003021401 > > The main changes are: > - clean ups (redundant & conflicting definitions, uppercase/lowercase > significance). > - improvements in light of the UeB glossary. > - new terms defined. > > A more detailed list of changes can be found in the document change > log[1] and in the CVS log[2]. > > Some work has to be done in order to: > - categorize (or not!) terms properly; see [3] and [4] for details. > - ensure consistency with the architecture document. > > Comments are welcome. Please hold off any comment on "a-priori > knowledge", since I am intending to send an email about "no a-priori > knowledge" and issue 1[5] in the coming week. > > Regards, > > Hugo > > 1. http://dev.w3.org/cvsweb/~checkout~/2002/ws/arch/glossary/wsa-glossary.html?rev=1.32&content-type=text/html&only_with_tag=edcopy_2003021401#changelog > 2. http://dev.w3.org/cvsweb/2002/ws/arch/glossary/wsa-glossary.html#rev1.32 > 3. http://lists.w3.org/Archives/Public/www-ws-arch/2003Feb/0000.html > 4. http://lists.w3.org/Archives/Public/www-ws-arch/2003Feb/0018.html > 5. http://www.w3.org/2002/ws/arch/2/issues/wsa-issues.html#x1
Received on Friday, 14 February 2003 05:45:09 UTC