Regarding max and version metadata for an IDE library – for example, the Processing IDE (PDE) accesses a central listing of contributed libraries and tools for that exist in multiple versions and have updates – but having varying compatibility with Processing 2, 3, 3.4 / 3.5 etc.
Contributions Manager (analogous to the Inform “Public Library” tab) consults a list of properties .txt files to build its listings and indicate which resources are available / recommended for a given version of the software.
So, for the Rosetta Examples for Processing library, there is a simple INI-style metadata file, rosetta_examples_p5.txt:
name=Rosetta Examples for P5
sentence=Common coding tasks in Processing (Java mode) from the Rosetta Code chrestomathy website.
and this txt file URL silently corresponds (same name, same path) to a library file with a different extension, rosetta_examples_p5.zip (the equivalent of the .i7x).
If the author doesn’t specify a max Processing version (typical), then it is 0 – if at some later point Processing 4 comes out and the example set doesn’t work anymore, that max can be added without changing the library release number.
Also note in this example, no min is specified – because it is an example set. Some of the material works with Processing 1, 2, and 3, some with 2 & 3, and some only with 3, so the responsibility is on the user. But most library authors do specify a min because they don’t want support requests from something that won’t work.