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 9032 - WS-Fragment RFC 2119 issues
Summary: WS-Fragment RFC 2119 issues
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Fragment (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-16 20:26 UTC by Gilbert Pilz
Modified: 2010-03-17 10:51 UTC (History)
1 user (show)

See Also:

Attachments

Description Gilbert Pilz 2010-02-16 20:26:23 UTC 
WS-Fragment has a couple of RFC 2119 problems.
Comment 2 Robert Freund 2010-02-16 20:45:04 UTC 
resolved with the proposal in comment #1
additionally 
in Transfer
Transfer: When this operation is used to replace the entire XML representation, any OPTIONAL values (elements or attributes) not specified in the Put request message will be set to a resource-specific default value.
s/will/MUST