I understand what you were asking for now, but the only situations I'm aware of where the wiki markup is automatically changed before saving is for ~~~~, which is only supposed to be used on talk pages. Enabling a template inclusion to be automatically rewritten during a save has no precedent, so it would require a lot of community support to push the feature through. I think we are all trying to think of the best ways to integrate the workflow of Wikidata and Wikipedia, but Wikidata isn't mature enough yet to know exactly what problems we will run into. I think articles will be updated more frequently than items for the foreseeable future. I think the primary concern is that people will be drawn to do more vandalism on Wikidata because then their changes are visible in more places. That is why Wikidata changes for your watched articles already show up in your watchlist.
> From: [email protected] > Date: Sat, 6 Apr 2013 23:21:41 +0200 > To: [email protected] > Subject: Re: [Wikidata-l] Page history and properties > > On 6 April 2013 23:05, Michael Hale <[email protected]> wrote: > > No, it is not an example of a solution. If you wrote a property inclusion > > like that, and then someone changed the value on Wikidata, and then someone > > made an arbitrary edit somewhere else in the article, then when they save > > the page again the parameter that you have provided makes no sense. > > Michael, this makes no sense to me. I think your scenario makes > perfect sense to everyone: > > Wikipedia page V1, content written:: x {{#property:population}} > Wikipedia page V1, content stored:: x > {{#property:population|value-when-saving-page=309000000}} > property:population on Wikidata changed to 300 > Wikipedia page V2: wikitext x changed to U, property function call > changes on saving to: > U {{#property:population|value-when-saving-page=300}} > > In both cases the value-when-saving-page is correct, transparent and > makes sense. > > But forget it, if no-one likes it. I am not arguing about this. I am > arguing about employing Wikipedia editors for the sake of proofreading > Wikidata changes, while at the same time avoid making them feel > helpless and no longer in charge of "their" pages. > > > The correct solution would be to change the behavior of the renderer to look > > for old versions of templates and data items, > > I agree, as I wrote this is a preferrable solution for that part of > the problem. > > It does not solve the diff-transparency problem, however, which I > consider the more important problem. > > > but Wikidata wouldn't be > > pressured to do this until Wikipedia changed the way it renders templates. > > I am not trying to pressure you or make war on you. > > I prefer to believe we both are on the side of discussing how as many > contributors as possible are motivated to contribute to the growing > commons of Wikipedia and Wikidata, and how the quality of it can best > be upheld. > > Gregor > > _______________________________________________ > Wikidata-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikidata-l
_______________________________________________ Wikidata-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-l
