1 of 54

12-14 November 2024, Costa Rica and Online

RDA 23rd Plenary Meeting (RDA P23) | Sustainable Science

Vocabulary Services IG �(aka VSSIG, Vocabulary and Semantic Services IG): �All About Terms and Ontologies (You Can Help!)

RDA 23rd Plenary Meeting

www.rd-alliance.org

2 of 54

Agenda

  • VSSIG Introduction for new participants – 10 minutes (Alexandra Kokkinaki-remote)
  • I-ADOPT: Latest achievements and Activities – 10 minutes (Gwen Moncoiffe in person)
  • Metadata Task Group – 10 minutes (Clement Jonquet-remote)
  • FAIR Mapping WG Activities
    • SSSOM - 7 minutes (Nico Matentzoglu remote)
    • FAIR mapping group updates - 3 minutes (Yann Le Franc in person)
  • Working Session: Identifying and Prioritizing Evaluation Methods for Choosing Terms and Ontologies – 50 minutes (All of Us)

RDA 23rd Plenary Meeting

www.rd-alliance.org

3 of 54

Housekeeping for all attendees

Please complete the table Attendee Check-in to indicate your attendance in the Collaborative Notes: here

Reminder: The session is being recorded

There will be time for questions after each talk, so please:

Participants in the room ask questions using the microphone

Virtual participants ask questions on the chat starting with @nameOfPresenter and following with your question

RDA 23rd Plenary Meeting

www.rd-alliance.org

4 of 54

VSSIG group: Who we are

by Alexandra Kokkinaki and the other VSSIG co-chairs:

Yann Le Franc, John Graybeal, Juliane Schneider

RDA 23rd Plenary Meeting

www.rd-alliance.org

5 of 54

Semantic artefacts and FAIR guiding principles

I2: (Meta)data use vocabularies that follow the FAIR principles

task forces, groups and projects focusing on

#semantic interoperability #semantics#ontologies #vocabularies #semantic artefacts

RDA 23rd Plenary Meeting

www.rd-alliance.org

6 of 54

The VSSIG past & present

  • Created in 2015

  • 4 co-chairs: Yann Le Franc (2017), John Graybeal (2017), Alexandra Kokkinaki (2020), Juliane Schneider (2022)

RDA 23rd Plenary Meeting

www.rd-alliance.org

7 of 54

Vision

Our vision is to harmonize our ways of working/current practices with Semantic Web technologies through Knowledge and Expertise exchange across all domains.

Join the group: https://www.rd-alliance.org/groups/vocabulary-services-interest-group/work-statement/

RDA 23rd Plenary Meeting

www.rd-alliance.org

8 of 54

Groups

Working group

  • I-ADOPT - B. Magagna/G. Moncoiffé/M.Stoica/A.Derajavu

Task Groups

  • Minimum Metadata Task Group - C. Jonquet
  • Terms and Concept Recommendations - J. Graybeal

BoFs

  • BoF – FAIR Mappings – Let’s start working

RDA 23rd Plenary Meeting

www.rd-alliance.org

9 of 54

Collaboration

Focus on collaboration

  • Other RDA Working Groups and Interest Groups
  • With you
  • With other projects

where semantics are involved

RDA 23rd Plenary Meeting

www.rd-alliance.org

10 of 54

I-ADOPT: Latest achievements and Activities�

Gwenaëlle Moncoiffé

12-14 November 2024, Costa Rica and Online

RDA 23rd Plenary Meeting (RDA P23) | Sustainable Science

11 of 54

Outcome:

Motivation:

  • Addressing the “I” of FAIR
  • Enabling interoperability between existing terminologies
  • Promoting the use of FAIR terminologies to annotate research data with well identified, unambiguous and machine-readable vocabularies

Led by a core group made of 4 co-chairs (Barbara Magagna, Gwenaëlle Moncoiffé, Anusuriya Devaraju and Maria Stoica) plus Sirko Schindler and Alison Pamment, with regular contributions from many others.

InteroperAble Descriptions of Observable Property Terminologies”

The RDA I-ADOPT Working Group�Active work: 2019-2021 - Status: Maintaining Deliverables

12 of 54

  1. Descriptions should be human and machine-readable
  2. Descriptions should be explicit and sufficient
  3. Use of semantic artefacts
  4. Use of I-ADOPT ontology
  5. Reuse of I-ADOPT aligned terminology

