Define a top-level field that describes the feed's update frequency about jsonfeed HOT 4 OPEN

Doesn't WebSub support cover a lot of this? That is, any app or system that checks feeds often enough to need this would be using WebSub to get updates pushed to them anyway?

Not saying that this wouldn't be useful information to have in principle, just that WebSub lets feed consumers sidestep this problem for a lot of use cases.

from jsonfeed.

@baldurbjarnason I agree that the consumer can and should be able to override this if preferred, but shouldn't be required to infer it if the provider has better knowledge of how often it updates. I think it's best to allow the provider to have a standardized way of communicating this, in case the consumer would like to take advantage of it.

from jsonfeed.

I think it's best to allow the provider to have a standardized way of communicating this, in case the consumer would like to take advantage of it.

We already have Expires and Cache-Control: max-age at the HTTP level, for what it's worth.

from jsonfeed.

@JKingweb Is JSONFeed dependent on HTTP? As far as I knew, they're independent. If being transmitted over HTTP is a requirement of JSONFeed, then that might be worth considering, but then at that point why not pack more info into the HTTP headers, like Content-Disposition: JSONFeed; name="My Example Feed", rather than have it in the JSONFeed file itself?

from jsonfeed.