I am allowed to save in the api (via wbcreateclaim) the following:
This should be validated when the claim gets saved and return an error if the data value is not valid.
As it does get saved currently, we then see an error in the UI on an item page in the snak view:
"The value does not comply with the property's definition.
The value's data value type "ununserializable" does not match the property's data type's data value type "time"."
hmm... yeah, that's a tough one. On the one hand, do we really want to restrict it too much?
I would say that the error message is not too good. It should actually be "The data is saved with an unknown calendar model, to which we do not know how to translate to".
And then the saved data in proleptic gregorian could still be displayed.
@amir we have a patch for supporting /entity/QXXX in apache. It should work soon.
@Denny it seems any arbitrary url or string can be put as calendar model. bots will go astray and have a potential mess.
I think it's best to have validation checked during save, so the api user has a chance to get it "right". Not sure about hard-coding the calendar models though. If they could be configurable and more flexible, that would be nice.