-
Notifications
You must be signed in to change notification settings - Fork 582
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.
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
The difference among event source, event source type, event type, event ID is not explicit #71
Comments
Can we discuss this in the meeting? I can own and resolve this issue. But I prefer to get other people's input on this first |
ok I'll add it to the agenda |
@duglin This partially covers what I meant by examples in in the discussion of #41 . |
yep I agree. We ran out of time last week, I'm hoping we can get to it today, but I wanted to ask a similar question about “event-type”, “event-type-version” and “schema-url” since it feels like there might be some overlap between these three things and I wonder if schema-url alone couldn't convey all of the info needed. And if not then we need a very clear definition so there's no confusion about when, and how, to populate them - otherwise we won't get the interop we need. |
Good idea. A sample flow will help to illustrate issues in our current definition, such as overlap or gap. We may find out that some new attributes, such as correlation-token, need to be defined to really get the interop we need. I will try to draw the flow, show the boundary, and identify issues that need to be discussed. I can probably get this ready for discussion in the 2/22 meeting. |
@cathyhongzhang given the PRs we resolved on today's call, I wonder if we can close this one and then if you still think we need more clarity on event-* attribute you can open a new issue that just focuses on those? |
Ok. |
Suppose the event comes from a AWS S3, what is the event source, event source type, event type, event Identifier? From current definition, it is not very clear.
Assigned to: @cathyhongzhang
The text was updated successfully, but these errors were encountered: