Re: RDF's relative IRI resolution is ambiguous

Hi Ruben,

It is good to see those 306 tests and we are now happy that we understand 
it better.
The actual results with EYE Autumn15 10052241Z are:
306 tests, 306 passed, 0 failed, 0 errored

With kind regards,
Jos

Jos De Roo | Agfa HealthCare
Senior Researcher | HE/Advanced Clinical Applications Research
T  +32 3444 7618 | F  +32 3 444 8211 | M  +32 494 56 03 95
http://www.agfa.com/w3c/jdroo
http://twitter.com/josderoo

http://www.agfahealthcare.com
http://blog.agfahealthcare.com
R.O.: Septestraat 27, B-2640 Mortsel, Belgium | RLE Antwerp | VAT BE 
0403.003.524 | IBAN Operational Account BE81363012356224 | IBAN Customer 
Account BE20375104592856 | ING Belgium NV, B-1000 Brussels
Click on link to read important disclaimer: 
http://www.agfahealthcare.com/maildisclaimer 



From:   Ruben Verborgh <ruben.verborgh@ugent.be>
To:     RDF Comments <public-rdf-comments@w3.org>
Date:   05/09/2015 16:30
Subject:        Re: RDF's relative IRI resolution is ambiguous



Hi all,

I added a quick verification script to the gist, which tests each case 
independently:
https://gist.github.com/RubenVerborgh/39f0e8d63e33e435371a#file-test-iri-resolution-js


Here are results for parsers I have installed on my machine:

SERD 0.20.0: 210 passed, 96 failed, 0 errored
cwm 1.197: 306 tests, 148 passed, 158 failed, 0 errored
EYE Summer15 0904 2231: 306 tests, 154 passed, 152 failed, 0 errored
Raptor 2.8.0: 306 tests, 295 passed, 11 failed, 0 errored
N3.js (master from git): 306 tests, 306 passed, 0 failed, 0 errored

You can test your own parser by cloning the gist and running
    node test-iri-resolution-js rapper -g
where you replace "rapper -g" with the command needed to parse a file to 
stdout.

Best,

Ruben