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 7969 - Fragment: clarify behavior of optional xml
Summary: Fragment: clarify behavior of optional xml
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Fragment (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
Keywords: hasProposal
Depends on:
Reported: 2009-10-19 14:45 UTC by Doug Davis
Modified: 2009-12-09 09:29 UTC (History)
0 users

See Also:


Description Doug Davis 2009-10-19 14:45:19 UTC
WS-Fragment.Put has the following:

    This OPTIONAL element contains the fragment resource representation corresponding to the subset of the resource identified by the wsf:Expression element. 

It is not clear to what should happen to any optional/missing bits of XML
not included within this Value.  For example, are any snippets of XML
currently present left unchanged?  Removed? Defaulted to some resource-specific

We should follow the pattern established in Transfer, where it says:
Any optional values (elements or attributes) not specified in the Put request message will be set to a resource-specific default value. 

Add the following sentence to the end of the paragraph referenced above:

When @Mode is 'Insert' or 'Replace', any optional values (element or attributes)
within this subset that are not specified in the wsf:Value element will be set
to a resource-specific default value.
Comment 1 Robert Freund 2009-11-06 21:56:40 UTC
resolved with proposal