It's great to hear another endorsement for this idea! Though I have to disagree again that you "need" to store both the latest and the latest flagged/approved data (or even more versions than that) semantically. Of course, it's always nice to have more data, but I think just having queries be able to return approved data only is a big improvement. This seems like a textbook case of "don't let the perfect be the enemy of the good": being able to store only approved data would be pretty easy to do, while being able to query more than one set of data would require overhauling the whole SMW system.


2010/2/21 Anton Köstlbacher <someone3.0@googlemail.com>
Hi Sergey & Yaron,

I strongly second the idea of supporting FlaggedRevs extension as I'm
using SMW in a collaborative environment to edit data wich is then
exported to third party software. Therefore it is necessary to have
the data available in a specific revised state.

Our very, very basic workaround at the moment: We're saving the
{{REVISIONID}} and {{REVISIONUSER}} (provided by mediawiki) in extra
properties via templates, and allow importing of semantic data into
our third party systems only if the prop:revuserid has one of our
predefined values, so we guarantee that only data wich was last edited
by specific users goes into production systems.

As Sergey said, you would need to store two states of semantic data. I
would go even further and have the semantic data of _all_ revisions of
an article available. Some kind of versioned ontology (see:
http://www.w3.org/TR/owl-ref/#VersionInformation) would become
available. You could then for example query the semantic data of all
reviewed articles (FlaggedRevs) as it was at a specific date/time in
history. The Semantic History extension
(http://www.mediawiki.org/wiki/Extension:SemanticHistory) allows that,
but as I would say in a not so appropriate way and without support for

Regards, someone2.0

> Yaron,
> 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
> --
> Sergey Chernyshev
> http://www.sergeychernyshev.com/
> On Fri, Jan 29, 2010 at 1:59 PM, Yaron Koren <yaron57@gmail.com> wrote:
> > Hi,
> >
> > 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:
> >
> > http://www.mediawiki.org/wiki/Extension:FlaggedRevs
> >
> > 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?
> >
> > -Yaron
> >
> >
> > ------------------------------------------------------------------------------
> > 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.
> > http://p.sf.net/sfu/theplanet-com
> > _______________________________________________
> > Semediawiki-devel mailing list
> > Semediawiki-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
> >
> >

Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
Semediawiki-devel mailing list

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