- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 05 Nov 2009 17:01:45 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8205 Summary: MEX: can mex appear more than once in an EPR Product: WS-Resource Access Version: FPWD Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: MetadataExchange AssignedTo: public-ws-resource-access-notifications@w3.org ReportedBy: dug@us.ibm.com QAContact: public-ws-resource-access-notifications@w3.org 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. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug.
Received on Thursday, 5 November 2009 17:01:47 UTC