Re: [Fwd: Comments on dawg test cases]

Shall I send the material below as a reply to this comments-list comment?

	Andy

Seaborne, Andy wrote:
> To address some of these comments we would need to do some work on the test suite.
> 
> My answers inline.
> 
> 	Andy
> 
> (I can't run the HTML test generator)
> 
> -------- Original Message --------
>  > Subject: Comments on dawg test cases
>  > Date: Mon, 16 Oct 2006 10:12:37 +0200
>  > From: Faisal Alkhateeb
>  > To: public-rdf-dawg-comments@w3.org
> 
>  > Hello,
>  >
>  >    The result of the following query is not clear
>  > http://www.w3.org/2001/sw/DataAccess/tests/#dawg-triple-pattern-005
>  > and i think the result is empty.
>  >
>  > Regarding the sorting of the following query, is not it in the reverse order
>  > (that is descending as it is clear, since E > F > B > A).
>  > http://www.w3.org/2001/sw/DataAccess/tests/#sort-1
>  > And so on for the rest of sorting queries.
> 
> The recorded results are right - it looks like the HTML generator does not 
> respect the "index=" in the results files.
> 
> It would be clearer to SRX files for ordered results - the HTML generator 
> doesn't seem to understand, looking at their use elsewhere.
> 
>  >
>  > The sorting result of the following query is mixed (i.e., neither ascending
>  > nor descending)
>  > http://www.w3.org/2001/sw/DataAccess/tests/#sort-7
> 
> Ditto.
> 
>  > I want to know if it is syntactically possible to use the keyword FILTER as a
>  > namespace prefix as done in the following query:
>  > http://www.w3.org/2001/sw/DataAccess/tests/#keyword-filter-as-a-namespace-
>  > prefix
> 
> It's legal.  Any keyword can be used as a prefix.  This happens in the 
> tokenizing part of the grammar because "FILTER:" is a longer match than "FILTER"
> 
>  >
>  >
>  > In the following queries, we use '(' after WHERE clause instead of '{'.
>  >
>  > http://www.w3.org/2001/sw/DataAccess/tests/#dawg-unsaid-001
>  > http://www.w3.org/2001/sw/DataAccess/tests/#dawg-unsaid-002
> 
> Old syntax.  We should clear all these up.
> 
>  >
>  >
>  > And finally, for the following query, the result is not empty:
>  > http://www.w3.org/2001/sw/DataAccess/tests/#extendedtype-ne-fail
> 
> Open world issue.  != means not known to be different so unless the processor 
> knows about the types, they are not known to be different values so != does 
> not return true.
> 
> 	Andy
> 
>

Received on Monday, 30 October 2006 15:36:45 UTC