RDA I-ADOPT recommendations�DOI: 10.15497/RDA00071

13 of 54

The I-ADOPT Ontology �https://w3id.org/iadopt

14 of 54

  1. The I-ADOPT Challenge
  2. Regular meetings to discuss implementations, priorities
  3. On-going work of I-ADOPT adoption at RI levels as part of European projects >> Opportunities to test interoperability (e.g. Envri-Hub-Next)
  4. Interactions with FAIR mappings WG
  5. Interest in I-ADOPT as an OGC standard
  6. Service development for annotation (e.g. PARC, FAIR2Adapt, NFDI4Earth, based on rag - retrieval augmented generation- LLM approaches and NLP techniques)
  7. Activities related to methods and protocols

Highlights of latest activities�

15 of 54

When? Challenge 1 (16-29 Sept 2024), Challenge 2 (14-18 Oct 2024)

How many participated? 24 people/16 groups/different domains, but all data scientists

What was the purpose?�Reveal similarities and differences in the way different people use the I-ADOPT Framework to describe the same set of variables (30 variables in total)

What are the outcomes?

  • Opportunity to improve the framework and guidelines
  • Provide insights to develop a semi-automated I-ADOPT variable annotation service

The I-ADOPT Variable Modeling Challenge�https://i-adopt.github.io/challenge.html

16 of 54

First Challenge:

provided variables: 30

counted variables: 10 best

winner principle: highest scores

challenge period: two weeks

analysis: the more people model the better is their result

Second Challenge:

provided variables: 10 (highest variance)

counted variables: 5 of high quality > 12pts

winner principle: all with 5 quality variables

challenge period: 5 days

Add. material: DO’s and DON’Ts

analysis: Modelling tips help to make less errors, but the result is better the more is modelled

First versus Second Challenge

17 of 54

The I-ADOPT Variable Modeling Questionnaire�Answers from the participants

“some terminologies don’t resolve”

“providing meaningful labels”

“several options to model”

Why is I-ADOPT useful?

  • FAIRify data
  • FAIRify metadata
  • Manage semantic artefacts
  • Manage data repositories
  • Harmonise digital objects
  • Make data reusable
  • Integrate data

18 of 54

I-ADOPT Core team:

- Barbara Magagna (GO FAIR Foundation, NL)

- Gwenaëlle Moncoiffé (National Oceanography Centre - British Oceanographic Data Centre, UK)

- Anusuriya Devaraju (CSIRO, AU)

- Maria Stoica (University of Colorado, Boulder, US)

- Sirko Schindler (German Aerospace Center, DE)

- Alison Pamment (Centre for Environmental Data Analysis/Sience and Technology Facilities Council, UK)

External reviewers:

- Markus Stocker (TIB - Leibniz Information Centre for Science and Technology, GER)

- John Graybeal (Information Technology Consultant, US)

- Rob Atkinson (Open Geospatial Consortium, AU)

The I-ADOPT Challenge: Reviewer Team�

19 of 54

Challenge material:

- An introduction video to the I-ADOPT Framework

- A step-by-step guide for creating an I-ADOPT compliant variable description (video)

- Instructions for submitting modeled variables including participation and scoring rules (slides)

- The list of variables to be selected

- A questionnaire for background information about participants

Submission formats based on templates:

- human readable: Excel, text�- machine-readable: nanopublication, turtle

The I-ADOPT Challenge: Material prepared

20 of 54

Evaluation sheet includes:

  • list of variables, list of participants
  • scoring reference, criteria
  • all modelled variables as provided by Challenge participants and represented in Excel and evaluated accordion to the criteria
  • all modelled variables by core teams
  • agreed models and scoring results

I-ADOPT Challenge variables visualzed in the I-ADOPT Variable Examples repository

GitHub issues for discussing variable models

The I-ADOPT Challenge: Results

21 of 54

First Challenge:

1st prize - €400 plus 2 virtual attendance fees for RDA 23: �Anne Fouilloux and Jean Iaquinta (212.75 points)

2nd prize - €300 plus 1 virtual attendance fee for RDA 23: �Andrea Tarallo, Martina Pulieri, Christina Di Muri, and Jessica Titocci (208.5 points)

3rd prize - €200: �Jörg Klausen, Morgan Silverman and Gao Chen (170.6 points)

