lance opened a new issue, #3668: URL: https://github.com/apache/camel-k/issues/3668
When using a Twitter search source kamelet (and I assume it's applicable to all kamelets), I have found that the CloudEvent headers, while adhering to the CE spec, don't necessarily adhere to the spirit. Specifically, with the `source` attribute, the value provided is `source`. The [spec specifies](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#source-1) the `source` field is a URI reference. We could argue that `source` is a relative URI, but it's definitely not the actual source of the event. > Identifies the context in which an event happened. Often this will include information such as the type of the event source, the organization publishing the event or the process that produced the event. The exact syntax and semantics behind the data encoded in the URI is defined by the event producer. It would be much nicer if the `source` attribute could be used to identify the event producer uniquely. The `type` attribute could also be improved. That value is currently `org.apache.camel.event` which is pretty good. It adheres to the CE spec recommendation. > SHOULD be prefixed with a reverse-DNS name. The prefixed domain dictates the organization which defines the semantics of this event type. But really all we are getting with this value is the prefix. It would be great if, for example, the type could be something that would allow more finely grained filtering. E.g. `org.apache.camel.event.twitter.search` and `org.apache.camel.event.twitter.timeline`. 🙏 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
