Re: [Nut-upsuser] RFC - Propose to express dates using ISO 8601 when possible

2021-09-19 Thread Roger Price
On Sun, 19 Sep 2021, Jim Klimov wrote: Hello all,   Roger's point about ISO vs. RFC "original" spec accessibility sounds valid, since most of the ISO 8601 descriptions I've seen were re-tells - in wiki, date-parsing tools/libs docs, etc. Used it for years and did not realize :)   I revised

Re: [Nut-upsuser] RFC - Propose to express dates using ISO 8601 when possible

2021-09-19 Thread Jim Klimov via Nut-upsuser
Hello all, Roger's point about ISO vs. RFC "original" spec accessibility sounds valid, since most of the ISO 8601 descriptions I've seen were re-tells - in wiki, date-parsing tools/libs docs, etc. Used it for years and did not realize :) I revised and logged some thoughts at

Re: [Nut-upsuser] RFC - Propose to express dates using ISO 8601 when possible

2021-08-25 Thread Roger Price
On Tue, 24 Aug 2021, Arnaud Quette wrote: Le ven. 20 août 2021 à 17:38, Roger Price a écrit : On Fri, 20 Aug 2021, Jim Klimov via Nut-upsuser wrote: > It is a bit unclear what "or otherwise and Combined date and time > representations" means. An example of ISO 8601 date

Re: [Nut-upsuser] RFC - Propose to express dates using ISO 8601 when possible

2021-08-24 Thread Arnaud Quette via Nut-upsuser
Le ven. 20 août 2021 à 17:38, Roger Price a écrit : > On Fri, 20 Aug 2021, Jim Klimov via Nut-upsuser wrote: > > > It is a bit unclear what "or otherwise and Combined date and time > > representations" means. An example of ISO 8601 date representation (one > of > > many offered by the standard)

Re: [Nut-upsuser] RFC - Propose to express dates using ISO 8601 when possible

2021-08-20 Thread Roger Price
On Fri, 20 Aug 2021, Jim Klimov via Nut-upsuser wrote: It is a bit unclear what "or otherwise and Combined date and time representations" means. An example of ISO 8601 date representation (one of many offered by the standard) "or otherwise"? Which combined date and time would we take - e.g.

Re: [Nut-upsuser] RFC - Propose to express dates using ISO 8601 when possible

2021-08-20 Thread Jim Klimov via Nut-upsuser
Dittoing what I wrote in PR comments: It is a bit unclear what "or otherwise and Combined date and time representations" means. An example of ISO 8601 date representation (one of many offered by the standard) "or otherwise"? Which combined date and time would we take - e.g. MMDDTHHMMSSZ

Re: [Nut-upsuser] RFC - Propose to express dates using ISO 8601 when possible

2021-08-20 Thread Matus UHLAR - fantomas
Hello, On 20.08.21 15:01, Roger Price wrote: Will this apply to variables | ups.date | Internal UPS clock date | ups.mfr.date | UPS manufacturing date | ups.test.date | Date of last self test | battery.date | Battery change date (opaque string) | 11/14/00

Re: [Nut-upsuser] RFC - Propose to express dates using ISO 8601 when possible

2021-08-20 Thread Roger Price
On Fri, 20 Aug 2021, Arnaud Quette via Nut-upsuser wrote: Hi all, I've made a pull request in that sense: https://github.com/networkupstools/nut/pull/1076 I'll follow-up with applying to some drivers and propose more PRs. As usual, comments and feedback welcome. Will this apply to variables

[Nut-upsuser] RFC - Propose to express dates using ISO 8601 when possible

2021-08-20 Thread Arnaud Quette via Nut-upsuser
Hi all, I've made a pull request in that sense: https://github.com/networkupstools/nut/pull/1076 I'll follow-up with applying to some drivers and propose more PRs. As usual, comments and feedback welcome. cheers, Arno ___ Nut-upsuser mailing list