| Jdlrobson added a comment. |
To summarise the problems im hearing here from all sides:
- editors expect how descriptions display to match case when they edit them and this can cause edit confusion
- descriptions are inconsistent despite guidelines; wikipedia clients want to be consistent with how they display them
- from a design perspective it makes sense to render sentence case in this context as otherwise it will look like an incomplete sentence.
I still see this an editing problem. When editing a wikidata description it should guide me to not use sentence case if that is indeed a policy or it should remove any leading uppercase letter . That solves 1 and 2. I liken this problem to code linting. Some developers like to use tabs and some like spaces. The only way you can make consistency happen is invalidating when the rules are broken and enforcing it.
Wikidata is a data store. Just as we wouldn't expect clients to have to render dates mm/dd/yy we shouldn't expect them to have to use case. We should be caring about the content not how it's used. I think #3 is up to the client. Rather than say it's wrong it would be helpful to point out examples where it doesn't work. Right now these seem to be hypothetical and/or rare.
Cc: Jdlrobson, Esc3300, RHo, Mholloway, Niedzielski, siebrand, Amire80, JKatzWMF, dr0ptp4kt, Lydia_Pintscher, Deskana, Dbrant, Nirzar, JMinor, Jhernandez, bmansurov, Aklapper, Sjoerddebruin, GoranSMilovanovic, QZanden, Winter, JGirault, Izno, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
