Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

Attendees & Representation

...

Closed PRs


Panel
borderColorred
borderStylesolid

PR #86: Reset device-identifier.yaml version to "wip"

  • Reset YAML version to wip following 0.2.0-alpha.1 release

MEETING UPDATES

:

  • Already approved and merged


Existing PRs

None

New PRs


Panel
borderColorred
borderStylesolid

PR #87: Update Device object handling and description

  • Other APIs passing a Device object do this by passing a separate parameter named device, even if that is the only object passed in the request.

  • This PR:

    • Updates the Device Identifier API to use this pattern
    • Updates documentation on identifying the device from the access token following the current agreement in Commonalities
    • Updates the API error responses following the current agreement in Commonalities

MEETING UPDATES

:

  • Add examples for different request body scenarios
  • Leave open for comments until next meeting


Panel
borderColorred
borderStylesolid

PR #88: Update LastChecked description

  • Update description for lastChecked field to make its meaning clearer

  • Fixes Issue #80

MEETING UPDATES

:


...

Closed DiscussionsNone
Existing Discussions


Panel
borderColorred
borderStylesolid

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 UPDATES:

:

  • 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)

:

  • Axel Nennker to review and make proposal for additional physical device identifier

:

  • No update


New Discussions

None

Other Issues

  • None

AOB

  • Next meeting proposed to be held Friday 3rd January 2025 @ 09:00 UTC using Zoom

...