Hoi,
The parser would understand it because it stored information. The property
is still the same property, the label it uses is now seen as a local
overrride.
Daniel, there are many ways to solve this. The problem you face is based on
a misconception. Language are not meant for rigidity. Expectting that you
can has already been shown to be problematic. Consequently persisting on
labels to be always unique is a problem of your own choosing. A problem
that will not go away and is easiest solved now.
It is abundantly clear that you WILL use the requirement of Wikidata as an
excuse when a language has no alternative. At that time it will be even
more problematic to fix this issue. Not only because of the amount of data
that may need conversion but also because assumption about Wikidata have
grown even more fixed and rigid.
Thanks
GerardM
On 9 July 2015 at 11:42, Daniel Kinzler <[email protected]> wrote:
> Am 09.07.2015 um 11:21 schrieb Gerard Meijssen:
> > Hoi,
> > If that is the use case, not much changes. We are talking software. When
> a
> > property is selected, the software does not need to show the property
> number and
> > still store it. Nothing new here. It does not need to change the label
> either
> > when Wikidata decides to change the label. A report may be produced to
> show the
> > use of the old label... Again, nothing new here. It has been done and
> can be
> > done again.
>
> So, the label changes. Later, the page that uses it on Wikipedia is
> edited. The
> parser
> looks at the #property tag, and sees a label that it no longer understands
> (how
> would
> it). The data transclusion is broken. Wouldn't it be nice if the
> transclusion
> could keep working? Unique aliases would do that.
>
> Alternatively, we could do what Ricordisamoa suggests, and just put the
> P-ID
> into the wikitext. But then you couldn't easily see what
> {{#property:P1234}}
> means when looking at the wikitext. If people are OK with that - fine!
>
> Or we could just do away with wikitext completely. Then we wouldn't have
> this
> problem. We'd use the ID internally, and the label for display and
> editing, just
> like we do on Wikidata. But I don't think that's going to happen any time
> soon.
>
> -- daniel
>
>
>
>
>
> _______________________________________________
> Wikidata mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
_______________________________________________
Wikidata mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata
