3.5. Interfaces, APIs and client modules (TECHNOLOGY)

That’s clear that one has to find the right balance between sth understandable, usable by humans but at the same time parsable, checkable by machines … Just thinking a bit towards enabling more rigid validation (=raising the threshold): More rigid requirements/validation helps users to understand the semantics of the data structures used. At least for me validation is much easier implemented and maintained using a web ui (or bulk upload via api) converging into a yaml, json-ld and finally rdf pipeline… I think the maintenance of the “low threshold interface” is a pain with sth like Excel, if there are significant changes in the data model upstream the validation pipeline … but maybe that’s a question of available capacities/human resources to support these entry points.