Motivation Typology

Concept··Draft

These are broad community expectations of the performance of the ecosystem, and some of these are formalised in sets of principles (FAIR, TRUST, CARE) and in some cases, realised as sets of criteria and/ or elaborated as expected behaviour or levels of performance (guidance, best practices).

Concept··Draft

A motivation that includes aspects of more than one type, or is composed of motivations that span multiple concerns.

Concept··Draft

These motivations include risk aversion (for example by requiring two-factor authentication, open source code, and the like). For systems engineering, these will be important considerations - elements such as interoperability, modularity, topology, and scalability are included in this set of motivations.

Concept··Draft

Compliance is often mandatory, and is intended to ensure legality or a minimum level of performance. Examples include the EOSC PID Policy, or GDPR.

Concept··Draft

These ensure a minimum level of performance, readiness, or maturity as a prerequisite for participation in a network, an infrastructure, or a consortium.

Concept··Draft

Compliance may be required for a wide variety of published and well-known standards and conventions - e.g. ISO 27001, HATEOAS , and similar.