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 7968 - Transfer: allow for specialized updates
Summary: Transfer: allow for specialized updates
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: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-10-19 14:32 UTC by Doug Davis
Modified: 2009-12-09 09:41 UTC (History)
1 user (show)

See Also:


Attachments

Description Doug Davis 2009-10-19 14:32:32 UTC
Current draft of Transfer.Put says:

This operation will replace the entire XML representation of the resource. Any optional values (elements or attributes) not specified in the Put request message will be set to a resource-specific default value. 

For default Put this is true - meaning it replaces the entire XML representation.
However, when using an extension spec, like ws-fragment, its possible that
only part of the resource will be updated.  The case that I'm most worried
about is one where each property of a resource has a timestamp associated with
it.  If they use ws-frag then, per the Transfer spec, all of the timestamps
for all properties would need to be touched - which isn't really what's
expected.

Proposal:
Change the above text slightly to allow for extensions to define how they
modify the resource:

Unless otherwise specified by an extension, this operation will replace
the entire XML representation of the resource, and any optional values
(elements or attributes) not specified in the Put request message will be
set to a resource-specific default value.
Comment 1 Robert Freund 2009-10-20 20:50:40 UTC
resolved as proposed