thiemowmde added a comment. All patches listed above are unrelated to this issue. To be more precise, they belong to the closely related issue of PHP's parser magically "correcting" 31 September to 1 October. I listed the patches as an answer for @Jc3s5h.
This issue needs discussion: Do we want to accept values such as "31 September 2014"? Or should such values be rejected? And if we decide so, is this the job of the parser (which one?) or the validator? And what exactly should be validated? Leap years? Leap seconds? Against which calendar model? Personally I suggest to keep this as simple as possible. Enhanced validation should be done by external tools, as argued in my comment https://phabricator.wikimedia.org/T85296#1125065 above. What we **could** do is a very simple, very basic check: Instead of the current [0,31] range for all months we could have individual ranges for each month. **But** the range for February will be [0,29]. We will not implement leap year algorithms in the current architecture of datamodel, parsers and validators. TASK DETAIL https://phabricator.wikimedia.org/T85296 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: thiemowmde Cc: Lydia_Pintscher, Jc3s5h, Liuxinyu970226, Ricordisamoa, Addshore, thiemowmde, JanZerebecki, Aklapper, daniel, Smalyshev, Wikidata-bugs, aude, Malyacko _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
