Add `dpv:Service` as a concept

[coolharsh55]

Definition: "an activity undertaken to provide something other than goods",

based on Oxford dictionary: (edits mine): "~a business whose work involves~ doing something ~for customers~ but not producing goods; ~the work that such a business does~"

Concepts:

1. class dpv:Service would be a subtype of dpv:Process proposed in #121
2. property dpv:hasService would be the subproperty of dpv:hasProcess. This will allow it to be associated with other concepts, e.g. dpv:hasPurpose dpv:Purpose or vice-versa.
3. classes dpv:ServiceProvider and dpv:ServiceConsumer should be added as entity types. These are possible in configurations of B2B, B2C, etc. These roles are also distinct from DataController and DataSubject - so they will overlap across use-cases.
4. their corresponding properties dpv:hasServiceProvider and dpv:hasServiceConsumer to indicate who is providing/consuming the service.

Rationale:

• Service is mentioned in several purposes e.g. Service Provision
• Service is an industry term and is also considered 'common language' to the extent that a law doesn't need to define it
• Service is a way to group related purposes and operations with a common goal
• Service is more specific than Process and interpreted differently for business and legal meanings e.g. we ask what services are being provided in return for payment
• Service provides grouping together related processes based on a visible concept e.g. a product

[coolharsh55]

Discussed in meeting 22 NOV and meeting 29 NOV. General agreement on the concept and its usefulness, but questions on how it relates to other uses of System such as using AI System. To be discussed in next meeting(s).