The Gitter space for the TSC of the BioCompute Partnership, which is composed of BioCompute standard subject matter experts who serve as the leading authority in technical subject matter relating to the BioCompute standard.
Quick summary of the API chat with Michael @mr-c just now: I think BCO's are under a gravitational pull towards facilitating engaging execution engines programatically. Instead of prescribing a mechanism, an alternative solution would be to enable an authorized API call mechanism through a bearer token in the same APIs that are public without them. I think once that mechanism exists people naturally look for ways to tie them to resources that have to be governed. Michael said this is a very crowded domain and we should thread carefully. I completely defer to him on that space, where CWL surely offers him a unique vantage point. I can only speak for the extraordinary short attention span of people looking for services they can trigger with a HTTP-REST calls :-) .
Hi folks, following our discussions on Thursday, I have created a prototype that replicates biocomputeobject.org using Hugo: https://bco-public-website.netlify.app/
Source code: https://github.com/nanxstats/bco-public-website
Some notes on migration: https://docs.google.com/document/d/1S2C1G7EG--dJkRc-eJCmCwx-ptM7egVzgXtsyQfRKe4/edit?usp=sharing
@carmstrong1gw
@/all
https://biocomputeobject.org is now being served by https://github.com/biocompute-objects/bco-public-website
https://biocomputeobject.org is now being served by https://github.com/biocompute-objects/bco-public-website
@HadleyKing I get the following error message in Firefox when trying to connect:
Web sites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for biocomputeobject.org. The certificate is only valid for the following names: *.netlify.com, netlify.com
Error code: SSL_ERROR_BAD_CERT_DOMAIN
@nsoranzo I think Netlify has not enabled the certificate yet.. @HadleyKing said he would look at it with Chris. Unfortunately before we had
http -> https redirects so many may have linked to that variant.. In the new hosting http://biocomputeobject.org/leadership/#tsc (http) does not yet redirect. And that reminds me to update my oldie picture there!
@nsoranzo you broke the 'leadership' page. :-|
leadership.md to leadership.md2024I fixed it back to leadership.md
@/all
I started an agenda for tomorrow but please feel free to add or modify if you like
https://docs.google.com/document/d/1io5OBfsdEif_nWX-TmA22fz7gayHR1MsEwv2vI_QGBY/edit?usp=sharing
I started an agenda for tomorrow but please feel free to add or modify if you like
https://docs.google.com/document/d/1io5OBfsdEif_nWX-TmA22fz7gayHR1MsEwv2vI_QGBY/edit?usp=sharing
some kind of dark vs light theme setting probably
Should expand https://www.biocomputeobject.org/leadership/#tsc to make a new TSC page that can link to minutes, this chatroom and so on
CWL code of conduct https://github.com/common-workflow-language/common-workflow-language/blob/main/CODE_OF_CONDUCT.md as linked to from https://www.commonwl.org/#Code_of_Conduct
reference from Stian’s ongoing presentation: http://www.researchobject.org/ro-crate, https://www.nextflow.io
forgot the version at the end
This is still a WIP but LMK what you think if you have time to check it out. I will present next week.
Issues and PR welcome!
https://github.com/HadleyKing/bco-tool
Issues and PR welcome!
https://github.com/HadleyKing/bco-tool
Here's my Biocompute Object + RO-Crate presentation, recording I will supposedly give to FDA. https://www.dropbox.com/sh/7ks17lhrqblb0wu/AAAas0o-ngIeXW0TsUuueLp8a?dl=0
Hia, are we meeting in about 10 minutes..? I've updated the agenda but not sure about the webex room
I would name the entry after the IEEE standard and it would be careful to not equate the two names, as is done on the the BCO website