Meeting notes: https://docs.google.com/document/d/1vMhigtnyWoR0g_nEAK3AszNAL7Mvw_V6TqB9WkVdTGU/edit?usp=sharing v3 Questionnaire To be clear, this is not the Matrix. These are questions that prompt the user to either supply links to resources, or to choose to existing resources for reuse. In turn, these links to resources become the rows in the Matrix. Communities are the "Columns". https://docs.google.com/spreadsheets/d/1v-WZHwiByxe-3NCXJ5G2uQkhVjXjH49CCavPv6dYT6o/edit?usp=sharing ----- 1.0 What we did in this meeting: 1.1 Agreed that there is significant overlap between the “FAIR Data Train” approach in the 3 communities: PHT IN; the Food Systems IN; and the work at ZIN. 1.2 Reviewed the FAIR Convergence Matrix approach (slides https://osf.io/w3f67/ ) and the potential utility of the FAIR Implementation Profile (draft document https://osf.io/c4fth/ ) 1.3 Each of the 3 communities agreed to try and complete the v3 questionnaire, creating a FIP for each community (and possibly sub-communities) 1.4 Run an initial analysis over the 3 FIPs, seeking overlaps and opportunities to maximize reuse of standers/technology and interoperation. 1.5 Agreed to investigate a joint research project that “jumps tracks” and combines resources from Heath trains and Food trains (for example, agricultural pesticide use and human health impacts). 1.6 Agreed to create a presentation for the GO FAIR IN Meeting, Hamburg, Jan 23-24. ---- 2.0 ToDos for the Trains: 2.1 Define your community. We had a very interesting discussion yesterday. Pragmatically, a "FAIR community” or a “FIP community” could be defined as all those who agree on a particular FIP (no matter how they might cross-cut traditional definitions of community). We also concluded that it might be useful to form sub-communities (with clear relations to each other) and that these may choose to address only a limited subset of the questionnaire (e.g., only domain-specific elements). Between now and Hamburg we should collectively choose how to profile (metadata) and represent (nanopublications, RDF) the community. 2.2 Complete the v3.1 questionnaire. The current document (google sheet) is here: https://docs.google.com/spreadsheets/d/1ndkAxbQ0T7klq4oPLNxhmnZo1bB7qmKYcMfI4J63xPw/edit?usp=sharing Note: between now and December 18, this document is subject to slight editorial revisions and potential elaboration (see slide 21). When the document revision is completed, we will “freeze” and notify you. The frozen document will then be used in preparation for Hamburg. 2.3 FAIRsharing registration. As you accumulate a list of “digital resources” that compose your FIP, be prepared to register the “standards, data, and policy” elements in FAIRsharing, if they are not already there. FAIRsharing will keep a metadata description of the resource and issue a DOI. ------ 3.0 ToDos for the Matrix: 3.1 The Matrix team will be refining the v3 questionnaire until December 18. 3.2 The Matrix team will help to create nanopublication / RDF for FIPs. 3.3 The Matrix team will help analyse the resulting FIPs (including grafo visuals if possible) 3.4 The Matrix team will help prepare the reporting / presentation in Hamburg. Time frames: From today, we have 5 weeks. Next week: we will update you on the revised v3 questionnaire and final draft of the FIP paper. Week January 6: First attempt at questionnaire complete. We could stage a meeting in Leiden for comparing FIPs and discussion. Week January 13: Revision / elaboration of FIP. RDF and analysis. January 21-22: optional hackathon to tie up loose ends and polish presentation. January 23-24: IN meeting