The xpath entry targets version 1.0 of the spec. A change in the way the spec is handled in W3C system makes xpath an explicit alias of a new xpath-10 entry. The overwrite no longer works because it attempts to add a URL to something that should only have an aliasOf link. This prevents automatic updates.
The overwrite is not needed for the xpath-10 entry, as it already has the right URL. This update removes the overwrite as a result.
It could be argued that xpath should rather be an alias of xpath-31. In practice, it's not clear which version xpath should redirect to, and a couple of specs at least expect xpath to mean xpath-10 (DOM, WebDriver, RDF XML Syntax). This is also coherent with the xslt entry.
The
xpathentry targets version 1.0 of the spec. A change in the way the spec is handled in W3C system makesxpathan explicit alias of a newxpath-10entry. The overwrite no longer works because it attempts to add a URL to something that should only have analiasOflink. This prevents automatic updates.The overwrite is not needed for the
xpath-10entry, as it already has the right URL. This update removes the overwrite as a result.It could be argued that
xpathshould rather be an alias ofxpath-31. In practice, it's not clear which versionxpathshould redirect to, and a couple of specs at least expectxpathto meanxpath-10(DOM, WebDriver, RDF XML Syntax). This is also coherent with thexsltentry.