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 6413 - Transfer- Move Fragment support from RT to Transfer
Summary: Transfer- Move Fragment support from RT to Transfer
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: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords: hasProposal
Depends on: 6398
Blocks: 6392 6803
  Show dependency treegraph
 
Reported: 2009-01-14 00:15 UTC by Doug Davis
Modified: 2009-08-18 21:14 UTC (History)
1 user (show)

See Also:


Attachments

Description Doug Davis 2009-01-14 00:15:01 UTC
The features of WS-ResourceTransfer are a natural extension of WS-Transfer 
and really should be part of the WS-Transfer spec itself.  The reason for 
the current split is mainly history. Now would be the time to merge the 
fetures of RT into T so that we remove the need for an additional 
specification and reduce the complexity for the implementators and end 
users.

Proposal:
Move the following features from RT in T:
- Fragment support
  Pull would then become:
  <wst:Get Dialect="xs:anyURI"?>
    <wst:Expression ...> xs:any </wst:Expression> *
  </wst:Get>
  Note: if Dialect is not present then wst:Get acts like it does today.
  In other words, the child of wst:Get becomes the full representation of 
the resource.
 
  PullResponse would then becomes:
  <wst:GetResponse>
    <wst:Result ...> xs:any </wst:Result> *
  </wst:GetResponse>

  <wst:Put Dialect="xs:anyURI"?>
    <wst:Fragment Mode="Modify|Insert|Remove">
      <wst:Expression>xs:any</wst:Expression> ?
      <wst:Value ...>xs:any</wst:Value> ?
    </wst:Fragment> +
  </wst:Put>
  Note: if Dialect is not present then wst:Put acts like it does today.
  In other words, the child of wst:Put would becomes the full 
representation of the resource.

  Create would become:
  <wst:Create Dialect="xs:anyURI"?>
    <wst:Fragment>
      <wsmex:Metadata> ... </wsmex:Metadata> ?
      <wst:Expression>xs:any</wst:Expression> ?
      <wst:Value ...>xs:any</wst:Value>
    </wst:Fragment> *
  </wst:Create>
  Note: if Dialect is not present then wst:Put acts like it does today.
  In other words, the child of wst:Create would becomes the full 
representation of the resource.

- Move over the Dialects
- Move all faults associated with these features.

Note: if we do this then some of the other issues I've opened about BP 
compliant will go away because this already adds a wrapper/GED to the 
child of the env:Body.
Comment 3 Robert Freund 2009-03-12 00:31:38 UTC
Action-39 on Katy
Comment 7 Robert Freund 2009-07-08 06:09:25 UTC
2009-07-07 Resolved with the proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0006.html
 amended with the text
"Use of this URI indicates that the contents of the Delete element should be processed as specified by the WS-Fragment [WS-Fragment] specification. to "Use of this URI indicates that the contents of the Delete element MUST be processed as specified by the WS-Fragment [WS-Fragment] specification.
applied as appropriate where the underlying text appears in all four operations.