Events #5
Replies: 4 comments 4 replies
-
I think the feed space is in need of some evolution and standardization, yes. JSON Feed (and the discussion in manton/JSONFeed#49 especially) is worth having a look at. I know that EventStore uses Atom feeds as its data format and I've spoken to @gregoryyoung about their wish for it to evolve from XML to JSON. We also have CloudEvents which aren't dealing with feeds, but are still relevant on the item/entry level which was standardized in RFC 4287 and probably should be evolved and provided in a JSON format too. And I suppose we need to figure out how possible development in the feed space relates to Activity Streams as well? |
Beta Was this translation helpful? Give feedback.
-
API developers who provide webhooks (there are many), typically provide I would even suggest to incorporate CloudEvents as an envelope schema for these events in parity to https://github.com/cloudevents/spec/blob/v1.0.1/http-webhook.md. |
Beta Was this translation helpful? Give feedback.
-
So one question here would be whether or not a schema can be associated, if so is there some form of discovery mechanism? |
Beta Was this translation helpful? Give feedback.
-
I think it is definitely an interesting area, but there seem to be a number of efforts already ongoing. I'm not sure what value this group is would be looking to add. Would there be value in an link relation type for "events"? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I found this interesting:
https://blog.syncinc.so/events-not-webhooks
... and view it as potentially just a continuation / specialisation of work on feeds (e.g., Atom).
What do folks think? Worth spending time on some conventions here?
Beta Was this translation helpful? Give feedback.
All reactions