(web) service revision - new annotations

[lzehl]

At the moment all informative annotations around the function of a web service are not structured.
We assumed so far that this will be delivered through the connected software.
I would suggest to make those specific for the service.

SUGGESTIONS (that came up in the EBRAINS service working group):

1. Annotation about the role of a service for a system:

• property name: "systemicRole"
• expected value: 1, linked object (SystemicRoleOfService; new controlledTerms library)
• SystemicRoleOfService terms:
  • "operations": Any service that ensures the overall functionality of a system.
  • "core": Any service that provides key representative functions of a system.
  • "complementary": Any service that provides additional valued functions for a system.

2. Annotation about the overall innovation class:

• property name: "innovationClass"
• expected value: 1-N (?), linked object (InnovationClass; new controlledTerms library)
• InnovationClass:
  • "non-science innovation": Any innovation driven by non-scientific principles, not relying on scientific research or methodologies.
  • "science innovation": Any innovation grounded in scientific research and methods, aimed at advancing or solving scientific problems or creating new scientific solutions.
  • "science-infused innovation": Any innovation that integrates scientific principles or research into non-scientific contexts, improving a non-scientific product or solution.
  • "science-enabled innovation": Any innovation that depends on scientific research or methodologies to power or make possible a non-scientific product or solution.

3. Annotation about the type or function of the service:

• property name: "type" OR "function" ??
• expected value: 1-N (?), linked object (XTBDX; new controlledTerms library)
• XTBDX (schema name to be defined):
  • "management"
  • "editing"
    • "real time editing"
  • "monitoring"
    • "performance monitoring"
    • "usage monitoring"
  • "security"
  • "computation"
    • "analysis"
    • "simulation"
    • "visualization"
    • "validation"
    • "inference"
  • "collaboration"
  • "storage"
    • "long-term preservation"
    • "working storage"
    • "object storage" (maybe goes somewhere else)
    • "block storage" (maybe goes somewhere else)
  • "deployment"
  • "support"
  • "provenance"
  • "version control"
  • "neuromorphic computing"
  • "hardware access"
  • "communication"
    • "real time communication" vs ??
  • "documentation"
    • "interactive documentation" (e.g. live papers?)
  • "registry"
  • "acquisition" (may need further sub-elements?)
    (would in principle match the collection of software functions associated with a service)

4. Annotation about the interfaces of a service:

• property name: "interface type"
• expected value: 1-N (?), linked object (InterfaceType; new controlledTerms library)
• InterfaceType:
  • "application programming interface"
  • "command line interface"
  • "graphical user interface"

[lzehl]

@elenimath we can use this issue for further discussion on service types. Feel free to pin who you think should be involved here.

[lzehl]

@openMetadataInitiative/openminds-developers these annotations should be discussed. If we agree on them we can start triggering the respective updates in WebService and Software.