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 6549 - RT - Create focused on resource fragments
Summary: RT - Create focused on resource fragments
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: ResourceTransfer (show other bugs)
Version: FPWD
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Geoff Bullen
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-02-09 16:18 UTC by Geoff Bullen
Modified: 2009-09-30 10:02 UTC (History)
1 user (show)

See Also:


Attachments

Description Geoff Bullen 2009-02-09 16:18:01 UTC
The create operation assumes that the sender wants to pass fragments of the state of the resource to be created and that all dialects will follow this pattern. This seems overly restrictive. A create could be driven by a set of instructions that are very different from the resource representation. For example, I might want a CREATE dialect that takes an EPR to an existing resource and creates a new one just like the existing one.  This should be allowed.

It seems that WSRT currently contradicts itself wrt to Create. 
WS-RT outlines the Create factory model and points out that:
"... the information required to create a resource may *markedly differ* from the initial representation (the value as realized by a subsequent "Get" operation)."  
However, WS-RT goes on to tightly bind the fragments to the "resource representation" and ignores the possibility of different input.
Comment 1 Robert Freund 2009-02-11 07:58:37 UTC
Pending Action-10