{"id":1224,"date":"2011-06-12T23:04:33","date_gmt":"2011-06-12T22:04:33","guid":{"rendered":"https:\/\/www.entropywins.wtf\/blog\/?p=1224"},"modified":"2014-03-17T23:05:04","modified_gmt":"2014-03-17T22:05:04","slug":"semantic-mediawiki-update-2","status":"publish","type":"post","link":"https:\/\/www.entropywins.wtf\/blog\/2011\/06\/12\/semantic-mediawiki-update-2\/","title":{"rendered":"Semantic MediaWiki update"},"content":{"rendered":"
\n

It\u2019s been a while since I posted an update on Semantic MediaWiki<\/a> and extensions in general, and my work specifically. This is due to a pile of work that has been done on different components, each of which I\u2019ll address at the point it\u2019s released.\u00a0 In this blog post I\u2019ll provide you with a short overview of what\u201ds (been) going on in the SMW world.<\/p>\n

Semantic MediaWiki 1.6<\/strong><\/a><\/p>\n

\"Semantic<\/a>Almost two years after the latest big release, SMW 1.5, 1.6 comes with many important internal changes focused on performance, stability and extensibility and several new features. Here you have an extract of the release notes<\/a> as they currently are on SVN trunk:<\/p>\n

* Full support for synchronizing RDF stores<\/a> with SMW, and for answering #ask queries based on this data. The communication happens via SPARQL (1.1), and all SPARQL<\/a>-capable stores should be supported.
\n* The Type namespace has been abolished. Builtin types now are displayed by the special page Special:Types, and there are no \u201ccustom types\u201d 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.
\n* Changed the way in which units of measurement work. Type:Number now does not accept any units, and a new type \u201cQuantity\u201d 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.
\n* 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 \u201chas fields\u201d as before.
\n* 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.
\n* Added UNIX-style DSV (Delimiter-separated values) result format.
\n* 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.
\n* Fixed PostGre SQL<\/a> issues with the installation and upgrade code.
\n* Added API module (smwinfo) via which statistics about the semantic data can be obtained.<\/p><\/blockquote>\n

That\u2019s a lot of awesomeness<\/strong> no? \":)\"<\/p>\n

As you can deduce from the above notes, this release is not fully backwards compatibility with SMW 1.5.x, so it\u2019s possible you\u2019ll need to do some migration work. The Validator extension<\/a> is also introduced as an extra dependency, but it will come bundled with SMW, so you\u2019ll only need to care about this when getting the code from SVN.<\/p>\n

SMW 1.6 has been in testing phase for 2 weeks or so now, and most bugs have been taken care of. With some luck, the new version will be released in a week or two \":)\" Do feel free to try out the new version on non-critical wikis and report any issues you might find.<\/p>\n

I already stated that SMW 1.6 is not fully feature compatible with SMW 1.5.x, but it\u2019s also most definitely not compatible with earlier versions code-wise for extensions. This means that quite some SMW extensions released before the development on SMW 1.6 started won\u2019t be compatible anymore, and will require you to also update them to their latest release when upgrading SMW to 1.6 or later. The ones that are in the Semantic Bundle<\/a> are all compatible already on SVN trunk, so you should be able to upgrade everything as soon as SMW 1.6 is released.<\/p>\n

Maps and Semantic Maps 1.0<\/strong><\/p>\n

Another very significant release is the one of Maps<\/a> and Semantic Maps<\/a>. I\u2019ve been working on this version for quite a while; it was branched from version 0.7.3, and it\u2019s the most significant (and awesome<\/strong>) release since the creation of both extensions, hence the bump from 0.7.x to 1.0. These are the changes:<\/p>\n

* Added full Google Maps v3 support and set it as the default mapping service.
\n* Added new geocoder making use of the new GeoNames API.
\n* Added support for the auto-documentation features for parser hooks introduced in Validator 0.4.3.
\n* Added resizeable parameter to all mapping services except OSM.
\n* Removed compatibility with pre MediaWiki 1.17.
\n* Removed overlays parameter for Google Maps v2.
\n* Usage of the Resource Loader for all scripts and stylesheets.
\n* Rewrote all the map JavaScript to jQuery plugins.
\n* Rewrote the way parameters are translated to JavaScript. Now one big PHP object is json_encoded.
\n* Improved KML formatter.
\n* Use of Google Maps geocoding service v3 instead of v2.
\n* Fixed geocoding service overriding based on mapping service (merged in from Maps 0.7.5).
\n* Fixed fatal error occurring when running maintenance\/refreshLinks.php.
\n* Improved default width of maps (merged in from Maps 0.7.5).
\n* Improved map query parameter support in the Special:Ask GUI
\n* Rewrote the map printers to use the SMQueryHandler class.
\n* Added geocoding capability to the OpenLayers form input when having a GeoNames API account.
\n* Added \u2018update map\u2019 button to all form inputs.<\/p><\/blockquote>\n

This release of the mapping extensions requires MediaWiki 1.17 or later and the new SMW 1.6, or later. For people not running an MW older then 1.17 (which currently is still not released, pretty much blocking this release of Maps and SM), the 0.7.x branch still remains supported for a while. It\u2019s currently at 0.7.6, and I plan to release 0.7.7 soonish. Do note that Semantic Maps 0.7.x is NOT compatible with SMW 1.6 or later, it needs SMW 1.5.1 \u2013 1.5.7 alpha.<\/p>\n

Semantic Forms 2.2<\/strong><\/p>\n

Yaron Koren<\/a> has been working on the next big release of the most popular SMW extension, Semantic Forms<\/a>. It brings compatibility with SMW 1.6, and adds several new features, including:<\/p>\n