Closed maxl2287 closed 7 months ago
Hi,
In the guidelines it is said:
name | type | attribute description | cardinality |
---|---|---|---|
subject | string | describes the subject of the event - Not used in CAMARA notification. | optional |
We should align this in the guidelines. Either we keep it in the schema as optional and remove the "Not used in CAMARA notification.", or we keep the current schema without subject
.
Are other APIs documenting subject?
Hi,
In the guidelines it is said:
name type attribute description cardinality subject string describes the subject of the event - Not used in CAMARA notification. optional We should align this in the guidelines. Either we keep it in the schema as optional and remove the "Not used in CAMARA notification.", or we keep the current schema without
subject
.Are other APIs documenting subject?
No I haven't find any API, which has defined "subject".
But in the Guidelines it's also written as:
For consistency across CAMARA APIs, the uniform CloudEvents model must be used with following rules:
So in my understanding the model has to be used like described in the table and needs to offer the possibility to set an optional "subject".
I will close this issue. The subject can be left empty as I mixed up "subject" with "source".
The "source" cannot be empty on the external provider (of course), but this is already defined in this spec.
My fault! 😸
Problem description The "subject" is an optional field used for CloudEvents. Even when it's not used for CAMARA notifications, it's mandatory to be set in some Event-Hub services.
Expected behavior Add the "subject" as optional parameter
Reference
https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#122-event-notification