Hoi, My understanding is that it is machines that need to uniquely know what a property stands for. People are quite capable understanding what a combination of a P and a Q mean. At that time there is no disambiguation. With proper descriptions it is not hard at all to choose the right property when a new statement is made.
So really what IS the issue? Thanks, GerardM
On 9 July 2015 at 10:59, Daniel Kinzler daniel.kinzler@wikimedia.de wrote:
Am 09.07.2015 um 03:12 schrieb Ricordisamoa:
Il 08/07/2015 22:00, Daniel Kinzler ha scritto:
The idea was readability and internationalization.
Which one is more readable and internationalized,
{{#property:syntymäaika}} or
{{#property:P569}} ? The former makes reading and reusing templates from other wikis much
harder.
Well, yea, localizing things always makes them harder to use by people who do not speak the respective language. I'd say the natural language name is still more readable, since there are probably more people who know what "syntymäaika" means than what "P569" means.
But I see your point, especially with regards to cross-wiki template use (if we ever get that).
If there is consensus to not use human readable property names for
accessing
data, and solely rely on IDs instead, we could indeed stop all this
right now,
and just drop the uniqueness constraint for labels as well as for
aliases of
properties.
Yes!
Can you point to a community decision/discussion regarding this? Is the sentiment the same across several languages?
If this feature is *really* not needed/wanted, we can of course drop it. Would save a lot of trouble. But I'd want to be rather sure about that. After all, even MediaWiki's magic words like #REDIRECT are localized.
On a related note: what about the "#property" bit. Should that be localized?...
-- Daniel Kinzler Senior Software Developer
Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V.
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata