W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > March 2012

Re: Browsing Test Cases on rdfa.info

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sat, 17 Mar 2012 00:30:00 -0400
Message-ID: <4F641348.6090707@digitalbazaar.com>
To: Alex Milowski <alex@milowski.com>
CC: W3C RDFWA WG <public-rdfa-wg@w3.org>
On 03/16/2012 08:32 PM, Alex Milowski wrote:
> I looking to do some ad hoc testing on my RDFa 1.1 browser client
> implementation I've discovered I can't actually access the test case
> documents.  For example, this URL:
> http://rdfa.info/test-suite/test-cases/rdfa1.1/html5/0001.html
> returns a 500.

We had an issue with the test suite today. The search engine crawlers
found hundreds of links that made the test harness hit remote RDFa
processor sites, effectively DDoSing the site. Gregg has since fixed the
problem and the test suite is back to normal operation.

> Testing browser-based clients is proving to be a bit of a challenge
> given the way the test suite is setup.  That is, I'd prefer to have
> the ability to automate testing and that requires being able to
> browse an index (manifest) and load the tests over http.

There is a JSON-LD based manifest here, which would probably be better
for you:


> Ideally, I'd prefer to have the ability to have cross-origin
> requests. That means serving the manifest and test cases up with the
> "Access-Control-Allow-Origin: *" header.

We'll try and CORS-enable the tests for you in the next few days.

Have you thought about running your processor in node.js and providing a
processor URL endpoint?

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: PaySwarm Website for Developers Launched
Received on Saturday, 17 March 2012 04:30:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:30 UTC