Hi Denny, Finn, Sven, et al.,
I was hugely encouraged by your discussion on the Wikidata list RE: importing data, licence chains etc.
My own work on www.linkedheritage.eu<http://www.linkedheritage.eu> is covering the exact same issues you raised (database right, import from multiple source databases, open licenses for reuse) plus a couple more special to commercial sector data providers (risk and benefit of contributing to open data sources; commercial reuse potential of existing open data)...
If anyone is interested in sharing some thoughts just on these topics, especially the technical and organisational feasibility of managing this rights info, on or off list, I would be grateful and happy to share my summaries of the issues.
Best wishes,
Michael Hopwood
Linked Heritage Project Lead
EDItEUR
United House, North Road
London N7 9DP
UK
Tel: +44 20 7503 6418
Mob: +44 7811 591036
Skype: michael.hopwood.editeur
http://www.linkedheritage.org/http://editeur.org/
The information contained in this e-mail is confidential and may be privileged. It is intended for the addressee only. If you are not the intended recipient, please inform the sender and delete this e-mail immediately. The contents of this e-mail must not be disclosed or copied without the sender's consent. We cannot accept any responsibility for viruses, so please scan all attachments. The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the company.
EDItEUR Limited is a company limited by guarantee, registered in England no 2994705. Registered Office:
United House, North Road, London N7 9DP, United Kingdom
Hi,
Is there a test client system that works with the live wikidata.org? I'd
love to test it as early as possible.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
I thought people on this list would want to read
http://infotrope.net/2012/11/30/importing-data-is-hard/ , a list of
difficulties Alex Bayley (Skud, who used to work on Freebase)
experienced when attempting to reuse open data. Perhaps there are
things Wikidata is already doing to eliminate some of these problems for
our end users. In any case, I thought people here would be interested.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Hi,
There are several unanswered questions at
https://www.wikidata.org/wiki/Wikidata_talk:Glossary . Can any developer
please answer them or just edit the Glossary to make the answers obvious?
Thanks!
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
>
> 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.
--
