- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Tue, 3 Sep 2013 21:46:30 -0700
- To: Dave Longley <dlongley@digitalbazaar.com>
- Cc: "public-linked-json@w3.org" <public-linked-json@w3.org>
On Sep 3, 2013, at 7:13 PM, Dave Longley <dlongley@digitalbazaar.com> wrote: > On 09/03/2013 09:16 PM, Gregg Kellogg wrote: >> I've added the remote-doc test manifest, for testing the various requirements around loading remote documents. Note that this does _not_ use the documentLoader option, but specifies default behavior. Note that to run these tests, the do need to be accessed from the server, as it depends on .htaccess to do redirecting and set link headers. >> >> I've also updated the EARL report to include this set of tests. >> >> That completes all of the tests I had thought needed to be added for CR. It would be great if others could run their implementations, and particularly verify the expected behavior of the remote-doc tests. > > I'm currently working on it with jsonld.js. Unfortunately, I'll only be able to do this easily in node.js. The phantomJS (headless browser) can't fetch documents very easily; it would be nice if we could specify something in the manifest that would allow the test application to "mock" fetch documents. Yes, I was thinking that too, however, you end up duplicating a lot of apache config, and you'd need to be sure that a test runner accurately represented it. However, we could figure out a way to express the parameters in the manifest with some additional option properties. Gregg > -- > Dave Longley > CTO > Digital Bazaar, Inc. > >
Received on Wednesday, 4 September 2013 04:47:04 UTC