DRAFT
Attendees & Representation
...
Name | Organisation | |
---|---|---|
AT&T | x | |
CableLabs | ||
CableLabs | x | |
Deutsche Telekom | x | |
Deutsche Telekom | x | |
Deutsche Telekom | ||
Deutsche Telekom | ||
Ericsson | x | |
Ericsson | x | |
GSMA | x | |
Ola Ajibola | GSMA | x |
GSMA | ||
KDDI | ||
KDDI | ||
KPN | x | |
Limux Linux Foundation | ||
Nokia | ||
Orange | ||
Orange | ||
SingTel | x | |
SpryFoxNetworks | ||
Telefonica | x | |
Telefonica | ||
Telefonica | ||
Telus | ||
TMUS | x | |
Vodafone | ||
Vodafone | x |
Agenda
Antitrust Policy
Action Items Review
Open Discussions
Issues review
PRs review
Any Other Topics
...
Review of Action Items and Minutes from previous meetings
Task report | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Approved:
2024-09-16 Commonalities WG Minutes
...
https://github.com/camaraproject/Commonalities/discussions/309
Discussion if/how to adopt Arazzo in CAMARA is open
https://github.com/camaraproject/Commonalities/discussions/310
Consideration for the future.when one subscription with multiple event types is allowed
https://github.com/camaraproject/Commonalities/discussions/312
Answered for KYC Match idDocumunt issue
related to Runtime Restriction API proposal
Issues review
Issue #273 about scope of the next version was updated
https://github.com/camaraproject/Commonalities/issues/299
G. Murat Karabulut pointed out in the comment 2 aspects of initial event:
Agreed to count initial event when
subscriptionMaxEvents
is checked for the subscriptionsSpecial feature to distinguish whether an event notification message coming back in response to an initial event. or it is just an event occurrence - still open for discussion
https://github.com/camaraproject/Commonalities/issues/306
First we need to prepare the changes in requirements in the current document, then it will be reshaped
The draft PR with ToC will be opened to allow all interested to contribute
https://github.com/camaraproject/Commonalities/issues/308
newly added - waiting for views on unifying the set of Error codes present in every CAMARA API specification
https://github.com/camaraproject/Commonalities/issues/303 - covered in PR #313
https://github.com/camaraproject/Commonalities/issues/304
As issue occured to be related not only to subscriptions, but to access to resources the guidelines should be in dedicated section like: 11.7 API access restriction (based on token & clientId)
will be covered in PR #313
https://github.com/camaraproject/Commonalities/issues/294
As more related to implementation should be checked by GSMA and reviewed by TSC
https://github.com/camaraproject/Commonalities/issues/307
Clarified that Commonalities should start the next release with r1.1
https://github.com/camaraproject/Commonalities/issues/302
Waiting for proposal of solutions or guidelines that can be used by sub-projects to tackle multi-SIM subscriptions.
PRs are expected by the end of October to cover the scope of next release - cf #273
PRs review
https://github.com/camaraproject/Commonalities/pull/311
Prepared for patch release maintenance-0.4 branch is used
After patch release it can be merged in the main branch
https://github.com/camaraproject/Commonalities/pull/314 - proposed to be consedered by ICM and sub-projects that released the stable API releases.
https://github.com/camaraproject/Commonalities/pull/316
when agreed the changes should be applied to event subscription definitions and artifacts
https://github.com/camaraproject/Commonalities/pull/315
common data type where both Circle and Polygon are defined
In the next stage additional types of area (like postal code or administrative areas) can be added
https://github.com/camaraproject/Commonalities/pull/313
work in progress
#290 to be tackled when preparing new Guidelines document #306
AOB
The next meeting is on October 28th 2024 using https://zoom-lfx.platform.linuxfoundation.org/meeting/91016460698?password=d031b0e3-8d49-49ae-958f-af3213b1e547
...