Changes for page Technical details

Last modified by lzehl on 2021/07/05 18:57

From 50.1 to 49.1 From 59.1 to 58.1

From version 58.1

edited by lzehl
on 2021/06/23 15:26

Change comment: There is no comment for this version

To version 50.1

edited by lzehl
on 2021/03/21 15:21

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Parent

@@ -1,1 +1,1 @@
--Collabs.openminds.Documentation.WebHome
++Collabs.openminds.openMINDS core.WebHome

Content

@@ -21,107 +21,125 @@
  (% style="text-align: justify;" %)
  For this to work smoothly for the existing, but also for all new openMINDS metadata models, the corresponding openMINDS submodules (GitHub repositories) have to meet the following requirements:
++(% style="text-align:justify" %)
++* The openMINDS metadata model has to be located on a **public GitHub repository** and published under an **MIT license**.
++* The GitHub repository should have at least one **version branch** (e.g. "v1").
++* The version branch should have the following **main directory folders**: **##schemas##** (required), **##tests##** (recommended),  **##examples##** (recommended), and **##img##** (optional).
++* The **##schemas##** folder should contain the schemas of that metadata model implemented in the **openMINDS schema template syntax** (cf. below). The directory of the schemas can be further structured or flat.
++* The **##tests##** folder should contain test-instances (JSON-LDs) for the schemas in a flat directory. The file names for these test-instances should follow the convention of **##<<XXX>>-<<YYY>>.jsonld##** for files that should pass the tests, and **##<<XXX>>-<<YYY>>-nok.jsonld##** for files that should fail the test. In both cases, **##<<XXX>>##** should be replaced with the label of the schema that is tested, and **##<<YYY>>##** with a user defined label for what aspect is tested (e.g., **##person-withoutCI.jsonld##**).
++* The **##examples##** folder should contain examples for valid instance collections for that metadata model. Each example should receive its own directory (folder) with a **##README.md##** describing the example, and an **##metadataCollection##** subfolder containing the openMINDS instances (JSON-LDs). This subfolder can be further structured to group related instances.
++* The **##img##** folder should contain image files used on that GitHub repository (e.g., the logo of the new openMINDS metadata model). The directory of the images can be further structured or flat.
++
++=== The openMINDS vocabulary ===
++
  (% style="text-align: justify;" %)
--**(1)** The openMINDS metadata model has to be located on a **public GitHub repository** and published under an **MIT license**.
++Through the integration pipeline of the openMINDS generator, the openMINDS vocabulary is automatically gathered and stored in the main openMINDS GitHub in order to centrally maintain general definitions and references for **types** and **properties** used in schemas across all openMINDS repositories. How this works is explained in the following.
  (% style="text-align: justify;" %)
