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 6406 - MEX: define policy
Summary: MEX: define policy
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: needsAction
Depends on: 6403
Blocks: 6721
  Show dependency tree / graph
 
Reported: 2009-01-14 00:09 UTC by Doug Davis
Modified: 2009-12-09 09:35 UTC (History)
1 user (show)

See Also:

Attachments
per f2f discussions (55.50 KB, application/msword)
2009-09-30 12:18 UTC, Doug Davis 		Details
per f2f discussions (56.00 KB, application/msword)
2009-09-30 12:26 UTC, Doug Davis 		Details

Description Doug Davis 2009-01-14 00:09:31 UTC 
While the WSDL of an endpoint can be used to advertise some aspects of the 
features it supports, it can not be used to indicate all of them.  For 
example, there is no way to list all of the supported MEX Dialects.

Proposal:
Define WS-Policy expression(s) for all of the variables/features of 
WS-MetadataExchange (that can not already be described by its WSDL) so 
that an endpoint can advertise which features/options a client can use. 
Note: this will require we define a new MEX Dialect (not related to the 
'mex' dialect currently defined by the mex spec).
Comment 1 Doug Davis 2009-09-30 12:18:42 UTC 
Created attachment 757 [details]
per f2f discussions

just edited the prefixes for now
Comment 2 Doug Davis 2009-09-30 12:26:02 UTC 
Created attachment 758 [details]
per f2f discussions
Comment 3 Robert Freund 2009-09-30 12:28:20 UTC 
resolved with comment #2