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 8204 - MEX: metadata in an EPR is misleading
Summary: MEX: metadata in an EPR is misleading
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:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-05 16:53 UTC by Doug Davis
Modified: 2009-12-09 09:34 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2009-11-05 16:53:20 UTC 
In section 7 where we define how mex goes into an EPR we have this outline:
<wsa:EndpointReference ...>
    <wsa:Address>xs:anyURI</wsa:Address>
    <wsa:ReferenceParameters> xs:any* lt;/wsa:ReferenceParameters> ?
    <wsa:Metadata>
        <mex:Metadata> xs:any* </mex:Metadata>?
        xs:any*
    </wsa:Metadata> ?
    xs:any*
</wsa:EndpointReference>

notice the xs:any* in the <mex:Metadata> element.
This is a bit misleading because its not really an xs:any under mex:Metadata.
I'd like to change it to use the form we use in 6.2:

  <mex:GetMetadataResponse>
    <mex:Metadata ...> ...  </mex:Metadata>
    xs:any*
  </mex:GetMetadataResponse>

Proposal:
modify:
        <mex:Metadata> xs:any* </mex:Metadata>?
to be:
        <mex:Metadata ...> ...  </mex:Metadata>?