Page Comparison

DRAFT

Attendees & Representation

...

• Current "work in progress" version can be found here

PRs

• New PRs:
  • None

• Existing PRs:
  • None

...

• 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

ISSUE UPDATE:

• • • Current proposal is to introduce lastChecked response parameter, defined as follows:

...

• • Issue #30: Defined scopes and meanings, being discussed in Issue 
    • The two use cases (retrieve all parameters or only tac / manufacturer / model), two separate scopes are required
    • Should they be two scopes of same endpoint, or associated with separate endpoints

ISSUE UPDATE: 

• • • Updated proposal is to have two separate endpoints as follows:

      get-identifier with scope device-identifier:get-identifier which returns:

      • imeisv
      • imei
      • tac
      • model
      • manufacturer

      get-type with scope device-identifier:get-type which returns:

      • tac
      • model
      • manufacturer

MEETING UPDATE:

• • Issue #21: API Definition Terminology
    • Issue is out of date

...

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

...