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 10785 - MEX: PutMetadata is ambiguous on request with references
Summary: MEX: PutMetadata is ambiguous on request with references
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: LC
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
Depends on:
Reported: 2010-09-27 19:01 UTC by Doug Davis
Modified: 2011-01-11 22:03 UTC (History)
0 users

See Also:


Description Doug Davis 2010-09-27 19:01:44 UTC
In MEX PutMetadata it says:

    If a MetadataSection child contains a MetadataReference or MetadataLocation instead of the metadata in-lined, the endpoint MAY reject the PutMetadata request with an mex:UnsupportedMetadata fault. 

The spec is clear on what to do if the service doesn't like the references,
and to me, this implies that if it does like the references it will place use
those references when someone asks for the metadata.  In other words, 
the service is not supposed to follow those refs, grab the data so that it
can return the metadata inlined in a future getMetadata request. Instead it
should return these refs.  However, this isn't spelled out - as it current
stands someone might interpret the spec to imply that the service is supposed
to follow those refs.

High Level Proposal:
Add text clarifying that a service is not to follow the refs, rather
treat this PutMetadata operation as a way to update the references the
service is storing.
Comment 1 Robert Freund 2010-09-28 19:45:19 UTC
Resolved as proposed