W3C home > Mailing lists > Public > public-xsl-wg@w3.org > March 2016

RE: ACTION-2016-02-15-001: ABr to go over problematic links and suggest 302 redirects to Liam/Carine

From: Abel Braaksma <abel.braaksma@xs4all.nl>
Date: Thu, 10 Mar 2016 15:52:11 +0100
To: "'Public XSLWG'" <public-xsl-wg@w3.org>
Message-ID: <02cf01d17adc$6dfd36c0$49f7a440$@xs4all.nl>
I noticed another anomaly, for urls ending with "-3" (not "-30"), they point to the 3.1 version, i.e. https://www.w3.org/TR/xpath-datamodel-3/ and https://www.w3.org/TR/xpath-3/ point to 3.1. Not sure if this is on purpose, but it surprised me.

> -----Original Message-----
> From: Abel Braaksma [mailto:abel.braaksma@xs4all.nl]
> Sent: Thursday, March 10, 2016 2:24 PM
> To: Public XSLWG
> Subject: ACTION-2016-02-15-001: ABr to go over problematic links and
> suggest 302 redirects to Liam/Carine
> 
> As discussed during the F2F in Prague, we noticed that a long-standing wish is
> to harmonize the urls used by the specifications. The main difference is, for
> instance, that XSLT 2.0 is https://www.w3.org/TR/xslt20/ and XSLT 3.0 is
> https://www.w3.org/TR/xslt-30/. Remove the dash in the latter, or add it in
> the former and you will receive a 404 Document Not Found error.
> 
> The suggestion raised at the F2F was for Liam to create aliases or redirects for
> these links, if possible/feasible.
> 
> NOTE 1: Not all links under "Faults" need fixing, I just listed them for
> completeness sake NOTE 2: Essentially, the main thing to fix are the
> differences with dash "-" and without dash NOTE 3: Ideally, I guess one might
> envision the links without version affix would list all TRs, but I doubt W3C
> allows us to change existing, historical TR documents...
> NOTE 4: I also found inconsistencies in dealing with unmanaged versions (1.1,
> 2.1 etc), mentioned below where appropriate
> 
> XSLT 1.0:
> https://www.w3.org/TR/xslt
> and https://www.w3.org/TR/xslt/
> (no redirects between the two)
> 
> Faults:
> https://www.w3.org/TR/xslt10
> https://www.w3.org/TR/xslt-10
> 
> XSLT 1.1
> https://www.w3.org/TR/xslt11
> redirects to https://www.w3.org/TR/xslt11/
> 
> THIS STILL EXISTS...
> 
> I would assume, similar to XSLT 2.1 which shows XSLT 3.0, that it at least
> shows the XSLT 2.0 document, or redirect, or a link to it, but neither is true.
> Should we change this to redirect it to XSLT 2.0? There is, however, a notice,
> but since it is only a Draft, shouldn't we be more rigorous about it?
> 
> (of some interest is the existence of language bindings for IDL and
> ECMAScript in this document, which I believe was nor pursued in later
> versions)
> 
> XSLT 2.0
> https://www.w3.org/TR/xslt20
> redirects to https://www.w3.org/TR/xslt20/
> 
> Faults:
> https://www.w3.org/TR/xslt-20
> 
> XSLT 2.1
> https://www.w3.org/TR/xslt-21/
> THIS LINK DOES NOT REDIRECT AND SHOWS XSLT 3.0
> 
> I suggest we change this to redirect to xslt 3.0 to remove confusion
> 
> XSLT 3.0
> https://www.w3.org/TR/xslt-30
> redirects to https://www.w3.org/TR/xslt-30/
> 
> Faults:
> https://www.w3.org/TR/xslt30
> 
> XPath 1.0
> https://www.w3.org/TR/xpath
> redirects to https://www.w3.org/TR/xpath/
> 
> Faults:
> https://www.w3.org/TR/xpath10
> https://www.w3.org/TR/xpath-10
> 
> XPath 2.0
> https://www.w3.org/TR/xpath20
> redirects to https://www.w3.org/TR/xpath20/
> 
> Faults:
> https://www.w3.org/TR/xpath-20
> 
> XPath 2.1
> https://www.w3.org/TR/xpath-21
> redirects to https://www.w3.org/TR/xpath-21/
> 
> Other than XSLT 2.1, this document does not link to (though Latest Version),
> or redirect to XPath 3.0, nor has it a NOTICE.
> 
> Faults
> https://www.w3.org/TR/xpath21
> 
> XPath 3.0
> https://www.w3.org/TR/xpath-30
> redirects to https://www.w3.org/TR/xpath-30/
> 
> Faults:
> https://www.w3.org/TR/xpath30
> 
> XQuery 1.0
> https://www.w3.org/TR/xquery
> redirects to https://www.w3.org/TR/xquery/
> 
> Faults:
> https://www.w3.org/TR/xquery-10
> https://www.w3.org/TR/xquery10
> 
> XQuery 1.1
> https://www.w3.org/TR/xquery-11
> redirects to https://www.w3.org/TR/xquery-11/
> 
> Same comment as for XSLT 1.1 or XPath 2.1 THIS DOCUMENT DOES NOT LINK
> TO FUTURE VERSIONS AND HAS NO NOTICE
> 
> XQuery 2.0, 2.1
> None found
> 
> XQuery 3.0
> https://www.w3.org/TR/xquery-30
> redirects to https://www.w3.org/TR/xquery-30/
> 
> Faults:
> https://www.w3.org/TR/xquery30
> 
> XQuery 3.1
> https://www.w3.org/TR/xquery-31
> redirects to https://www.w3.org/TR/xquery-31/
> 
> Faults
> https://www.w3.org/TR/xquery31/
> 
> Serialization 1.0
> https://www.w3.org/TR/xslt-xquery-serialization
> Redirects to https://www.w3.org/TR/xslt-xquery-serialization/
> 
> Faults
> https://www.w3.org/TR/xslt-xquery-serialization-10/
> 
> Serialization 1.1
> https://www.w3.org/TR/xslt-xquery-serialization-11
> redirects to https://www.w3.org/TR/xslt-xquery-serialization-11/
> 
> Same comment as for XQuery 1.1
> THIS DOCUMENT DOES NOT LINK TO FUTURE VERSIONS AND HAS NO NOTICE
> 
> Serialization 2.0, 2.1
> None found
> 
> Serialization 3.0
> https://www.w3.org/TR/xslt-xquery-serialization-30
> redirects to https://www.w3.org/TR/xslt-xquery-serialization-30/
> 
> Faults (not really, historically there are no differences as with the other
> specs) https://www.w3.org/TR/xslt-xquery-serialization30/
> 
> XQueryX 1.0
> https://www.w3.org/TR/xqueryx
> redirects to https://www.w3.org/TR/xqueryx/
> 
> Faults
> https://www.w3.org/TR/xqueryx10
> https://www.w3.org/TR/xqueryx-10
> 
> XQueryX 1.1
> https://www.w3.org/TR/xqueryx-11
> redirects to https://www.w3.org/TR/xqueryx-11/
> 
> Same comment as for XQuery 1.1
> THIS DOCUMENT DOES NOT LINK TO FUTURE VERSIONS AND HAS NO NOTICE
> 
> XQueryX 2.0, 2.1
> None found
> 
> XQueryX 3.0
> https://www.w3.org/TR/xqueryx-30
> redirects to https://www.w3.org/TR/xqueryx-30/
> 
> Faults
> https://www.w3.org/TR/xqueryx30/
> 
> XQueryX 3.1
> https://www.w3.org/TR/xqueryx-31
> redirects to https://www.w3.org/TR/xqueryx-31/
> 
> Faults
> https://www.w3.org/TR/xqueryx31/
> 
> XDM 1.0
> https://www.w3.org/TR/xpath-datamodel
> redirects to https://www.w3.org/TR/xpath-datamodel/
> 
> Faults
> https://www.w3.org/TR/xpath-datamodel-10/
> https://www.w3.org/TR/xpath-datamodel10/
> 
> XDM 1.1
> https://www.w3.org/TR/xpath-datamodel-11
> redirects to https://www.w3.org/TR/xpath-datamodel-11/
> 
> Same comment as for XQuery 1.1
> THIS DOCUMENT DOES NOT LINK TO FUTURE VERSIONS AND HAS NO NOTICE
> 
> XDM 2.0, 2.1
> None found
> 
> XDM 3.0
> https://www.w3.org/TR/xpath-datamodel-30
> redirects to https://www.w3.org/TR/xpath-datamodel-30/
> 
> Faults (not really, historically there are no differences as with the other
> specs)
> https://www.w3.org/TR/xpath-datamodel30
> 
> XDM 3.1
> https://www.w3.org/TR/xpath-datamodel-31
> redirects to https://www.w3.org/TR/xpath-datamodel-31/
> 
> Faults (not really, historically there are no differences as with the other
> specs)
> https://www.w3.org/TR/xpath-datamodel31
> 
> 
> Note that for all links, the http version redirects to the https (SSL) version.
> And the "w3.org" redirects to "www.w3.org". I think that is a good thing an
> likely part of W3 policy.
> 
> Cheers,
> Abel
> 
Received on Thursday, 10 March 2016 14:52:45 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 10 March 2016 14:52:45 UTC