Hi Niklas,

This sounds like a great idea. I can't really help, since I would think the majority of the challenge would be in getting SMW queries to recognize different property names as equivalent, so I would think this would require assistance or at least advice from a core SMW developer; but hopefully one of them would be willing to help out.

And this sounds like a reasonable project size. If there's one thing you can learn from going through the list of the Wikimedia Foundation's past projects for GSoC, it's that "too little work for GSoC" is rarely an issue. :)


On Fri, Apr 26, 2013 at 11:57 AM, Niklas Laxström <niklas.laxstrom@gmail.com> wrote:
This is an idea I proposed for GSoC (as in a topic for a student).

Some links:

I've been trying to create a multilingual semantic mediawiki and found
it it is not easy nor possible to do it properly right now. Since I am
a developer of Translate extension I started thinking that these two
could be integrated.

There are multiple parts to reaching the end goal, and I can think of
at least three clearly separate ones:

1) Multilingual forms
Idea: When creating a form, you could choose to create a multilingual
form. In place of field labels there would be {{int:prefix-fieldname}}
calls that would pull translated version. Same for buttons and other
elements. The special page creating the form would also create all
necessary MediaWiki:prefix-fieldname messages having the default text.

This all can be done with plain MediaWiki. But it gets more useful if
integrated with the Translate extension [1]. SemanticForms can
register the group of messages belonging to the form as a message
group in Translate. Then it could be translated like anything else
with the translation editor, have statistics etc. Together with the
UniversalLanguageSelector [2] extension the users will see translation
version of the form in their language if it is available.

Some examples of this done manually: [3][4]

2) Multilingual templates
The same can be done for the templates that display the semantic properties

3) Multilingual properties
The names of properties could also be translated in similar way. The
names are displayed on various places: special pages, query results,
page names etc.

The three things above wont solve the problem of handling multilingual
content as values of semantic properties, but nevertheless it would be
great help to provide multilingual interface to the data.

* Is anyone willing to co-mentor this project with me? We have a
potential student for it.
* Any implementation blockers or flaws in this idea? Is this too much
or too little for GSoC?
* Do you like the idea?

[1] https://www.mediawiki.org/wiki/Help:Extension:Translate
[2] https://www.mediawiki.org/wiki/Extension:UniversalLanguageSelector
[3] http://tieteentermipankki.fi/mediawiki/index.php?title=Lomake:K%C3%A4site&action=edit
[4] http://tieteentermipankki.fi/wiki/Toiminnot:K%C3%A4%C3%A4nn%C3%A4?group=wiki-form-concept


Niklas Laxström

Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
Semediawiki-devel mailing list

WikiWorks · MediaWiki Consulting · http://wikiworks.com