Use date-time (RFC 3339) instead of XML dateTime #390

mmccool · 2022-08-08T14:39:09Z

in the XML definition of dateTime, the timezoneOffset is optional, which makes it ambiguous
The TD spec uses dateTime but adds an assertion to follow RFC3339, in which timezoneOffset is mandatory
The Discovery spec follows this approach to be consistent
However, we really should update the TD and Discovery ontologies to use date-time (following RFC3339 instead) and avoid the current weird patchwork

* updates * include VIAMEE results * absolute time, implied UTC * date-time Changed to require conformance with RFC3339, which makes timezone offset mandatory. Ideally we would get rid of dateTime altogether, follow up in #390

* updates * include VIAMEE results * absolute time, implied UTC * date-time Changed to require conformance with RFC3339, which makes timezone offset mandatory. Ideally we would get rid of dateTime altogether, follow up in w3c#390

mmccool mentioned this issue Aug 8, 2022

Absolute time in dateTime format #389

Merged

mmccool mentioned this issue Aug 8, 2022

Registration information timezone handling #321

Closed

mmccool added the defer to Discovery 2.0 label Aug 22, 2022

mmccool removed the defer to Discovery 2.0 label Mar 4, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Use date-time (RFC 3339) instead of XML dateTime #390

Use date-time (RFC 3339) instead of XML dateTime #390

mmccool commented Aug 8, 2022 •

edited

Loading

Use date-time (RFC 3339) instead of XML dateTime #390

Use date-time (RFC 3339) instead of XML dateTime #390

Comments

mmccool commented Aug 8, 2022 • edited Loading

mmccool commented Aug 8, 2022 •

edited

Loading