I think it's a much more complex question as data should not only be visible in one state, but in two states - for logged in users it is shown in latest version and to everybody else in only flagged version which means that SMW should start distinguishing between those two versions effectively storing two datasets or a dataset with two states for each triple.

I think as intermediary solution, administrator should be able to pick which one he wants, stable or latest, but to mimic the full functionality, both states of data should be saved (sounds scary).

Thank you,


Sergey Chernyshev

On Fri, Jan 29, 2010 at 1:59 PM, Yaron Koren <yaron57@gmail.com> wrote:

If anyone's not aware of the FlaggedRevs extension, it's a neat extension that allows for certain groups of users to flag specific versions of a page as being "valid". What's shown to regular readers is then the latest valid version, instead of just the latest version, in the same way that software usually has both "latest" and "stable" versions. You can see more here:


It's already in use on several language Wikipedias, including German, Russian and Arabic. It can be used both to guard against vandalism, and, for internal wikis, to mimic a "publish" feature that standard CMS's usually have - that information is not displayed officially until someone has approved it.

It seems to make a lot of sense to me for SMW to support FlaggedRevs, so that if that extension is installed, the semantic data for a page isn't saved on page saves, but instead on page "validations". I don't know how this would be done technically, but I'd imagine it wouldn't be that hard. Any thoughts?


The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
Semediawiki-devel mailing list