--**(2)** The GitHub repository should have at least one **version branch** (e.g., "v1").
++Schema types and properties are stored in dedicated JSON files (**##types.json##** and **##properties.json##**) under the folder **##vocab##** located in the main openMINDS GitHub directory. Each schema type and property occurring in the openMINDS metadata models is automatically represented in those files as nested dictionaries.
  (% style="text-align: justify;" %)
--**(3)** The version branch should have the following **main directory folders**: **##schemas##** (required), **##tests##** (recommended),  **##examples##** (recommended), and **##img##** (optional).
++The keywords of those nested dictionaries are pre-defined to consistently capture for all schema types and properties their namespace, their occurrence, their general description, and possible references to related or matching schema types and properties of other metadata initiatives (e.g. schema.org). This setup also allows us to define some values/entries to be automatically filled in by the openMINDS integration pipeline with each commit to one of the openMINDS repositories (e.g., the namespace and occurrence) and others to be manually editable later on (e.g., the general description and references).
  (% style="text-align: justify;" %)
--**(4)** The **##schemas##** folder should contain the schemas of that metadata model implemented in the **openMINDS schema template syntax** (cf. below). The directory of the schemas can be further structured or flat.
++For security, outdated entries in those openMINDS vocabulary files (e.g. because the namespace of the schema type or property changed or the schema type or property was deleted) are not automatically deleted, but kept and marked as being deprecated. After evaluation, deprecated schema types or properties can be deleted manually from openMINDS vocabulary.
  (% style="text-align: justify;" %)
--**(5)** The **##tests##** folder should contain test-instances (JSON-LDs) for the schemas in a flat directory. The file names for these test-instances should follow the convention of
++With that, the openMINDS vocab reflects always an up-to-date status of the schema types and properties in use across all openMINDS metadata models, while providing the opportunity to centrally review and maintain their consistency and references.
--(% style="text-align: center;" %)
--**##<<XXX>>-<<YYY>>.jsonld##**
++=== The openMINDS schema template syntax ===
  (% style="text-align: justify;" %)
--for files that should pass the tests, and
++All openMINDS metadata models use a light-weighted schema template syntax for defining the expected metadata. The correspondingly formatted schema files use the extension: **##.schema.tpl.json##**.
--(% style="text-align: center;" %)
--**##<<XXX>>-<<YYY>>-nok.jsonld##**
--
  (% style="text-align: justify;" %)
--for files that should fail the test. In both cases, **##<<XXX>>##** should be replaced with the label of the schema that is tested, and **##<<YYY>>##** with a user defined label for what aspect is tested (e.g., **##person-withoutCI.jsonld##**).
++Although, as the file extension suggests, this openMINDS schema template syntax is inspired by JSON-Schema, it facilitates or even excludes technical aspects that are generally expected for the openMINDS schemas making them more human-readable, especially for untrained eyes. Behind the scenes, within the openMINDS integration pipeline (cf. below), this schema template syntax is then interpreted and flexibly translated to various formal metadata formats (e.g., JSON-Schema).
  (% style="text-align: justify;" %)
--**(6)** The **##examples##** folder should contain examples for valid instance collections for that metadata model. Each example should receive its own directory (folder) with a **##README.md##** describing the example, and an **##metadataCollection##** subfolder containing the openMINDS instances (JSON-LDs). This subfolder can be further structured or flat.
++Despite the simplification in comparison to JSON-Schema, the openMINDS schema templates are also, at the core, specially formatted JSON files using a particular syntax, meaning special key-value pairs that define the validation rules of a schema.
  (% style="text-align: justify;" %)
--**(7)** The **##img##** folder should contain image files used on that GitHub repository (e.g., the logo of the new openMINDS metadata model). The directory of the images can be further structured or flat.
++Please find in the following a full documentation of the openMINDS schema template syntax and how it's key-value pairs need to be defined and interpreted.
--=== The openMINDS vocabulary ===
--
  (% style="text-align: justify;" %)
--Through the integration pipeline of the openMINDS generator, the openMINDS vocabulary is automatically gathered and stored in the main openMINDS GitHub in order to centrally maintain general definitions and references for **types** and **properties** used in schemas across all openMINDS repositories. How this works is explained in the following.
++===== Target & concept templates =====
  (% style="text-align: justify;" %)
--Schema types and properties are stored in dedicated JSON files (**##types.json##** and **##properties.json##**) under the folder **##vocab##** located in the main openMINDS GitHub directory. Each schema type and property occurring in the openMINDS metadata models is automatically represented in those files as nested dictionaries. Here a cutout of the **##types.json##**:
++Same as in JSON-Schema, all openMINDS schema templates define the expected name (written in **##lowerCamelCase##**) and value of the metadata, typically called property, under the key **##properties##** as nested dictionaries. Furthermore, the names of obligatory metadata can be listed under the key **##required##**. Here a generalized example:
  {{code language="json"}}
  {
--  ...,
--  "https://openminds.ebrains.eu/core/Person": {
--    "description": "Structured information on a person (alive or dead).",
--    "name": "Person",
--    "translatableTo": [
--      "https://schema.org/Person"
--    ]
--  },
--  ...
++ "properties": {
++  "propertyNameA": {},
++  "propertyNameB": {},
++  "propertyNameC": {}
++ },
++ "required": [
++  "propertyNameA",
++  "propertyNameC"
++ ]
  }
  {{/code}}
--... and a cutout of the properties.json:
++(% style="text-align: justify;" %)
++In addition, an openMINDS schema //has to have// a key **##"_type"##** to be recognized as **target template**. In other words, the **##"_type"##** is used to define the openMINDS namespace of a corresponding schema using a particular naming convention. Here again a generalized example:
  {{code language="json"}}
  {
--  ...,
--  "givenName": {
--    "description": "Name given to a person, including all potential middle names, but excluding the family name.",
--    "name": "Given name",
--    "nameForReverseLink": "Is given name of",
--    "sameAs": [
--      "https://schema.org/givenName"
--    ],
--    "schemas": [
--      "core/v3/actors/person.schema.tpl.json"
--    ]
--    },
--  ...
++ "_type": "https:~/~/openminds.ebrains.eu/<<schema-model>>/<<schema-name>>",
++ "properties": {}
  }
  {{/code}}
  (% style="text-align: justify;" %)
--The keywords of those nested dictionaries are pre-defined to consistently capture for all schema types and properties their namespace, their occurrence, their general description, and possible references to related or matching schema types and properties of other metadata initiatives (e.g., schema.org). This setup also allows us to define some values/entries to be automatically filled in by the openMINDS integration pipeline with each commit to one of the openMINDS repositories (e.g., the namespace and occurrence) and others to be manually editable later on (e.g., the general description and references).
++Note that **##<<schema-model>>##** has to be replaced with the label of the openMINDS metadata model to which the corresponding schema belongs to, and **##<<schema-name>>##** has to be replaced with the corresponding name of the schema (written in **##CamelCase##**).
  (% style="text-align: justify;" %)
--For security, outdated entries in those openMINDS vocabulary files (e.g., because the namespace of the schema type or property changed or the schema type or property was deleted) are not automatically deleted, but kept and marked as being deprecated. After evaluation, deprecated schema types or properties can be deleted manually from openMINDS vocabulary.
++If an openMINDS schema template //does not// define a key **##"_type"##** (as in the first example above), it is interpreted as a **concept template** which //has to be// extended to a target template.
  (% style="text-align: justify;" %)
--With that, the openMINDS vocab reflects always an up-to-date status of the schema types and properties in use across all openMINDS metadata models, while providing the opportunity to centrally review and maintain their consistency and references.
++Concept templates are and should be used when multiple target templates have the same subset of properties, because they facilitate the long-term maintenance of those shared properties: Instead of defining the same properties repeatedly within multiple target templates, the common subset can be defined within a single concept template and passed on to all extending target templates.
--=== The openMINDS schema template syntax ===
++(% style="text-align: justify;" %)
++To define that a target template is the extension of a concept template, the target template can state under **##"_extends"##** the relative path to the concept template. For example, the openMINDS core target template **##Dataset##** extends the core concept template **##researchProduct##** as indicated here:
++{{code language="json"}}
++{
++ "_type": "https:~/~/openminds.ebrains.eu/core/Dataset",
++ "_extends": "products/researchProduct.schema.tpl.json"
++}
++{{/code}}
++
  (% style="text-align: justify;" %)
--All openMINDS metadata models use a light-weighted schema template syntax for defining the expected metadata. The correspondingly formatted schema files use the extension: **##.schema.tpl.json##**.
++Note that this convention requires the concept and corresponding target templates to be located in the same openMINDS metadata model repository. Note also that for properties, the following rules apply for target and concept template:
++1. A concept template has to define some properties which will be inherited by all extending target templates.
++1. If a concept template additionally states that some of these properties are required, all extending target templates will require the same properties.
++1. A target template can require properties of the concept template, that are not explicitly required within the concept template. In such a case, the other target templates extending the same concept template will not require those properties.
++1. A target template can (but does not have to) define and require additional properties that were not defined and required in the concept template. These additionally defined and required properties will not be shared with the other target templates extending the same concept template.
++
  (% style="text-align: justify;" %)
--Although, as the file extension suggests, this openMINDS schema template syntax is inspired by JSON-Schema, it facilitates or even excludes technical aspects that are generally expected for the openMINDS schemas making them more human-readable, especially for untrained eyes. Behind the scenes, within the openMINDS integration pipeline (cf. below), this schema template syntax is then interpreted and flexibly translated to various formal metadata formats (e.g., JSON-Schema).
++How to define the expected value of a property will be explained for the different property types in the following sections.
  (% style="text-align: justify;" %)
--Despite the simplification in comparison to JSON-Schema, the openMINDS schema templates are also, at the core, specially formatted JSON files using a particular syntax, meaning special key-value pairs that define the validation rules of a schema.
++===== Defining expected values =====
  (% style="text-align: justify;" %)
--Please find in the following a full documentation of the openMINDS schema template syntax and how it's key-value pairs need to be defined and interpreted.
++The expected value of a property can be defined in large parts in the same way as in JSON-Schema, with some openMINDS syntax specific simplifications and modifications.
  (% style="text-align: justify;" %)
--(//**coming soon**//)
++On the first level, the **##"type"##** of the expected property value needs to be defined. In principle, the openMINDS template syntax supports the same value types as JSON-Schema Draft 7.0, meaning:
+++ **##"string"##**
+++ **##"number"##**
+++ **##"integer"##**
+++ **##"array"##**
+++ **##"boolean"##**
+++ **##"null"##**
+++ **##"object"##**
++Also very similar to JSON-Schema, additional type-specific keys can be used to set further requirements for the expected value. H
++
++
  === The openMINDS integration pipeline ===
  (//**coming soon**//)