Hi,
regarding an actual topic in Germany about publication of the
timetable-data of Deutsche Bahn (German national railway company) and
their willingness of a discussion with other Open-Data-Supporters it may
be a good idea of providing an expiration dates for Wikidata-records.
In their open letter to Mr. Kreil [1] they announced that it may cause
problems providing the timetable-data in an open way if e.g. anybody
uses old data.
Marco
[1] http://www.db-vertrieb.com/db_vertrieb/view/service/open_plan_b.shtml
Hi Everyone,
My name is Bernardo and I work as a Business Intelligence Consultant in
Toronto, Canada. I've been reading pretty much everything about WikiData
over the past few days, and I'm really excited about this project! I would
love to participate and collaborate in developing tools to bring data from
external sources, particularly the vast open data sets that are so common
right now.
I have some questions about the project and how can I participate, that you
might be able to help me with:
1) I know the data import is planned for a future phase 2. Do you think it
would be useful to start working on some of that now?
2) I also learned that you guys had a round
table<http://wikidataroundtable.eventbrite.com/>on June 21 about this
topic (wish I could have known about Wikidata and
been there!) but I couldn't find what the outcome of that discussion was.
Is there anywhere where I can find what was discussed there?
3) Is there anyone else on the list working on the subject of how to bring
data in? I have some ideas on the subject, but again, don't know if this is
too early in the project.
Thanks,
Bernardo Najlis
CRM & Business Intelligence Consultant
On Wed, Nov 14, 2012 at 9:50 PM, Marco Fleckinger
<marco.fleckinger(a)wikipedia.at> wrote:
> (...)
> First of all the priority lies on data already present on Wikipedia. Wikidata should not be a data storage for everything structured in the world, so we should first start to transfer data already present on Wikipedia to Wikidata.
> (...)
Wouldn't that kind of transfer be a violation of the CC-BY-SA license
used on Wikipedia, considering it is not compatible[1] with CC0?
Best regards,
Helder
[1] http://wiki.creativecommons.org/Frequently_Asked_Questions#Can_I_combine_tw…
Hi all!
Our demo system needs some love to get the same software versions as
wikidata.org. On Monday the demo repo and client (on
http://wikidata-test.wikimedia.de/) will be unavailable for some time
after 9:00 a.m. GMT / 10 a.m. CET.
Thanks in advance for your patience.
Best, Silke
--
Silke Meyer
Systemadministratorin und Projektassistenz Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. (030) 219 158 260
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt
für Körperschaften I Berlin, Steuernummer 27/681/51985.
>
> Is there any reason not to have links from wikidata/FooBar to
> en.wiki/FooBar and de.wiki/Foo#Bar? It would be a directed edge, but is
> that a problem?
I think this should not be possible becaus the german article cant link to
3 english articels.
> I think there are a lot of articles especially in the german wikipedia
> where you don't have FooBar but Foo#Bar.
>
> LB
>
But if the tag __STATICREDIRECT__ would be support you cold do a workaround
by linking to the germane redirect de:Foobar therefor see Bug 40755
https://bugzilla.wikimedia.org/show_bug.cgi?id=40755 . But i am not shure
if we realy want this kind of linking.
Sk!d
Today a question appeared: what to do if an edit is request that actually
does not change the content (e.g. setting the sitelink of an item to X when
it is already X in the language).
Currently, the API reports an error because the save failed (there is
nothing to save, obviously). If you try the same on MediaWiki core, it
behaves as if everything went well, but doesn't do a save (i.e. the save
does not happen, but the state is the same and thus the software just lets
you proceed as if you have made the edit).
(Actually, the front end is currently too smart to let you do that, but a
similar situation appears when someone else has changed it to the value you
wanted to change it to while you have been viewing the page. Right now we
make a conflict. Is this the desired behavior?)
We should be consistent through all API modules, obviously.
Cheers,
Denny
--
Project director Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. +49-30-219 158 26-0 | http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Hey,
(Mail mainly directed at Denny)
I am wondering to what extend we want to be able to specify the "data type"
of a property on wiki. Right now one can only provide which DataType to use
(where DataTypes are system defined) and nothing else. Do we also want to
be able to specify things such as a list of allowed values, which
ValueValidators to use, ect? I'm asking since Tpt poked me asking about
doing exactly such a thing, which is written down here:
https://www.wikidata.org/wiki/User_talk:Tpt/Support_of_external_ids
I have been working under the assumption we do not want this (at least
initially) so there currently is no place to track such per-property info
internally. If we do want to support this any time soon, I'd like to know
now so we can already facilitate it. (By facilitate it I mean holding it
into account when writing new code or modifying existing stuff, not
actually implementing it.)
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
I suppose Wikidata will be enabled on the Wikipedias when the dependancies of bug 38975 [1] are fixed and the Wikibase Client & Wikibase Lib extensions are installed on the wikipedias.
The dependancies of bug 38975 are bug 38542 [2] and bug 41345 [3]. On bug 38542 db asked if gerrit change 31657 [4] has fixed the problem. At least I can´t repreduce the bug on the demo repo, with the first revision of item Q5786.[5]
[1] https://bugzilla.wikimedia.org/show_bug.cgi?id=38975
[2] https://bugzilla.wikimedia.org/show_bug.cgi?id=38542
[3] https://bugzilla.wikimedia.org/show_bug.cgi?id=41345
[4] https://gerrit.wikimedia.org/r/#/c/31657/
[5] http://wikidata-test-repo.wikimedia.de/w/index.php?title=Q5786&oldid=169681…
----- Original Message -----
From: denny.vrandecic(a)wikimedia.de
Sent: 11/27/12 04:56 PM
To: Discussion list for the Wikidata project.
Subject: Re: [Wikidata-l] Deadlines - phases #1-3
As said, this is correct with regard to deployment. We will not, though,
halt developing phase 2 until phase 1 is fully deployed. So development of
phase 1 is finished, its deployment is not yet. And we cannot promise or
predict when deployment of phase 1 will be completely finished.
Development of phase 2, in the meanwhile, is continuing.
I hope that clears it up.
Cheers,
Denny
I am afraid that phase #1 should be finished in the moment, when
wikidata-interwiki-data are used by other wikis. And this is not yet.
Now Wikidata are some kind of toy, but when these data are not used
and when (almost all) interwiki bots updates only other wikis but not
the wikidata, phase #1 is not finished.
JAnD
> Date: Tue, 27 Nov 2012 03:57:21 -0600
> From: Alexander Jones <happy5214(a)gmail.com>
>
> Jan Ku?era wrote:
>
>> Hi there,
>>
>> can we have ONE place where there will be info about current progress and
>> WHEN will be particular phase really launched? I also would like to see
>> reasons why original deadlines were not met... I guess phase #1 was due to
>> about two months ago?
>>
>> Can it be you already are coding phase #2 while #1 still is not launched?
>> What is the reasoning behind this?
>>
>> I dont want to be pain in the ass but I think more people might be
>> interested in clearly watching the project progress without having to dig
>> for info themselves. One is getting confused and demotivated for future
>> volunteering seeing targets are not met without much reasoning (or at
>> least much publicly readable communication).
>>
>> Thx.
>>
>> Jan
>
> Not a developer, so I can't answer about the deadlines, but phase #1 IS
> already live on wikidata.org
>
> Alexander
Hi,
I wanted to ask how you implement the requirement that critical functions
must also work with JavaScript disabled.[1] The Wikidata-Repository is
allmost only Javascript and it is not possible to add, edit or delete
something without JS.
Btw: I have one notes on the HTML in the Repository [2]:
* there is a stray end-tag div in line 76
<!-- /bodyContent -->
</div>
<!-- /content -->
[1]:
http://www.mediawiki.org/wiki/User_interface_guidelines#JavaScript_and_jQue…
[2]: http://www.wikidata.org/wiki/Q560
LB