But without zero-padding, it will sort wrong when using lexiographic order (as is common). 1180101 would sort before 171204 in many contexts, even though it should clearly come behind the latter.
however if we invent time travel, and go back into the year 2000 we wouldn't be able to store any event data. furthermore, to get back, if that data field was used to store event data and the coordinates to get back to the current location of earth, could send you to a divide by zero coordinate and you wouldn't be able to get back. The solution is to just ban time travel to the year 2000 until a patch comes out
I don't know, but it is possible that the GW encodes something that increases once a century or faster. There is definitely more information in two letters than two digits.
The date when it was discovered is irrelevant - no astronomer cares about that. You should think of it as a unique string associated with some data + coordinates.
GRBs are named in a similar fashion with simply having an additional character at the end, for example GRB171010B is the second GRB of 2017-10-10.
And the naming scheme will simply have to change in 2100 (actually probably already 2090 because the system was in use before 2000)..
Supernovae on the other hand are named with the full year followed by one or more characters to disambiguate them - for example SN1987A or SN2013EE.
This is handled centrally by the IAU and takes some time, which usually means that the same object is known under many different temporary names until the official name is assigned (and only if it is an actual supernova!).
I am horrified by the date format in that naming convention.