Term:OSLa54549fc328f4e5c941d7c5d3b74abf3: Difference between revisions

From Onterface Dataspace
Term:OSLa54549fc328f4e5c941d7c5d3b74abf3
()
(add graphviz)
Line 14: Line 14:


The existing (battery) ontologies [https://github.com/emmo-repo/EMMO EMMO], [https://github.com/BIG-MAP/BattINFO BattINFO] and [https://github.com/Battery-Value-Chain-Ontology/ontology BVCO] in combination already cover the essential requirements of Onterface ( see Fig. 1).  
The existing (battery) ontologies [https://github.com/emmo-repo/EMMO EMMO], [https://github.com/BIG-MAP/BattINFO BattINFO] and [https://github.com/Battery-Value-Chain-Ontology/ontology BVCO] in combination already cover the essential requirements of Onterface ( see Fig. 1).  
<div class="graphviz">
digraph G {
    subgraph cluster_0 {
        node[color=blue]
        ec [label="bvco:ElectrochemicalCellTesting"]
        ec -> "battinfo:IntentionalElectrochemicalProcess" [label="HasPart"]
        "battinfo:ElectrochemicalCell" -> ec [label="HasInput", dir=back]
        "bvco:BatteryTester" -> ec [label="HasParticipant", dir=back]
        label = "Physical";
    }
   
    subgraph cluster_2 {
        node[color=red]
        vec [label="bvco:VirtualElectrochemicalCellTesting"]
        "battinfo:BatteryContinuumModel" -> vec [label="HasInput", dir=back]
        "emmo:SimulationApplication" -> vec [label="HasParticipant", dir=back]
        label = "Virtual";
    }
   
    subgraph cluster_1 {
        node[color=green]
        ed [label="bvco:ElectrochemicalData"]
        eq [label="battinfo:ElectrochemicalQuantity"]
        ed -> ec [label="HasOutput", dir=back]
        ec -> eq [label="DefinesSome"]
        ed -> vec [label="HasOutput", dir=back]
        vec -> eq [label="DefinesSome"]
        "Maccor-CSV-Export" -> ed [label="IsA"]
        label = "Data";
    }
}
</div>


Thus, concepts describing the battery cell, its properties (e. g. CellVoltage) and internal chemical processes (e. g. IntentionalElectrochemicalProcess) can be found in BattINFO. BVCO, on the other hand, describes devices (e. g. BatteryTester) and external processes (e. g. ElectrochemicalCellTesting) for characterizing the cells. Basic aspects for modelling (e. g. SimulationApplication) are already available in the base ontology EMMO.
Thus, concepts describing the battery cell, its properties (e. g. CellVoltage) and internal chemical processes (e. g. IntentionalElectrochemicalProcess) can be found in BattINFO. BVCO, on the other hand, describes devices (e. g. BatteryTester) and external processes (e. g. ElectrochemicalCellTesting) for characterizing the cells. Basic aspects for modelling (e. g. SimulationApplication) are already available in the base ontology EMMO.

Revision as of 08:22, 1 October 2022

For the "HasDescription" annotation, the parser was unable to determine a language code (i.e. "foo@en").

OSLa54549fc328f4e5c941d7c5d3b74abf3
ID OSLa54549fc328f4e5c941d7c5d3b74abf3
UUID a54549fc-328f-4e5c-941d-7c5d3b74abf3
Ontology IRI
Relations (Outgoing)
Relations (Incoming)

Short description

Domain ontology for (raw) data description. An example of ‘synthetic’ knowledge graph.

D1 – Domain ontology for (raw) data description. An example of ‘synthetic’ knowledge graph.​

ABSTRACT/SHORT SUMMARY incl. Objective of deliverable

Review and connect existing ontologies to the BIG-MAP ontology (BattINFO). Develop an ontology or extend an existing one for electrochemical characterization. Instantiate the ontology with a KG based on exemplary data sets from Fraunhofer or other BIG-MAP partners.

Domain ontology for (raw) data description

The existing (battery) ontologies EMMO, BattINFO and BVCO in combination already cover the essential requirements of Onterface ( see Fig. 1).

digraph G {

   subgraph cluster_0 {
       node[color=blue]
       ec [label="bvco:ElectrochemicalCellTesting"]
       ec -> "battinfo:IntentionalElectrochemicalProcess" [label="HasPart"]
       "battinfo:ElectrochemicalCell" -> ec [label="HasInput", dir=back]
       "bvco:BatteryTester" -> ec [label="HasParticipant", dir=back]
       label = "Physical";
   }
   
   subgraph cluster_2 {
       node[color=red]
       vec [label="bvco:VirtualElectrochemicalCellTesting"]
       "battinfo:BatteryContinuumModel" -> vec [label="HasInput", dir=back]
       "emmo:SimulationApplication" -> vec [label="HasParticipant", dir=back]
       label = "Virtual";
   }
   
   subgraph cluster_1 {
       node[color=green]
       ed [label="bvco:ElectrochemicalData"]
       eq [label="battinfo:ElectrochemicalQuantity"]
       ed -> ec [label="HasOutput", dir=back]
       ec -> eq [label="DefinesSome"]
       ed -> vec [label="HasOutput", dir=back]
       vec -> eq [label="DefinesSome"]
       "Maccor-CSV-Export" -> ed [label="IsA"]
       label = "Data";
   }

}

Thus, concepts describing the battery cell, its properties (e. g. CellVoltage) and internal chemical processes (e. g. IntentionalElectrochemicalProcess) can be found in BattINFO. BVCO, on the other hand, describes devices (e. g. BatteryTester) and external processes (e. g. ElectrochemicalCellTesting) for characterizing the cells. Basic aspects for modelling (e. g. SimulationApplication) are already available in the base ontology EMMO.

For the popular CSV export format or tabular data in general, other existing ontologies like the CSVW Ontology can be used.

An example of ‘synthetic’ knowledge graph

For the creation and use of a first knowledge graph, a web platform was set up under[1] based on OpenSemanticLab. Figure 2 shows an example section of the knowledge graph in which an individual cell (MyCell1) is described on the basis of its active materials (Graphite, NMC111).

The materials are linked to material models of the simulation framework BattMo. An execution of a simulation with BattMo based on the specification can now determine a characteristic of the cell such as the discharge curve, whereby the result is in turn linked to the cell instance in the knowledge graph.

Anhang


📎 Select files (or drop them here)... 📷 Camera

    Graph

    { "root":"Term:OSLa54549fc328f4e5c941d7c5d3b74abf3", "properties":[ "-HasOutput"], "edit": true, "permalink":true, "depth":1, "edge_labels": false}


    OSLa54549fc328f4e5c941d7c5d3b74abf3 +
    LabelMulti-language label 
    D1: Domain ontology / Example KG (en) +
    a54549fc-328f-4e5c-941d-7c5d3b74abf3 +
    Cookies help us deliver our services. By using our services, you agree to our use of cookies.