Hello! We (Onototext) are considering using SMW for the next version of the project www.researchspace.org. This is still in the future, but we may decide to use (some parts of) SMW+. So we'd be interested in this collaboration
Hi Vladimir,
That's Ontotext, right (as in the developer that's involved in Europeana, among other things)? I'd be very interested to keep an eon your work if you decide to go ahead and use either SMW or SMW+.
Anyway, this is actually the wrong venue. To contact the SMW devs (which I'm not), it's probably best to use the mailing list: http://sourceforge.net/mailarchive/forum.php?forum_name=semediawiki-devel. I don't know what the story is with SMW+ these days.
I wouldn't say this is the wrong venue, actually - this is a discussion that's not restricted to just current SMW devs. And on the main page, it says "Please use talk pages for commentary."
Hi Cavila, nice to meet you! Yes, we provide a sparql endpoint for Europeana's EDM data, currently on trial basis.
Hi Yaron! The more I read about SMW the more I think it's the right platform for ResearchSpace.
- The reason I want to explore SMW+ is mostly WYSIWYG: I am told repeatedly that art researchers cannot learn Wikitext nohow noway.
- WikiMedia has started a major dev effort to create a fully-featured and safe visual editor: wikipedia:Wikipedia:VisualEditor. But it still doesn't handle a lot of stuff.
- If we can't revive Halo's WYSIWYG, I guess we can just go with the pattern "form on top, followed by a free-text field, that uses some WYSIWYG editor"
- The client at BM is also fond of pretty-looking UIs (which a MW skin would cover)
- So you may want to emphasize WYSIWYG and skinning options in your brief.
For the sake of adding to the movement, like Vladimir, I'm also particularly interested in WYSIWYG. Right now, I'm stuck at MW 1.16 because it works (the most) reliably with SF 2.4 / FCKEditor. I've played with MW updates and associated SMW extension updates, and they have a lot of cool features that I can use immediately, but unfortunately most of my contributors need the editor. As it stands, I'm once again considering moving to MW 1.17 just to get the current OntoLTS installed... but with 1.20 out and stable, and semantic bundle about to not care about mw 1.17, I'm not crazy about that plan.
As far as I can tell, the WYSIWYG functionality exceeds the planned fuunctionality of the new VisualEditor, particularly in the area of Word import... though obviously roadmaps may change.
I'm probably too new and too busy to contribute, but if I can I will.
Take care. Sal
but with 1.20 out and stable, and semantic bundle about to not care about mw 1.17
Please understand that SMW+ extensions have many interfaces to both MW and SMW. Sure there'll be those that work with MW 1.18+ also, but I think it's important for our present goals to be focused on MW LTS version, with express understanding that all SMW+ extensions must work with the most recent, and all legacy, SMW versions.
I'm not bothered by SemBundle's policy that its deployment is without regard to MW LTS, but I'd be a bit surprised to hear that it'll reach a point that it can't be installed on MW 1.17.
