W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2012

Re: Local references in ReSpec

From: David Grogan <dgrogan@google.com>
Date: Fri, 9 Nov 2012 09:05:12 -0800
Message-ID: <CAOZbSt2dA=vvbd3sQ8YPmzziR-yMk35tfCP6BcexDi4jnDVJGA@mail.gmail.com>
To: Giuseppe Pascale <giuseppep@opera.com>
Cc: "spec-prod@w3.org" <spec-prod@w3.org>, Robin Berjon <robin@w3.org>
On Wed, Oct 31, 2012 at 10:03 AM, Giuseppe Pascale <giuseppep@opera.com>wrote:

> Good stuff!
>
> What about adding a line of code using this in the "test specification"[1]
> or even better document it?
>
> BTW is [1] still updated or is it moved somewhere else (or is it simply
> not updated?)
>

I'm also curious to hear the answer to this.


>
> [1] http://dev.w3.org/2009/dap/**ReSpec.js/documentation.html<http://dev.w3.org/2009/dap/ReSpec.js/documentation.html>
>
>
> On Wed, 31 Oct 2012 11:41:47 +0100, Robin Berjon <robin@w3.org> wrote:
>
>  Hi all,
>>
>> just a quick heads up since many people have asked for this: you can now
>> define references specific to your spec in ReSpec (or override the ones in
>> the biblio). Just add a "localBiblio" field to your config, and store as
>> many { FOO: "..." } references as you want in there.
>>
>> Just a couple notes:
>>
>> - Please only use this when you have no alternative, either because
>> sharing the reference makes no sense or because you're in a hurry (and will
>> fix later). Otherwise we'll all lose the benefits of a shared references DB.
>>
>> - Those of you (you know who you are :) who are using pre-processing
>> hacks to implement this, please remove them soon and use this instead. The
>> reason for that is that all of those hacks hook in to internal
>> functionality that *will* be changing. So it will break at some point.
>>
>> Other than that, share and enjoy!
>>
>>
>
> --
> Giuseppe Pascale
> TV & Connected Devices
> Opera Software
>
>
Received on Monday, 12 November 2012 07:22:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 12 November 2012 07:22:16 GMT