2024-02-19 Commonalities WG Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community: @Rafal Artych, @Sachin kumar @Ming Hui Foo @Pierre Close @Jan Friman  Murat Karabulut, Toyeeb Rehman

Agenda

• Roll Call

• Action Items Review

• Agenda Bashing

• General Topics

  •  

• Any Other Topics

Minutes

Action Item Review

Housekeeping topics

• Pedro Díez García - new codeowner representing TEL
  
  

• Results of Poll on Moving Commonalities meetings to The Linux Foundation platform 

•  

  • Next call on 4th March will be set up on LF platform
    
    

  • Next Open Office Hours has been scheduled on Feb 21st at 08:00 Pacific / 17:00 CEST.  Register with this link: https://zoom-lfx.platform.linuxfoundation.org/meeting/95532477210?password=d9756c7f-4114-4d1a-b44f-a6d6d25543c0

• Release 0.3.0 has been published and announced
  
  

Merged PRs for Release 0.3.0:

• PR #110 API linting implementation guideline

• PR #74 Initial CAMARA OAS linting ruleset

• PR #57 Update OpenAPI security guidelines

• PR #132 Added filter criteria related Issue 103

• PR #139 Update documentation/MeetingMinutes/README.MD

• PR #134 CHANGELOG.md and README.md for release 0.3.0

Current Discussions

• Centralized, generic, domain-agnostic API for event subscription and notification
  
  

  • New idea for Network Events pub/sub system

• Release 0.4 Schedule

  • Topics to be covered by the next release

  • How to solve the dependency between Identity&Consent Management documents amd commonalities artifacts

• Sim Swap Certification - 3 Legged authorization implementation

  • Possibly to be transferred to  IdentityAndConsentManagement subproject

PRs review

• PR #120 Update CAMARA_common.yaml: add Device headers, fix address

  • Final review expected

• PR #143 Update Design Guidelines with character set guidance

  • Please review

Issues review

• Issue "Good reason to upgrade to openapi 3.1.x ?" - was converted to discussion

• Issue #76 Clarification need for linting response severity

  • Proposed to be closed 

  • Comment on rules severity will be added

• Issue #77 Mandatory Response Headers - agreed to be closed

• Issue #122 Proposal to add a standard for defining durations for API Design guidelines

  • potentially API Design Guidelines section 11.5 can extended to address it and issue #93

• Issue #113 Guidance on error responses - are error messages standardized or can they be custom?

  • The original question was whether the message field in error response can be custom (i.e. in other language)  or should be exactly the same as defined in specification

    • the possible solution with additional error cause was indicated in the earlier discussion

    • the proposed approach assumes that message field can be customized

• Issue #133 Adopt RFC 9457 error response format

  • new edit added to the issue description clarifying proposed approach

  • due to limited attendance no new views were captured

  • TSC proposes to prepare clear proposal for new response format guidelines

    • it should be ready before the next TSC on 7th of March 

    •  it can be prepared in off-line mode - as a new PR if there are volunteers
      
      

  • the final decision should be taken in the next Commonalities meeting

    • Slide deck for review on March 4, 2024: 20240304-CAMARA-Issue 133 - RFC 9457 URN Option.pdf

AOB

The next meeting is on Mar 4th 2024 using https://zoom-lfx.platform.linuxfoundation.org/meeting/91016460698?password=d031b0e3-8d49-49ae-958f-af3213b1e547

Action items