Community Attendees:
Community Attendees:
LF Staff:
)Agenda
Antitrust Policy
Any comment on previous meeting minutes?- See prepared minutes
Minutes
Priority is to deliver our API assets for Milestone 4
OTP Validation
New
- Remove 405 code in the yaml & test definition (issue #79 & PR #80)
- Alignement with Commonalities issue #285
- To be merged today
SIM Swap
New
- Change sim swap file name for commonalities alignement (Issue #138 & PR# 139)
- Change the yaml name from
sim_swap.yamltosim-swap.yaml 
Done
- Change the yaml name from
Contact and TermsOfService fields should be removed from info object (issue #141)
- Alignement with Commonalities
- PR done
- Exclusion of the alpha version of sim-swap-subscriptions (issue #142)
- Check if any opposition
- "how-to" to be discussedIn fact 2 topics are discussed:
- How to manage a repo with 2 APIs with distinct maturity level (stable and alpha for example)?
- Keep them in same repo or distinct repos
- Both are possible (explanation by Jorge & Herbert in the thread)
- Keep them in same repo or distinct repos
Do we want to have the sim-swap-subscriptions part of this meta-release?
- How to manage a repo with 2 APIs with distinct maturity level (stable and alpha for example)?
- Obsolete/wrong statement in API description that "either one or both endpoints could be implemented" (issue #144)
- As discussed in commonalities the proposal is:
- We have a discussion on SimSwap API and in particular the challenge to provide the date for some implementation. Diego provided his perspective; this is covered with the current API where we can sent back null information if date is not available. To be discussed in the simswap group but this proposal could avoid splitting.
- As discussed in commonalities the proposal is:
Ongoing
- Test Case merged (PR #70)
- Updating of the user story (PR #139 + issue #131) - merged
- What to do when the SIM Swap date is greater than the max historic days that the Telco allows for Privacy Reasons?
- Good discussion on the issue - seems that adding a monitoredPeriod attribute to retrieveSimSwapDate to provide at least this information if there is no date returned
- See proposal
- Item for next meta-release
- Request body is required but all properties are optional (Issue #118)
- No update from commonalities
- As change will be a breaking change in future no sure we have not here a 'de facto' decision.
Number Verification
New
- replace OAuth2 by OpenId Connect (Issue #133 & PR #134)
- OK for the modification
- Do you think that we still need this additional document? and its content should not be in the yaml?
- Change error NUMBER_VERIFICATION.INVALID_TOKEN_CONTEXT for just INVALID_TOKEN_CONTEXT (issue #135 & PR #136)
Ongoing
- User story - Are they still blocking point to marge them? it must be done before the end of the week
- To be checked with Axel Nennker and Fernando Prado Cabrillo
- Test definition for Number Verification (PR #124)
- Open comment regarding use of 401 or 403
- (reminder of last meeting but we haven't created an issue) potential use of SIM swap to perform a numberVerification
- Need to be discussed in Commonalities because must be enforced for all our APIs.
- Make sense to be shared also with the OpenGateway Product
- Axel Nennker would trigger the issue to Commonalities