FAIR Metadata RDA 10 Luiz Olavo Bonino luiz
FAIR Metadata RDA 10 Luiz Olavo Bonino – luiz. bonino@dtls. nl - September 21, 2017
FAIR DATA PRINCIPLES https: //www. nature. com/articles/sdata 20 1618 Findable: Accessible: F 1. (meta)data are assigned a globally unique and persistent identifier; A 1. (meta)data are retrievable by their identifier using a standardized communications protocol; F 2. data are described with rich metadata; A 1. 1 the protocol is open, free, and universally implementable; F 3. metadata clearly and explicitly include the identifier of the data it describes; F 4. (meta)data are registered or indexed in a searchable resource; A 1. 2. the protocol allows for an authentication and authorization procedure, where necessary; A 2. metadata are accessible, even when the data are no longer available; Interoperable: Reusable: I 1. (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation. R 1. meta(data) are richly described with a plurality of accurate and relevant attributes; I 2. (meta)data use vocabularies that follow FAIR principles; R 1. 1. (meta)data are released with a clear and accessible data usage license; I 3. (meta)data include qualified references to other (meta)data; R 1. 2. (meta)data are associated with detailed provenance; R 1. 3. (meta)data meet domain-relevant community standards;
FAIR DATA PRINCIPLES - METADATA Findable: Accessible: F 1. metadata are assigned a globally unique and persistent identifier; A 1. metadata are retrievable by their identifier using a standardized communications protocol; F 2. data are described with rich metadata; A 1. 1 the protocol is open, free, and universally implementable; F 3. metadata clearly and explicitly include the identifier of the data it describes; F 4. metadata are registered or indexed in a searchable resource; A 1. 2. the protocol allows for an authentication and authorization procedure, where necessary; A 2. metadata are accessible, even when the data are no longer available; Interoperable: Reusable: I 1. metadata use a formal, accessible, shared, and broadly applicable language for knowledge representation. R 1. metadata are richly described with a plurality of accurate and relevant attributes; I 2. metadata use vocabularies that follow FAIR principles; R 1. 1. metadata are released with a clear and accessible data usage license; I 3. metadata include qualified references to other (meta)data; R 1. 2. metadata are associated with detailed provenance; R 1. 3. metadata meet domain-relevant community standards;
FAIR DATA PRINCIPLES - DATA Findable: Accessible: F 1. data are assigned a globally unique and persistent identifier; A 1. data are retrievable by their identifier using a standardized communications protocol; F 2. data are described with rich metadata; A 1. 1 the protocol is open, free, and universally implementable; F 3. metadata clearly and explicitly include the identifier of the data it describes; F 4. data are registered or indexed in a searchable resource; A 1. 2. the protocol allows for an authentication and authorization procedure, where necessary; A 2. metadata are accessible, even when the data are no longer available; Interoperable: Reusable: I 1. data use a formal, accessible, shared, and broadly applicable language for knowledge representation. R 1. data are richly described with a plurality of accurate and relevant attributes; I 2. data use vocabularies that follow FAIR principles; R 1. 1. data are released with a clear and accessible data usage license; I 3. data include qualified references to other (meta)data; R 1. 2. data are associated with detailed provenance; R 1. 3. data meet domain-relevant community standards;
FAIR DATA PRINCIPLES – SUPPORTING INFRASTRUCTURE Findable: Accessible: F 1. (meta)data are assigned a globally unique and persistent identifier; A 1. (meta)data are retrievable by their identifier using a standardized communications protocol; F 2. data are described with rich metadata; A 1. 1 the protocol is open, free, and universally implementable; F 3. metadata clearly and explicitly include the identifier of the data it describes; F 4. (meta)data are registered or indexed in a searchable resource; A 1. 2. the protocol allows for an authentication and authorization procedure, where necessary; A 2. metadata are accessible, even when the data are no longer available; Interoperable: Reusable: I 1. (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation. R 1. meta(data) are richly described with a plurality of accurate and relevant attributes; I 2. (meta)data use vocabularies that follow FAIR principles; R 1. 1. (meta)data are released with a clear and accessible data usage license; I 3. (meta)data include qualified references to other (meta)data; R 1. 2. (meta)data are associated with detailed provenance; R 1. 3. (meta)data meet domain-relevant community standards;
”Rigor on metadata maximizes power of data” John Graybeal RDA 10 – Sept 20 th 2017
METADATA LAYERS Data Repository (FDP)
METADATA LAYERS Data Repository (FDP) (Dataset) Catalog(s) Dataset Distribution DCAT/HCLS
METADATA LAYERS Data Repository (FDP) (Dataset) Catalog(s) Dataset Distribution Data Record DCAT/HCLS RML
EXTENDING THE METADATA LAYERS VOCABULARIES Data Repository (FDP) (Dataset) Catalog(s) Dataset Distribution Data Record
EXTENDING THE METADATA LAYERS VOCABULARIES DCAT dcat: publisher biosch: organization "@context": "http: //schema. org", "@type": "NGO", "address": { "@type": "Postal. Address", "address. Locality": "Utrecht, The Netherlands", "postal. Code": “ 3511 GC", "street. Address": “Catharijnesingel 54" }, "email": “info(at)dtls. nl", "@type": “Organization”, “@type”: “not-for-profit”, "name": “Dutch Techncentre for Life Sciences", "telephone": "( 31) 85 30 30 711"
EXTENDING THE METADATA LAYERS – EXTENDED MODEL Data Repository (FDP) Dat. A Tag Suite (DATS) (Dataset) Catalog(s) Dataset PROV Distribution PROV-O Data Record
MODEL EXTENSION EXAMPLE foaf: Agent dct: publisher dct: title dcat: Dataset dcat: landing. Page dct: identifier
MODEL EXTENSION EXAMPLE foaf: Agent dct: publisher dct: title dcat: Dataset dcat: landing. Page dct: identifier ENOUGH?
MODEL EXTENSION EXAMPLE dats: Publication foaf: Agent dats: citations dct: publisher dcat: Dataset dats: Dataset provo: Entity provo: was. Attributed. To provo: Agent provo: generated. At. Time provo: used provo: Activity dct: title dcat: landing. Page dct: identifier
Dat. A Tag Suite (DATS) Dataset citations primary. Publications Publication
Q&A/CONTACT INFO Luiz Bonino E-mail: luiz. bonino@dtls. nl Skype: luizolavobonino
- Slides: 17