The Request for Information suggests a central role for Data Commons and therefore FAIR interoperability using GraphQL. We're experimenting on this using Genomic Data Commons (GDC) REST API.
A while back we looked at this git flow article as a model for development going forward. It helped clarify development and allowed group work on a project with minimal dead branches and conflicts. Now there is a git-flow extension that makes our workflow even easier. If followed correctly, this simplifies maintenance and hotfixes in the future. That, combined with some awesome alternative shells, make for a great opportunity for us.
Tableau interactive, www.theinformationlab.co.uk/tabcommunicate - "TabCommunicate was created for one simple purpose…to encourage everyone to code, to create awesome apps & scripts to work with the Tableau Server’s REST API."
Let's all pick a GraphQL endpoint and play with it for the duration of the session.
A. Choosing a BaaS endpoint:
B. Let's Query them
We'll use graphqlbin.com to keep track of how each of us solves the following challenges
GraphQL design, in-depth discussion - www.youtube.com/watch?v=Oh5oC98ztvI - it emerged as the solution for a death-or-live challenge at Facebook towards reliance on web computing. Remember "Mark Zuckerberg: Our Biggest Mistake Was Betting Too Much On HTML5"? It wasn't :-), as the video shows, he was just ahead of his time and Facebook research.