Scope of QualityOnDemand for Fall24 CAMARA release

[hdamker]

This issue shall define which issues are within scope of both APIs of the Sub Project for the Fall24 release and will be regularly updated based on the decision within the QoD meetings.

Split into quality-on-demand and qos-profiles

• Proposal to split QoS Sessions and QoS Profiles into two separate API definitions #265

Duration, extendDuration & Co

• Consolidated issue for duration, extentDuration, startedAt, expiredAt, maxDuration and their formats (to be updated) #291
  • includes Duration in QosProfile and SessionInfo #249, Duration in QoS Session and QoS Profile #266, Clarification of session creation and startedAt #280, startedAt y expiredAt do not follow date-time format #281, Duration behavior during session extension #288

Device object alignment with Commonalities and related error messages

• Align with Commonality decision about optional device object and respective documentation #313
• Return 422 instead of 501 if the service is not implemented for specified device  #315
• Align error responses for Device Object with v0.4.0 of Design Guidelines #316
• Align quality-on-demand with Commonalties regarding optional device object and error messages #326 (will address the three issues)

Enhancements

• Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement #244 (Add required security scheme and scopes #295)
• Extend QoS Profile queries to list profiles based on specific users or devices #166
• List endpoint for active sessions of authenticated user #101

Smaller issues

• Error behaviour when session cannot be created due to "time cap" limitation #257
• Align phoneNumber with guidelines, with prefix + mandatory #298
• Add more HTTP Status Codes for improved Error Handling #305 (Add HTTP-429 for quality-on-demand #306)
• Purpose of messages array in SessionInfo schema is undocumented #309 (Remove unused messages object in SessionInfo schema #312)
• Remove unresolved reference within quality-on-demand documentation #321
• Remove cucumber code from the repository #322
• Alignment of notification web hook to CloudEvent subscription model #332
• Update reference to the QoS Profiles API #333
• Remove reference to protocol in sink description #338
• New API Readiness Checklists for quality-on-demand and qos-profiles #320

New API (added as discussed in QoD meeting May 31st)

• Provision mode for QoD #268 (PR New API QOD Provisioning #299)

Post r1.1 issues & PRs (relevant for M4)

• Update and enhance test definition file for QOD API #245 (QoD Test definitions #349, Update QoD_API_Test.feature  #350)
• Review and update User Story for Quality On Demand #342
• Operation to get qos-profiles for a device MUST use a verb and needs a security object #345 (Updating names qos-profile of endpoints #348)
• Create PR for public release r1.2 (M4) #352
• Mentioning of the device object in the Session Info description #340

[hdamker]

Added #298 to the list above.

[hdamker]

Added #268 and linked PR #299 as discussed in QoD meeting May 31st.

[hdamker]

Added #305, #309 (done), and #313 as discussed in QoD meeting June 28th.

[hdamker]

Restructured the scope, added new issues #315, #316, #321, added "Release Assets" #245, #320, #322 for discussion within QoD meeting July 12th (further updates after the meeting)

[hdamker]

Updates based on the QoD Meeting July 12th: removed #286 from scope, moved #322 into smaller issues.

[hdamker]

Added #332 which need to done to be compliant with Commonalities 0.4.0

[hdamker]

Added the corrections of #333 and #338 to the scope

[hdamker]

Collected the (currently) remaining issues and PR to be done before M4 in the issue description. Added issues

• Review and update User Story for Quality On Demand #342
• Operation to get qos-profiles for a device MUST use a verb and needs a security object #345
• Create PR for public release r1.2 (M4) #352

[hdamker]

Release r1.2 created, all issues within scope done.