(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 (e.g., property name "system role"):

• "operations" (for services that are crucial to keep the system running)
• "core" (for services that are representing/providing key values/functions for a system)
• "complementary" (for services that are representing/providing additional values/functions for a system)

3. Annotation about the service categories (e.g., property name "category"):

• "data"
• "knowledge"
• "modeling"
• "computing"
• etc
  This annotation should be available in the same way on software version.
  We should discuss if multiple types are allowed and if any of them are exclusive.
  Operations services might be difficult to categorize besides (operations).

3. Annotation about the type of a service (e.g., property name "type"):

• "data management"
• "visualization"
• "security"
• etc
  This annotation should be available in the same way on software version.
  There seems to be also a general need to distinguish between "science" and "non-science" services.
  We should discuss if multiple types are allowed and if any of them are exclusive.

4. Annotation about the interfaces of a service (e.g., property name "interfaces"):

• "application programming interface"
• "command line interface"
• "graphical user interface"
  This annotation should be available in the same way on software version.

[lzehl]

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