You are welcome!
While I was reviewing your previous work on food additive, I think I detected some P279 that had been entered in a reverse manner. I mean, there was a confusion between the subject and the object of the property.
A -subClassOf -> B where A is the subject (the Item on which we add the property), and B the object (the Item to which the property points), means that A is a sub class of B (A is more specific than B. All the A instances are also Bs, but the Bs are not As). That's the way it should be.
Could you check that some other P279 that you entered in wikidata were oriented correctly?
It might be that some P279 with the reverse orientation are still present. It can lead to serious problems.
Could help me refining the WIGOS regex? See Property_talk:P4136#regex_WIGOS.
@Dirac, regex fixed, thanks for reporting! See P4136 talk page for an update too.
Meteorological Service of Canada climate ID
I've created a request for a Meteorological Service of Canada climate ID that is, essentially, an adaptation of your request for the BoM station number.
I thought it could interest you to give your opinion on this proposal. While there, if you could also look at the one below, for a Weather observations data interval it would be appreciated.
Hello, about : It is interesting idea to specify unit classes. But it is not applicable for all properties. For example arshin (Q1172583) is instance of unit of length (Q1978718), but this unit is not compatible with wavelength (P2808) by historical reasons.
Looks like this broke many working constraints. Please roll it back.
Hmmm I'll undo/fix the use of classes in this constraint. I misunderstood the allowed qualifiers for allowed units constraint (Q21514353) but have now attempted to document how it works at Help:Property constraints portal/Units
Constraint reports updating will be run soon. So I reverted your edits for now. units used for this property (DEPRECATED) (P2237) deletion was reverted too unfortunately. I can delete P2237 using bot. But deletion discussion is not closed as I see.
I think PfD should go through before removing/deprecating these.
BTW, phab:T164372 is about to implement another approach.
Thanks Ivan @ Jura1. Sounds like a good plan.
I did have a look at https://github.com/wikimedia/mediawiki-extensions-WikibaseQualityConstraints/blob/master/src/ConstraintCheck/Checker/AllowedUnitsChecker.php and it appears that phab:T164372 has been resolved/closed without providing a units constraint that works on a class basis. There are quite a few properties (examples: budget (P2769), cost (P2130), length (P2043), etc) which could be commonly used with dozens or 100's of different units. Listing every single currency as a unit for budget (P2769), cost (P2130) and the multitude of other currency quantity units is not ideal. A units constraint that accepts relation (P2309) and class (P2308) qualifiers would allow both use cases--specifying individual units, and/or specifying classes of units.
Yeah, the currency one definitely need a better approach.
The others might be too broad to do any sort of checks.
Your feedback matters: Final reminder to take the global Wikimedia survey
Mozilla Firefox (Q698)
Hey, in my opinion, putting every release subversions - specially BETA subversions is not a good idea. Today this page is so long, soon we will have this item long as 20 screens - this regards also other popular and most often updated software. --Jasc PL (talk) 17:07, 28 March 2018 (UTC)
There are some improvements which could be made to the display/rendering of items in the web interface to improve the situation. For properties with more than 10 values, only the preferred value could be shown with the remainder hidden behind a "show other 105 values" link. User:MichaelSchoenitzer/Updown exists to improve the speed of navigation on large items, but not necessarily the page rendering times in a browser. A longer term solution is to create a new item for each software release, then create a new "latest software release" property for use on software (Q7397) that links to a software release item. This has been talked about before, but not yet implemented, likely due to the high amount of work required. Dhx1 (talk) 22:20, 28 March 2018 (UTC)
Hi @Dhx1, sorry for my so late answer. If we really need (e.g. enwiki article) absolutely every subversion of FF, all other browsers and same regularly updated soft, we must play with it so good as possible. The separate item for every main version? Good direction but... for today it is 60+ (incl. beta and alpha, developer, nightly...?) and the next every 2-3(?) months. My idea is to
- keep all most present versions in one main, existing item
- move every ten main versions to the separate archive item (0.1-10, ... 41.0-50.0, 51.0-60.0 - when stable 61.0 will be released)
With above model we will have the only 6 new items now, and not so much semi-automated work. --~~~~
Hi @Jasc_PL:. My thoughts were more along the lines of having bots create new Wikidata items automatically when new software releases occur. Generally this information is easy for a bot to discover by checking git (and other version control system) tags and/or web directory contents for the latest versions released. There are numerous advantages to this approach, including the ability to perform queries such as "show me the number of times each month that a new stable web browser version is released" (histogram), "what was the longest time between beta software releases of software X". Further, an archive version of a software item would be excluded from Wikidata under Wikidata:Notability/Exclusion criteria ("any archiving pages"). Dhx1 (talk) 12:16, 15 April 2018 (UTC)
@Dhx1, if I good understand (maybe not), exclusion concerns "any Wikipedia archiving pages"? Using well configured bots is very helpful, but in what concrete way do you plan to maintain versions in such elements?
However, probably much more important and long existing problem (for peoples - not for scripts/bots) is to have all versions sorted automatically.
Reminder: Share your feedback in this Wikimedia survey
Share your experience and feedback as a Wikimedian in this global survey
Open Food Facts
I noticed your many accepted property proposals for Food and food related topics. Having pushed many properties, I'm glad to see even more, especially to start modelling additives :-)
I was wondering if you knew about Open Food Facts. We're doing a crowdsourced Wikipedia of all food products on the planet.
Also, wondering if you had the datasets handy for a potential import using Mix N'Match.
Thanks @Teolemon. I am aware of Open Food Facts (great project!) and just tried adding and editing a few entries the other day. There are some good Wikidata integration opportunities for ingredients, additives, places/countries of ingredient origin, places/countries of purchase, places/counties of manufacture, etc.
For the new food related properties, I have added the food additive taxonomy located in section 2 of CAC/GL 36-1989: Class names and the international numbering system for food additives, 2017 English revision (Q47123809). I have also extracted and cleaned up the data found in section 3 of CAC/GL 36-1989: Class names and the international numbering system for food additives, 2017 English revision (Q47123809) (list of food additives and their uses). The next step is to convert that data into QuickStatements format and link in the relevant JECFA database IDs for each additive (provides links to toxicology/evaluation reports for each additive). The final step is to import that section 3 list of food additives, complete with at least use (P366), International Numbering System number (P4849), JECFA database ID (P4852) and CAS Registry Number (P231) statements.
I considered mix'n'match but for this import, I find it easier/more accurate to just do the import by hand. I'll let you know when the import is complete--shouldn't be too far away.
Thanks a lot :)
Your work on additives is going to be tremendously useful. We have started trying to do smart things using Wikidata (like displaying maps of wine regions…), and additives is certainly an area where people want reliable and sourced information.
I granted the bot flag.
Thank you @Lymantria:. I'll get the bot started and monitor its progress.