Closed jorge-cardoso closed 12 years ago
I tend to remove all of this Roles into a Business Model vocabulary ore the OSSN.
Even to provider role is something like the gr:hasBrand.
Similar to #16 and #18
This means:
remove hasStakehodler, hasIntermediary, hasBusinessOwner, hasConsumer, hasStakeholder from core.
I believe we do need the notions of RoleType (Owner, Provider, Consumer, etc), and the notion of Role (e.g., entity A playsRole Provider in this situation...).
There has been considerable effort devoted to modelling Roles etc. We should adopt some of these approaches.
My feeling though is that the notion of Roles would not belong to OSSN which I believe is more about inter-services relationships?
My first thoughts are to aggregate all the roles (remove hasStakehodler, hasIntermediary, hasBusinessOwner, hasConsumer, hasStakeholder from core) around one new class. New actual roles needed can be decided in 6 month. The ones that we have seem to be a good starting point.
Proposal:
New class usdl-core: Roles and the propoerty usdl-core:hasRoles attached to the ServiceOffering ? Or to the service?
Related to issue #17, #18, #32, #29, #6
Since we have so many roles (hasProvider, hasBusinessOwner, hasConsumer, hasIntermediary, hasStakeholder), should a class usdl-core:Roles be created to aggregate all this properties?