Skip to content

Align responses with commonalities r4.4 - #153

Open
GillesInnov35 wants to merge 8 commits into
mainfrom
Align-Responses-with-Commonalities-r4.4
Open

GillesInnov35 wants to merge 8 commits into
mainfrom
Align-Responses-with-Commonalities-r4.4

Conversation

@GillesInnov35

@GillesInnov35 GillesInnov35 commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

What type of PR is this?

Add one of the following kinds:

  • correction

What this PR does / why we need it:

Align responses section with commonalities r4.4 according

  • CAMARA_common.yaml
    - DEPRECATED error responses - The Generic* responses are DEPRECATED as of Commonalities 0.9.0
    - normalize naming of local errors according to CAMARA_common.yaml

  • CAMARA_event_common.yaml

  • sample-service.yaml
    - include locally HTTP-50x errors and specific definitions

Which issue(s) this PR fixes:

Fixes #152

Updated the Verified Caller API specification to include detailed descriptions, parameters, and response examples for the pre-announcement functionality.
Updated the Verified Caller API specification to include detailed descriptions of functionality, parameters, and error handling.
@camara-validation

camara-validation Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

CAMARA Validation — PASS (with warnings)

0 errors, 3 warnings, 8 hints | Profile: standard

View full results

@GillesInnov35

Copy link
Copy Markdown
Contributor Author

@ALL,if we take a look at what CAMARA_event_common.yaml, new errors content are included.

What I understand is that if we'd like to be fully aligned with CAMARA_event_common.yaml by updating callbacks\ notifications\responses: some responses may be no more compatible with the previous version. That's why not all commonalities changes have been applied. WDYT ?

@alpaycetin74

Copy link
Copy Markdown
Contributor

hello @GillesInnov35 , I undertand you are only asking about the errors for the notifications?
This api is still a pre-release version, and notifications did not exist in the previous meta release. I think it is ok to change error responses.

@GillesInnov35

Copy link
Copy Markdown
Contributor Author

hello @GillesInnov35 , I undertand you are only asking about the errors for the notifications? This api is still a pre-release version, and notifications did not exist in the previous meta release. I think it is ok to change error responses.

Oh yes you're right. Ok I'm going to include reference for notification errors. Thanks

@alpaycetin74

Copy link
Copy Markdown
Contributor

hello @GillesInnov35 , I undertand you are only asking about the errors for the notifications? This api is still a pre-release version, and notifications did not exist in the previous meta release. I think it is ok to change error responses.

Oh yes you're right. Ok I'm going to include reference for notification errors. Thanks

Hi @GillesInnov35 , are you going to further modify this pr? Thank you

@GillesInnov35

Copy link
Copy Markdown
Contributor Author

Hi @GillesInnov35 , are you going to further modify this pr? Thank you

@alpaycetin74 , yes I’ll do it quickly

@alpaycetin74 alpaycetin74 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please have a look at the linter warnings @GillesInnov35 ? Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Align responses with commonalities r4.4

2 participants