Additional documentation for checking correctness within inside-schema properties

[aeidi89]

Here we should comment on the dependency-check between inside-schema properties (property cross-check).
These dependencies are difficult to express within a schema, but they are necessary for the logic of the schema and to be able to use SANDS as we wish.

Example: an annotation is connected on a 1-1 basis with a term for a specific version of a reference atlas. In the brainAtlas schema both the properties annotationSet and terminology will collect annotations (connected to specific anatomicalEntities (connected to a terminology)) and terms (connected to specific annotations). The terminology must match to fullfill the requirements for a brain atlas (a specific brain atlas version cannot have 2 different terminologies).

[lzehl]

Very nice! Let's keep track of the individual dependencies collectively here. For each dependency scenario/case make sure to reference the corresponding schemas (e.g., via the revision-schema issues).

[UlrikeS91]

anatomicalEntity:

• source is optional, but is required for being connected to brainAtlas (a brain atlas version has to have a terminology)

• parentStructure (= another anatomicalEntity) has to have the same source as the child

• parentStructure allows shaping your own hierarchy, but EBRAINS/HBP goal for SANDS is to capture the atlas structures as they were published --> parentStructure needs to reflect the same hierarchy as the publication dictates

also described in #26

[aeidi89]

Moving property laterality from anatomicalEntity.schema.json to annotation.schema.json (Ref. issue #26)

• When removing information about laterality from the region (anatomicalEntity) to the annotation we must ensure that bi-lateral regions have two annotations (left and right).