- From: Charles Pritchard <chuck@jumis.com>
- Date: Mon, 5 Sep 2011 13:02:07 -0700
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Marcos Caceres <marcosscaceres@gmail.com>, Jarred Nicholls <jarred@extjs.com>, Philippe Le Hegaret <plh@w3.org>, Doug Schepers <schepers@w3.org>, Anne van Kesteren <annevk@opera.com>, public-webapps <public-webapps@w3.org>, Ian Hickson <ian@hixie.ch>
On Sep 5, 2011, at 11:54 AM, Julian Reschke <julian.reschke@gmx.de> wrote: > On 2011-09-05 16:13, Marcos Caceres wrote: >> ... >> Most don't, in my experience. Specially those from other consortia. They love cling the dated specs and then pretend they are somehow more stable then the Editor's Draft. It's simply nonsense, but the W3C Process document seems to codify this. >>> bleeding edge quite often. It's a game of "who can have the latest and greatest first and the best". >> Not always so. Other industries believe that having a stable reference point will cut down their interop issues (specially for environments where it's difficult to update software). I know, how ridiculous and illogical is that?! >> ... > > Well, dated and immutable specs *indeed* are more stable. If you need "stability" as in "what it says today it will say tomorrow as well" then dated snapshots are the right thing to use. > > I do see that it's a problem when people use outdated specs; but maybe the problem is not the being "dated", but how they are published. As far as I can tell, there's not nearly as much confusion on the IETF side of things, where Internet Drafts actually come with an Expiration Date. > > Best regards, Julian Oh, I'd like seeing an expiration/succession note on WD specs. I don't like the big obtrusive warning labels, but an expires by would be nice, as would an occasionally updated, the latest draft is newer as of date X. > Currently, WD specs just link to "the latest draft is over there".
Received on Monday, 5 September 2011 20:02:34 UTC