Current spec says that:
Two shorter variations for specifying time should be supported:
YYYY-MM-DDTHH:MM:SS(implies a time of YYYY-MM-DDTHH:MM:SS.000000)
where the sub-seconds are interpreted to be zeros and
YYYY-MM-DD(implies a time of YYYY-MM-DDT00:00:00.000000)
where the hour, minute, second and sub-second are interpreted to be zeros.
But having these two variants be optional means that client code must either decide whether they are supported on a datacenter by datacenter basis or always use the full time. Making these two time formats required would add very little code to the service implementations, but make it simpler for client writers in general, and much easier when people are typing in URLs by hand.
Recommend the "should be supported" be changed to "must be supported".
Current spec says that:
But having these two variants be optional means that client code must either decide whether they are supported on a datacenter by datacenter basis or always use the full time. Making these two time formats required would add very little code to the service implementations, but make it simpler for client writers in general, and much easier when people are typing in URLs by hand.
Recommend the "should be supported" be changed to "must be supported".