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 8185 - Frag: fragment Put @Mode="Insert" underspecified
Summary: Frag: fragment Put @Mode="Insert" underspecified
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Fragment (show other bugs)
Version: LC
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
Depends on:
Reported: 2009-11-04 18:52 UTC by Gilbert Pilz
Modified: 2010-03-17 11:17 UTC (History)
1 user (show)

See Also:


Description Gilbert Pilz 2009-11-04 18:52:57 UTC
The description of /wst:Put/wsf:Fragment/wsf:Expression@Mode="" reads as follows:

"When the Mode attribute is set to a value of "" the resource representation specified within the Value element MUST be added to the resource representation. If the expression targets a repeated element (maxOccurs > 1), the fragment MUST be added at the end. If the expression targets a non-repeated element (maxOccurrs = 1) that already exists, the resource MUST generate a wst:InvalidRepresentation fault. If the expression targets an existing item of a repeated element, the fragment MUST be added before the existing item."

The above text seems to assume that Value will always target an element, however it is possible for Value to target an attribute or set of attributes, etc. It seems that not all @Modes make sense for all target Values.

Strawman Proposal: In each language section (Sections 5, 6, and 7) clearly identify which targets support which @Modes.
Comment 1 Doug Davis 2010-03-03 02:29:51 UTC
Resolve on 3/2/2010 with proposal in:

with the following modifications:
- Keep a "Remove" mode
- "Replace" mode MUST have a Value element
- to "Replace" add something like:
    If the expression is invalid per the xsd, assuming xsd checking, 
    then it MUST generate an invalidExpression fault
- Rename "Insert" to "Add"