Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document subscriber model for events (descriptive events) #66

Closed
afrittoli opened this issue Sep 20, 2022 · 0 comments · Fixed by #77
Closed

Document subscriber model for events (descriptive events) #66

afrittoli opened this issue Sep 20, 2022 · 0 comments · Fixed by #77
Assignees
@afrittoli
Milestone
v0.1

Comments

@afrittoli
Copy link
Contributor

afrittoli commented Sep 20, 2022 •
edited
Loading

Make it clearer in the spec that CDEvents are descriptive and not directed to a specific client.
We can use a diagram to represent this:

Document decision (from CDEvents community summit) about prescriptive events in the spec.
@e-backmark-ericsson e-backmark-ericsson added this to the v0.1 milestone Sep 20, 2022
@afrittoli afrittoli self-assigned this Oct 4, 2022
afrittoli added a commit to afrittoli/cdevents-spec that referenced this issue Oct 13, 2022
@afrittoli
Document how to adopt and adapt CDEvents
cbd1919 
Document a series of scenarios about adopting CDEvents producer and
consumer side. Describe how to adapt CDEvents with customData and
how to contribute new fields and events to the community.

Document declarative vs. imperative events and the subscriber model.

Fixes: cdevents#66
Fixes: cdevents#42

Signed-off-by: Andrea Frittoli <[email protected]>
afrittoli added a commit to afrittoli/cdevents-spec that referenced this issue Oct 13, 2022
@afrittoli
Document how to adopt and adapt CDEvents
36f3d67 
Document a series of scenarios about adopting CDEvents producer and
consumer side. Describe how to adapt CDEvents with customData and
how to contribute new fields and events to the community.

Document declarative vs. imperative events and the subscriber model.

Fixes: cdevents#66
Fixes: cdevents#42

Signed-off-by: Andrea Frittoli <[email protected]>
@afrittoli afrittoli mentioned this issue Oct 13, 2022
Merged
4 tasks
afrittoli added a commit to afrittoli/cdevents-spec that referenced this issue Oct 13, 2022
@afrittoli
Document how to adopt and adapt CDEvents
71d1feb 
Document a series of scenarios about adopting CDEvents producer and
consumer side. Describe how to adapt CDEvents with customData and
how to contribute new fields and events to the community.

Document declarative vs. imperative events and the subscriber model.

Fixes: cdevents#66
Fixes: cdevents#42

Signed-off-by: Andrea Frittoli <[email protected]>
@afrittoli afrittoli moved this from Todo to In Progress in CDEvents Releases Oct 18, 2022
afrittoli added a commit that referenced this issue Oct 19, 2022
@afrittoli
Document how to adopt and adapt CDEvents
80a4987 
Document a series of scenarios about adopting CDEvents producer and
consumer side. Describe how to adapt CDEvents with customData and
how to contribute new fields and events to the community.

Document declarative vs. imperative events and the subscriber model.

Fixes: #66
Fixes: #42

Signed-off-by: Andrea Frittoli <[email protected]>
Repository owner moved this from In Progress to Done in CDEvents Releases Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@afrittoli afrittoli

Labels
None yet
Projects
CDEvents Releases
Status: Done
Milestone
v0.1
Development

Successfully merging a pull request may close this issue.

Document how to adopt and adapt CDEvents afrittoli/cdevents-spec
2 participants
@afrittoli @e-backmark-ericsson