Consider introducing a fake format info document for a generic programming language

[bansp]

This stems from issue #265 .

Consider adding an information file to our repository of Data Deposition Formats whose long name would be something like "Generic Programming Language Source File", abbreviation: ProgLang, ID: fProgLang . It would explain that a programming language is a broad notion that denotes tools for various functions, among others expressing, creating (by a.o. joins) or styling data, and therefore files containing programming language source code may also be deposited, at least in the category of "Tool Support". In most cases, the actual data format for a programming language source will be plain text, unless it's e.g. XML (which, all in all, is a specialisation of plain text...).

A recommendation by a centre to use a "programming language" in the domain of "tool support" would be a classic case of a coarse-grained recommendation that relies on the <comment> section for fine tuning, and it's the comment section that would say that the given centre recommends using Python for one thing, but JavaScript for some other. (And will accept XSLT, R, and Postscript, just to throw some extras into the soup...)

Would that feel as a gross hack? Can we do something else to capture the existing and not-yet-existing programming languages in more or less a single place?

One alternative would be to say that this sort of information should be located in the <info> section for the centre.