Ontology for the semantic enhancement, database definition and management and revision control
blurock
56 views
84 slides
Jul 12, 2024
Slide 1 of 84
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
About This Presentation
This paper describes the use of ontologies interacting with a noSQL database (Google Cloud Firestore) in multiple capacities in the database system CHEMCONNECT. The motivation is to implement the ‘Data on the Web Best Practices” as recommended by the W3C (https://www.w3.org/TR/2017/REC-dwbp-20...
This paper describes the use of ontologies interacting with a noSQL database (Google Cloud Firestore) in multiple capacities in the database system CHEMCONNECT. The motivation is to implement the ‘Data on the Web Best Practices” as recommended by the W3C (https://www.w3.org/TR/2017/REC-dwbp-20170131/, 2017) in an application within the physical chemistry and instrumentation. First, the ontology provides semantic enhancement to each database object through meta-data, standard vocabularies and data object relationships. There is a one-to-one correspondence between the database objects and the ontology objects. Another use of the ontology is to provide a data-driven model for the creation, provenance and versioning of database objects. One aspect of this is the use of domain specific templates to guide the construction of the database objects. The definition of each database object is in a hierarchy of catalog objects, record objects and components (using the DCAT ontology model). Within each of these object definitions is a link describing how a create a set of automatically generated RDF objects within the CHEMCONNECT database. The RDFs facilitate searching the database. To facilitate versioning, data source tracking and data quality control, operations on the database are organized as transactions. In CHEMCONNECT a transaction has a one to one correspondence with the underlying JAVA operation in the implementation. Within the transaction definition, the set of prerequisites and the output of the operation is defined. The use of transactions helps organize and give semantic enhancement to the set of individual operations within the implementation. The work in this paper is on-going and as the first use-case is concentrating experimental and theoretical information in the chemical domain. The implementation is written in JAVA and is using Google Cloud firestore as the database.
Size: 50.2 MB
Language: en
Added: Jul 12, 2024
Slides: 84 pages
Slide Content
Ontology for the Semantic Enhancement, Database Definition and Management and Revision Control Edward S. Blurock Blurock Consulting AB [email protected]
Case Study: CHEMCONNECT Web application in the chemical and scientific instrumentation domain using Google Cloud Firebase ( Firestore NoSQL database and blob stora ge)
Motivation FAIR Data Management Concept Data Management Plans: Recommendations of G7 Science Ministers EU: Open Research Data (ORD) Projects Traceability, Accountability and Validation
Ontology Role of the Ontology Domain Specific Templates and Information Database Object Specifications Semantic Enhancement Data (Ontology) Driven Software
Ontology Role of the Ontology Domain Specific Templates and Information Database Object Specifications Semantic Enhancement Data (Ontology) Driven Software
Ontology Role of the Ontology Domain Specific Templates and Information Database Object Specifications Semantic Enhancement Data (Ontology) Driven Software
Ontology Role of the Ontology Domain Specific Templates and Information Database Object Specifications Semantic Enhancement Data (Ontology) Driven Software
Ontology Role of the Ontology Domain Specific Templates and Information Database Object Specifications Semantic Enhancement Data (Ontology) Driven Software
Ontology Role of the Ontology Domain Specific Templates and Information Database Object Specifications Semantic Enhancement Data (Ontology) Driven Software
Program – ontology structure Web Interface (Restful Services) Web Interface (Angular) Background Services (JAVA) Google Firebase Ontology Database Google Firestore Authentication Blob Storage Google Storage Ontology
Objects: Ontology – Program – database interaction Google Firestore Database JSON Object (Google GSON map) DCAT: Catalog DCAT: CatalogRecord dcat:record DCAT: Component dcterms:hasPart Static Data Object Specification Instances of Data Objects
Documentation and specification Use of ontology for semantic enhancement
Ontology: core of data driven processes To promote generic (JAVA) code. Maximize Process Specific information in ontology, minimize process specific code
Transaction definition Transaction Hierarchy Result of Transaction Input Information Transaction Prerequisite 1b 3 2 1a 4
Ontology based data driven Software: Catalog object Transaction Database Catalog Object Transactions Input information template Transaction Process Transaction prerequisites type choices Input information Selected Transaction Prerequisites Catalog Object Template Select Transaction Prerequisites Persistent Object Hierarchy Catalog Object Hierarchy Specification RDF Specification Database RDFs Ontology Interface Google Firebase Storage Database 1b 1a 2a 2b 2c 3a 3b 4 5 6
Role of the Ontology Domain Specific Templates and Information Database Object Specifications Semantic Enhancement Data (Ontology) Driven Software Ontology
Thank you Blurock Consulting AB: https://sites.google.com/view/blurock-consulting-ab/home Additional Information about techniques described in this poster: https://sites.google.com/view/chemconnecttechniques/about CHEMCONNECT project: https://sites.google.com/view/chemconnect/chemconnect