Wikidata is broken.
It has allsorts of kludges to link items to the items they should be in.
Lets merge all these Categories, lists, duplicate articles in a different
language etc. with the items they should have been part of from the
beginning. (Normal rules apply - If you were to describe the
Congratulations GerardM
Here's to the next million
Joe
On Tue, 5 Jan 2016 23:43 Stryn wrote:
> Agreed.
> Someties it's hard to see any difference between bots and "normal users"
> on Wikidata.
>
> *Stryn*
>
>
> 2016-01-06 1:39 GMT+02:00 Ricordisamoa
Why have instance of item and instance of superclass of that item?
If Glasgow is instance of : city of Scotland and
City of Scotland is subclass of : city
Then we should not have Glasgow instance of : city
This principle should cut down a lot of these extra 'instances '
Joe
On Sat, 28 Nov 2015
Hi Thomas.
https://www.wikidata.org/wiki/Wikidata:WikiProject_Economics is looking to
do something a bit like this. It has been moving slowly as we waited for a
currency datatype to become available but that has now happened so it
should start moving.
https://opencorporates.com/ is also working
We will be moving to Commonsdata which will let us do queries to generate
millions of category like groups on the fly. There is little point in
messing with commons categories before then.
Joe
On Mon, 31 Aug 2015 09:54 Steinsplitter Wiki
wrote:
> Overwriting the
Use the same properties for family relationships of animals and humans
Sex /gender is the only property that has values for female / male
creatures different from the values for male / female humans.
Joe
On Wed, 26 Aug 2015 12:45 Ole Palnatoke Andersen palnat...@gmail.com
wrote:
I've just
Hypercubes and csv flat files belong in commons in my opinion (commons may
have a different opinion ). That's if we even want to store a copy.
This source data should then be translated into wikidata triples and
statements and imported into wikidata items.
The statements in wikidata are then
Can I just ask all of you who want to demand an enquiry as to how this
happened to hold off until the problem has been fixed
Please
No post mortem while the patient is still alive
Joe
On Tue, 30 Jun 2015 18:39 Lydia Pintscher lydia.pintsc...@wikimedia.de
wrote:
Hi everyone,
I have some bad
://www.wikidata.org/wiki/Property:P1448property. Of course this
should be done by a gadget, or we may have to find a special treatment for
the ''name'' properties.
2015-04-28 23:06 GMT+02:00 Joe Filceolaire filceola...@gmail.com:
I agree up to a point. Transliteration is not appropriate for labels
I agree up to a point. Transliteration is not appropriate for labels for
all items. There are however a few categories of items for which
transliterated labels are appropriate. For example :
* English labels for villages and towns
* English labels for people
*English labels for bands and albums
When we use auto transliteration to generate English labels then I think we
should follow the practice of the English Wikipedia with other
transliterations demoted to aliases.
Similarly auto generated German labels should follow the transliteration
practices in the German wikipedia.
When we use
If you change the datatype for identifiers from string and the other
properties with string datatype are changed to monolingual then we won't
have much need for the string datatype
On 6 Apr 2015 15:09, Lydia Pintscher lydia.pintsc...@wikimedia.de wrote:
On Sun, Apr 5, 2015 at 6:52 PM, Magnus
I think there is a case for including this structured data disguised as
text but it should go in the reference for a statement
On 4 Apr 2015 18:07, Daniel Kinzler daniel.kinz...@wikimedia.de wrote:
For things that actually *are* free text, and not terribly long, a
monolongual
(or, in the
We do have the Quote property (P1683) which has monolingual text
datatype. You could certainly put free text in the value for this property
and add this to a reference or even use it as a qualifier.
Joe
On Wed, Apr 1, 2015 at 9:54 AM, Daniel Kinzler daniel.kinz...@wikimedia.de
wrote:
Am
I agree that word for word translations are not appropriate for English.
If there are languages which traditionally do use word for word then that
might be appropriate for those languages
On 12 Mar 2015 10:24, Daniel Kinzler daniel.kinz...@wikimedia.de wrote:
Am 12.03.2015 um 10:03 schrieb
I suspect these are not wikidata aliases. They are probably labels in other
languages.
While wikidata doesn't have a multilingual datatype it does allow you to
add labels (and aliases) in any language and these labels, if they are
correct, are the appropriate thing to use to localise osm place
If you want to list the properties called by a template then you need a
property which links to other properties - ie it has a property datatype.
Property datatype is not available yet but is coming soon.
You can then use the labels for this property in various languages to label
the
Country (p17) should be used for a general affiliation. Dublin has a
general affiliation with Ireland.
On the other hand City of Dublin is in the administrative territorial
entity Dublin region which is in the administrative territorial entity
Republic of Ireland which is on the geographical
There is a proposal to create a 'subproperty of' property but it is on hold
until we can have a property as a datatype
Joe
On 9 Jan 2015 16:26, Thad Guidry thadgui...@gmail.com wrote:
https://www.wikidata.org/wiki/Property:P279 aka the superclass ...
seems to have an equivalent property that
Till now our subclass of has developed organically from the bottom up.
Their has been some discussion about adopting an existing upper level
ontology but no decisions.
In principle there is no reason why we can't incorporate all of these -
after all the English Wikipedia category tree has three
First:
A band is an organisation, not a person.
Second
P17 is deliberately a bit ambiguous so it can be used for those cases where
we don't have specific info. We also have specific properties for those
cases where we have specific info.
We can have an architect born in Germany who spent most of
The terms of use are the minimum requirements. Each wiki may have more
requirements.
Joe
On 2 Jan 2015 10:16, Flaken Aldnonymous aldnonymo...@yahoo.com wrote:
On [[m:TOU]] already explain what you should do.
Terms of use - Meta
[image: image]
Terms of use - Meta
Translate this page
Gerard
Do you want to delete sitelinks to wikipedia redirects or wikidata items
which redirect to other items?
Joe
On 17 Oct 2014 06:27, Gerard Meijssen gerard.meijs...@gmail.com wrote:
Hoi,
If there is something like a hatmaker, it can have an item even when there
is no article in the
Having sitelinks to redirects in my wikipedia makes it easier for other
wikipedias to link to my wikipedia.
If I dont care about that then I may delete those redirects from my
wikipedia and the sitelink to my wikipedia will go too.
The wikipedias have the final say on what they do and do not
Jane
I disagree.
Sitelinks to wikipedia redirects are useful because they help one wikipedia
get useful links to other wikipedias even where the structure of the
wikipedias is different, without having to force the various wikipedias to
follow the same structure.
Your comment that wikipedias
Gergo
One of the big advantages of commonsdata over wikitext is that commonsdata
is Internationalised and ready for localisation.
For this reason alone I believe it is worth looking closely at all wikitext
to see if it can be expressed as a Commonsdata statement.
Joe
On 10 Oct 2014 17:09,
I agree with Amir.
Especially since we can use aliases to record possible alternative names as
well.
Joe
On 15 Sep 2014 15:20, Amir E. Aharoni amir.ahar...@mail.huji.ac.il
wrote:
2014-09-15 16:16 GMT+03:00 Lydia Pintscher lydia.pintsc...@wikimedia.de:
As for simply allowing sitelinks to
Except that the problem isn't incompatible licenses; its lack of licenses.
Most pix uploaded to wikipedias have no license. They are there under fair
use rationales which are specific to each use and to the laws which apply
in countries using that language. These pix are not free to reuse. Each
Is this being inported into wikidata?
Joe
On 11 Sep 2014 23:16, Benjamin Good ben.mcgee.g...@gmail.com wrote:
FYI we are already starting work on importing Chem information. e.g. we
are assembling files for import like:
PubChem:CID114709 MESH:D004827 therapeutic 17516704
PubChem:CID97226
(properties???) so that it can later be retrieved
via queries into a list?
https://cs.wikipedia.org/wiki/Seznam_nejv%C4%9Bt%C5%A1%C3%ADch_%C4%8Desk%C3%BDch_firem_podle_tr%C5%BEeb
Thanks!
2014-06-16 10:35 GMT+02:00 Joe Filceolaire filceola...@gmail.com:
Oops.
My mistake. The properties I
here are my thoughts about this:
MAYOR OF FOO VERSUS MAYOR OF FOO
I am in favour of a separate item for every town and village which has a
mayor or a council.
I am against have a Mayor of Foo item for each these. If the mayor gets
an item then the deputy mayor and the sheriff and the dog cacher
includes them they are notable in Wikidata.
Thanks,
GerardM
On 17 June 2014 19:56, Joe Filceolaire filceola...@gmail.com wrote:
here are my thoughts about this:
MAYOR OF FOO VERSUS MAYOR OF FOO
I am in favour of a separate item for every town and village which has a
mayor or a council
a link and an example of a fleshed out use of these properties?
Thanks,
GerardM
On 15 June 2014 21:49, Joe Filceolaire filceola...@gmail.com wrote:
Exactly.
If the data in the table cannot be expressed as a set of statements
(probably with a qualifier for each column of the table) then why
I think it is a reasonable ambition that the 'preferred' statement should
always provide accurate information even when the qualifiers are missing.
For example, if we have population figures for various years and 'applies
to part' figures for males, females, under 20's etc. then the most recent
Never forget that even the full data, with all the qualifiers included, is,
in most cases, little more information than what is contained in the lead
paragraph of a complete wikipedia article.
Wikidata will be useful but it will never replace the encyclopedia articles
and will, I believe, be most
Even where there is complete agreement that a human settlement is a 'city'
there is still usually a question over the population of that city. The
question is down to what to include.
A city in many cases is understood to include the contiguous built up area
but this will often extend far beyond
:
This is good news, and helps a lot — thanks for taking the time to respond
Joe. It may be a lot of work, but it would be great if you could reference
the actual property names by URL for the properties you mentioned.
//Ed
On Jun 9, 2014, at 6:10 AM, Joe Filceolaire filceola...@gmail.com wrote
Edward
Yes Wikidata has a mechanism for adding qualifiers and references to claims.
Where there are multiple values we can also mark one of them as preferred
and then simple queries will just get the preferred value.
For population figures each value would typically have qualifiers for
* Point
Remember that we are also recording the wikipedia article names in multiple
languages, which may or may not be the same as the label in those languages
On Fri, Jun 6, 2014 at 4:32 PM, David Cuenca dacu...@gmail.com wrote:
On Fri, Jun 6, 2014 at 5:05 PM, Daniel Kinzler
Well they can ask.
As there is no real definition of what is a city and what the limits of
each city are I'm not sure they will get a useful answer. The population of
the City of London (Q23311), for instance, is only 7,375! Should we
change it from 'instance of:city' to 'instance
We have a number of 'name' properties (with string datatype)
+ Birth name
+ short name
+ pseudonym
+ provisional designation
and proposed name properties (with monolingual text datatype).
+official name
There are a number of other name properties we may need
+nom de plume
+nom de guerre
+art
Simple tables that are in wikipedia:
* league tables with columns for games won, drawn, lost, goals for, goals
against, points, rank and rows for each of the teams in the league.
* election results with columns for votes for each party and seats won by
each party and rows for each region, state
I am not a developer, nor a librarian. I am one of the volunteers trying to
piece together a logical set of relations between the millions of Wikidata
items and, in the process probably reinventing the wheel again each day.
On the practical issue of the various 'levels' of works and what
should be able to have hard coded reverse properties and
symmettric properties.
Joe filceolaire
On Wed, May 14, 2014 at 2:33 PM, Markus Krötzsch
mar...@semantic-mediawiki.org wrote:
Hi Eric,
Thanks for all the information. This was very helpful. I only get to
answer now since we have been quite
See
Wikidata:Requests_for_comment/How_to_classify_items:_lots_of_specific_type_properties_or_a_few_generic_ones%3F#Subproperty_of
for a discussion of a 'subproperty' relation. where a property can have a
statement that it is a 'subproperty' of another property and the query
engine could search on
Mark it deprecated and include a quotation (It's a string property) about
how dubious it is in the source statements.
Joe
On Mon, May 5, 2014 at 3:42 PM, Jane Darnell jane...@gmail.com wrote:
Well in the case of attributions of artworks, these things tend to go
back and forth a lot, so
. Labels, statements and
links. It is best imho not to complicate things and leave this partition in
place.
Thanks,
GerardM
On 4 May 2014 22:17, Daniel Kinzler daniel.kinz...@wikimedia.de wrote:
Am 04.05.2014 09:00, schrieb Lydia Pintscher:
On Sun, May 4, 2014 at 1:28 AM, Joe
Where are we with fallback languages?
I did a session for new editors with Magnus last weekend and one of the
questions that came up was why one of the students couldn't see most of the
labels - he had his language set to British English. He asked why there was
no fallback to international
Property 'Official name' with datatype 'monolingual text' has already been
approved but is waiting for that datatype before it is created. It is
designed for the use you described - listing the various official names
with qualifiers for language, start date, end date etc. No matter what your
I agree that it makes sense that one of the first things to do when
creating a new wikipedia article should be to create an infobox which is
automagically linked to the creation of a wikidata item. There are a number
of considerations related to this.
1. Notability. The current rules for Wikidata
I've left some comments.
You might get more responses with a request on
https://www.wikidata.org/wiki/Wikidata:Project_chat
Joe
On Mon, Mar 3, 2014 at 3:48 PM, Thomas Douillard thomas.douill...@gmail.com
wrote:
Hi, it would be a good idea to start a discussion on Wikidata project
chat,
As long as it is possible to override it. There are all kinds of strange
corner cases that we need to accommodate. For instance in elections to the
Senate of the Republic of Ireland (
https://en.wikipedia.org/wiki/Seanad_%C3%89ireann the votes are calculated
to 3 decimal places!
On Mon, Nov
I would propose adding a 'languages' tab to the user settings. That is
where users expect to set their UI preferences.
Let us tick boxes for as many 'additional languages' as we want.
On 12 Nov 2013 11:05, Gerard Meijssen gerard.meijs...@gmail.com wrote:
Hoi,
At this moment, it seems like a
Actually the problem isn't that you can only have one link from a
wikisource work from a wikidata item. We have separate wikidata items
for each edition of a work (because these have different metadata) so
multiple editions of the same work on a wikisource link to different
wikidata items.
This
work.
C. Adapt the wikipedia infobox visual editor so it can edit as 2. above.
Deploy the revised visual editor on wikidata first so we can test it before
it goes live elsewhere.
This is just my opinion but I offer it as a conversation starter. Is my
list very different from yours?
Joe (filceolaire
In Wikimedia Slovakia we are preparing Wikimedia Central and East Europe
Meeting, see https://meta.wikimedia.org/wiki/Wikimedia_CEE_Meeting_2013
[1]
There is interest about Wikidata and I would like to invite Wikidata
representative to have speak there. Unfortunately, core WD team can not
attend
56 matches
Mail list logo