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 6404 - MEX- define the MEX dialect
Summary: MEX- define the MEX dialect
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords: hasProposal
: 6420 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-14 00:07 UTC by Doug Davis
Modified: 2009-04-21 21:29 UTC (History)
3 users (show)

See Also:


Attachments

Description Doug Davis 2009-01-14 00:07:33 UTC
The MEX specification doesn't really define what metadata is to be 
returned when the Dialect value on the GetMetadata operation is set to "
http://schemas.xmlsoap.org/ws/2004/09/mex".  It just says its "this 
specification".  I've heard rumors that it means "return everything you 
can" while the absence of a dialect on the GetMetadata operation means 
"return whatever you want".  This should be cleared up.

Proposal:
Its not clear to me that we need to have both "everything" and "whatever" 
options.  So my preference is to have the "mex" dialect be the default 
value (ie. when the Dialect isn't present on the GetMetadata operation) 
and have it mean "return everything you can".

If we really do need to have these two distinct (albeit poorly defined) 
options - then, aside from defining what the "mex" dialect means, we 
should also define a new URI to mean "whatever" so that people can be 
explicit in the GetMetadata request and fill in the Dialect value with a 
well defined URI that means "whatever".
Comment 1 Robert Freund 2009-01-14 18:26:57 UTC
*** Bug 6420 has been marked as a duplicate of this bug. ***
Comment 2 Geoff Bullen 2009-01-14 23:18:00 UTC
These are the notes from the MEX interop..

For the GetMetadata operation, if the GetMetadata request were to contain the
MEX dialect what should a provider return?  The specification should clarify
this for the GetMetadata operation.

Proposed Clarification:
       No dialect element = service can choose the Metadata Sections to return 
       Dialect element with MEX dialect = service should return all Metadata
Sections 
       Dialect element with X dialect = service should return all Metadata
Sections with dialect X.
Comment 4 Robert Freund 2009-03-10 19:39:00 UTC
Geoff: No dialect = everything, MEX = those specified in MEX.
Dug proposal: no dialect = mex, mex = everything client can see
Ashok: Counter proposal - MEX = policy, schems, WSDL, ALL = everything you know. Prohibit nothing.
Comment 5 Robert Freund 2009-03-11 19:55:37 UTC
Agreement:
no dialect == everything that the provider considers important with the ability to optimize

dialect="ALL" == all known metadata with ability to optimize

one can specify a dialect list on the getmetaadatarequest
N.B
the dialect "MEX" on a getmetadaterequest shall return no metadata sections