RDFIO Versions Save

Similar to the just released RDFIO 3.0.1, this release fixes the Content-type for SPARQL queries containing CONSTRUCT queries, setting that to RDF/XML (the only supported output RDF format at the moment).

Thus, now SPARQL CONSTRUCT queries are possible from external tools like SWI-Prolog SPARQL client:

See commit for more details: a6727bcf73ef39493fc017503c8674cd02a56b89

This release contains a smaller - but potentially important - fix to the SPARQL endpoint included in RDFIO, so that it provides the correct Content-type header for SPARQL result documents by default, allowing to query the SPARQL endpoint in RDFIO with external tools.

See the commit for details: 060c63d10b335f4a6c2df75ef9a86fe451fbe58b

The functionality verified by querying a local Semantic MediaWiki / RDFIO installation from SWI-Prolog, using its bundled SPARQL client. See screenshot:

This release includes some potentially breaking changes due to an overhaul of the permissions setup, as well as (yet another) rename of the configuration parameters (for future-proof consistency and clarity). Thus it bumps the major version indicator.

In more details, the release:

• Adds appropriate permission levels and groups for accessing special pages. See issue #49
  • Permission levels: rdfio-admin, rdfio-import, rdfio-sparql
  • Groups: rdfioadministrator, rdfiocurator (similar to the smwadministrator and smwcurator).
  • rdfioadministrator gets all permissions (rdfio-admin, rdfio-import, rdfio-sparql)
  • rdfiocurator gets content editing permissions (rdfio-import, rdfio-sparql)
• Updates the i18n config to use json files (see issue #47), and also makes sure to use i18n strings everywhere in the special pages.
  • So, now you can contribute translations for your language, by copying the strings in en.json into your language's file! :+1:
• Now supports RDF/XML in the RDF import form (again). See issue #30
• Did some long over-due code clean-up in the wiki title conversion code. See issue #27

Note also the very recently added:

• Support for latest Semantic MediaWiki 2.5 / MediaWiki 1.29 (v.2.4.0)
• Support for blank RDF nodes in import (v.2.3.0)

The vagrant box (automated virtual machine setup) is also updated with RDFIO 3.0.0, providing the absolutely easiest way to try out RDFIO.

This release incorporates changes to make RDFIO support the latest stable SMW version (2.5.x).

It also works well with MediaWiki 1.29, and PHP 7 (7.0.x at least, which is used e.g. on Ubuntu 16.04 LTS).

More fixes are in the pipe, but we wanted to release this asap, so people interested in using it with SMW 2.5 can install it via composer.

This is a small release to fix #31.

(If this is confirmed to fix support for MW 1.29, we might do a larger release later, or do it together with SMW 2.5 support a little later.)

This release adds support for blank nodes in RDF import data, thus closing issue #35 .

In brief, a construct like:

ex:someSubj
   ex:hasInfo [ rdfs:label "someLabel" ; ] .

... will result in a link on the SomeSubj page, to an intermediate page named "Blank node [6-digit id]", on which the rdfs:label fact will be inserted.

Some minor code refactorings to improve code quality were also made.

Note: RDFIO does not yet support later versions than MediaWIki 1.27 and Semantic MediaWiki 2.4.

This is a bugfix release, fiding issue 44, about non-working web forms in MW 1.27 because of wrong action URLs.

This is a minor release, fixing some problems.

Notably, it:

• Introduces better support for non-English language wikis, by using i18n versions of property and category namespaces (see #41)
• Fixes #42 , where the RDF Import form was reliant on a global variable being set, which was meant to be used for remote SPARQL editing only.

This release adds:

• A new commandline script, exportRdf.php, for batch export of RDF data from the wiki, was added.
• Numerous stability improvements and bug fixes! (We [improved our quality store on Code Climate] from 2.6, to 3.75 (of 4.0 max), fixing hundreds of code issues of varying severity).
• More Unit tests added.

This is a very minor fix. See release notes for v2.1.0 instead.