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 11850 - MEX needs to clarify "empty" response to GetMetadata
Summary: MEX needs to clarify "empty" response to GetMetadata
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: CR
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
Depends on:
Reported: 2011-01-24 22:50 UTC by Gilbert Pilz
Modified: 2011-09-13 21:31 UTC (History)
1 user (show)

See Also:


Description Gilbert Pilz 2011-01-24 22:50:28 UTC
With respect to the GetMetadata request - given a particular set of metadata (at a service) and a particular set of @Dialect elements and attributes (in a request), it is possible for a GetMetadata request to effectively narrow down the set of returned metadata sections to the empty set - i.e. there is no metadata matching the requester's selection criteria. The spec is silent about what happens in this case.

Proposal - add the following sentence to the end of the description of [Body]/mex:GetMetadataResponse/mex:Metadata:

"Note, in cases where the requester, through the use of @Content and/or mex:Dialect sub-elements in the GetMetadata request, has excluded all the metadata maintained by the service, this element will be empty."
Comment 1 Robert Freund 2011-02-01 20:50:48 UTC
resolved as proposed