This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6594 - Transfer: Add extensibility points for WS-Transfer wrappers
Summary: Transfer: Add extensibility points for WS-Transfer wrappers
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on: 6398 6672 6673
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-19 00:12 UTC by Doug Davis
Modified: 2009-06-24 00:00 UTC (History)
1 user (show)

See Also:


Attachments

Description Doug Davis 2009-02-19 00:12:54 UTC
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.
Comment 1 Robert Freund 2009-03-03 12:27:19 UTC
proposed on 2009-02-28 in http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/0154.html
Comment 2 Robert Freund 2009-03-17 20:51:00 UTC
Action-52