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 8205 - MEX: can mex appear more than once in an EPR
Summary: MEX: can mex appear more than once in an EPR
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 17:01 UTC by Doug Davis
Modified: 2010-03-17 11:28 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2009-11-05 17:01:45 UTC 
We define wsa:Metadata/mex:Metadata as:
--
<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>

/wsa:EndpointReference/wsa:Metadata/mex:Metadata
    A unique mex:Metadata element appearing as a direct child of the wsa:Metadata endpoint reference element. 
--

What not clear is whether or not there can be more than one
mex:Metadata element under the wsa:Metadata element since the xs:any could
technically include it.  I see no reason to ban it.

Proposal:
Change the ? to a * on mex:Metadata and remove the word "unique".

or if we do want to ban it then we need to add some text being explicit about it.
Comment 1 Doug Davis 2009-12-08 13:48:02 UTC 
To be clear - my proposal is to allow it.
Comment 2 Doug Davis 2010-01-27 18:23:51 UTC 
wu proposes to add: "It may also embed multiple metadata as separate metadata sections under one metadata element"
Comment 3 Robert Freund 2010-01-27 18:24:48 UTC 
resolved as proposed with additional recommendation text