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 13151 - MEX schema missing minOccurs='0' on PutMetadataResponse/Metadata
Summary: MEX schema missing minOccurs='0' on PutMetadataResponse/Metadata
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: CR
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 17:46 UTC by Gilbert Pilz
Modified: 2011-09-13 21:29 UTC (History)
1 user (show)

See Also:

Attachments

Description Gilbert Pilz 2011-07-05 17:46:02 UTC 
The spec says:

[Body]/mex:PutMetadataResponse/mex:Metadata
This OPTIONAL element comprises the representation of all the metadata sections of the resource that have been updated during the PutMetadata operation.

but the schema sez:

  <!-- Put Metadata response -->
  <xs:element name='PutMetadataResponse'>
    <xs:complexType>
      <xs:sequence>
        <xs:element ref='tns:Metadata'/>
        <xs:any namespace='##other' processContents='lax' minOccurs='0'
                maxOccurs='unbounded'/>
      </xs:sequence>
      <xs:anyAttribute namespace='##other' processContents='lax'/>
    </xs:complexType>
  </xs:element>
Comment 1 Doug Davis 2011-07-05 17:52:32 UTC 
Proposal:

modify:
        <xs:element ref='tns:Metadata'/>

to:
        <xs:element ref='tns:Metadata' minOccurs='0'/>