Changes for page Technical details

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

From version 63.1
edited by lzehl
on 2021/06/24 12:53
Change comment: There is no comment for this version
To version 66.1
edited by lzehl
on 2021/06/24 16:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -120,21 +120,20 @@
120 120  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. 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.
121 121  
122 122  (% style="text-align: justify;" %)
123 -For the more inexperienced programmers, let's start by explaining first some general terms that will be later used in the openMINDS schema template syntax specification. More experienced programmers can of course skip these explanations and jump directly further down.
123 +For the more inexperienced programmers, let's start by explaining first some general terms that will be later used in the openMINDS schema template syntax specification. More experienced programmers can of course skip these explanations and jump directly further down to Specifications.
124 124  
125 -**What is a string, an integer, a float or a boolean?**
125 +**What are strings, integers, floats or booleans?** Generally speaking strings, integers, floats or booleans are derived **data types**. A **string** is defined as a sequence of characters between quotes (e.g., ##"Is this a string? YES!"## or ##'thisIsAlsoAString'##). For a string, openMINDS accepts Unicode characters. An **integer** is a whole number, positive or negative, without decimals, of unlimited length (e.g., ##5##, ##-5## or ##1238921234##). A **float** represents a real number, written with a decimal point dividing the integer and fractional part, both of unlimited length (e.g., ##5.15##, ##-5.15## or ##1238921234.1345##). A **boolean** represents a logical proposition by means of the binary digits ##0## (##false##) and ##1## (##true##), especially in computing and electronics. How a boolean is written depends highly on the format or computational language.
126 126  
127 -**What is a key-value pair?**
127 +**What is a list or array?** A **list** is a data structure that is a mutable ordered sequence of values (also called items). The values of a list are typically defined between square brackets (e.g., ##[value1, value2, value3]##). Note that the values within a list do not have to have the same data type. In contrast, an **array** is a data structure that is a mutable unordered sequence of values of the same data type. What data types are accepted for values in a list or in an array is highly depending on the format or computational language.
128 128  
129 -**What is a list?**
129 +**What is a key-value pair or an associative array?** A **key-value pair** (sometimes also called name-value pair, attribute-value pair, property-value pair, or field-value pair) is a basic data representation and standard language feature in computing languages, systems and applications. In most cases this concept is used to build an **associative array** (also called **dictionary**), meaning an unordered list of unique keys with associated values typically defined within curly brackets (e.g., ##{key1: value1, key3: value3, key2:value2}##). What data types are accepted for keys and values highly depends on the format or computational language. Note that a value could also be a data structure, such as a list, an array or an associative array.
130 130  
131 -**What is a dictionary?**
131 +**What is JSON?** JSON is short for **J**ava**S**cript **O**bject **N**otation, a lightweight data-interchange format which is built on associative arrays with key-value pairs and lists. Each JSON document/file begins as associative array. The keys are separated from the values via a colon and key-value pairs are separated by a comma. While a key always has to be a string in double quotes, a value can be a string in double quotes, an integer, a float, a boolean (written as true or false), null, a list or an associative array. Nesting of these structures is unlimited. For more information please go to the official webpage: [[https:~~/~~/www.json.org/>>https://www.json.org/]]. Several serialisation formats have been built on the JSON specification, such as JSON-LD (cf.[[ Application details: JSON-LD - the openMINDS serialization format>>doc:Collabs.openminds.Documentation.Application details.WebHome||target="_blank"]]). In addition, several schema languages have been developed to annotate and validate JSON documents, such as JSON-Schema and SHACL (cf. The openMINDS integration pipeline).
132 132  
133 -**What is a JSON?**
133 +==== Specifications ====
134 134  
135 +(coming soon)
135 135  
136 -
137 -
138 138  === The openMINDS integration pipeline ===
139 139  
140 140  (//**coming soon**//) If you'd like to learn more about the openMINDS integration pipeline, especially if you'd like to contribute to it, please get in touch with us (the openMINDS development team) via the issues on the openMINDS or openMINDS_generator GitHub or the support email: openminds@ebrains.eu
Public

openMINDS