Problem description
lastStatusTime is required when the reachability status is returned, but some backend implementations do not include any clue as to the date when the reachability status they provide was last updated. Such implementations either have to use a "default" date, or be non-compliant by not providing a lastStatusTime value.
Possible evolution
Allow lastStatusTime to be nullable, so that null can be provided as a value when the implementation has no clue when the reachability status they provide was known to be correct. The API consumer must then decide for themselves whether the reachability status provided is of any value to them.
Alternative solution
The format for lastStatusTime could be removed, allowing arbitrary string values to be returned. But this makes OAS validation problematic, as any string would then be valid.
Additional context
Some other APIs are using the nullable property as a solution to this problem
Problem description
lastStatusTimeis required when the reachability status is returned, but some backend implementations do not include any clue as to the date when the reachability status they provide was last updated. Such implementations either have to use a "default" date, or be non-compliant by not providing alastStatusTimevalue.Possible evolution
Allow
lastStatusTimeto be nullable, so thatnullcan be provided as a value when the implementation has no clue when the reachability status they provide was known to be correct. The API consumer must then decide for themselves whether the reachability status provided is of any value to them.Alternative solution
The
formatforlastStatusTimecould be removed, allowing arbitrary string values to be returned. But this makes OAS validation problematic, as any string would then be valid.Additional context
Some other APIs are using the nullable property as a solution to this problem