Open pchainho opened 9 years ago
The following is an commented and extended version of the first version above.
Daily Life
Similar to #1 but in this case each participant is subscribed to different CSPs, having each one the service behavior set by its CSP (e.g. Alice conversation usage experience is set by its service provider).
The emntioned entities above are are not actors as listed and described in "Actors and roles". These are business roles, which are sometimes also present under the same name as actor. Actors would be:
Alice communicates with Bob
no communication between Alice and Bob
Not currently possible with Web Communications. Essential to achieve seamless interoperabilty between any user without having the need to use more than one conversational App. Overcomes the domination of established communications providers. Building bridges across network borders.
@sdruesedow the actors described in "Actors and roles" are instances of generic Business Roles for the Usage Scenario. I've started describing these generic Business Roles at https://github.com/reTHINK-project/use-cases/blob/master/docs/D1.1/business-models/business-roles.md
But in general I agree with your more detailed description. A few additional comments:
we (from W1/4 perspective) added authentication and authorization to the pre-condition in order to have a clear separation between registration (1-time process) and authentication/authorization, which happens on every login
Agree, but what is the difference between registration and subscription?
Subscription is taking on the service, creating an account, specifying preferences. Registration - if it is the same as logging to the service - is current participation which also signifies current availability.
My Best
Rebecca
On 10 March 2015 at 11:13, pchainho notifications@github.com wrote:
Agree, but what is the difference between registration and subscription?
— Reply to this email directly or view it on GitHub https://github.com/reTHINK-project/use-cases/issues/2#issuecomment-78034512 .
In @sdruesedow comment there is a separation between registration and login, if I understood correctly
sorry for the confusion. I agree with Rebecca's comment. In my previous comment I used the wrong term "registration" instead of "subscription"
WP1 Telko reviewed and changed the use case.
Actors
Alice and Bob are Identified Consumer that are Conversation Participants
Alice and Bob are subscribers of different Communication Service Providers.
Pre-conditions
81 #83 Alice and Bob are using different CSPs, but are registered (authenticated, authorized) at the IdP of their CSP.
Description
Similar to #1 but in this case Alice and Bob are subscribed to different CSPs. They are using the corresponding service behavior - user interface of their CSP (e.g. Alice conversation user experience is set by its service provider).
Differentiation - Market Relevance
Not currently possible with Web Communications. Essential to achieve seamless interoperabilty between any user without having the need to use more than one conversational App.
Remark: The above mentioned description is one option, in which each user keeps their original user experience. There is also the possibility that only one user experience is provided, this would mean that e.g. that Alice (who initiates the call) user experience is ported to Bob, once he accepts the call.