Some Trusted Cloud datatypes have counter-intuitive names
Concretely I think the following classes should be renamed:
-
LegalInformationProvider
(can be misunderstood as "someone who provides legal information") →ProviderLegalInformation
(correct interpretation: "legal information about a provider") - same for
CompanyProfileProvider
- same for
...Subcontractor
instead of...Provider
As the Trusted Cloud criteria catalogue does not prescribe concrete names, I think we can improve them on our own.
Afterwards, we need to re-generate the artifacts (SHACL, OWL) and re-deploy them to the Creation Wizard.