...
- 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 Diez Garcia 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
...