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 8192 - Fragment: when is InvalidFragment fault generated?
Summary: Fragment: when is InvalidFragment fault generated?
Status: CLOSED REMIND
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
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-04 23:09 UTC by Doug Davis
Modified: 2010-03-17 11:23 UTC (History)
0 users

See Also:


Attachments

Description Doug Davis 2009-11-04 23:09:12 UTC
Put says:
--
[Body]/wst:Put/wsf:Fragment
    This element contains an expression that identifies the location of a fragment in the resource and a value for the fragment. If the contents of this element are invalid a wsf:InvalidFragment fault MUST be generated. 
--

Its not clear to me when this fault would be generated.  In the definition
of each subelement we define faults for when the data in them is bad, so
we need to explain when this higher level fault would be generated or
(if never) then just remove it.

As it stands, someone may read this (and the other faults) and think that
either one can be generated - which of course is an interop problem.

Proposal:
remove the last sentence and the InvalidFragment fault.
Comment 2 Robert Freund 2010-01-12 21:40:32 UTC
resolve with proposal in http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Dec/0072.html