W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2009

Re: Editing specifications with ReSpec.js

From: Robin Berjon <robin@robineko.com>
Date: Thu, 6 Aug 2009 17:34:06 +0200
Cc: <marcosc@opera.com>, <jmcf@tid.es>, <public-device-apis@w3.org>
Message-Id: <57CA3798-426D-4B62-8084-F416D73B217D@robineko.com>
To: <richard.tibbett@orange-ftgroup.com>
On Aug 6, 2009, at 17:10 , <richard.tibbett@orange-ftgroup.com> wrote:
> Agree with Marcos. Any output of ReSpec.js should be saved statically
> (minus scripting) before publication.

Yup. Contrast for instance:

   Saved snapshot:

The latter passes PubRules, the former will never get close. But I  
know which source I'd rather edit :)

> I agree that Javascript is a good
> authoring system though - quite accessible and debuggable to the  
> widest
> audience.

Agreed. In developing this the availability of FireBug has been  

> This should apply to all types of spec drafts and if that
> output process could be automated (?) then even better. Is this what  
> you
> had in mind Robin?

It's what I've implemented :)

> Summarising the problems: with JS I can't rely on a.) it being enabled
> in the browser, b.) element markup rendering correctly across all
> browsers c.) when saving the spec for offline reading, whether the JS
> files remain attached (w/ HTML5 offline apps - probably. Relying on JS
> being always attached in all other cases - probably not).

After processing is performed, ReSpec removes itself from the  
generated spec, so it leaves no traces.

Robin Berjon
   robineko  setting new standards
Received on Thursday, 6 August 2009 15:35:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:38 UTC