W3C home > Mailing lists > Public > public-linked-json@w3.org > August 2013

Re: Testing API options

From: Dave Longley <dlongley@digitalbazaar.com>
Date: Sat, 24 Aug 2013 14:02:17 -0400
Message-ID: <5218F529.60000@digitalbazaar.com>
To: public-linked-json@w3.org
On 08/24/2013 06:21 AM, Markus Lanthaler wrote:
> On Friday, August 23, 2013 9:42 PM, Dave Longley wrote:
>> We could provide a function name and then describe what the function
>> must do/provide example code -- which, I assume, is what Gregg was suggesting.
>> We could also define the test function as one that just returns test contexts from an in-memory map.
> That's a great idea. We can define the behavior of the callback and make it
> part of the test runner. We don't even need a name in that case, let's keep
> it as simple as possible. There's one such callback. If it should be used,
> we simply set a "useDocumentLoader" flag to true. The reason for not using
> documentLoader directly is to allow implementations in different programming
> languages. The definition of that callback defines what it returns for a
> number of URLs and what happens for unknown URLs.

+1

-- 
Dave Longley
CTO
Digital Bazaar, Inc.
Received on Saturday, 24 August 2013 18:02:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:39 UTC