...
- 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 #47: Add ageOfInformation field to API response
ISSUE UPDATE:
- Current proposal is to introduce
lastChecked
response parameter, defined as follows:
- Current proposal is to introduce
lastChecked:
description: Last time that the associated device identity was checked and updated if necessary
type: string
format: date-time
MEETING UPDATE:
- 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 #30: Defined scopes and meanings, being discussed in Issue
ISSUE UPDATE:
...
Updated proposal is to have two separate endpoints as follows:
get-identifier
with scopedevice-identifier:get-identifier
which returns:- imeisv
- imei
- tac
- model
- manufacturer
get-type
with scopedevice-identifier:get-type
which returns:- tac
- model
- manufacturer
MEETING UPDATE:
- Issue #21: API Definition Terminology
- Issue is out of date
- Issue #21: API Definition Terminology
...