2024-01-22 Commonalities WG Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community: Rafal Artych Shilpa Padgaonkar Sachin kumar Toshiyasu Wakayama Ludovic Robert Eric Murray Jan Friman Pierre Close Ming Hui Foo Mark Cornall Murat Karabulut, Toyeeb Rehman

Agenda

• Roll Call
• Action Items Review
• Agenda Bashing
• General Topics
  • Release management guidelines for subprojects
  • Pull Requests review
  • Issues review
  • Any Other Topics

Minutes

Action Item Review

Release management guidelines for subprojects

2024-01-18 TSC Minutes:

the guideline discussion within the Release Management meetings as opposed to the Commonalities group.

As Release Management meetings happen weeks, it is good place to discuss issues consolidate as Issue #9 in Release management repo. All participants interested in  working on

that topics are kindly ask to join Release Management calls.

Note: Reminder about EasyCLA for CAMARA as indicated in TSC meeting notes.

PRs review

• PR #57 Update OpenAPI security guidelines
  • The content should be aligned with Identity and Consent documents
  • Then it should be ready for final review
• PR #74 Initial CAMARA OAS linting ruleset / PR #110 API linting implementation guideline
  • Final version of ruleset implementation delayed
  • Versioning of implementation files needs to be added
  • It should be ready for final review before the next call
• PR #115 Set X-Correlator as Required in OAS Definition, X-Version removed
  • Ready to be merged
  • Possibly the X-Correlator header definition can be added to CAMARA_common.yaml
• PR #117 Create API-Testing-Guidelines.md
  • The last remaining point in the discusssion is the granularity of .feature files - the proposed text will be added to the PR
  • Then it can me merged
• PR #120 Update CAMARA_common.yaml: add Device headers, fix address
  • Definition of parameters in headers to be used in GET request as required in Design Guidelines for privacy protection
  • Changes in name of IPv4 address objects
• PR #123 Update API-design-guidelines - Issues 97&98
  
  • Changest proposed to clarify issue on response filtering
  • Ready for review

Issues review

• Issue #122 Explicitly state how to identify "API Name"
  • "API Name" is used in the BasePath, the format should be clarified

  • PR #57 defines:  api-name is the API name specified as the base path, prior to the API version, in the servers[*].url property

  • Recomendation on creation of "API Name" variable or the inventory of approved names
• Issue #114 Glossary update
  • definitions of "application provider", "application service provider", "communication service provider / MNO" needed
    
  • PR expected
• Issue #112 Guidance on the inclusion of charsets in content-type response headers
  • The RFC 8259 for JSON was changed to require the use of UTF-8 when transmitted over a network
  • PR expected
• Issue #87 Mandate '+' in all Phone Number formats
  • Example in CAMARA_common.yaml is without '+' sign
    
  • PR expected

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

  • Issue #31 Adopt RFC 7807 error responses
  • Consolidation issue will be prepared to summarize current discussion

AOB

Zoom platform for Commonalites calls?

The next meeting is on Feb 5th 2024.

Action items

• X-Correlator header definition to be added to CAMARA_common.yaml
• Propose the text on files granularity to PR #117
• Recommendation clarifying BasePath format
• Propose definitions of "application provider", "application service provider", "communication service provider / MNO"
• PR for Guidance on the inclusion of charsets in content-type response headers (Issue #1120)
  
• PR for Mandate '+' in all Phone Number formats (Issue#87)
  
• Consolidation of discussion on error response format
• PR for Response Filtering update
• Open poll for moving calls to Zoom platform by LF