A clearer definition of "resources"

[bianchini88]

Description

Refer to https://rdmkit.elixir-europe.org/tool_resource_update

Whilst it is understandable what a tool is, the term "resource" is considerably more vague and open to interpretations. The possibility of linking with FAIRsharing would make one think that "standards", "databases", and "policies" are all to be considered as "resources" and should be in the yml file. In the case of standards, this is implemented e.g. for MINSEQE here. The same approach is, however, not implemented in many other pages (e.g. MIxS here).

Another interpretation of the FAIRsharing linking would be to use it for "standards", "databases" and "policies" which are supported by the various "tools" or "resources", in which case metadata standards should not be in the yml file. I am sure other interpretations are also possible.

Personally, I am in favour of the first interpretation, as it would provide richer information and the possibility of linking towards both the webpage of the "resource" and the registries (FAIRsharing, bio.tools, TeSS). One could also consider having other categories that behave as "tools" but use other icons (it would be weird to have that wrench icon close to e.g. a database or policy).

Independently from the paragraph above, we should clarify and be more explicit about what is a "resource" (i.e. what has to go in the yml file and what does not).