W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2005

Re: Negative tests

From: Seaborne, Andy <andy.seaborne@hp.com>
Date: Thu, 15 Dec 2005 12:35:01 +0000
Message-ID: <43A162F5.7050904@hp.com>
To: Steve Harris <S.W.Harris@ecs.soton.ac.uk>
CC: RDF Data Access Working Group <public-rdf-dawg@w3.org>



Steve Harris wrote:
> On Thu, Dec 15, 2005 at 11:52:17 +0000, Andy Seaborne wrote:
> 
>>
>>Steve Harris wrote:
>>
>>>On Thu, Dec 15, 2005 at 11:08:32 +0000, Andy Seaborne wrote:
>>>
>>>
>>>><insert type="request for negative syntax tests"/>please<insert>
>>>
>>>
>>>Ack. I'm thinking of a :sense property which takes values :positive or
>>>:negative, sound OK?
>>>
>>>- Steve
>>>
>>
>>I'd prefer it done as classes because that is how I do it at the moment:
>>
>>http://cvs.sourceforge.net/viewcvs.py/jena/ARQ/Vocabularies/test-manifest-x.n3?rev=1.2&view=markup
>>
>>http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0246
> 
> 
> Sorry, must have missed that. Id really rather it wasn't done in that way
> though, as it limits negative tests to sytax only. Having it as a class is
> OK, but why not a seperate class structure:
> 
> :test a :QueryTest ;
>       a :NegativeTest
> 
 > ?

We can emumerate good/bad as subclasses of QueryTest, SyntaxTest and 
SerializationTest.

I haven't felt a need for negative query tests so far (got an example?) if for 
no reason that it's negativeness is hard to define.  Negative syntax means 
syntax error (parsing failure) and corresponds to MalformedQuery.

Managing to return something from a "bad" query (or bad data) isn't wrong 
because it's out of the scope of SPARQL.  It might be QueryRequestRefused - 
but QueryRequestRefused can occur for temporary reasons as well - it might be 
an incomplete result set (started streaming, query had to abort).

	Andy

> 
> - Steve
> 
Received on Thursday, 15 December 2005 12:36:28 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:25 GMT