RE: warnings on outdated specs/docs

> The harder question is where to find the data (xxxx and yyyy), I suspect

Presumably that would have to be part of the communication between a WG and the Systems Team when a publication request goes in.

Resurrecting that information for everything in /TR could be a challenge, hence my concern that the cost could be non-trivial even if it's obvious that there's significant benefit.

-----Original Message-----
From: David Singer [mailto:singer@apple.com] 
Sent: Wednesday, March 25, 2015 4:19 PM
To: Steve Faulkner
Cc: Stephen Zilles; Michael Champion (MS OPEN TECH); Janina Sajka; ted@w3.org; Birkir Gunnarsson; public-w3process@w3.org; W3C WAI Protocols & Formats
Subject: Re: warnings on outdated specs/docs


> On Mar 25, 2015, at 15:48 , Steve Faulkner <faulkner.steve@gmail.com> wrote:
> 
> 
> On 25 March 2015 at 22:35, Stephen Zilles <szilles@adobe.com> wrote:
> Since the team is allows to make changes to Stylesheets without any other process, Headers and/or Footers could be introduced on historical documents without changing their content, only their Stylesheet.
> 
> Warnings could be added today with existing CSS, no need to wait.

That’s what I meant by a header or footer — a floating hoojum that says “outdated/obsoleted by xxxx on yyyy”

The harder question is where to find the data (xxxx and yyyy), I suspect

David Singer
Manager, Software Standards, Apple Inc.

Received on Wednesday, 25 March 2015 23:30:37 UTC