ACTION-2016-03-10-001: our options for what https://www.w3.org/TR/xslt

should result in
Reply-To: 
In-Reply-To: <02cf01d17adc$6dfd36c0$49f7a440$@xs4all.nl>

On Thu, Mar 10, 2016 at 03:52:11PM +0100, Abel Braaksma wrote:
> > 
> > XSLT 1.0:
> > https://www.w3.org/TR/xslt
> > and https://www.w3.org/TR/xslt/
> > (no redirects between the two)

We could change the shortname for this one to xslt-10 
and have a cover page at /TR/xslt explaining the different XSLT
specifications, level of maintenance, and maturity (for 3.0)

> > XSLT 1.1
> > https://www.w3.org/TR/xslt11
> > redirects to https://www.w3.org/TR/xslt11/
> > 
> > THIS STILL EXISTS...


This one already has a statement in the status of the document saying 
it's no longer developed and pointing to xslt20. I think it's fine as is.

> > XSLT 2.0
> > https://www.w3.org/TR/xslt20
> > redirects to https://www.w3.org/TR/xslt20/

There's nothing we can do about the trailing slashes, it's the same for 
almost all the W3C specs.

But, we might have an additional redirect from xslt-20 to xslt20.


> > 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

Fixed already.


> > XSLT 3.0
> > https://www.w3.org/TR/xslt-30
> > redirects to https://www.w3.org/TR/xslt-30/


> > XPath 1.0
> > https://www.w3.org/TR/xpath
> > redirects to https://www.w3.org/TR/xpath/

It is not redirecting but there's a big red box with a statement pointing
to XPath-31. I suppose it's fine.
That's the alternative to the cover page that we could implement for /TR/xslt

I suggest that we have both the cover page (+change of shortname to xslt-10) 
AND a big red box with such a statement. While there was no intent to 
make 1.0 obsolete when 2.0 became a Recommendation, I think it is now 
time to move on.

> > 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.

Good point. I think it could redirect to xpath-30. 
This also applies to:

https://www.w3.org/TR/xquery-11
https://www.w3.org/TR/xslt-xquery-serialization-11
https://www.w3.org/TR/xqueryx-11
https://www.w3.org/TR/xpath-datamodel-11

Maybe Liam can tell more about those.

-- 
Carine Bournez /// W3C Europe

Received on Thursday, 24 March 2016 10:41:40 UTC