W3C home > Mailing lists > Public > public-w3process@w3.org > March 2015

RE: warnings on outdated specs/docs

From: Stephen Zilles <szilles@adobe.com>
Date: Thu, 26 Mar 2015 03:53:26 +0000
To: "Michael Champion (MS OPEN TECH)" <Michael.Champion@microsoft.com>, "David Singer" <singer@apple.com>, Steve Faulkner <faulkner.steve@gmail.com>
CC: Janina Sajka <janina@rednote.net>, "ted@w3.org" <ted@w3.org>, "Birkir Gunnarsson" <birkir.gunnarsson@deque.com>, "public-w3process@w3.org" <public-w3process@w3.org>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
Message-ID: <BN1PR0201MB0802B96161CB414024BDE78DAE080@BN1PR0201MB0802.namprd02.prod.outlook.com>
I probably should have been more explicit about the Headers and Footers. Another piece of the mechanism is the ability to set strings based on the values of elements in the HTML. That allows the reporting of things like the creation date of the specification without any edits to the specification. Of course, as noted, one could also add, via CSS,  a warning that the spec is out of date and check the TR page for a more up-to-date version. The TR spec will (as of recently) also have a pointer to a more current editors draft if there is a relevant one.  Still no cost other than a Stylesheet change.

Steve Zilles

> -----Original Message-----
> From: Michael Champion (MS OPEN TECH)
> [mailto:Michael.Champion@microsoft.com]
> Sent: Wednesday, March 25, 2015 4:30 PM
> To: David Singer; Steve Faulkner
> Cc: Stephen Zilles; Janina Sajka; ted@w3.org; Birkir Gunnarsson; public-
> w3process@w3.org; W3C WAI Protocols & Formats
> Subject: 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 Thursday, 26 March 2015 03:54:00 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 26 March 2015 03:54:01 UTC