Such a representation naturally avoids the Y2K38 problem, and could go beyond Y10K. It's traditional in Windows and DOS (neither of which have the Y2K38 problem) to store timestamps as a structure of fields.
The other things you noted I agree with, however.
Plus, it's unambiguously human readable, for users, bystanders, platform developers, everyone. There's a useful usability principle in there.