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 11625 - Mex: Unclear about deleting deleted metadata
Summary: Mex: Unclear about deleting deleted metadata
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (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: hasProposal
Depends on:
Blocks:
 
Reported: 2010-12-31 13:42 UTC by Doug Davis
Modified: 2011-09-13 21:25 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2010-12-31 13:42:34 UTC 
In the DeleteMetadata section, MEX says:
-----
An endpoint MUST reject a DeleteMetadata request if it is unable to process all of the metadata deletes requested. If the dialect type or identifier specified in one or more of the Dialect elements is unsupported by the endpoint, the endpoint MUST generate a mex:UnsupportedMetadata fault. If the deletion of the specified Metadata will render the endpoint invalid, the endpoint MUST generate an mex:InvalidMetadata fault. 
-----

This is missing the case of deleting metadata that's already been deleted.
IMO this should not be considered an error, rather the service should just
silently ignore the request since the state of the metadata is already in
the client's desired data.

Proposal:
Add to the end of the above text:
-----
Note: an otherwise valid request that refers to metadata that has does not
exist is not considered an error condition. Rather, the service MUST silently ignore that one delete request.
-----