These are both currently defined here as subclass of Resource, but it's unclear how to model them: the bio.tools API already handles databases and tools and we should re-use this so far as possible (an implementation of a database and tool model in the IFB catalogue may not be necessary, or perhaps just a simple one that leverages the bio.tools API).