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

Revisit the name "source" in Events #58

Closed
inlined opened this issue Feb 1, 2018 · 2 comments
Closed

Revisit the name "source" in Events #58

inlined opened this issue Feb 1, 2018 · 2 comments

Comments

@inlined
Copy link
Contributor

inlined commented Feb 1, 2018 •
edited by duglin
Loading

On February 1st 2018, we tentatively changed "resource" to "source". We agreed that "resource" is too confusing, but also that "source" may not be the best name. After clarify the meaning of this term we can reaffirm or change the name.

Assigned to: @inlined
@deissnerk deissnerk mentioned this issue Feb 2, 2018
Closed
@schatekar
Copy link
Contributor

@duglin the idea of profiles can simplify this issue greatly. Irrespective of the domain/use case, there will always be an origin or source indicating who the publisher of the event is.

Then a FaaS profile can add relevant extension fields to capture the information about various intermediate systems that the event passes through before it hits the function.

inlined added a commit to inlined/cloudevents that referenced this issue Feb 7, 2018
@inlined
Clarify the meaning of "source"
111976b 
Related to cloudevents#58, this is a follow-up to last week's meeting to clarify the meaning of source (fka resource).

The change is minimal and builds on the vocabulary of "occurrence" to be clearer that this is the first piece of software where the event originates, not the latest software to forward the event in a federated system. I've also added real examples from Google Firestore in case our interpretation helps others.

I'll add another PR to suggest an additional source-service.
@inlined inlined mentioned this issue Feb 7, 2018
Closed
inlined added a commit to inlined/cloudevents that referenced this issue Feb 7, 2018
@inlined
Clarify the meaning of "source"
52ccf9b 
Related to cloudevents#58, this is a follow-up to last week's meeting to clarify the meaning of source (fka resource).

The change is minimal and builds on the vocabulary of "occurrence" to be clearer that this is the first piece of software where the event originates, not the latest software to forward the event in a federated system. I've also added real examples from Google Firestore in case our interpretation helps others.

I'll add another PR to suggest an additional source-service.

Signed-off-by: Thomas Bouldin (inlined@google.com)
inlined added a commit to inlined/cloudevents that referenced this issue Feb 7, 2018
@inlined
Clarify the meaning of "source"
10415f9 
Related to cloudevents#58, this is a follow-up to last week's meeting to clarify the meaning of source (fka resource).

The change is minimal and builds on the vocabulary of "occurrence" to be clearer that this is the first piece of software where the event originates, not the latest software to forward the event in a federated system. I've also added real examples from Google Firestore in case our interpretation helps others.

I'll add another PR to suggest an additional source-service.

Signed-off-by: Thomas Bouldin (inlined@google.com)
inlined added a commit to inlined/cloudevents that referenced this issue Feb 7, 2018
@inlined
Clarify the meaning of "source" as where the event occurs.
1096c11 
Related to cloudevents#58, this is a follow-up to last week's meeting to clarify the meaning of source (fka resource).

The change is minimal and builds on the vocabulary of "occurrence" to be clearer that this is the first piece of software where the event originates, not the latest software to forward the event in a federated system. I've also added real examples from Google Firestore in case our interpretation helps others.

I'll add another PR to suggest an additional source-service.

Signed-off-by: inlined <inlined@google.com>
@inlined inlined mentioned this issue Feb 7, 2018
Closed
inlined added a commit to inlined/cloudevents that referenced this issue Feb 7, 2018
@inlined
Clarify the meaning of "source" as where the event occurs.
fc34d76 
Related to cloudevents#58, this is a follow-up to last week's meeting to clarify the meaning of source (fka resource).

The change is minimal and builds on the vocabulary of "occurrence" to be clearer that this is the first piece of software where the event originates, not the latest software to forward the event in a federated system. I've also added real examples from Google Firestore in case our interpretation helps others.

I'll add another PR to suggest an additional source-service.

Signed-off-by: Thomas Bouldin <inlined@google.com>
@duglin duglin added the assigned label Feb 7, 2018
@inlined
Copy link
Contributor Author

inlined commented Apr 16, 2018

This seems to be quite settled.

@inlined inlined closed this as completed Apr 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@schatekar @inlined @duglin