proposal: time: new predefined layouts

[emre-onal]

Currently, time package have this predefined layouts;

Layout      = "01/02 03:04:05PM '06 -0700" // The reference time, in numerical order.
ANSIC       = "Mon Jan _2 15:04:05 2006"
UnixDate    = "Mon Jan _2 15:04:05 MST 2006"
RubyDate    = "Mon Jan 02 15:04:05 -0700 2006"
RFC822      = "02 Jan 06 15:04 MST"
RFC822Z     = "02 Jan 06 15:04 -0700" // RFC822 with numeric zone
RFC850      = "Monday, 02-Jan-06 15:04:05 MST"
RFC1123     = "Mon, 02 Jan 2006 15:04:05 MST"
RFC1123Z    = "Mon, 02 Jan 2006 15:04:05 -0700" // RFC1123 with numeric zone
RFC3339     = "2006-01-02T15:04:05Z07:00"
RFC3339Nano = "2006-01-02T15:04:05.999999999Z07:00"
Kitchen     = "3:04PM"
// Handy time stamps.
Stamp      = "Jan _2 15:04:05"
StampMilli = "Jan _2 15:04:05.000"
StampMicro = "Jan _2 15:04:05.000000"
StampNano  = "Jan _2 15:04:05.000000000"
DateTime   = "2006-01-02 15:04:05"
DateOnly   = "2006-01-02"
TimeOnly   = "15:04:05"

This proposal is for adding new constants as below;

// dotted
"2006.01.02 15:04:05" // new layout
"2006.01.02 15:04" // new layout
"2006.01.02" // new layout

// hyphened
"2006-01-02 15:04:05" // already exist
"2006-01-02 15:04" // new layout
"2006-01-02" // already exist

[bcmills]

What would the names for these layouts be?

What RFCs specify them, or what notable uses of them exist that would justify putting them in the standard time package?

[dsnet]

See #52746, there doesn't seem to be any wide usage of dot-separated time fields among the top 31 formats used in open-source.

[gopherbot]

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)