This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
2009-03-11 Resolved with propose namespace still points to rddl, rddl points to everything, end of spec reference to xsd is a direct uri
in specs
Please make my changes