Inconsistencies between schema 1.0 PDF and JSON instances

PDF section 6.4 'contactUri' allows for email-adresses but the Schema allows only the format 'uri' which a "normal" mail-adress does not conform to. Easiest would be to allow the format 'email' (additionally) for the JSON field. (See merge request https://gitlab.hzdr.de/hmc/hmc/cct-1-mapping/category-definitions/-/merge_requests/21). Alternativly we could force (through our pipeline) every entry to have the prefix 'mailto:' which makes it URI-conform.
https://gitlab.hzdr.de/hmc/hmc/cct-1-mapping/category-definitions/-/blob/master/hmc_schemas/hmc_repository_1_0_0.json asked for strings where the PDF allowed for arrays and vice versa in 4 cases. ("dataAccess", "databaseAccess", "DataUploadType "and "offersEnhancedPublication"). This got fixed here -> 59b61f67
PDF controlled list 'dateType' allows only 3 values for 8.2 'dateType' while the corresponding 'common_Proporties' JSON allows a fourth type called "other". We decided to disallow "other" again for now, until we have a way to augment differing dateTypes with more helpful info then "other" (see #42).
Some small Schema improvements where already carried out in the JSONS and should be tracked in our next 1.1 PDF Version (and added maybe to 1.0.1 (#35 (closed)) .
Other inconsistencies between the JSONs and the PDF 1.0. will most likely come up but we should probably track them in future (PDF) versions, or maybe somehow produce PDFs automatically from our JSONs, to keep them in Sync. -> see https://gitlab.hzdr.de/hmc/hmc/cct-1-mapping/schema-specification-document/-/issues/4

Edited Oct 04, 2022 by Konstantin Pascal Walter