Hey all,

As most of you probably already know, SMW is approaching it's next major release, version 1.6. This release has been in the making over the past four months and includes contributions by many people. It brings significant improvements to SMWs architecture and introduces many new features. It's not quite yet ready for the actual release, but to give people a chance to test if their setup works with 1.6 and potentially find remaining bugs, a release candidate is now available. If no significant issues are found, 1.6 release will be made in about 2 weeks.

An overview of changes made in this version:

* Full support for synchronizing RDF stores with SMW, and for answering #ask
  queries based on this data. The communication happens via SPARQL (1.1), and
  all SPARQL-capable stores should be supported. The following settings are
  needed in LocalSettings.php:
    $smwgDefaultStore = 'SMWSparqlStore';
    $smwgSparqlDatabase = 'SMWSparqlDatabase';
    // The following should be set to the URLs to reach the store:
    $smwgSparqlQueryEndpoint = 'http://localhost:8080/sparql/';
    $smwgSparqlUpdateEndpoint = 'http://localhost:8080/update/';
    $smwgSparqlDataEndpoint = 'http://localhost:8080/data/'; // can be empty
  The specific support that SMW used to have for the RAP RDF store has been
* The Type namespace has been abolished. Builtin types now are displayed by the
  special page Special:Types, and there are no "custom types" any longer.
  By default, the Type namespace is gone and existing pages in this namespace
  can no longer be accessed. This can be changed by setting
  $smwgHistoricTypeNamespace = true in LocalSettings.php before including SMW.
* Changed the way in which units of measurement work. Type:Number now does not
  accept any units, and a new type "Quantity" is used for numbers with units.
  Units must be declared on the property page (not on the Type page as before),
  and only units that have a declared conversion factor are accepted.
* The declaration of Type:Record properties has changed. Instead of a list of
  datatypes, the declaration now requires a list of properties that are to be
  used for the fields of the record. The declaration is still done with the
  property "has fields" as before. Properties must not be used more than once
  in has_fields, or the order of values will be random.
* Introduced pre-defined builtin properties for every datatype. For example,
  the property String is always of type String and available on all (English)
  wikis. This helps to keep some of the old Tpe:Record declarations valid.
* Changed the way parameters in query printers are specified and handled
  using the Validator extension. This includes improvements to the parameter
  options in the Special:Ask GUI and better error reporting for ask queries.
  These changes are fully backwards compatible, ie the syntax of #ask has not changed.
* Added UNIX-style DSV (Delimiter-separated values) result format.
* Reworked internal data model, cleaning up and re-implementing SMWDataValue and
  all of its subclasses, and introducing new data item classes to handle data.
  The class SMWCompatibilityHelpers provides temporal help for extensions that
  still depend on the old format and APIs.
* Fixed PostgreSQL issues with the installation and upgrade code.
* Added API module (smwinfo) via which statistics about the semantic data can
  be obtained.
* Added second parameter to #info that allows chosing either the info or warning
* Added #smwdoc parser hook that displays a table with parameter documentation for
  a single specified result format.

Many bugfixes and internationalization updates have also been made.

Installation instructions can be found at [0], including a section on updating from SMW 1.5.x [1].

Semantic MediaWiki 1.6 RC1 can be obtained via:
* Direct download, including Validator: http://goo.gl/Le5TW
* svn checkout http://svn.wikimedia.org/svnroot/mediawiki/tags/extensions/SemanticMediaWiki/REL_1_6rc1/

Do note that SMW 1.6 and above requite the Validator extension [2]. If you get the zip release, you don't need to care about this, as it's included,
and will be automatically loaded. If you get the code from SVN, you'll also need to get your own copy of Validator.

In order to provide more regular updates on SMW (and extensions) development, Twitter and indenti.ca accounts been setup:
* https://twitter.com/#!/SemanticMW
* https://identi.ca/smw

Please report any issue you might encounter.

[0] http://semantic-mediawiki.org/wiki/Help:Installation_1.6.0
[1] http://semantic-mediawiki.org/wiki/Help:Installation_1.6.0#Upgrading_SMW_1.5.0_or_higher
[2] https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:Validator


Jeroen De Dauw
Don't panic. Don't be evil.