Data Fabric Plenary Session

Data Fabric P5 Plenary Session   

DFIG Co-Chairs: Rob Pennington, Peter Wittenburg, Yunqiang Zhu

This Data Fabric Interest Group (DFIG) plenary session will present the Data Fabric in broad terms to all interested WG and IG experts to gather their input and to plan joint activities. The session will be open to anyone interested in RDA. In preparation, a number of WG/IG chairs were contacted about this session focusing on the issues that we are facing in our scientific labs and centers when creating, managing and processing data as part of our daily job. It is important to sharpen the role of DFIG in the landscape of WGs and IGs and discuss further steps on how to improve already fruitful interactions. We see DFIG as a platform for interested experts to discuss how activities with a close relation to the daily scientific data machinery can contribute to an overall framework and how the framework needs to be structured to cover their needs and approaches.

This session has a number of goals:

  • Explain the DF approach to the other WGs/IGs and gather reactions and ideas for structured interactions, test beds, etc. In this session we expect to spend much time on explanations and Q/A on comments and questions from the audience, since we will have many new participants who were not involved in earlier discussions.
  • Discuss and comment on the White Paper on Data Fabric to fine-tune DFIG activities.
  • Ask all interested groups to locate themselves on the landscape relevant to the scientific data machinery, where they see close relations that need to be discussed, which components/services they see as essential and whether the ideas so far fit with the needs.
  • Invite experts from community directed groups to explain their expectations and how they would seem to fit in the landscape.
  • Discuss what needs to be done to let all activities move forward in a synchronized way.
  • TAB chairs are invited to contribute to this discussion.

 

The planned agenda for this session leaves sufficient space for discussions and interactions.

Agenda for Monday 9 March DFIG Session

Data Fabric Plenary Session Agenda
10.15 Introduction to DFIG Intentions and Approach Rob
10:22 Use Cases: Components and Services Peter
10:30 Use Cases: template and intentions Zhu
10:35 Open Discussion  
10:55 Wrap up, next steps Peter, Rob, Zhu
11:00 Session Ends  

 

                

 

 

 

 

 

Appendix

For outreach and training purposes RDA Europe created recently an "impact" flyer which indicates graphically how the results of the first WGs all fit into the "data creation and processing" machine which we are all using. However, this may be inefficiently organized when working across boundaries, such as institutes, projects, countries, or disciplines. The graphic may stimulate discussions, since it tries to schematically indicate the continuous creation and processing loop where existing data is being put together in various ways to create new data. Processing can be of various types: management and preservation operations, data analytics operation, etc.

RDA Data Fabric IG (DFIG): Use Case Description Template

Rob Pennington, Peter Wittenburg, Yunqiang Zhu

Proper Use Case descriptions are essential for the DFIG ...(bottom up, based on existing expertise, abstraction, etc.).  Refer to the White Paper for background info and the Wiki where to deposit Use Cases.

1. Scientific Motivation and Outcomes (max. 0.5 pages)

Provide a short summary of the scientific or technical motivation for the use case. What would be the best possible outcome and why?

2. Functional Description (max. 1 page)

Give at least one diagram that indicates the overall structure/architecture of the data creation and consumption machinery that is being used in the lab/infrastructure. Describe in simple words the functioning of the machinery.

3. Describe essential Components and their Services (max. 1 page)

Describe the most essential infrastructural components of the machinery and the kind of services they offer. These descriptions don't have to be comprehensive.

4. Describe optional/discipline specific Components and their Services (max. 1 page)

Describe the most optional infrastructural components of the machinery and the kind of services they offer. These descriptions don't have to be comprehensive.

5. Describe essentials of the underlying Data Organization (max. 1 page)

Describe the most important aspects of the underlying data organization and compare it with the model outlined by DFT.

6. Indicate the type of APIs being used (max. 1 page)

Describe the most relevant APIs and whether they are open for being used.

7. Achieved Results (max. 0.5 pages)

Describe the results (if applicable) that have been achieved compared to the original motivation.