Also this is all arguably just props up anb insufficient solution.
For me at least, the only reason I care about the date is that it's the best *indirect* indicator of whether something say, works with jack or lv2 or what have you.
An ontology that would be far more useful than the indirect reporting of a date would be to (and some of this is done on the site)
list the types of inputs (midi, jack, etc) and outputs of a program
Whether they are meant for low latency "live" performances or not
List what kind of plugin standards the thing works with
Include, if possible, similar programs that may be more difficult or less difficult to learn, for people of various dedication and skill.
The "ontology" part of this is important because ideally there could be a "web app" where you could string your stack together of different applications.
These could also be used for demonstration purposes to help other people understand the various ways things can fit together.
Because in practice, at least I have spent a lot of time in trying to learn what some software is good at, what it does for me, and how I could possibly connect it with everything else.
These things are relatively simple to communicate but currently as far as I know, isn't happening.