Update: jena-core, jena-arq, jena-tdb, and jena-sdb now all done.
No changes for jena-jdbc and jena-hadoop - tests pass unchanged.
Fixed to tests in
* jena-security - see next email.
* jena-querybuilder. See below.
When set up for RDF 1.1, the main build passes.
--------------------------
To run in RDF 1.1 mode:
1/ Change jena-core :: JenaRuntime.isRDF11 = true
2/ Change TestSystemSetup (this check the mode to avoid jena2 in RDF 1.1
mode()
3/ In ARQ, under "testing/" there are pairs of results files with
"RDF_10" and "RDF_11" in the file name. Need to install the right version.
4/ mvn clean install
Reloading persistent data that used explicit xsd:string is necessary.
If the data never used explicit xsd:string, it should work (in theory!)
--------------------------
Notes::
:: jena-querybuilder
addWhere(?,?,"three") adds an xsd:string (I didn't expect that)
But in RDF 1.1 that is printed as "three", not "three"^^xsd:string.
Some of the tests are sensitive to the presentation form.
The tests generate a lot of:
WARN setResultVars(): no query pattern
Claude ::
Jena_Commons and Jena_New_Tests were not being run. I've tried to fix
them as best I can but I would be grateful if you'd check them.
On 01/12/14 19:26, Andy Seaborne wrote:
Update: jena-core & jena-arq status
If you want to play, set:
JenaRuntime.isRDF11 = true
Do not run on persistent storage yet.
Data using explicit xsd;string will need to be reloaded.
** jena-arq:
Todo-2/
ARQ sorts deterministically, even where the SPARQL spec does not require
it. The spec requires simple literals before datatype literals. ARQ
then sorts by lexical form then by datatype URI.
The most compatible sort order now active (for RDF 1.1)
Note: Bonus: TransformFilterEquality can now process the string case as
an optimization.
Done.
