Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Descriptions for date fields clashes with examples and what the type is called #67

Open
hmpf opened this issue Oct 5, 2021 · 2 comments

Comments

@hmpf
Copy link

hmpf commented Oct 5, 2021

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".

@SotosTsepe
Copy link
Collaborator

@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.

@SotosTsepe
Copy link
Collaborator

SotosTsepe commented Oct 22, 2021

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.

EDIT: It is already reported in #66 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants