1. RDA Data Foundation and Terminology (DFT) IG: Introduction Prepared for RDA 6 th Plenary Paris, Sept. 25, 2015 Gary Berg-Cross, Raphael Ritz Co-Chairs DFT IG Goal: Describe a basic, abstract (but clear) data organization model that systemizes the already large body of definition work on data management terms, especially as involved in RDA’s efforts.

2. DFT IG Session Friday 9/25 (11:30-13:00) Agenda Overview of the DFT IG, Case Statement & the Breakout Session- Goals and Plans Gary Berg-Cross Overview of the Ted-T tool, Plans & Maintenance (Raphael/Thomas) Discussion of Liaison relation to other RDA IGs and WGs & Solicitation of ideas for additional Use Cases and candidate vocabulary items MIG and related RDA work Practical policy Research Data Canada (RDC)/Consortia Advancing Standards in Research Administration Information (CASRAI) interactive Glossary Data Publishing Workflow Define the terms describing the expected Quality-of-Service and Data-Lifecycle of their storage infrastructure (INDIGO-DataCloud). Science Europe Working Group on Research Data Legal interoperability Also Provenance Data Fabric General Discussion Discussion of follow on work & Plan for follow up virtual meetings.

3. Among the problems RDA efforts to make data sharing easier Data organizations (DOrg) and ideas about it are all different We are all using different vocabularies, wasting time and misunderstanding each other in a variety of data projects Different DOrgs make data discovery and integration very time consuming, inefficient and thus expensive Different DOrgs prevent us developing maintainable data infrastructure & support software There is a wide impacted across domains, professions, etc. All efforts to integrate and make data open What are the ramifications of not having the problem resolved? Combining data of all sorts across different origins (projects, repositories, disciplines, etc.) is a nightmare and requires a lot of curation and transformation before the actual scientific analysis can start Interoperability remains a challenging goal. What Problem(s) are we trying to help with?

4. Terminology Issue What do we expect from RDA ? Adopt one or build own language? Spend years on terminology debates? Build our own language stepwise, Other - such as cooperate with other efforts?

5. DFT WG: https://rd-alliance.org/groups/data-foundation-and-terminology-wg.html DFT IG: https://rd-alliance.org/groups/data-foundations-and-terminology-ig.html DFT IG Case Statement: https://www.rd-alliance.org/group/data-foundations-and-terminology- ig/case-statement/case-statement.html TeD-T Term Definition Tool: http://smw-rda.esc.rzg.mpg.de/index.php/Main_Page More Information on Products

6. Case Statement and TAB issues Issues are being addressed in an updated version of the Case Statement conferring with outside people in order to effect a proper response. Add to our statement the discussions with people from international efforts like Data Publication Workflow group and members, such as Walter Stewart, of Research Data Canada Science Europe Working Group on Research Data (Peter Doorn) and Paul Millar’s work funded under H202 project INDIGO-DataCloud to define the terms a user-community uses when describing the expected Quality-of-Service and Data-Lifecycle of their storage infrastructure.

7. Prior DFT WG Activities & Accomplishments One of the first RDA WGs Drafted 4 related Model Documents on core work; 1.Data Models 1: Overview – 20 + models 2.Data Models 2: Analysis & Synthesis 3.Data Models 3: Term Snapshot 4.Data Models 4: Use Cases- Work with other RDA WGs on use cases to illustrate data concepts Presented draft work & held community discussions at RDA P1-P3 meeting Participated in cross WG discussions Developed Semantic Media Wiki Term Definition Tool (Ted-T) to capture initial list of terms and definitions for discussions, demo held at P3 (see http://smw-rda.esc.rzg.mpg.de/index.php/Main_Page) Participated in Adoption Day -Common Language Resources and Technology Infrastructure Adopting DFT, DataFed.net, CLARIN etc. Candidate List Evolved to Refined List Tool demo at Plenary 3

8. Portion of Terms in TeD-T http://smw-rda.esc.rzg.mpg.de/index.php/Special:AllPages Digital Inform ation Object A digital item or group of items referred to as a unit, regardless of type or format that a computer can address or manipulate as a single object.

9. Digital Data Management including unregistrered (is a braoder concept) Concept map overview of Core Terms Broadening the Discussion (Stepwise or Scope- wise) Data Management (and use) is broader still Digital Object Management (registered, digital data) Where are datasets???

10. Clarifying Concepts: we discussed organizing model ideas Digital Object (aka Digital Entity) A digital object is composed of structured sequence of bits/bytes. As an object it is named. This bit sequence can be identified & accessed by a unique and persistent identifier or by use of referencing attributes describing its properties. Note Digital Entity definition from X.1255 ITU standard “machine-independent data structure consisting of one or more elements in digital form that can be parsed by different information systems; the structure helps to enable interoperability among diverse information systems in the Internet.” Link data management principles to the actual workflow of generating data Data Management Workflow Structured Object – includes provenance, versioning, and output MD (from PP)

11. Objectives for P6 1.Continue IG discussion and leverage existing work and approach but improve both 1.We are expecting considerable discussion of new requirements coming out of groups nearing completion, but also support as part of adoption. 2.We can also leverage the experience of other IGs as to success factors 2.Focus on facilitating community discussion on core concepts 1.Based on feedback, some curated revisions on definitions and extension of the current synthesis model can be expected to finalize and stabilize the effort for subsequent use. 3.Facilitate approach for definition development 1.Potential adopters will be encouraged at P6 to provide feedback on additional use case scenarios to illustrate what areas of work they plan on using the models and vocabulary for. 2.This will serve to plan work and virtual meetings between P6 and P7.