Versions Compared

Key

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

...

  • Approval of previous meeting minutes #14 and meeting agenda

  • Open issues and PRs

    • Issues: #40 #48 #50 #51

    • PR

  • Timeline and next steps

  • AoB

...

#

Company

Summary

Issue#40

Ericsson

Area Data-type

Issue#48

Telefonica

New release scope

Issue#50

Telefonica

Aling with guidelines for async responses

Issue#51

Ericsson

Support time Windows in the past

Approval of previous meeting minutes & documentation (1)

Meeting Minutes #14#15

Approved

API proposal review (2)

Issue#40

...

AP: provide direct feedback on the commonalities issue Issue #242. Groups is ok to create a homogeneous definition of the area types, as long as each API can later select granularly which types apply (and not getting obligation to support all the types, or getting involved in a complex data model).

Status: Issue included in spring25 commonalities scope, participantes to comment there. API will be aligned accordingly.

Issue#48

Propose new scope for next release.

...

Issue#50

Include alignment with commonalities for the async response mechanism.

Status:

Issue#51

Support time window for past time frames, historical data.

Status:

AoB (4)

Next steps:Move sessions to Ad-hoc meetings, when required by open issues or scope discussion.

Discussion Summary

#

Summary

Status/conclusion

Issue#40

Area Data-type

ALL to provide feedback into commonalities issue

Issue#48

New Release Scope

ALL to provide more proposals

Issue#50

Aling with guidelines for async responses

Issue#51

Support time Windows in the past

Next steps

  1. Scope for next release → #16#17

  • Next call will be TBD