You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a field is marked to be of the type "Date", the examples show a date without time, but the description always includes "Encoded using the relevant ISO 8601 Date and Time compliant string". Not: "and Time". So, is a date + time also valid or should the description contain just "Encoded using the relevant ISO 8601 Date compliant string".
The text was updated successfully, but these errors were encountered:
@hmpf good catch. We are going to update the description of the Date type fields by removing "and Time". The values in these fields must follow the YYYY-MM-DD format.
Taking a look at the DateTime fields, I strongly suggest that we use a timezone designator so that we avoid localization problems. Format should be YYYY-MM-DDThh:mm:ssTZD, as specified in ISO 8601. TZD can be expressed with Z, +hh:mm or -hh:mm.
When a field is marked to be of the type "Date", the examples show a date without time, but the description always includes "Encoded using the relevant ISO 8601 Date and Time compliant string". Not: "and Time". So, is a date + time also valid or should the description contain just "Encoded using the relevant ISO 8601 Date compliant string".
The text was updated successfully, but these errors were encountered: