...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Attendees & Representation
...
- Existing PRs:
- PR #55: Update CAMARA Mobile Device Identifier API.yaml
- Proposed changes:
- Separates API into two endpoints:
retrieve-identifier
to obtain individual device detailsretrieve-type
to obtain type of device
- Add scopes for each endpoint
- Add
lastChecked
field to indicate when information about device was last confirmed correct - Updates documentation on MSISDN being treated as secondary MSISDN by network
- Separates API into two endpoints:
- Fixes issues #47 and #30
- Proposed changes:
- PR #55: Update CAMARA Mobile Device Identifier API.yaml
MEETING UPDATE:
- PR is approved by the meeting
...
- New Issues
- None
- Existing Issues
- Issue #47: Add ageOfInformation field to API response
- Follows on from Discussion #35
- Current API response gives no indication of when the physical device information was collected for the specified subscription identifier (e.g.
phoneNumber
). Dependent on the backend implementation, this information could have been collected some time earlier, and potentially be out of date - Current proposal is to introduce
lastChecked
response parameter, defined as follows:
- Issue #47: Add ageOfInformation field to API response
...
AGREEMENT: Leave discussion open for now, but prioritise returning IMEI / IMEISV
- Closed Discussions
- None
Other Issues
- Kevin raised the point that YAML schemas should use the common schemas defined in CAMARA_common.yaml where appropriate. Ideally, they could be directly referenced, though this can cause issues with some OAS viewers.
- ACTION: Kevin to check how OAS viewers handle external references
Discussion on IMEI Fraud API
...