Namings

[edgarmueller]

This a list of type names, which I think could be improved upon:

• DataService: isRelevantKey -> needsNotificationAbout?
• DataService: initialRootRun -> initDataChangeListeners
• DataService: notifyChange -> notifyDataChangeListeners
• DataServiceListener: notifyChange (same name as DataService) -> dataChanged?
• RuntimeListener: notify -> runtimeChanged
• BaseControl: inputElement -> createInputElement as the contract seems to be to return a new element on each invocation, do not model as property
• Rename JsonFormsHolder to JsonForms
• Rename JsonForms to JsonFormsElement (as the actual element name does not matter much anyways)
• JsonForms has almost same methods as a Renderer. Try to unify both types, if not possible rename methods in JsonForms to resemble those of Renderer

Consistency-related issues

• Capital usage: UISchemaElement vs UiSchemaTester/UiSchemaRegistry etc.
• When finding elements via services/registries: most fitting vs. best vs. applicable
  • UISchemaRegistry: getBestUiSchema -> findMostApplicabeUISchema
• Consistent usage of register/deregister -> follow-up issue Services should use common naming scheme for listeners registration #583