Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
DRAFT
Attendees & Representation
Name | Company | Attendee |
---|
Eric Murray | Vodafone |
|
Sachin Kumar | Vodafone (moderator) |
|
Kevin Smith | Vodafone |
|
Alex Ferreira | Phronesis |
|
Matthew Hornsey | Phronesis |
|
Matthew Hand | Phronesis |
|
Sébastien Synold | Intersec |
|
S, Vigneshwaran | Cognizant |
|
Karthik Raj Rethinakumar | Cognizant |
|
Manish Jain | Cognizant |
|
Huub Appelboom | KPN |
|
Rafal Artych | DT |
|
Axel Nennker | DT |
|
Abhisek Das | Infosys |
|
Brian Smith | Shabodi |
|
Umair Ali Rashid | Shabodi |
|
Foo Ming Hui | Singtel |
|
Vilim Duganic | Infobip |
|
Surajj Jaggernath | Vodacom |
|
Walid Trabelsi | Sofrecom (Orange) |
|
Aleksander Brankovic | Ipification |
|
Agenda
- Review of previous meeting minutes
- Review of Device Identifier API status
- AOB
Review of Device Identifier API status
- Current "work in progress" version can be found here
PRs
New PRs |
PR #85: Prepare pre-release r2.1- Preparation of release r2.1 for device-identifier v0.2.0-alpha.1
MEETING UPDATE :
|
Existing PRs |
PR #78: remove misleading sentence on from where the API can be called- Proposal to remove description text stating that API can be called by "an application server or other 3rd party server"
- Discussion and revision required as the API clearly can be called by an application or other 3rd party server
MEETING UPDATE :
|
Closed PRs |
PR #83: Add global tag definitions to OAS definitionMEETING UPDATE :
PR #84: Rename CAMARA Mobile Device Identifier API.yaml to device-identifier.yaml- Update API filename using convention agreed in Commonalities
- New name is device-identifier.yaml
MEETING UPDATE :
PR #72: Initial Test Definitions for DeviceIdentifier retrieve identifier- Proposal for test definitions in response to Issue #68
- Final review required by more API participants
MEETING UPDATE :
PR #73: Add EUDI Wallet and Mobile Device Insurance User Stories- Additional user stories for Device Identifier
- Adds a use case where the physical device itself requests its own IMEI (because OS will not provide it to the app)
- Review required by API participants
MEETING UPDATE :
|
Issues
New Issues | None |
Existing Issues |
Issue #71: Why "The API can be called by an application server or other 3rd party server"- Issue associated with PR #78
MEETING UPDATE :
Issue #80: Purpose of the lastChecked field in the response?lastChecked response field is not clear to all potential API consumers- This is the last time that the API provider checked which IMEI was being used by a specific MSISDN
- Could be "now", or could be some minutes ago. Implementation dependent.
- How to fix?
- Rename field (maybe to
lastConfirmed )? - Better description in YAML itself?
MEETING UPDATE :
Issue #21: API Definition Terminology
MEETING UPDATE : ACTIONS: - Eric to update issue text (still open)
|
Closed Issues |
Issue #79: Use API name as file name of the the YAML and with the info.title field- Naming standard has been informally adopted for meta-release APIs, but not yet formally defined by Commonalities
MEETING UPDATE :
Issue #68: API Test Cases Required to be Defined
MEETING UPDATE : - See PR #72
- Issue can be closed when above PR is merged
|
Discussions
New Discussions | None |
Existing Discussions |
Discussion #36: Alternative device identifiers- An alternative proposal is to salt the IMEI with an API consumer specific salt and then hash it
- This would a less useful identifier (only useful to the API consumer) but easier to justify providing under an opt-out or no consent basis
- Use cases for such an alternative identifier are not clear
MEETING UPDATE : - Discussion updated by Axel Nennker with proposal to include PPID as a 3rd device identifier that can be requested (in addition to IMEI or TAC)
MEETING UPDATE :
|
Closed Discussions | |
Other Issues
AOB
- Next meeting proposed to be held Friday 1st November 2024 @ 09:00 BST using Zoom