On 03.04.2013 23:23, Bináris wrote:
> A good question from huwiki:
>
> When I click on an earlier version of the page in the history, will the
> "then-value" of the property be shown or the current value?
> If I read the 2013 version of [[United States of America]] in 2018, will Obama
> be the pre
> when templates (or, in the case of wikidata, properties) get deleted or
> renamed.
> Nobody has come up with a good solution yet.
I think we did discuss a simple, working solution: Saving the value
together with the Wikipedia page.
The major argument against that was: it is a waste of storage
Gregor Hagedorn, 04/04/2013 11:39:
If an editor saves a page with {{#property:population}} the parser
looks up the current value and changes this to:
{{#property:population|current value=2348732}}
and stores this wikitext version in the Wikipedia. The same would
apply to updating, saving {{#pr
This is in my opinion an upstream issue for MediaWiki proper. I do not
think that templates and images from Commons are that different. Take this
image for example:
<
https://en.wikipedia.org/wiki/File:Treaty_of_Accession_2011_Ratification_Map.svg
>
It always reflects the current state of ratific
Denny Vrandečić, 04/04/2013 12:10:
This is in my opinion an upstream issue for MediaWiki proper. I do not
think that templates and images from Commons are that different [...]
...and that's already been rejected (for now):
https://bugzilla.wikimedia.org/show_bug.cgi?id=34778
One way would b
There was a discussion about this months ago and I think that the
conclusion was every property should have a valid_from and a valid_to
field [default = end of the universe].
So you can get snapshots for past versions without any magic.
An example for a hypothetic cashflow-database (dates are
Are you saying every property should have a valid_from and valid_to date or
every claim? If you want that information for queries to be able to show
information about deprecated properties then I don't understand the example
because both queries use the same properties. If it is for claims, then
> don't see what value we'd gain from storing that extra metadata. Every
> scenario I can think of where you care about past states of the database is
> already handled by the compare selected revisions feature.
If that is so simple, can the {{#property:xxx}} call in a wikipedia
simply resolve to
I thought one of the main reasons we are making Wikidata is so that you can
update a value there, and then everywhere it is used will be automatically
updated. If we find a more precise measurement for the depth of an ocean
trench, then I just want to update it on Wikidata, and then every articl
And what are you doing when you want the knowledge of the world from 5
years ago? Isn't this a valid need? To compare what have changed for
example in the measurement of ocean depth?
These snapshots could be a low hanging fruit with valid_from and
valid_to and it is saving disk space compared
We will use qualifiers to tag values with dates for which they are relevant if
there isn't a better place to put the information. We commonly use the example
of historic population values. MediaWiki software saves disk space by delta
encoding edit histories. http://en.wikipedia.org/wiki/Delta_en
I don't think, that the most claims are immutable.
Am Fr 05.04.2013 00:30, schrieb Michael Hale:
We will use qualifiers to tag values with dates for which they are
relevant if there isn't a better place to put the information. We
commonly use the example of historic population values. MediaWiki
I don't have any data to agree or disagree with you about that, but most of the
edits I have made have been for films. Most of those claims are immutable.
Date: Fri, 5 Apr 2013 00:34:21 +0200
From: bene...@zedat.fu-berlin.de
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Page histor
Good Point! The first things I thougt about were populations and other
country, region or city oriented data.
But would two fields that can be set to NULL as default - valid_from ->
the beginning of the time, valid_to -> the end of the universe - hurt
anyone?
Am Fr 05.04.2013 00:37, schrie
Well, I don't know if they would hurt anyone, but I don't think people would go
through the extra effort to set them. Here are our current properties.
http://www.wikidata.org/wiki/Wikidata:List_of_properties We could categorize
them according to mutability, but we'd also need to know how many ti
15 matches
Mail list logo
