DRAFT

Attendees & Representation

Agenda

Antitrust Policy

• Action Items Review

• Issues review

• PRs review

• Any Other Topics

Minutes

Review of Action Items and Minutes from previous meetings

Merged PRs

• nits: typos and added missing sensitive word in .spectral.yml by Kevsy · Pull Request #350 · camaraproject/Commonalities

• Error alignments for Event Notifications Artifact by PedroDiez · Pull Request #351 · camaraproject/Commonalities

• Add enum value for `terminationReason` attribute in the guideline document by bigludo7 · Pull Request #356 · camaraproject/Commonalities

• Fix broken link in API-design-guidelines.md ToC by eric-murray · Pull Request #360 · camaraproject/Commonalities

PRs Review

• Update rules when using POST for sensitive data by eric-murray · Pull Request #358 · camaraproject/Commonalities

• Correct CAMARA_common.yaml Generic503 error code to UNAVAILABLE, to match API design guidelines by eric-murray · Pull Request #359 · camaraproject/Commonalities

• Subscriptions and Notifications artifacts errors aligment -enum values- by PedroDiez · Pull Request #361 · camaraproject/Commonalities

• Provide ACCESS_TOKEN_EXPIRED termination reason guidance by bigludo7 · Pull Request #364 · camaraproject/Commonalities

Issues review

• Improve definition of x-correlator header · Issue #352 · camaraproject/Commonalities

  • PR will be prepared with extended length in the pattern

• Error responses in event-subscription-template.yaml does not use enumeration of error status and code allowed values · Issue #354 · camaraproject/Commonalities

  • PR #361 ready for review

• Should errors 405, 415, 500, 501, 502, 503, 504 be listed in CAMARA_common.yaml · Issue #355 · camaraproject/Commonalities

  • Option 2 preferred (keep definitions as optional)

  • PR will be prepared

• Handling Notifications for Expired Access Tokens in Sink Credentials · Issue #357 · camaraproject/Commonalities

  • PR #364 ready for review

• Clarifications on breaking changes due to the latest changes in error responses · Issue #363 · camaraproject/Commonalities

  • 2024-12-19 TSC Minutes: APIs should strictly apply semantic versioning regarding breaking changes. Any change that may break an implementation (e.g. changes in error response codes) should be considered as a breaking change

• Should error 429 (TOO_MANY_REQUESTS) be mandatory in CAMARA specifications? · Issue #365 · camaraproject/Commonalities - comments expected

AOB

Meeting on January 6th 2025 - postponed to 13th 

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

Action items