Hi Magnus,
Are these values for contact times of eclipse (P2569) currently blocked by QS or by the API:
Q4820591 P2569 +00000002016-08-18T09:25:00Z/13 Q4820591 P2569 +00000002016-08-18T09:42:00Z/13 Q4820591 P2569 +00000002016-08-18T09:59:00Z/13
I get ERROR (set_date) : Malformed input:
I keep reading that it should be possible by api, but I can't actually find a sample where it's done.
Probably not possible with API, setting precision to 13 generates code: "modification-failed", info: "Out of range, must be no higher than 11"
I tried a few variants, but for some I get
ERROR (set_date) : Invalid snak. ($timestamp must resemble ISO 8601, given +0000002016-08-18T09:25Z)
Timestamp should match https://github.com/wikimedia/mediawiki-extensions-Wikidata/blob/master/vendor/data-values/time/src/DataValues/TimeValue.php#L236 (i. e. seconds should be there). However it looks like there is a hardlimit for max precision 11. You can find out this by running:
Q4115189 P2569 +00000002016-08-18T00:00:00Z/13
This is a clear example, the max precision is 11: https://www.wikidata.org/wiki/Special:ApiSandbox#action=wbparsevalue&format=json&datatype=time&values=1994-02-08&options=%7B%22precision%22%3A14%7D&validate=1 The validation clearly shows the precision can't be higher than 11.
It could also mean that precision should be 11 if the input has precision 11.
As it's probably too early, I listed P2569 for deletion.