change (or add to) the representation of galaxy services as relations between entries

[hmenager]

Once again this comes from the discussion of https://bio.tools/workflow4metabolomics with @lecorguille and @joncison.
Currently there is a link type of "galaxyService" for bio.tools entries, but this link does not enable cross-entry semantics such as specifying that a Galaxy instance deploys a tool, or that a tool is deployedBy a Galaxy instance. In the case of Workflow4Metabolomics, we therefore used uses and usedBy relations instead.
Could we add deploys and deployedBy relations?
cc @hansioan

[matuskalas]

This is back-and-forth AGAAAIN ......

Of course we need it. We always needed it. Many of us always knew we needed it.

And we need it a bit more generic, also for tools that provide access to other tools via web APIs, e.g. data sources in Galaxy, or external Web services in Jalview, thus deploys is too restricted.

We've many times agreed on something like provides(AccessTo), whatever we called it, and the corresponding inverse. And they were afterwards always removed by ad hoc project management decisions. Could we please stop wasting the bulk of the project time on such back-and-forth changes?

Btw., whenever we introduce it yet again, it will mean I have to redo my onerous curation from the beginning of January 2020, and all further curation I'll do in the next weeks & months. It's all about Galaxy and Debian tools.

[hansioan]

If there are uses cases supporting this, I am all open to have it.
My only request is to carefully consider what to add (I prefer additions to changing things) so that we don't come back in 6 months and remove/change it back.

[joncison]

So this is what we have currently, which was intended to be general / a foundation:

• isNewVersionOf / hasNewVersion - _The software is a new version of an existing software, typically providing new or improved functionality.
• uses / usedBy - _The software provides an interface to or in some other way uses the functions of other software under the hood,e.g. invoking a command-line tool or calling a Web API, Web service or SPARQL endpoint to perform its function.
• includes / includedIn - A workbench, toolkit or workflow includes some other, independently available, software.

Let's please @hmenager @matuskalas @hansioan agree on a revision - which (retains but) extends the above. And try to be very conservative - include only things we're certain about . Bear in mind it's a de facto mini-ontology represented as a flat enum, so the semantics need to be precise, to avoid confusion / misuse.

To me, deploys sounds like a specialism of includes and provides sounds very much like uses as defined.

Please suggest some possibilities with definitions below.

[joncison]

PS. see also these old threads (#107 and #106) which include some of your older notes on this subject @matuskalas

[joncison]

Hi @matuskalas @hmenager
Me and @hansioan will begin work on schema-related things, so if you have some concrete proposals (beyond what was already said above) pls. let us know here so we can consider it for next biotoolsSchema revision.

Thanks!

[joncison]

@matuskalas @hmenager ... me and @hansioan are going ahead with biotoolsSchema 3.3.0 - so if you have suggestions for above, they can be included in a subsequent release.

[hechth]

@joncison @hmenager @matuskalas @hansioan So what's the current status on this? Just came across that and it doesn't seem like this problem is actually solved. Also, there are multiple layers to it - one is how to represent the Galaxy tool(s) for a package and the other is the availability of the tool on a specific server.

[hechth]

@hechth for self reference