- From: Alex Milowski <alex@milowski.com>
- Date: Fri, 16 Mar 2012 21:39:45 -0700
- To: W3C RDFWA WG <public-rdfa-wg@w3.org>
On Fri, Mar 16, 2012 at 9:30 PM, Manu Sporny <msporny@digitalbazaar.com> wrote: > 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. I see that has been fixed. Thanks! > > > There is a JSON-LD based manifest here, which would probably be better > for you: > > http://rdfa.info/test-suite/manifest.json Sure. That will work just fine. > > >> 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? Running in node.js is an interesting idea but I really want to test it in the browser environment. The implementation provides the RDFa API as well and I'd like to test it all together. Thanks! -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics
Received on Saturday, 17 March 2012 04:40:14 UTC