I disagree that these particular questions are "too localized." The Stack Exchange UI is not very good at explaining what this reason means.
"Too localized" should be used for very tiny geographic regions or vanishingly small periods of time. It is used when a question cannot possibly be answered because nobody participating in the site is likely to know the answer, and even if it were answered, nobody else would care.
For me, the canonical "too localized" question would be:
Why is there a green Honda Civic parked out in front of my house?
This is too localized because:
- Who cares?
- Is it even still there? Go check.
- What are the chances that this question could ever be answered in a way that would benefit anyone else?
- Now is it there?
I have been dismayed to see knee-jerk closing of questions as "too localized" throughout Stack Exchange simply because they mention a time span or because they mention a geography. I think some people have misunderstood this close reason to mean ... "anything time-bound or location-bound must be closed."
In this particular case the Sklivvz reasonably thought that the questions are too localized in time because they reflect constantly changing knowledge or rapidly changing events.
This would be a valid concern, however,
Stack Exchange was specifically designed to adapt well to rapidly-changing events. That's why it has Wiki features. Like Wikipedia, we are not content to wait for the first historians to write the book. We're happy to answer questions in the context of what is true today, knowing that as facts change, the answers can easily be edited or replaced.