search

RDA-DMP-Common / RDA-DMP-Common-Standard

Official outputs from the RDA DMP Common Standards WG
The Unlicense
65 stars 34 forks source link

Definition of time and dates to be refined #6

Closed cmzwolf closed 4 years ago

cmzwolf commented 5 years ago

The format used for the date should be specified (e.g. AAAA/MM/DD of the Gregorian Calendar).

Moreover the time used (ex. in the fields "created" and "modified") miss the time zone used for expressing the time.

dcmi commented 5 years ago

I suggest we standardise on ISO 8601 for dates - e.g. today's date would be expressed as:

2019-04-17

TomMiksa commented 4 years ago

Current specification of the application profile has no information on which date/time standard to use.

hmpf commented 4 years ago

For the time bit in datetimes, the most explicit storage/interchange format is hh:mm:ssZ, that is: 24 hours, 60 minutes, up to 62 seconds (because leap seconds), and timezone set to UTC as a Z.

I hope it won't be necessary for people making a plan to ever have to deal with full-on timestamps (they should get away with just dates!), but for all automated timestamps like "created at X, last modified at Y", this is the format to use.

I was thinking of RFC 3339: https://tools.ietf.org/html/rfc333

hmpf commented 4 years ago

Here's ECMA itself weighing in:

[Ecma-262 Edition 5.1: 15.9.1.15 Date Time String Format](https://ecma-international.org/ecma-262/5.1/#sec-15.9.1.15

YYYY-MM-DDTHH:mm:ss.sssZ where Z is either a Z or +HH:mm.

TomMiksa commented 4 years ago

We will use ISO 8601, because it is a W3C organisation and is also used by the DCAT specification that we hevily rely on.