6594 2009-02-19 00:12:54 +0000 Transfer: Add extensibility points for WS-Transfer wrappers 2009-06-24 00:00:28 +0000 1 1 1 Unclassified WS-Resource Access Transfer FPWD PC Windows XP CLOSED REMIND hasProposal P2 normal --- 6398 6672 6673 1 dug dug bob public-ws-resource-access-notifications oldest_to_newest 23823 0 dug 2009-02-19 00:12:54 +0000 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. 24025 1 bob 2009-03-03 12:27:19 +0000 proposed on 2009-02-28 in http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/0154.html 24298 2 bob 2009-03-17 20:51:00 +0000 Action-52 24322 3 bob 2009-03-19 09:49:12 +0000 Proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0088.html 25125 4 bob 2009-05-13 08:01:11 +0000 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