Re: basic-only langMatches test

Seaborne, Andy wrote:
> 
> 
> Eric Prud'hommeaux wrote:
>> * Lee Feigenbaum <lee@thefigtrees.net> [2007-08-06 09:01-0400]
>>> ACTION: ericP to write a test showing that langMatches doens't do 
>>> extended matching
>>
>> I checked with i18n-core and it appears that there are no tests that
>> basic matches but extended does not match.
>>   http://www.w3.org/mid/46A62549.7010807@yahoo-inc.com
>>
>> I propose:
>>
>> http://www.w3.org/2001/sw/DataAccess/tests/data-r2/expr-builtin/manifest.ttl 
>>
>>   LangMatches-basic
>>
>> Data:
>> @prefix : <http://example.org/#> .
>>
>> :x :p3 "abc"@de .
>> :x :p4 "abc"@de-DE .
>> :x :p5 "abc"@de-Latn-DE .
>>
>> Query:
>> PREFIX : <http://example.org/#>
>>
>> SELECT *
>> { :x ?p ?v . FILTER langMatches(lang(?v), "de-DE") . }
>>
>> Results:
>> ┌────────────────────────┬───────────┐ 
>>
>> │                       p│          v│
>> ├────────────────────────┼───────────┤ 
>>
>> │<http://example.org/#p4>│"abc"@de-de│
>> └────────────────────────┴───────────┘ 
>>
>>
>> and i pass it...
> 
> ARQ does pass this test.

Glitter does also, but...

> The results do not reflect the syntactic input which has de-DE.  (ARQ 
> actually returns "abc"@de-DE for ?v. -- all matching and equality is 
> done case-insensitively but not by forcing to lower case on data loading.)
> 
> Had it been the JSON results, the results would be different.
> 
> As the point of the test is the FILTER, I suggest changing the results to
> reflect the data and use @de-DE

My test harness thinks I fail it because it does (incorrectly) case 
sensitive comparisons. Could you make this change so that the results 
match the case of the data, Eric?

thanks,
Lee

Received on Friday, 10 August 2007 22:06:18 UTC