This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The schema at http://www.w3.org/2011/03/ws-mex/MetadataExchange.xsd is incorrect. The definition of the 'GetMetadata' request element is missing the following line: <xs:attribute name='Content' type='xs:anyURI'/>
GetMetadata is defined as: <mex:GetMetadata Content='xs:any' ? ...> <mex:Dialect Type='mex:QNameSerialization' Identifier='xs:anyURI' ? Content='xs:anyURI' ? .../> * xs:any* </mex:GetMetadata> and the xsd shows: <xs:element name='GetMetadata'> <xs:complexType> <xs:sequence> <xs:element ref='tns:Dialect' minOccurs='0' maxOccurs='unbounded'/> <xs:any namespace='##other' processContents='lax' minOccurs='0' maxOccurs='unbounded'/> </xs:sequence> <xs:attribute name='Content' type='xs:anyURI'/> <xs:anyAttribute namespace='##other' processContents='lax'/> </xs:complexType> </xs:element> And 'Dialect' is defined as: <xs:element name='Dialect'> <xs:complexType> <xs:attribute name='Type' type='tns:QNameSerialization' use='required'/> <xs:attribute name='Identifier' type='xs:anyURI'/> <xs:attribute name='Content' type='xs:anyURI'/> <xs:anyAttribute namespace='##other' processContents='lax'/> </xs:complexType> </xs:element> Isn't that right? Notice the 'Content' attribute in the last bit.
The schema that I downloaded from http://www.w3.org/2011/03/ws-mex/MetadataExchange.xsd does *not* have a @Content attribute defined for the GetMetadata element. It runs from lines 29-37 and looks like this: <xs:element name="GetMetadata"> <xs:complexType> <xs:sequence> <xs:element ref="tns:Dialect" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> </xs:element> Notice the lack of <xs:attribute name='Content' . . .
Its not supposed to. The 'Content' attribute is under the Dialect element - referenced from: <xs:element ref="tns:Dialect" minOccurs="0" maxOccurs="unbounded"/>
Never mind - I see what you mean now - I was looking at the wrong Content attribute. doi!
it appears the the spec has the right info but the xsd is out of sync with it.
Fixed with the sync-up work done over the last weekend.