Fri, Feb 8
Aug 14 2018
Jun 21 2018
q="don't escape the backslash" :)
Jun 20 2018
Maybe page properties should include counts of lemmas, forms and senses, as they do for statements and identifiers.
Do we have any discussion of this usecase onwiki? It seems contrary to a problem raised onwiki.
Jun 18 2018
Jun 17 2018
Jun 15 2018
Thanks. I can get it to load know. Not sure what happened. I will have a look.
Thanks. I added details there as well.
Jun 14 2018
I had a look at the sample, but there doesn't seem to be any data. The three compressed files seem empty.
Jun 13 2018
(tries to imitate Lydia's voice) "it is fine"
Jun 12 2018
You mean (e.g.) "visualize" and "visualise" on https://www.wikidata.org/wiki/Lexeme:L11 ?
To restrict search to properties, one can use "p:". Is it already planned somewhere to use "l:" for lexemes?
Jun 11 2018
In recent days, I noticed it for newly created items as well
Noticed that as well.
How about doing this in the other direction: T85444#4271029
Shouldn't users opt-in to this?
When using https://query.wikidata.org/sparql in a browser, it displays an XML with some information about the database.
Jun 10 2018
Couldn't be set as prefix or variable?
Thanks for looking into this.
It seems that even when using URI, the same service can be called just once.
Jun 9 2018
Coming to the second part:
Jun 4 2018
Special:NewLexeme should also include a way to add a sense directly
Probably not. If the "Gloss" was added by a vandal I suppose this couldn't have happened without a "Sense" that should also be deleted.
If it's a problem having both formats, I think the input format only should be exported.
"I can not remove the last Gloss of a Sense" </quote>
@Amire80 what's langcom's view on these?
May 30 2018
Moving it to search wont solve it then.
I don't see clear disadvantages of doing the indexing Multichill suggests.
In terms of functionalities, what's the outcome of this?
May 29 2018
I think it would help to not wait too long before fixing this.
May 28 2018
It might be useful as a Wikibase feature, but on Wikidata itself it might not fully scale anymore.
Do we still need this?
It needs a cleanup of data in there as well.
Sounds like an interesting idea. It might be easier to do a static set and measure how that evolves. Uses can change a lot through changes in templates.
May 23 2018
Apr 16 2018
On Wikidata Query Server. Currently xds:integer(?v) is needed on quantities
Don't hold your breath ..
Could the output include an integer triple as well?
at some point "unique" was changed to "distinct" on Wikidata constraints.
I'm not sure if it's a good idea to allow any convertible unit by default.
Jan 28 2018
Sep 11 2017
what part is missing?
yeah .. probably the same thing. Hadn't notice that I unfocused it though.
At Wikidata, I tried to change or add value to statements with item datatype, e.g. enter the place of birth a person. The border around the entry field changes colors (depending on whether the value meets constraints or not), but then fails to allow me to save it (cancel or remove are enabled).
Sep 6 2017
Sep 5 2017
Thanks! I will try that.
The simplicity of this approach seems convincing. It could complement number of sitelinks and statements.