Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Agree with Roger, we have a documented, unambiguous definition of "Anywhere on Earth".
If we want to use a date format that is not ambiguous, ISO 8601 (YYYY-MM-DD) is not it. YYYY-MM-DD is as equally "ambiguous" (and confused) as mm/dd/yyyy. An unamibous format would be to spell out the date using the full name of the month e.g. "February
22, 2022" which is unambiguous (in this time-space reference frame and calendar system), as are variations such as "Feb 21, 2022" or "22-Feb-2022" and so on. Just pointing out the facts.
But we digress. (and yes, I picked February 22, 2022 for my examples because it's hard to misinterpret this in any format and I like irony).
🙂.
We could just do as we have for decades, relying on the context-sensitive adaptive grey matter of our attendees to parse based on context, e.g. the "March Plenary" will occur in only 1 month out of 12.
Why not?
Ben
From: ***** IEEE 802 Executive Committee List ***** <STDS-802-SEC@listserv.ieee.org> on behalf of Roger Marks <r.b.marks@IEEE.ORG>
Sent: Wednesday, February 23, 2022 3:26 PM To: STDS-802-SEC@LISTSERV.IEEE.ORG <STDS-802-SEC@LISTSERV.IEEE.ORG> Subject: Re: [802SEC] reminder - 802 meeting fee increases friday at 11:59PM UTC, not AoE Andrew,
I fully agree about the date format. I disagree that AOE is ambiguous. I created AOE so that "the deadline has not passed if, anywhere on earth, the deadline date has not yet passed.” It’s documented here. Cheers,
Roger
On Feb 23, 2022, 3:34 PM -0700, Andrew Myles (amyles) <00000b706269bb8b-dmarc-request@listserv.ieee.org>, wrote:
To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1 To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1 |