This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jan/0043.html Once/if we decide on wrappers for the Transfer operations we should make sure they have proper extensibility points - in particular modify Transfer as follows: T-GetResponse: <wst:GetResponse ...> xs:any + </wst:GetResponse> change the xs:any+ to xs:any* T-PutRequest: <wst:Put ...> xs:any + </wst:Put> change the xs:any+ to xs:any* T-PutResponse: <wst:PutResponse ...> xs:any ? </wst:PutResponse> change the xs:any+ to xs:any* T-DeleteResponse: <wst:DeleteResponse ...> xs:any ? </wst:DeleteResponse> change the xs:any? to xs:any* T-CreateResponse: <wst:CreateResponse ...> <wst:ResourceCreated> xs:any ? </wst:CreateResponse> change the xs:any? to xs:any* By making this change it will allow for extension specifications to have more flexibility in what they send/receive.
proposed on 2009-02-28 in http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/0154.html
Action-52
Proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0088.html
resolved with http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Apr/att-0162/I6594-6672-6673-prop-ibm.doc on 2009-05-12