Preparation of Meta-relase Fall25 scope

[rartych]

Problem description

According to initial timeline for Fall25 the following milestone dates are expected

Milestone	Target date	Target status
M0	03-31	kick-off preparation
M1 (Commonalities & ICM)	04-15	Alpha release

For these meta-relase we need to align with proposed timeline, to give sub-projects time for alpha-release preparation and proper testing.

Expected action
Prepare the scope before M0.
Review of pending issues and propose new issues to be discussed before M0.

[rartych]

Proposed topics:

• for milestone M1:

  • Cleanup and slim down design guidelines document #306
    • CAMARA API Design Guide document #441
    • Provide a specific document for CAMARA API Event Subscription and Notification #442

• second turn of improving documents clarity:

  • Clarifications related to request body and response definition #445

    • Request response definitions and other clarifications in chapter 5 of API Design Guide #450

  • Review of Security chapter in API Design Guide #446

    • Update of Security chapter in CAMARA-API-Design-Guide.md #467

  • Capitalization of Key Words CAMARA API guides #447

  • Enhancements in "sorting" feature #448

  • error definitions

    • Clarification required on usage of UNAUTHENTICATED and AUTHENTICATION_REQUIRED error codes #368
      • Remove AUTHENTICATION_REQUIRED error code #429
    • Remove 422 IDENTIFIER_MISMATCH error code as this can allow PII leakage #431
      • Remove IDENTIFIER_MISMATCH error and introduce DeviceResponse object #455
    • Adding a section in API info.description to provide rationale for not documented Error responses and a reference for their format #438
      • Not Documented Error Responses info.description section #457

  • Proposal for x-correlator format change #436

    • X-Correlator Format Change #463

  • Enhancements for CAMARA Subscription/Notification Architecture #437

    • Enhancements Subscription/Notification Architecture for Fall25 #464

  • Update types property of Subscription schema in event-subscription-template.yaml #432

  • pending issues

    • Proposal to add a standard for defining durations for API Design guidelines #137
      • Text description aligment for duration format fields #459
    • Include Reference Link to CAMARA API Design Guidelines in Notification Cloud Events Artifact #290
      • Links to CAMARA API Event Subscription and Notification Guide in artifacts #453
    • Follow the principle of data minimization for events based on explicit subscriptions #295
    • Guidelines for asynchronous response in callback #297
    • Synchronization Status for initialEvent = true notifications #299

• for milestone M2:

  • Update of linting ruleset #188
    • Add a type-check for the linting-rules #433
    • Linting rules definition update #466
  • Provide Test Definition template for explicit subscription API #293
    • Add event-notification feature file template #470

[hdamker]

As an outcome of review of #441 the new issues #445, #446, #447 and #448 were created. Are they as well in scope of Fall25 or not?