The changes you've made to this property have caused issues with it's use in video games (instance of Q7889), it seems like it's been narrowly defined as a hardware platform? (In the case of video games they are software that can run on bare hardware, as software running on an OS, or within a virtual machine environment.) A lof of the other property checks are on the basis of platform being present. I'm not aware all the other issues related to this property, but I'm wondering if this change should this be reviewed. Do you have any thoughts?
Changes to platform property (P400)
The changes I made were done in order to extend the scope of the property to virtual machines, PAAS, browsers, software frameworks and apps beyond hardware and OS. The problem is that currently none of them is a subclass of computing platform (Q241317). We could adjust the computing platform ontology or we could explicitly require the value of platform (P400) to be an instance of operating system (Q9135), web browser (Q6368), virtual machine (Q192726), platform as a service (Q1153767), software framework (Q271680) and computer hardware (Q3966) (maybe computer hardware (Q3966) is too wide).
Wondering why you've added P31 as a qualifier, rather than a substantive property, in EN 300 236 (Q52161288). Wrong, by my reading of instance of (P31). --Tagishsimon (talk) 11:35, 25 April 2018 (UTC)
You're perfectly right. My fault. Thank you for pointing it out.
No probs ;)
So there are 1452 of these...
Sorry - report is borked because template madness ... I'll try to fix that. ... now fixed
Yes, I added them all with QuickStatements but I didn't noted the mistake. To solve the problem we need to find all the ids of the affected items. Do you know of a way to quickly do it?
Sure - the report, above, lists the items with this issue. We can take the first column, and then in QS, remove the P1462, and then reinsert the P1462 and a couple of P31s. Simples :)
OK, thank you very much. I'll do that.
No probs. Enjoy!
Now it should be OK.
Agreed; is good. Thanks.
Thanks to yo
I think your QuickStatements batch got the wrong entity.
Thank you very much. I typed P698 instead of Q698. I'm sorry.
Np. Happens to most of us once in a while.
I thought it might be some interesting info on software they are running.
@Sjoerddebruin Ok, thanks for the advice. I didn't know it.
Please take part in the Flow satisfaction survey
(That message in other languages: العربية • bosanski • català • Deutsch • Esperanto • français • עברית • polski • português • português do Brasil • русский • اردو • 中文 – translate that message)
Like some other community members, you are using Flow.
An increasing number of communities now use Flow or are considering it. Although Flow itself is not scheduled for major development during 2016 fiscal year, the Collaboration Team remains interested in the project and in providing an improved system for structured discussions.
You can help us make decisions about the way forward in this area by sharing your thoughts about Flow — what works, doesn't work or should be improved?
Thanks for your ideas and opinions about Flow!
Borse Alessio Guidetti per Wikimania 2016
Ciao, come forse saprai quest'anno Wikimania, il raduno annuale delle comunità Wikimedia, si terrà a Esino Lario (Lecco) dal 22 al 28 giugno.
Come per le scorse edizioni dell'evento, anche per il 2016 l'associazione Wikimedia Italia intende rendere disponibili alcune borse di partecipazione.
Trovate invece tutte le informazioni su Wikimania Esino Lario sul sito ufficiale dell'evento
Alexmar983 13:24, 24 April 2016 (UTC)