The RDA TIGER Programme sponsored the attendance fees for the winners.

Qualified for the Second Challenge getting each €100:

Margherita Martorana, Samantha Blakeman, Petra ten Hoopen, Naouel Karam, �Juliana Menger, Saurav Kumar, and Norbert van Dijk

The I-ADOPT Challenge: Winners!

22 of 54

Metadata Task Group (Clement Jonquet)

Metadata for Ontology Description and Publication Ontology

Main focus of this task group was/is to develop MOD, as standard vocabulary to describe semantic artefacts.

https://github.com/FAIR-IMPACT/MOD

Work done since 2022 in the context of the EOSC project FAIR-IMPACT

RDA 23rd Plenary Meeting

www.rd-alliance.org

23 of 54

MOD

  • Presented several time at RDA VSSIG (MOD 2)

  • Extension / profile of DCAT2

  • To describe any type of semantic artefacts (from metadata schemas to terminologies, thesauri, ontologies, etc.)

RDA 23rd Plenary Meeting

www.rd-alliance.org

24 of 54

MOD example

RDA 23rd Plenary Meeting

www.rd-alliance.org

25 of 54

Now MOD v3.2

  • Multiple design issues discussed and decided in MOD 3

  • Now properties available to describe each objects including the mod:SemanticArtefactCatalog

  • FAIR-IMPACT’s M4.3 - Specification of semantic artefact description

https://dx.doi.org/10.5281/zenodo.10725304

RDA 23rd Plenary Meeting

www.rd-alliance.org

26 of 54

MOD-API - specification of an API for semantic artefact catalogues

  • FAIR-IMPACT’s D4.3 - Specification of shared metadata description of semantic artefacts and their catalogues including common reference API
  • https://dx.doi.org/10.5281/zenodo.12579779

  • https://github.com/FAIR-IMPACT/MOD-API/
    • Describes the HTTP calls to implement so that multiple SACs can speak the same language
    • Relies on RDF, OWL, SKOS and MOD too to specify the objects to return
    • Objects being described with MOD listed metadata properties or more….

RDA 23rd Plenary Meeting

www.rd-alliance.org

27 of 54

A Simple Standard for Ontological Mappings 2024:

A quick guide for getting started with publishing better entity mappings @ RDA’s 23rd plenary

Contributors: Alasdair Gray, Alex Wagner, Amelia L. Hoyt, Andrew Williams, Anita Caron, Anne Thessen, Benjamin M. Gyori, Bill Baumgartner, Cassia Trojahn, Charlie Hoyt, Chris Mungall, Chris T. Evelo, Christopher Chute, Clement Jonquet, Damien Goutte-Gattat, Damion Dooley, Davera Gabriel, David Osumi-Sutherland, Emily Hartley, Ernesto Jimenez-Ruiz, Harold Solbrig, Harry Caufield, Harshad Hegde, Henriette Harmse, HyeongSik Kim, Ian Braun, Ian Harrow, James Malone, James McLaughlin, James Overton, James P. Balhoff, James Stevenson, Javier Millán Acosta, Jiao Dahzi, Joe Flack, John Graybeal, Jooho Lee, Julie McMurry, Kori Kuzma, Kristin Kostka, Lauren Chan, Melissa Haendel, Melissa Haendel, Monica Munoz-Torres, Nicolas Matentzoglu, Nicole Vasilevsky, Nomi Harris, Núria Queralt-Rosinach, Sabrina Toro, Sebastian Koehler, Shahim Essaid, Sierra Moxon, Simon Jupp, Sophie Aubin, Sue Bello, Sujay Patil, Sven Hertling, Thomas Liener, Tiffany Callahan, Tim Putman, Vinicius de Souza, William Duncan

https://w3id.org/sssom

28 of 54

What are entity mappings?

28

“Friedreich's Ataxia”

OMOP:441554

Entities are symbols, such as codes in a terminology, classes in an ontology, permissible values in a data model, identifiers in a database or simply strings in a text field that are intended to refer to a real world thing.

29 of 54

The anatomy of a SSSOM-style semantic entity mapping

are insufficient

29

SUBJECT

PREDICATE

OBJECT

�subject_id:

EFO:10000070

�object_id:

MONDO:0006071�

�object_label:

adenofibroma�

�subject_label:

Adenofibroma�

�predicate_id:

skos:exactMatch

JUSTIFICATION

mapping_justification: semapv:LexicalMatching

subject_match_field: rdfs:label�object_match_field: oio:hasExactSynonym

match_string: adenofibroma

mapping_date: 2022-12-13

reviewer_id: orcid:0000-0002-7356-1779

mapping_tool: wikidata:Q64360017

confidence: 0.8

JUSTIFICATION

mapping_justification: semapv:ManualMappingCuration

author_id: orcid:0000-0002-7356-1779

confidence: 0.8

30 of 54

SSSOM aims to

Provide a simple model to capture mapping evidence and provenance

30

30

mapping_set_id: https://w3id.org/sssom/commons/mouse-human/mappings/mp_hp_mgi_all.sssom.tsv

mapping_set_title: All mappings of MP terms to HPO terms generated by MGI

mapping_set_description: "Consolidated list of all HPO to MP mappings done by MGI…."

creator_id:

- orcid:0000-0003-4606-0597

license: https://creativecommons.org/licenses/by/4.0/

object_source: obo:hp

subject_source: obo:mp

curie_map:

HP: http://purl.obolibrary.org/obo/HP_

MP: http://purl.obolibrary.org/obo/MP_

orcid: https://orcid.org/

obo: http://purl.obolibrary.org/obo/

Mapping Table

31 of 54

What entity mappings are covered?

31

MONDO:0006071

Type 1: lexical token - identifier

Type 2: identifier - identifier

Type 3: complex

EFO:1000070

MONDO:0006071

adenofibroma

Hypertensive heart disease without congestive heart failure

modifies

Not

Congestive heart failure

AND

Hypertensive heart disease

Experimental

32 of 54

SSSOM is not for data structure mappings / schema crosswalks

New kid on the blog: LinkML-Map for �FAIR schema crosswalks!�https://linkml.io/linkml-map/

PERSON:001 ;

rdf:type my:Person ;

my:Name “Chris Mungall” .

PERSON:001 ;

rdf:type schema:Person ;

schema:givenName “...?...” ;

schema:familyName “...?...” .

But of course we can use SSSOM metadata to annotate crosswalks!

subject_id

predicate_id

object_id

my:Name

skos:narrowMatch

schema:givenName

my:Name

skos:narrowMatch

schema:familyName

???

We will integrate this with RDA FAIR Mappings effort!

33 of 54

The FAIR mappings community aims to�Promote the creation of interoperable FAIR mapping registries

  • Entity mappings are the glue of the Web of Research Data
  • Curating mappings is hard and expensive
  • We are building a global community of practice to
    • Share interoperable mappings
    • Develop shared curation and metadata practices (trainings, documentation, etc)

33

m1.sssom.tsv

m2.sssom.tsv

m3.sssom.tsv

b.sssom.tsv

Registry

Shared QC, � automatic reconciliation

Wrong mapping!

Collaborative curation

34 of 54

SSSOM 1.0: The data model is now stable

With support from 79 community members contributing 1230 comments, 154 pull requests and 13 releases over the past 4 years, SSSOM 1.0 was finally released in August 2024.

34

2 functional, independent and interoperable implementations:

  • sssom-java: https://incenp.org/dvlpt/sssom-java/
  • sssom-py: https://github.com/mapping-commons/sssom-py

Database (Oxford), Volume 2022, baac035, https://doi.org/10.1093/database/baac035

35 of 54

Acknowledgements and call to action

35

Funding

