Aqueous KOH Electrolyte#

This example, let’s describe an instance of some aqueous potassium hydroxide (KOH) electrolyte with some properties. The JSON-LD description of the material is given below:

 1{
 2   "@context": "https://w3id.org/emmo/domain/electrochemistry/context",
 3   "@type": "Electrolyte",
 4   "hasSolvent": {
 5      "@type": "Water"
 6   },
 7   "hasSolute": {
 8      "@type": "PotassiumHydroxide",
 9      "hasProperty": {
10            "@type": ["AmountConcentration", "ModelledProperty"],
11            "hasNumericalPart": {
12               "@type": "Real",
13               "hasNumericalValue": 7
14            },
15            "hasMeasurementUnit": "emmo:MolePerLitre"
16      }
17   },
18   "hasProperty": [
19      {
20            "@type": ["Density", "MeasuredProperty"],
21            "hasNumericalPart": {
22               "@type": "Real",
23               "hasNumericalValue": 1.289
24            },
25            "hasMeasurementUnit": "emmo:KilogramPerLitre"
26      },
27      {
28            "@type": ["IonicConductivity", "MeasuredProperty"],
29            "hasNumericalPart": {
30               "@type": "Real",
31               "hasNumericalValue": 65
32            },
33            "hasMeasurementUnit": "emmo:SiemensPerCentiMetre"
34      }
35   ]
36}

This example highlights a few things:

  1. EMMO distinguishes properties according to how they were determined. In this example, a ConventionalProperty is a property whose value is assigned by convention (e.g. from a technical specification sheet, handbook, etc.). EMMO also provides terms for MeasuredProperty for properties which were actually determined by some measurement and ModelledProperty for properties that were obtained from some model.

  2. EMMO has a specific way of expressing quantitative properties. As shown in the example, a quantitative property has a @type that describes what kind of property it is, hasNumericalPart describes the value, and hasMeasurementUnit defines the unit. Please adhere to this format when expressing quantities in your linked data.

  3. We can re-use terms from common vocabularies like schema.org. One of the core principles of linked data is to re-use existing vocabularies when possible. The schema.org vocabulary was developed to support internet search engines and contains terms for things that people often search for (e.g. people, organizations, products, etc.) In this case, we can re-use schema.org terms to describe the manufacturer and product.