- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 05 Nov 2009 16:53:20 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8204
Summary: MEX: metadata in an EPR is misleading
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
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>?
--
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 16:53:29 UTC