Phenomics First (NIH / NHGRI #1RM1HG010860-01): Spec, sssom-py CLI��Monarch (NIH / OD #5R24OD011883): outreach, knowledge graph integration

Bosch Gift to LBNL: sssom-py IO, testing, converters, tutorials

DARPA: Young Faculty Award W911NF2010255�(PI: Benjamin M. Gyori)

�Community contributions: https://w3id.org/sssom

Learn about SSSOM!

  1. Do a basic training
  2. Study the documentation

1

Spread the word

  1. All data initiatives will at some point produce mappings
  2. Bake mapping standardisation into your FAIR Data Publication plan!

4

Set up a SSSOM Mapping Registry for your community

3

  1. Use our template to create a mapping registry with quality control checking
  2. Collaborate with other groups on your mappings!

Publish your entity mappings in SSSOM format and share with RDA FAIR Mappings WG

2

  1. Starting point: SSSOM 5-Star mapping practices
  2. Publish in public version control system
  3. Let us know at https://bit.ly/rda-fair-mappings-issues

36 of 54

FAIR Mapping WG

Yann Le Franc, PhD

CEO e-Science Data Factory/ Head of EUDAT Secretariat

RDA 23rd Plenary Meeting

www.rd-alliance.org

37 of 54

Where did we start?

Two workshops about mappings and crosswalks during the RDA P21/International Data Week conference

  • Generic session on mappings aiming at presenting the ongoing work of the FAIR IMPACT and FAIRCORE4EOSC projects

  • A Bird Of a Feather session presenting 13 potential usages of mappings and discuss the relevance of creating an RDA Working Group.

RDA 23rd Plenary Meeting

www.rd-alliance.org

38 of 54

Where did we start?

Two workshops about mappings and crosswalks during the RDA P21/International Data Week conference

  • Generic session on mappings aiming at presenting the ongoing work of the FAIR IMPACT and FAIRCORE4EOSC projects

  • A Bird Of a Feather session presenting 13 potential usages of mappings and discuss the relevance of creating an RDA Working Group.

LOADS OF COMMUNITY FEEDBACKS

RDA 23rd Plenary Meeting

www.rd-alliance.org

39 of 54

Where are we now?

  • Co-created by FAIR IMPACT and FAIRCORE4EOSC

  • Under TAB Review

  • Initial activities

    • Bird of a Feather session during RDA P22

    • First working meeting in November

    • Bird of a Feather session during RDA P23 (“WG Kick-off”)

RDA 23rd Plenary Meeting

www.rd-alliance.org

40 of 54

Which problems do we address ?

  • Mapping are hard to find and reuse

  • Mapping are scattered across version control systems

  • Mapping are expressed in formats not meant for automated processing

  • Meaning of the term mapping is context sensitive leading to ambiguity

RDA 23rd Plenary Meeting

www.rd-alliance.org

41 of 54

What are our planned outputs?

  • Technical recommendations to make FAIR Mappings and FAIRness evaluation grid

  • Practical mapping framework and guidelines

  • Harmonized mapping use case collection

  • Mapping classification/ontology

  • Generic exchange model and the associated metadata

  • FAIR Mapping Knowledge Base

RDA 23rd Plenary Meeting

www.rd-alliance.org

42 of 54

Working Session: Identifying and Prioritizing Evaluation Methods for Choosing Terms and Ontologies (John Graybeal & OntoChoice Team)

RDA 23rd Plenary Meeting

www.rd-alliance.org

43 of 54

About the OntoChoice Project: �Evaluations for Choosing Terms and Ontologies

Project Goals

  1. Collaboratively document evaluation criteria for choosing terms and ontologies
  2. Provide proof of concept demonstrations/examples/framework for these criteria

Work to Date

RDA 23rd Plenary Meeting

www.rd-alliance.org

44 of 54

Introducing Evaluations Team and Facilitators

  • John Graybeal (facilitator Breakout 1)
  • Anna Maria Masci (facilitator Breakout 2)
  • Hande McGinty (facilitator Breakout 3)
  • Asiyah Lin (facilitator Breakout 4)
  • Juliane Schneider (Zoom facilitator for team)
  • Alexandra Kokkinaki (roving facilitator)
  • Eric G Stephan
  • Aryan Dalal
  • Christian Kindermann
  • Muhammad (Tuan) Amith

RDA 23rd Plenary Meeting

www.rd-alliance.org

45 of 54

Planned Activity: What’s Happening Here?

  • Today we all work together to improve this document
  • Each breakout group will focus on a particular section
  • Breakout discussions may organize, define, or discuss the work
  • Contribute concretely with edits, additions, changes, or comments
    • Or just take notes
    • Escribe en inglés o español, podemos convertir después
  • Come back together at end to hear how it went

RDA 23rd Plenary Meeting

www.rd-alliance.org

46 of 54

Overview of Working Document

🟢 0A. Introduction

🟢 0B. Categories of Evaluation Criteria (Relevance, Popularity/Reuse, Best Practices, Governance/Intl)

🔶 1. Category Descriptions and Detailed Criteria: Relevance Group (John)

🟢🔶 2. Category Descriptions and Detailed Criteria: Popularity and Reuse Group (Anna Maria)

3. Category Descriptions and Detailed Criteria: Best Practices and Analytics Grp (Hande)

🔶🟢 4. Category Descriptions and Detailed Criteria: Governance & Internationalization (Asiyah)

🔶 5. Existing Evaluation Systems, Technologies, and Models

6. Recommended Evaluation Facets (from the list in captures 1-4)

🔶 7. Use Cases to Discuss

8. Evaluation Guidance

9. Future Tasks

🔶 10. Resources and Bibliography

🟢 : first-draft complete. (Additions/improvements still welcome.) 🔰 : useful text and guidance but needs work. 🔶 : outline topics/example only. ⭕ : little useful content.

Our�Focus�Today

RDA 23rd Plenary Meeting

www.rd-alliance.org

47 of 54

The Categories of Evaluation Criteria

  • Relevance (a weed-out: these must be satisfied to use the ontology or term)
    • Does the ontology/term address the necessary topic(s) and have necessary approval?
  • Popularity and Reuse
    • How well-loved is the ontology/term? How often has it been used by others?
  • Best Practices and Analytics
    • Does the ontology/term content follow best practices defined for these assets?
    • Does the ontology/term’s measured qualities (size, depth, width, detail, …) meet needs?
  • Governance and Internationalization
    • Do the ontology/term maintenance processes follow best practices?
    • Is the ontology/term actively maintained?
    • Does the ontology/term provide appropriate internationalized content?

RDA 23rd Plenary Meeting

www.rd-alliance.org

48 of 54

Breakout Plan

  • We will have breakout rooms for 4-5 chapters (#1 through #4 at least)
  • The Relevance Group breakout will be in the main auditorium (‘here’)
    • This room will have simultaneous translation into Spanish
    • Other breakout rooms will be English speaking only
    • We encourage remote English speakers to go to other breakouts (#2 or higher)
  • Writing in spanish is welcome in this exercise/these documents. �(Escribiendo en español está bien en este ejercicio/estes documentos.)
  • We will integrate and address all the breakout content after the meeting.

RDA 23rd Plenary Meeting

www.rd-alliance.org

49 of 54

Today’s Goals

✅ Expose participants to the project and its progress

  • Make the document better
  • Find things missing from the document
  • Provide new perspectives
  • Create more opportunities to contribute to and improve this resource
  • Reward contributors (you) for your contributions: credit

Create content and feedback about this document!

RDA 23rd Plenary Meeting

www.rd-alliance.org

50 of 54

What You Will Do (in 25 minutes!)

  • Decide which facilitated topic you care about most
  • If remote, go to that Zoom breakout session
  • Everyone: go to the corresponding shared document (next page)
  • Work with your breakout group to make that section better
    • Working alone is OK too—tell the facilitator to avoid conflict!
    • If your group has no facilitator, choose one from the team (fast)
  • If you contribute to the document, enter your name/ORCID at top
  • When breakouts end, stay for summary and to fill out a tiny survey
  • You can keep working on the document after the session completes

RDA 23rd Plenary Meeting

www.rd-alliance.org

51 of 54

BREAKOUT SESSIONS AND LINKS      

Starred (*) breakouts are facilitated. Two-star (**) breakouts may be facilitated.

These links go to the breakout copy of that chapter. And choose your Zoom breakout session with the same title. (See this slide at link bit.ly/ontochoice.)

RDA 23rd Plenary Meeting

www.rd-alliance.org

52 of 54

  1. Relevance Criteria Breakout: What We’ll Do
  • Open bit.ly/ontochoice1. Note that the links below are also there.
    • Add your name to the authors list if you are willing to be cited
    • Add your initials to any substance changes you make, for future discussion/credit.
  • Read the introduction section. Do you understand what we are addressing?
  • There are three categories of Relevance Criteria. Do they make sense?
    • If you have knowledge or insight to add, start adding it.
    • Let’s discuss the content for each as appropriate.
  • Overall comments also welcome.

RDA 23rd Plenary Meeting

www.rd-alliance.org

53 of 54

Return from Breakout: How was that for you?

  • Summaries from facilitators
  • Please fill out this Menti for us…
  • Thank you for your participation in this product-building exercise!

RDA 23rd Plenary Meeting

www.rd-alliance.org

54 of 54

THANK� YOU

RDA 23rd Plenary Meeting

www.rd-alliance.org