Yes indeed, 2015 looks very promising, not least for Wikidata.
In London we are getting of the mark quickly with London Wikidata Meetup 2
<https://meta.wikimedia.org/wiki/Meetup/London/Wikidata2> on Wednesay 7th
Jan. (If any of you are around in in London, it would be great to see you).
These meetups run alongside more generic meetups and grew out of a training
session Magnus kindly gave us last October
will be our second meet up and we have also discussed having a training
event/meet up in Manchester later on in 2015.
We also have a list for our Wikidata working group
<http://lists.wikimedia.org.uk/mailman/listinfo/wikidata-l>, which having
looked at the archive, does not have much overlap with this or the tech
list. The purpose of the list is to bring together people around events and
community building in and around the UK (which actually means we want to
have a good relationship with Wikimedians in Ireland in particular).
So having read Lydia's blog
it seemed useful to share on this list our activities. For myself, I get
lost quite early on with much of the technical discussion, but I am keen to
see ways developed which will help newcomers to projects like Wikidata get
their heads around everything which is going on.
So I hope this has helper everyone understand what we are setting out to do
with these meetups in London.
all the best
Volunteer Support Organiser,
Address: 56-64 Leonard St,
London EC2A 4LT
Phone:020 7065 0990
*Mobile: *07840 455 746
Wikimedia UK is a Company Limited by Guarantee registered in England and
Wales, Registered No. 6741827. Registered Charity No.1144513. Registered
Office 4th Floor, Development House, 56-64 Leonard Street, London EC2A 4LT.
United Kingdom. Wikimedia UK is the UK chapter of a global Wikimedia
movement. The Wikimedia projects are run by the Wikimedia Foundation (who
operate Wikipedia, amongst other projects).
Visit http://www.wikimedia.org.uk/ and @wikimediauk
Hey folks :)
I'll be doing another office hour for Wikidata on IRC next Friday at
18:00 UTC. It'll happen in #wikimedia-office on Freenode IRC.
Everyone is welcome for discussions and question answering. Logs will
be posted afterwards.
For your timezone see
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
I am working on cloud computing platform (http://conceptjs.com) that
lets folks build applications the Wiki way, where you can read and edit
the code behind any page with a browser. We want democratize
web-application development the way Wikidata is democratizing data.
We have some example apps like the Mammal Explorer
<http://bit.ly/1BbALz8>, World Fact Book <http://bit.ly/1qvBffm> and
Periodic Table <http://bit.ly/1yv4MFn> which integrate with various
open-data sources including Wikidata. We want to build more such apps
with real user requirements.
If anyone in this group is looking for tools that will help you
validate, summarize or update information in Wikidata, we are happy to
collaborate with you to build them. All our work will be CC0 licensed
and hosted for free. Please let me know at sridhar(a)lambdazen.com.
Freebase originally had 2 modes. View and Edit. And then changed to only
an Edit mode (where some properties were no longer hidden)
Wikidata as far as I know only has Edit (All properties are shown in the UI)
Derived properties might work, but only in a "View mode". Or only if
Derived properties where specially marked visually as such. There should
always be an option to have the UI show all properties.
Freebase's Metaschema is much like the idea of derived properties. Where
some rules govern the population or assumption of a property value.
Details here: https://developers.google.com/freebase/v1/search-metaschema
On Wed, Jan 14, 2015 at 8:37 AM, apohllo(a)o2.pl <apohllo(a)o2.pl> wrote:
> Referring to the NIST classification of semantic relations, general
> affiliation is a different relation than part-of. That's why conflating
> them is not the best idea.
> But this is a minor issue in that context. I am wondering if there is any
> list of "properties for beginners", that should not be treated as a real
> part of the knowledge base?
> As I wrote earlier there are two problems with ambiguous entities:
> 1. indicating super-properties
> 2. inferences drawn with such properties
> I don't question the usefulness of properties such as "country", i.e.
> searching all cities in one country or searching all bands that originated
> in another country.
> I am just concerned with the duplication and as a result coherence of the
> data that is in Wikidata. One of the basic principles of DB design is that
> data should be stored in only one place. That's why DB normal forms where
> developed. Even more - that's why Wikidata was extracted from individual
> Wikipedias in the first place!
> In the case of Dublin, country and Ireland. At present we have two
> distinct claims expressing the same fact, that one day may become
> Being constructive - maybe it's the time to consider derived properties?
> Thus claims like "Dublin country: Ireland" would be visible in the UI, but
> would be computed based on the contents of the knowledge base. The same
> applies to age and many other properties, that are useful for 'beginners',
> but can be computed from the other properties and rules expressed in the
Freebase has mutexes that store incompatible type information.
For instance, in Wikidata I noticed on the U2 band topic, that they have
P17 Country - sovereign state of this item.
P740 Location of formation - location where a group or organization was
In Freebase we have basically that P740, "Place where musical career
began".but not a Country property with that sort of definition.
But having "sovereign state of this item" on an instance of band, seems
weird, and perhaps should not be allowed , or incompatible. Unless the P17
Country property had an expanded definition of "sovereign state (or
originating sovereign state) of this item"
1. How does Wikidata want to handle Property / Statement rule enforcement
and Freebase's incompatible types ?
2. How does Wikidata want to handle locking down Property descriptions
(Freebase uses Permissions and Owners), where the complete meaning of
something being changed might cause severe wrongful polluted data ?
Does anybody know the current documentation of the precision of the
globe coordinate datatype? This precision was introduced after the
original datamodel discussions.
I used to believe that it was a rough, informal indication of a
precision based on an (easy-to-process but necessarily rather
inaccurate) bounding box. After all, the UI only allows for a small
number of predefined settings.
However, the data contains many values with precision value "null". What
is this supposed to mean and how should consumers treat it? The
precision of a measure cannot be "0" (and in any case, 0 is none of the
supported constants in the UI).
In addition, the data also contains some seemingly arbitrary numbers as
precision, such as a precision of 10.372851422071 degrees for the
location of Oceania (Q538). Now given the fact that the Earth is not
flat and Oceania is not a square, I fail to see the possible utility of
such an extremely detailed custom precision value. My point is that the
area (bounding box) that any such tolerance describes on Earth depends
on the location of the center point, and is hardly capturing our exact
amount of uncertainty in any strong sense. So why bother with such
At first I thought this would be an error in the data, but the UI has a
special handling for it (quite literally: it shows the word "special"
with the precision in parentheses). However, I cannot edit this value as
a user without resetting it to one of the predefined values. This seems
a huge limitation, which would require a very good reason for supporting
such odd values at all. Or is the behaviour of the UI just a way of
recovering from an error while avoiding to simply fix it by itself?
Should we have a bot that corrects such cases to the nearest existing
<quote name="Thad Guidry" date="2015-01-06" time="19:59:18 -0600">
> And so after some digging, and lack of responses on this thread,
I'm worried that the relevant people from the Wikidata/Wikibase project
just aren't seeing your messages on this mailing list. I'm cc'ing here
the wikidata list.
For those on the Wikidata list, see the full thread here:
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |