W3C home > Mailing lists > Public > public-rdf-comments@w3.org > November 2013

[RESOLVED] Re: Turtle "coverage" test suite issues with N-Triples

From: Gregory Williams <greg@evilfunhouse.com>
Date: Tue, 5 Nov 2013 16:37:10 -0800
Cc: public-rdf-comments Comments <public-rdf-comments@w3.org>
Message-Id: <0684F8C7-C9B5-40FC-ADE7-005854EBC45F@evilfunhouse.com>
To: Eric Prud'hommeaux <eric@w3.org>
On Nov 3, 2013, at 10:24 AM, Eric Prud'hommeaux <eric@w3.org> wrote:

> * Gregory Williams <greg@evilfunhouse.com> [2013-03-04 12:41-0500]
>> Gregg alerted to me to the fact that I had overlooked the "coverage" part of the test suite. In trying to run those, I've run into another problem that I wish to comment on.
>> The two eval tests:
>> #literal_with_FORM_FEED
>> #literal_with_BACKSPACE
>> are based on a comparison with N-Triples files that seem to rely on the new, unpublished N-Triples grammar (with the use of escaped forms \b and \f in strings). However, I don't see that this has anything to do with testing of Turtle, and wonder why those files don't use the serialization format from the existing N-Triples grammar (using the \u escaped form). Moreover, even when/if a new N-Triples document is published, I don't believe it's wise to base the new Turtle test suite on the also new N-Triples grammar. The N-Triples files in the Turtle test suite should conform to the existing grammar.
> The traditional N-Triples representation was restored on 4 March. I left that as the resolution, but in the interested of completeness, I should ask if this resolution addressed your comment. If so, please reply with the subject prefixed by "[RESOLVED]".

Resolved, thanks.

Received on Wednesday, 6 November 2013 00:37:32 UTC

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