Issue | Who | Status | Comments |
|---|
https://github.com/camaraproject/CustomerInsights/issues/3 | DT, WG | | 28/NOV: This issue is to be managed after Zoom meetings are in place and initial API information can be provided. With that a PR can be generated |
https://github.com/camaraproject/CustomerInsights/issues/8 | TEF, WG | | 28/NOV: Issue will be kept open until Zoom Meetings are managed |
https://github.com/camaraproject/CustomerInsights/issues/9 | TEF | | 28/NOV: Issue to cover initial User Stories. Related PR#10 created
Explained during the meeting the rationale of the Use cases. To be checked offline and provide comments. Other Use case are welcome to be gathered now or in the future. This document is mandatory for the MetaRelease |
https://github.com/camaraproject/CustomerInsights/issues/11 | TEF | | 28/NOV: Issue to cover Baseline API proposal for discussion. Related PR#12 created Main Points indicated: Algorithm generating the rating: Kev Scarr indicates we would need to agree on an aligned algorithm rules to generate analogous ratings from Telco Operators. Pedro Díez García indicates this is not part of the design but the underlying BE logic that provide the score. And yes, we need to talk about that in order to reach an alignment.
VF is beginning to work in solutions for this kind of solutions. TEF has a pilot in VIVO (BR) and will compile information to check solution in place. DT has solutions in some central European countries and also check internally Rating Models: Two initial Models presented, other model could also be incorporated by other Operators based on their business needs. At least TEF is using the “veritasIndex” Model (solution in BR) WG agrees that a future discussion, not in terms of definition, but in the context of GSMA OGW is to have alignment in the (minimum) set of models to be supported by a Telco operator for interoperability purposes.
Error Model: Initial approach but that will have to be enhanced / corrected with the upcoming agreements from Commonalities within MetaRelease Spring 25. Regulations Constraints: Rafal Artych comments that internally each telco review the wording used within the context of the API to check if any legal regulation problem could exist, and based on that make some rewording. to be checked internally by all.
PR will be reviewed offline and provide comments |
AoB | WG | | Need to generate a “parent” issue to compile MetaRelease Spring 25 actions:
- API release tracker
- User Stories
- API Spec
- API Readiness Checklist
- API testing
Sub-Project Information:
CAMARA repository: https://github.com/camaraproject/CustomerInsights
Confluence Subproject site: CustomerInsights |