Hey everyone,
I am looking for a great PHP developer to join the software
development department at Wikimedia Germany. We have a lot of backend
tasks to do around Wikidata especially for the support of Wikimedia
Commons. More details about the position are available at
https://wikimedia.de/wiki/PHP_Backend_Developer_(f/m) If this is you
please do apply. If you know someone who fits please send them them
the link. This is a great chance to make a difference around
Wikidata's software.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Product Manager for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
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.
Hello,
I'm glad to can announce my last experiment working with Wikidata and
Wikipedia-coordinates:
http://tools.wmflabs.org/wp-world/wikidata/superclasses.php?lang=en
This list shows how many objects we have in different classes and
provide links to maps with only this specific class.
I think it's much more useful than in the past where 80% of our
coordinates were simply a "landmark". Now we have maps full with roller
coaster or with museums.
To create this tool I used properties "is instance of"[1] and "is
subclass of"[2]. To extract this properties it was necessary to use
"Wikidata Query".
Now all classes, where an object is a member, are in a numerical
array-element in the database. So with an index on this array it should
have a good performances.
Next steps are to try to bring more order inside this list and support
the community to create more "is instance of"-entries in Wikidata. (Only
30% off all objects have such an entry).
Greetings from Switzerland
Kolossos
[1]https://www.wikidata.org/wiki/Property:P31
[2]https://www.wikidata.org/wiki/Property:P279
Hi,
I am at a the Multilingual Web Workshop in Madrid. I had a discussion here
with a person who specializes in multilingual terminology translation about
how Wikipedia and its sister sites can be more useful and reliable for
people who search for translations of terms from different professional
fields - medicine, communications, law, etc.
For example, if you go to the Wikipedia article [[Aorta]], how can you know
that this term is actually recognized as the English term by any
professional medical associations? And if you go to
https://www.wikidata.org/wiki/Q101004 , how can you know the same things
about each of the translations of this term? For example, how do you know
that "Srdcovnica" is recognized as a Slovak term by any medical association
or linguistic committee?
By itself, the interlanguage link to Slovak is not reliable. A translator
to Slovak can, of course, go to a website of a relevant linguistic
committee and check the term there. But can it be more direct and
machine-readable?
A property could probably be created, which would hold an id of a term in
such a terminology database, but would it be appropriate to include it in
an item page, given that such information is language-specific? It seems
reasonable to me, but I wanted to make sure that everybody find it
acceptable.
And if there are such properties already, I'd love an example :)
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Hi,
I'm having some cases where a work has been attributed to an author by a
source, but the source itself says this attribution is "dubious", or it is
contesting a previous attributions as "spurious".
As I see it, the rank of the statement is not deprecated (in fact it is
"normal" or even "preferred"), but I have no way of representing this
"claim uncertainty" or "claim rebuttal".
Is there any hidden parameter for this or should it be addressed with a
qualifier?
Cheers,
Micru
Hello all,
I am playing around with properties at the moment, especially filtering
out a certain kind of properties.
So I wondered if it wouldn't be a nice thing, if properties were
classified in some way.
Example: (Numbering is just for readability and does not hold any semantics)
P… is the placeholder for the actual property-Id, did not want to look
them all up
1) Relations
1a) Mathematical relations
1b) Relations in human interaction
1b1) Social relation
1b1a) P… (is employee of)
1b1b) P… (is heir to)
1b2) Biological relation
1b2a) P… (brother of)
1b2a) P… (sister of)
…
2) External IDs
…
and so on, I think you get the idea.
Has something like this bees discussed before?
Cheers,
Fredo