W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > May 2008

Re: 2 RDFa SPARQL Test Harness Issues

From: Benjamin Nowack <bnowack@semsol.com>
Date: Mon, 19 May 2008 13:35:48 +0200
To: Manu Sporny <msporny@digitalbazaar.com>, RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>
Cc: Dave Beckett <dave@dajobe.org>, Andy Seaborne <andy.seaborne@hp.com>
Message-ID: <PM-GA.20080519133548.2FF0D.1.1D@semsol.com>

Heya Manu,
thx for the info.

On 17.05.2008 14:53:29, Manu Sporny wrote:
>We currently have two test cases that use UTF-8 characters (TC#60 and
>TC#108). The SPARQL.org and ARC SPARQL engines both die processing
>queries containing multi-byte UTF-8 characters:
UTF-8 queries *should* work fine, ARC just re-uses the capabilities
of it's runtime container (PHP and/or MySQL, depending on the activated
components). I can't get TC60 to display properly on my machine (all I 
get are the 4 ?s), but the characters are stored as multi-byte string 
and the query is run against an UTF-8 literal, too (and passes here).

TC108 renders fine here, but the query fails. This could be due to 
the linebreaks in the HTML not being considered equal to the "\n" in the
query, though. ARC also (deliberately, for practical reasons) auto-trims
outer whitespace in literals, i.e. RDFa tests for leading or trailing 
WS will always fail in ARC.

My general suggestion would be to separate whitespace tests from pure
UTF-8 tests. This could simplify debugging and also the creation of 
feature comparisons for the different RDFa implementations.


>-- manu
>Manu Sporny
>President/CEO - Digital Bazaar, Inc.
>blog: DB Launches Medical Record Sales Service with Shepherd Medical
Received on Monday, 19 May 2008 11:36:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:28 UTC