Skip to content

Propose the addition of FollowsFrom semantics#161

Closed
erikerikson wants to merge 1 commit into
cloudevents:masterfrom
erikerikson:follows-from
Closed

Propose the addition of FollowsFrom semantics#161
erikerikson wants to merge 1 commit into
cloudevents:masterfrom
erikerikson:follows-from

Conversation

@erikerikson
Copy link
Copy Markdown
Member

Propose the addition of FollowsFrom semantics to facilitate event correlation into data flows.

Signed-off-by: Erik Erikson erik.m.erikson@nordstrom.com

…orrelation into flows.

Signed-off-by: Erik Erikson <erik.m.erikson@nordstrom.com>
@erikerikson
Copy link
Copy Markdown
Member Author

Apologies in advance, having not participated in a standards body previously, for any obvious oversights or violation of best practice.

@duglin
Copy link
Copy Markdown
Collaborator

duglin commented Apr 13, 2018

@erikerikson what is the relationship between this and #128 ? It feels like these two should be merged in some way to allow for a linking of events but with some kind of additional property to indicate the type of relationship between them.

@erikerikson
Copy link
Copy Markdown
Member Author

Ooh. Still loading here and I missed that one. Merging seems appropriate. I will engage there.

@duglin
Copy link
Copy Markdown
Collaborator

duglin commented Apr 13, 2018

@erikerikson great - thanks!

Comment thread spec.md

### followsFrom
* Type: String
* Description: The eventID of the event that caused this event. The semantics
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

one could argue that a set of eventID(s) could be the cause of an event and that this field should allow for this. allowing delimited eventID(s) to be supplied could satisfy that fact at the cost of complexity

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.

2 participants