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 11189 - MEX: Unable to specify Content when all metadata required
Summary: MEX: Unable to specify Content when all metadata required
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Katy Warr
QA Contact: notifications mailing list for WS Resource Access
Depends on:
Reported: 2010-11-01 17:24 UTC by Katy Warr
Modified: 2011-02-01 18:26 UTC (History)
1 user (show)

See Also:


Description Katy Warr 2010-11-01 17:24:35 UTC
Working on the WS-Mex primer, I noticed it's not possible to say the following with the current syntax:
"Get all the metadata supported by an endpoint, return it inlined"

This is because, in order to say "Get all the metadata" you need to omit the dialect element. 
However, the Dialect elemet is required in order to specify the Content attribute (which indicates that the returned metadata should be inlined).

There are a number of ways we could fix this:

Proposal 1
Move the Content attribute to the GetMetadata
This places the restriction that you can only specify one content type for all metadata.

Proposal 2
Allow the Content attribute on GetMetadata only when no dialects are specified.  

Proposal 3
Allow the Content attribute on GetMetadata.  
When Content Attributes also appear on the Dialect, they override (i.e. the one on the GetMetadata is the default).
Comment 1 Katy Warr 2010-12-07 09:36:30 UTC
Proposed resolution here: