W3C home > Mailing lists > Public > public-rdf-comments@w3.org > December 2014

Re: issues with TriG Test Suite

From: Ruben Verborgh <ruben.verborgh@ugent.be>
Date: Sun, 28 Dec 2014 10:53:14 +0100
Cc: public-rdf-comments@w3.org, Markus Lanthaler <markus.lanthaler@gmx.net>
Message-Id: <1D671D4A-83E0-420F-96D2-3643BF96C9CF@ugent.be>
To: Gregg Kellogg <gregg@greggkellogg.net>
Hi Gregg,

> Indeed, I'll send a fixed Manifest to Ivan for him to update

Great, thanks for that!

> Where did you find the <http://www.w3.org/2013/TriGTests/> URL? The RDF 1.1 Test Cases document [1] references <http://www.w3.org/2013/TrigTests/>.

- http://www.w3.org/2013/TrigTests/trig-subm-27.trig contains http://www.w3.org/2013/TriGTests/,
  and so does http://www.w3.org/2013/TrigTests/trig-subm-27.nq 
- The TriG spec (http://www.w3.org/TR/trig/) uses http://www.w3.org/2013/TriGReports/index.html

> Not an official response, but _:s is a Blank Node, not a PName, so it is defined as "_:" followed by PN_CHARS_BASE, which doesn't include ':'. PNAME_LN uses PN_LOCAL, which does include ':'. I believe the test is valid.

Yes, I think you are right. That's good news.

> I can certainly create a new report

Good. I'll fix the blank node issue then, and then I'll have a fully compliant parser.


Received on Sunday, 28 December 2014 09:53:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:59:46 UTC