This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Description: There is a similar issue 6398, which involves putting a wrapper around Transfer messages for both WSI BP compliance and extensibility reasons. It would seem that we should also make GetMetadata request and response messages do the same thing, as currently they are not extensible. In Section 5.2 of WS-MetadataExchange these messages look like: [action] http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata/Request [Body] <mex:GetMetadata > (<mex:Dialect>xs:anyURI</mex:Dialect> (<mex:Identifier>xs:anyURI</mex:Identifier>)? )? </mex:GetMetadata> [action] http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata/Response [Body] <mex:Metadata > </mex:Metadata> Proposal: Add wrappers and extension points as necessary to these messages: [action] http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata/Request [Body] <mex:GetMetadata > (<mex:Dialect>xs:anyURI</mex:Dialect> (<mex:Identifier>xs:anyURI</mex:Identifier>)? )? xs:any * </mex:GetMetadata> [action] http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata/Response [Body] <mex:GetMetadataResponse ..> <mex:Metadata > </mex:Metadata> xs:any * </mex:GetMetadataResponse>
proposal accepted