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 11723 - Fragment: unclear on which fault to throw for InsertAfter/Before w/attrs
Summary: Fragment: unclear on which fault to throw for InsertAfter/Before w/attrs
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Fragment (show other bugs)
Version: CR
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:
Depends on:
Blocks:
 
Reported: 2011-01-10 21:36 UTC by Doug Davis
Modified: 2011-09-13 21:29 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2011-01-10 21:36:16 UTC 
InsertBefore and InsertAfter modes say:
  Note, this Mode MUST NOT be used for attributes. 
but it doesn't say what to do if someone tries.

Proposal:

Add the following text to the end of the above sentence:
... for attributes, and if it is then a wsf:InvalidInput fault MUST
be generated.

Add a new wsf:InvalidInput fault:

[Code]       s:Sender
[Subcode]    wsf:InvalidInput
[Reason]     The specified request contain invalid input.
[Detail]     <<detail about what's wrong with the request>>