W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2005

RE: Primer Review

From: Liu, Kevin <kevin.liu@sap.com>
Date: Wed, 6 Jul 2005 13:40:45 -0700
Message-ID: <3470F33FF8ED12498D07F3A9651AA18E2CF651@uspale20.pal.sap.corp>
To: "David Orchard" <dorchard@bea.com>, <www-ws-desc@w3.org>
Thanks for the clarification. 
I like the idea of adding "checkAvailability" to the address URL. The
change is checked in 

Best Regards,



	From: David Orchard [mailto:dorchard@bea.com] 
	Sent: Wednesday, Jul 06, 2005 1:06 PM
	To: Liu, Kevin; www-ws-desc@w3.org
	Subject: RE: Primer Review

	My earlier comment that it should be {checkAvailability} was
wrong.  It should remain as {checkInDate}.  


	I believe that only leaf nodes can be specified.  Section 4.2
IRI style says it has to be a sequence.


	As I read the spec, the example with location="{checkInDate}"
should become a URI option a).  Perhaps the example address attribute
should be updated to add the "checkAvailability" to be a more
descriptive URI.






	From: Liu, Kevin [mailto:kevin.liu@sap.com] 
	Sent: Wednesday, July 06, 2005 12:46 PM
	To: David Orchard; www-ws-desc@w3.org
	Subject: RE: Primer Review


	Hi David,


	While incorporating your suggestions below, I came across a few
more questions. Please see below.

	Best Regards,




		From: www-ws-desc-request@w3.org
[mailto:www-ws-desc-request@w3.org] On Behalf Of David Orchard
		Sent: Thursday, Jun 30, 2005 12:19 PM
		To: www-ws-desc@w3.org
		Subject: Primer Review

		I reviewed the primer for the HTTP binding and
ext/versioning examples.  I did find a few things that need or could use



		As DavidB suggests, the example should be
		[Kevin] I don't quite understand your point here. Do you
mean change the value of whttp:location in example 2-12 to
"{CheckAvailability}"? That doesn't answer the question in the Ed note.


		Let's have a closer look at the definition of


		      <xs:element name="checkAvailability"
		      <xs:complexType name="tCheckAvailability">     
		          <xs:element  name="checkInDate"
		          <xs:element  name="checkOutDate"
		          <xs:element  name="roomType"


		The question is what kind of elements can be assigned to
the whttp:location.  Should it only be "leaf" element such as
"checkInDate"? or can it be an element that is defined using a complex
type, such as CheckAvailability which contains three children elements.
In the following example, if we let whttp:location =
"{CheckAvailability}, then how the serialization works?   


		If we let whttp:location= "{checkInDate}", should
"checkAvailability" be part of the URI? more specifically, should the
URI be a, b, or something else? 


-5&roomType=foo> . 




		Upon further reflection, I'd suggest changing the
section a bit by having the first example use the safe attribute 

		 and then an example that shows methodDefault, rather
than the inverse as is done now.


		I suggest that example 2-14 just shows setting the

		[Kevin]  you mean take whttp:methodDefault="GET" out
from example 2-12, and move it to example 2-14? 


	 Change "The reservation service can accept" to
"The reservation service is changed to a newer version that can accept" s/Mandadtory/Mandatory/g Formatting of example needs indenting, operation
needs closing > Formatting of example needs indenting for
wsoap:action  The example should be


		<xs:element name="ghns2:makeReservation"


		<interface . . .>

		   <operation name="makeReservation">

		       <input messageLabel="In"
element="ghns2:makeReservation" />

Received on Wednesday, 6 July 2005 20:42:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:55 UTC