Hi Karima, another thing I noticed is with respect to aggregation functions. Marmotta fails on many of them because it tries to be more precise here, e.g.: - for AVG Marmotta always returns xsd:double, because this is the precision it computes; your tests expect xsd:decimal here - for COUNT, FLOOR, CEIL, Marmotta always returns xsd:integer, because these functions are actually supposed to return xsd:integer; your tests expect the original datatype here (e.g. xsd:decimal) which for me does not really make sense
As far as I can see the SPARQL specification does not provide any details here, do you have any further reference why the testsuite expects different datatypes here? Greetings, Sebastian 2014-11-04 17:16 GMT+01:00 Sebastian Schaffert <[email protected]>: > Hi Karima, > > thanks for putting up your really valuable website. I have fixed many of > the conformity issues for the development snapshot of Marmotta, maybe you > can update to the latest version and run the tests again? > > Additionally, I have some more comments: > - some of your queries are actually illegal, particularly those querying > named graphs where the named graph is given as a file name instead of a > proper URI (e.g. exists02) > - it would be nice to also add performance metrics so we can see how fast > the query evaluation in the different triple stores actually is > - some of the queries use quite sophisticated features (e.g. OWL-DL > entailment); maybe it makes sense to score in a way that users can see how > the triple stores perform for basic SPARQL queries and how they perform for > more sophisticated features? > > Greetings, > > Sebastian >
