- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 28 Feb 2009 15:41:45 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641 Summary: How to get the XSD Product: WS-Resource Access Version: FPWD Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: All AssignedTo: public-ws-resource-access-notifications@w3.org ReportedBy: dug@us.ibm.com The WSRA specs are a bit inconsistent w.r.t. how people are supposed to get the XSD. mex: provides a pointer to the mex.xsd tra: points people to the ns rddl doc rt : provides a pointer to the rt.xsd evt: points people to the ns rddl doc enu: points people to the ns rddl doc We should be consistent. Telling people to go to the NS rddl doc to get the XSD is a bit misleading. The rddl doc isn't just for the XSD, it will also provide a pointer to the WSDL. In all of the specs when we tell people where to find the WSDL, rather then sending them to the NS rddl doc (which can work - just like it does for the xsd) we provide them with a direct URL to the .wsdl doc. Proposal: Change how we point to the XSD so that it is consistent across all of the specs and consistent with how we refer to the WSDL - for the XSD rather than sending people to the NS rddl doc, provide the actual URL to the XSD. This impacts: transfer, eventing and enumeration. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
Received on Saturday, 28 February 2009 15:41:54 UTC