Versions Compared

Key

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

...

New Issues
Panel
borderColorred
borderStylesolid

Issue #71: Why "The API can be called by an application server or other 3rd party server"

  • Issue associated with PR #78

MEETING UPDATE :

  • <MEETING UPDATE>
Panel
borderColorred
borderStylesolid

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 :

  • <MEETING UPDATE>
Panel
borderColorred
borderStylesolid

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 :

  • <MEETING UPDATE>
Existing Issues
Panel
borderColorred
borderStylesolid

MEETING UPDATE  :

    • See PR #72
    • Issue can be closed when above PR is merged
Existing Issues
Panel
borderColorred
borderStylesolid
  • Issue #21: API Definition Terminology

    • Issue is out of date

MEETING UPDATE  :

    • No update

MEETING UPDATE :

    • <MEETING UPDATE>

ACTIONS:

    • Eric to update issue text (still open)
Closed Issues
Panel
borderColorred
borderStylesolid
  • Issue #61: Simplification of Device object - short term solution

    • Commonalties proposes to revise DeviceObject
      • Should be optional, with 3-legged access token normally used to identify the mobile subscription
      • If 2-legged token is used, device object should be provided to API
      • Network Access Identifier (3GPP External Id) option to be removed as support not common
    • Will be closed by PR #64

...