Hoi,
If none of this is visible to users, the whole point of names of properties
are senseless. Why have them in the first place and prevent this whole
issue by using the property identifier itself.
The number of languages is only relevant in so far that it is absolutely
clear that you assume that you will have sensible property names in the
first place. It is not smart to do so. It has been indicated that there are
issues.
Thanks,
GerardM
On 11 July 2015 at 22:20, Daniel Kinzler <daniel.kinzler(a)wikimedia.de>
wrote:
Am 11.07.2015 um 09:28 schrieb Gerard Meijssen:
Hoi,
I blogged about it. My argument is that Wikipedia should not be fenced
in by
assumptions from Wikidata.
Your blog post seemsw to assume that the wikidata label will be displayed
on
wikipedia. That's not the case. We are discussing the use of localized
property
names (let's just stop calling them labels, it's misleading) for
properties in
the {{#property}} parser function, in order to retrieve the value. Only the
value. So, is an ID better than a localized unique name? Both will only be
visible in wikitext, and, in practice, only in wikitext in templates.
Your blog post states that labels cannot be changed once they are set.
This is
wrong. The can be changed. Currently, that will however break all wikitext
(templates) that use that name to refer to the property. This is what we
are
trying to fix by allowing properties to be accessed by an alias. The
downside is
that this requires aliases to be unique.
I'm not sure how the number of languages is relevant at all. The name(s)
of a
property have to be unique per language. How many languages there are
doesn't
matter at all for this, since there can not be conflicts between languages.
In any case, *non* of this is at all visible to readers.
--
Daniel Kinzler
Senior Software Developer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata