Content Comparison

PR #94: Release r1.2 (Spring'25 M3)

• Publication of Spring'25 M3 release candidate v0.2.0-rc.1

MEETING UPDATES

07 Feb 2025:

• Reviewed by Release Management (Tanja). Some changes to be made.
• Request for compliance with Commonalities 0.5.0-rc.1 and ICM 0.3.0-rc.1
• Issues / PRs raised following Release Management review:
  • ICM template: #98
  • X-Correlator header pattern: #99
  • Error documentation: #101

07 Mar 2025:

• PR merged and r1.2 pre-release now published

PR #101: Update error documentation in info.description

• Update error documentation in info.description

  • Some errors
  • Some details are out of date
  • Better explanation of CAMARA or API specific errors
• Needs to be approved and merged for Spring'25 meta-release

MEETING UPDATES

07 Feb 2025:

• Leave open for comments until end of Tuesday 11 Feb 2025, and then merge before requesting final review of PR #94

07 Mar 2025:

• PR approved and merged

PR #102: Reset version numbers to WIP following release r1.2 Update error documentation in info.description

• Admin PR, to reset all version numbers to wip following publication of release candidate

MEETING UPDATES

07 Mar 2025:

• PR approved and merged

PR #103 r1.3 Spring'25 Meta-Release M4 PR

• M4 PR for release 0.2.0
• No changes relative to 0.2.0-rc.1, other than version number updates

MEETING UPDATES

07 Mar 2025:

• < Meeting update >

PR #89: Remove multi-sim text

• Multi-SIM support is not well-understood and should be "solved" for all CAMARA APIs.

• Multi-SIM support was discussed in several CAMARA API subprojects without solution.

• For interoperability reasons API providers should handle the Multi-SIM case in the same manner.

MEETING UPDATES

03 Jan 2025:

• Eric Murray to propose more generic text describing different options for multi-SIM scenario handling

07 Feb 2025:

• Alternative wording proposed in this comment

07 Mar 2025:

• < Meeting update >

PR #92: Use scopes and introduce a pairwise pseudonymous identifier

• This PR proposes two changes to the API definition:

  • Introduction of a third device identifier ppid, which is a pairwise pseudonymous identifier for the device
  • Control of fields included in the response by individual scopes, rather than by a single scope covering all possible response fields

MEETING UPDATES

03 Jan 2025:

• Discussion:
  • PPID as third device identifier is fine, but should be introduced as additional endpoint rather than controlling through scopes
  • A better description of the properties of a PPID is required, in addition to the external link
    • For example, if a new SIM (from the same MNO) is used in the physical device, should the PPID be re-generated?
• Eric Murray to comment in PR

07 Feb 2025:

• Cannot now be merged before Spring'25 meta-release. Leave open in case Axel Nennker wants to revise. Otherwise raise new issue on PPID introduction following Spring'25 meta-release.

07 Mar 2025:

• < Meeting update >