|
-
-
-
- |
- ||
|---|---|---|
| .. | -||
| - - - - - cmd_ro.txt - - - - | - -||
| - - - - - config.yml - - - - | - -||
| - - - - - output_ro.html - - - - | - -||
diff --git a/docs/structured_data/data_integrity.rst b/docs/structured_data/data_integrity.rst index e87c0215e..e0e2c3f30 100644 --- a/docs/structured_data/data_integrity.rst +++ b/docs/structured_data/data_integrity.rst @@ -60,11 +60,19 @@ Consistency consistency - Consistency corresponds to what current market tools offer; - first it is a typed base validation, and then it is a schema-based validation. + Consistency is validating the value of a variable in relation to other + variables in the :term:`context`. + This does not only concern only the variables themselves, such as their type. + Of course there is a typed base validation. + + The aim is to validate a variable in a :term:`configuration`, + the :term:`structured data` and the :term:`user data` based on the situation, + + This is what we call a "context"—meaning the dataset to which a variable is linked. For example, if a minimum value and then a maximum value are requested, - the minimum must be lesser than the maximum. + the minimum must be lesser than the maximum. This is not type consistency, + but this is yet consistency. Context access control ~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/tutorial/01 b/docs/tutorial/01 deleted file mode 100644 index 571938239..000000000 --- a/docs/tutorial/01 +++ /dev/null @@ -1,646 +0,0 @@ - - -
- - -|
-
-
-
- |
- ||
|---|---|---|
| .. | -||
| - - - - - cmd_ro.txt - - - - | - -||
| - - - - - config.yml - - - - | - -||
| - - - - - output_ro.html - - - - | - -||