Pierre, The report is accurate there were no big improvements since that publications. The key issue is that Virtuoso uses built-in SQL data types whenever possible. Say, there's no xsd:boolean (it's stored as plain integer 1 or 0). SPARQL compiler rejects some queries that are formally correct but looks like errors, not like real queries; say, unbound variable in filter may be reported as an error because in real life it's usually a typo in variable name, not something useful.
So Virtuoso SPARQL does not match W3C recommendation 100%, and it's a decision with its reasons. It is not misunderstanding of the spec; it is not a consequence of a sum of occasional errors and omissions. On the other hand, I believe that SPARQL protocol is implemented according to the W3C spec; any protocol-level deviation from W3C should be treated as an implementation error; it will be fixed ASAP if reported. Best Regards, Ivan Mikhailov, OpenLink Software. On Mon, 2008-02-04 at 16:14 +0100, Pierre De Wilde wrote: > What is the Virtuoso SPARQL conformance with W3C recommandation (*) ? > Is SPARQL Implementation Coverage Report (**) accurate? > > > Pierre > > > (*) http://www.w3.org/TR/rdf-sparql-query/ - 15 January 2008 > (**) http://www.w3.org/2001/sw/DataAccess/tests/implementations > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ Virtuoso-users mailing list > Virtuoso-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtuoso-users
