Earlier quoted context omitted.
The problem would be how you guarantee the release of the keys at a time in the future. If it was possible to create a "time-locked" blockchain vault would be interesting. I can't see any way of doing that which wouldn't boil down to taking bets on the speed of advances in computing, though. But that might be good enough if the goal is just to ensure it takes "long enough" rather than guarantee a specific amount of t…
As the archiver I first have to publish (once) the public part (key) of a Bitcoin address I own. To archive something I keep a copy (file) of it (it may be an archive storing many files), calculate some digest (let's say SHA512) of the file, then immediately publish the file on my archive-webserver, and its size (amount of octets) and digest an the existing and active blockchain (in this case: Bitcoin). As a courtesy…
1. Your suggested approach handles provenance for data you yourself arranges to "open up" in the future.
2. Additionally people may want to ensure the longevity of the data - this is "easily" done by simply archiving all referenced archives multiple places.
3. Some people wants to ensure important data eventually will get released, but don't dare / can release it now and/or worry that they will be prevented from releasing it in the future (be that for a nefarious reason, or simply because you might die of natural causes before you get a chance).
The last case is what I meant by a "time locked" system. Being able to archive something now even though you're not prepared to publish it now in a way that doesn't require you to take complicated steps to guarantee that "someone" is trusted to release the right keys would be powerful.
What you suggest also have value, it just covers a different set of use cases.