2024-04-15 Commonalities WG Minutes

DRAFT

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community:

Agenda

• Roll Call

• Action Items Review

• Agenda Bashing

• General Topics

  • Closed issues and merged PRs

  • Release 0.4.0 scope

  • Discussions

  • PRs

  • Issues

• Any Other Topics

Minutes

Action Item Review

Closed issues

• Issue #76 Clarification need for linting response severity

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

  • Can be resolved in https://github.com/camaraproject/Commonalities/issues/175

• Issue #114 Glossary update

• Issue #122 Explicitly state how to identify "API Name"

• Issue #126 Proposal - Runtime Restrictions API

  • converted to discussion

• Issue #157 Adopting RFC 9457 for Error Handling

  • TSC decision

Merged PR

• PR #143 Update Design Guidelines with character set guidance

• PR #148 Mandate '+' in all phoneNumber formats

• PR #152 Update API Design Guidelines on usage and style of operation tags

Release 0.4.0 planning

• Scope: Issue #175

  • The proposed list of topics will be reviewed by TCS on 18/04

  • Comments on the topics are welcome in the issue

  • At the next Commonalities meeting (29/04) the scope should be agreed  to reach M1

Current Discussions

Not discusses at the meeting

PRs review

• PR #168 Remove pattern UUID for x-correlator

  • to be merged

• PR #169 [Bugfix]: Linting rules problem with Traffic Influence API

  • to be merged

• PR #145 Added 501 Not Supported error response

  • Covered by issue #127, the same approach should be used here

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

  • @Kevin Smith will be asked to reply

  • @Pedro Díez García will prepare change suggestion

• PR #170 x-correlator_support_guidelines_in_notifications

  • to be merged

• PR #174 CAMARA_common.yaml bugs and typos fix

  • to be reviewed

  • Error responses should be aligned with the changes proposed in Issue #180

• PR #177 update-design-doc-with-explicit-sub-scope-changes

  • to be discussed on dedicated meeting on subscription model  

Issues review

• Issue #127 Which error send back when Device Identifier not supported by API Server?

  • the way of implementing the agreed solution is related to Issue #180 Revision of Chapter 6 Error Responses in API Design Guidelines

• Issue #179 Is "application" relevant for Camara?

  • Is identifier for application useful in multiple subprojects and should be defined in Commonalities  - discussion is open

  • Is simple application API relevant for CAMARA ?

  • Edge Cloud APIs use App Id

• Issue #178 Introducing product categories

  • some technical solutions are proposed to indicate categories

  • the source question is on naming YAML files in Device Status to be unique across CAMARA

• Issue #176 Align Common Design Model for Cloud Event specversion field in APIs Design

  • PR will be prepared to mandate the use of enum for specversion

  • the changes need to be implemented by subprojects using CloudEvents

•  Issue #171 Revise the device object definition to simplify it

  • More opinions are expected

AOB

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

Action items