This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Change the MEX schema to put <wsmxp:MetadataContent> element as a child element of <wsmxp:MetadataExchengeDialect> rather than as a sibling. The rationale is that the the Content element qualifies the Dialect element. If it is a sibling it gives the impression that it can be used independently which does not make sense. The schema is currently as below: <wsmxp:MetadataExchange ...> <wsmxp:MetadataExchangeDialect ...> xs:anyURI </wsmxp:MetadataExchangeDialect> * <wsmxp:MetadataContent ...> xs:anyURI </wsmxp:MetadataContent> * ... </wsmxp:MetadataExchange> This issue suggests that is be changed to: <wsmxp:MetadataExchange ...> <wsmxp:MetadataExchangeDialect value='xs:anyURI'b> <wsmxp:MetadataContent ...> xs:anyURI </wsmxp:MetadataContent> * </wsmxp:MetadataExchangeDialect> * ... </wsmxp:MetadataExchange>
resolved as proposed