W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > November 2010

[Bug 11189] New: MEX: Unable to specify Content when all metadata required

From: <bugzilla@jessica.w3.org>
Date: Mon, 01 Nov 2010 17:24:35 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-11189-2780@http.www.w3.org/Bugs/Public/>

           Summary: MEX: Unable to specify Content when all metadata
           Product: WS-Resource Access
           Version: PR
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: MetadataExchange
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: katy_warr@uk.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org

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

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).

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Monday, 1 November 2010 17:24:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:39 UTC