Attendees & Representation
...
| Representative | Organization | Role | |
|---|---|---|---|
| Herbert Damker | Deutsche Telekom AG | TSC Chair, Active Maintainer | x |
| Shilpa Padgaonkar | Deutsche Telekom AG | Active Maintainer | x |
| Jan Friman | Ericsson | Active Maintainer | x |
| Toshi (Toshiyasu) Wakayama | KDDI | Active Maintainer | x |
| Ludovic Robert | Orange | TSC Deputy Chair, Active Maintainer | x |
| Adnan Saleem | Radisys | EUC Representative | |
Doug Makishima | Summit Tech | EUC Representative | x |
| Diego González Martínez | Telefonica | Active Maintainer | x |
| Jose Luis Urien | Telefónica | Active Maintainer | x |
| Mahesh Chapalamadugu | Verizon | EUC Representative | |
| Eric Murray | Vodafone | TSC Deputy Chair | x |
| Kevin Smith | Vodafone | Active Maintainer | |
| Chris Howell | Vonage | Active Maintainer | |
| George Glass | TM Forum | TM Form Representative | |
| Henry Calvert | GSMA | GSMA Representative | |
| Mark Cornall | GSMA | GSMA Representative | x |
...
- Reports given by Ludovic and Eric
- Important updates:
- Progress with linting, adaption ongoing by sub projects
- Work move forward for Test Case as some company provided comment on issue Test definitions - implementations guidelines and artifacts · Issue #94 · camaraproject/Commonalities (github.com)
- Shilpa offered to create a short Camara-API-Testing-Guidelines.md doc
- Call for action (mains)
- Version 0.2.0 of documents and artefacts available. Sub project are asked to state to which release they are compliant.
- Issue about X-Correlator (Set X-Correlator as Required in OAS Definition, X-Version removed by jlurien · Pull Request #115 · camaraproject/Commonalities (github.com)) as we have a consensus.
- This will not go in release 0.2 but next release
- Shilpa mentioned the CAMARA_common.yaml PR (Update and rename CAMARA_common.json to CAMARA_common.yaml by shilpa-padgaonkar · Pull Request #107 · camaraproject/Commonalities (github.com)) that define common data types for CAMARA APIS
- Probable impact on some API
- Eric raised the point about tagging the issue related to input from the End_User council.
- We need to think about it.
...
- Report given by Diego
- Documentation update with securitySchemes final agreement.
- PR: https://github.com/camaraproject/IdentityAndConsentManagement/pull/93. Comment by Eric has been considered as an addition, Client Credentials now appearing as an option
- Release 0.1.0 to be made available once former point is merged
- Issue about adding further clarification for scenarios where user consent is not given (PR#86 Auth code flow update to fix issue #70 by jpengar · Pull Request #86 · camaraproject/IdentityAndConsentManagement (github.com))
- Issue about securitySchemes final agreement (Documentation update with securitySchemes final agreement by jpengar · Pull Request #93 · camaraproject/IdentityAndConsentManagement (github.com) ) we are on final steps before validation
- Jan mentioned the issue Claims to be used in oAuth Access tokens/ OIDC Identity tokens · Issue #100 · camaraproject/IdentityAndConsentManagement (github.com)
- It could be resolved by documentation. This is not a showstopper for the release 0.1 - Then we can solve this one and release 0.2.
- Jan mentioned the issue Claims to be used in oAuth Access tokens/ OIDC Identity tokens · Issue #100 · camaraproject/IdentityAndConsentManagement (github.com)
- Question about how we can proceed for CAMARA Profile - Do we want to use existing one or build one.
- Diego think it's better to craft our own profile (and filling gap from OIDF one) in order to move faster.
- Shilpa agreed on this and making a combination from FAPI2 assets & new from CAMARA
...