W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2012

Changes/Dates usability suggestion on specs, was Re: [proximity] The initial state of the proximity sensor (was: Tests and ref imp)

From: Marcos Caceres <w3c@marcosc.com>
Date: Wed, 23 May 2012 11:07:20 +0100
To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <CDF7FF3A56E04907A5886E0251F8A07F@marcosc.com>


On Wednesday, 23 May 2012 at 08:34, Anssi Kostiainen wrote:

> (To make sure on-one gets confused, I'll have to mention the above draft is an old one despite ReSpec.js showing the current date.)

I was going to bring this up because it's causing me a bit of confusion - it means I need to be checking the HG repo also for changes (which is ok), but it would be really nice if the spec linked to the repo.  

About the date problem, in other working groups we commonly have:

  Overview.src.html (unprocessed) and Overview.html (processed) online.  

That avoid the problem of having the wrong date show up…. could also determine the last modified date from a HTTP head request, though I've tried doing that before and ran into cross browser issues.  

Another solution would be to XHR the list of changes from HG directly into the document (or just display the HG repo page relating to the spec in an iframe under a section Change Log - that would be trivial, and super useful.)

--  
Marcos Caceres
http://datadriven.com.au
Received on Wednesday, 23 May 2012 10:08:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 23 May 2012 10:08:03 GMT