DRAFT MINUTES

Attendees & Representation

...

• Commonalities and ICM release candidates:
  • Commonalities Release 0.4.0-rc.1 (draft PR)
  • Identity and Consent Management Release 0.2.0-rc (PR in review)
  • Any new issues for QualityOnDemand?
    • Create new issue to make Device object optional and add text according to (merged) Commonalities PR #233 Proposal to simplify device object and improve interoperability...
• Governance: Sub Project can have multiple API repositories going forward
  • Update of ProjectStructureAndRoles to allow Sub Projects (API families) with multiple API repositories
  • QoS Profiles and/or QoD Provision into own repositories? 
    • Randy: keeping together for now make sense
    • No motion to split into additional repositories now

Open Pull Requests (open for review)

• PR #295 Add required security scheme and scopes by Eric Murray
  • Ready for final review.From last meeting:Eric will update the

• PR with documentation for the following points:
  • Endpoints which have different behaviour with 2-legged vs 3-legged
  • Endpoints which don't require 3-legged token (no user resource involved)
• The dependency of the Device object on the used authentication will be documented in a separate PR (after decision in Commonalities #171)
PR #306 Add HTTP-status-codes for better Error Handling
• PR for new issue #305
• Add additional HTTP status codes 405, 406, 429
• Supersedes also the (draft) PR #297 Add error 429 QUOTA_EXCEEDED?
• Maximilian Laue to address comments done during the meeting, afterwards ready for final review

• PR #299 New API QOD Provision
  • Name of endpoint to be discussed (see comments from Randy Levensalor within the PR). Eric: "provision" is mobile terminology.
  • From last meeting:
    • Jose introduced the proposed API
    • Eric: Does the API still allow to have multiple provisions per device? Or should it be restricted to one, and enhance the complete traffic of the device (would simplify the API a lot)
      • Jose: all traffic is only one possible use case (hence 'applicationServer' is proposed to be optional)
      • Open: Are there use cases to provision QoD for specific flows (defined by applicationServer)? - Jose will ask on product side
  • , would be good to avoid.
  • Jorge Garcia Hospital will ask Jose Luis Urien Pinedo to address the comments.
  • To be able to include it within the release candidate we need to conclude the discussions about the PR until the next meeting (starting the final review).

Closed issues

• #310 Remove terms of service and contact from APIs
  • Done with PR #311

...

• #309 Purpose of messages array in SessionInfo schema is undocumented
  • Ramesh Shanmugasundaram creating PR, if no objection will create the PR
  • If there are no objections to delete the parameter we will do so.

• #305 Add more HTTP Status Codes for improved Error Handling
  • see PR
  #302 Providing developers with alternate to QoS profile
  • new enhancement proposal by Mahesh Chapalamadugu 
  • discussion to be continued within the issue
  • Proposal to put into backlog for next release => put into the issue as proposal.#306

Issues relevant for v0.11.0

• #292 Scope of QualityOnDemand for Fall24 CAMARA release
  
  • From last call: Need to add Issue #268 Provision mode for QoD to this release
  • New additions?
    • Issue to make device object optional => Herbert Damker to create the issue.
    • Issue #305
    • Issue #309

• #101 List endpoint for active sessions of authenticated user
  • Jose Luis Urien Pinedo proposed a list endpoint for provisions within PR
   #299
  • #299 and recommends to take this
  as 
  • as template
  • PR need needs to created soon to get it into the release.
  • Randy: name of the endpoint to be considered, see comment in PR #299

...

• #244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
  
  • see addressed by PR #295

• #245 Update and enhance test definition file for QOD API
  • add Add issue to decide if we keep "cucumber" directory or update it (Herbert Damker )
  • Request to all participants to consider to contribute current .feature files

• #257 Error behaviour when session cannot be created due to "time cap" limitation
  • PR #297 replaced by PR #306 ?(check with Jose Luis Urien Pinedo )

• #268 Provision mode for QoD
  • See PR 299

...

• #300 Simplification of Device object - short term solution
  • Commonalities PR #233 Proposal to simplify device object and improve interoperability is merged and will be part of 0.4.0
  • => new issue to be created Herbert Damker 

Further Issues

• #302 Providing developers with alternate to QoS profile
  • new enhancement proposal by Mahesh Chapalamadugu 
  • discussion to be continued within the issue
  • Proposal to put into backlog for next release, as the discussion can't be concluded for the current release => put into the issue.

Any other topics

• Next QoD meeting will be on July xx, at 14:00 CEST / 12:00 UTC
• We don't plan to skip meeting until the release (at least for now).

...