Re: YA proposal to bring /TR/ into the 21st century

Hello Ian,

Monday, October 28, 2013, 3:16:04 PM, you wrote:


> On Oct 28, 2013, at 9:11 AM, Simon Sapin <simon.sapin@exyr.org> wrote:

>> Le 28/10/2013 13:50, Ian Jacobs a écrit :
>>>>> We have that today for all specs. Click on the date on the TR page. Example:
>>>>>  http://www.w3.org/standards/history/css-cascade-3
>>>> 
>>>> That page shows "Retired" at the bottom. What does that mean? I
>>>> can't imagine a spec that went to CR on 2013-10-03 to be retired
>>>> already.
>>> Retired means "The group told us they don't intend to pursue it but
>>> are not yet ready to publish an end Note."
>> 
>> This may be off topic, but I’m not aware of this being the case for
>> css-cascade. The spec is in CR with no known open issue, and implementations
>> are being worked on.

> Thanks, Simon.

> I'm roping in Chris Lilley and Bert Bos to shed light on this, as well as the webmaster.

Simon is correct, this is a current specification which we only just
moved to CR, and it should not be marked as 'retired'.

> If the specification is incorrectly labeled, please send a webreq to correct it. thanks!

OK, but I'm also interested to find out how it got so labelled in the
first place.

Wait. It looks as if "retired" is just a heading for an empty section?
 (If so , I can see how that would be confusing. The section should
 say "none" or something, after the heading.

Looking at
http://www.w3.org/standards/techs/css#w3c_all
there are four specs listed as retired, and css-cascade-3 is not one
of them.





-- 
Best regards,
 Chris                            mailto:chris@w3.org

Received on Monday, 28 October 2013 15:21:18 UTC