bio-tools / biotoolsSchema

biotoolsSchema : Tool description data model for computational tools in life sciences
Creative Commons Attribution Share Alike 4.0 International
36 stars 12 forks source link

Binaries, binary package, Source code, Source package ... OTT? #164

Open joncison opened 4 years ago

joncison commented 4 years ago

To have Binaries and Binary package, also Source and Source package - in Downloads - to me seems to make unnecessary distinctions, and thus is OTT.

I propose we just manage with Binaries and Source code.

Any objections @hansioan @matuskalas @hmenager ? If so, pls. explain why needed.

joncison commented 4 years ago

Go with:

BUT retain Source and Binaries

matuskalas commented 4 years ago

Probably switch Package (Conda) with Package (Bioconda). See also #158

joncison commented 4 years ago

Go with this for now:

Can always extend with more specific concepts for packages, if / when required.

joncison commented 4 years ago

@matuskalas @hansioan again, we can follow the pattern in future:

i.e. move Software package out of download enum into its own element

joncison commented 4 years ago

@bgruening @hmenager is (or likely will in the next 6 months, say) the "ecosystem" be at a stage that its worthwhile remodelling biotoolsSchema for softwarePackage as per suggestion above (whilst leaving Binaries and Source code as-is (see above) ?

See also https://github.com/bio-tools/biotoolsSchema/issues/158.

cc @matuskalas @hansioan

joncison commented 4 years ago

hi @bgruening @hmenager cc @matuskalas

could you please advise re remodelling of biotoolsSchema for software packages, to better handle data integration for the "ecosystem" as per thread above? Me and @hansioan are beginning to look at schema-related things this week and might be able to include the changes in the next release, which is coming soon. Thanks!

joncison commented 4 years ago

hi @bgruening @hmenager cc @matuskalas - me and @hansioan are going ahead with release 3.3.0, so if you have suggestions for above (please let's have them), they can go into a subsequent release. Ta!