> If we want to avoid this complexity, we could just go by prefix. So if the
> languages is "de", variants like "de-CH" or "de-DE_old" would be
considered ok.
> Ordering these alphabetically would put the "main" code (with no suffix)
first.
> May be ok for a start.
I find this issue potentially
conversation in one place, I will reply to
> David, Denny, and Philipp in one mail. It's going to be a bit long,
> sorry...
>
> Am 11.11.2016 um 23:17 schrieb David Cuenca Tudela:
> > Hi there!
> >
> > 1) a possible solution could be to have another category of it
On Mon, Jan 20, 2014 at 6:13 PM, Lydia Pintscher
lydia.pintsc...@wikimedia.de wrote:
* We should allow more than one badge per sitelink.
* We can start with supporting just one badge per sitelink.
I agree with your two points. Since badges don't need statements, just
associated items to any
On Mon, Jan 20, 2014 at 7:43 PM, Bene* benestar.wikime...@gmail.com wrote:
Hi, I am not sure if you got the point which I criticize. While with some
effort we could create an interface on Wikidata supporting several badges
[1] we are still facing a problem on the client. How should we choose
A couple of months ago there was a conversation about what to do with the
identifiers that should be owl:sameAs [1]
Then there is another discussion about using a formatter URL property to
use any catalogue/db as an id instead of creating a property [2]
Now there is another property proposal to
