Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The official introduction of the phantastic Stack Exchange Data Explorer (SEDE) made me wonder how the implied Open Data Protocol (OData) endpoints relate to the API?

Obviously there is great overlap in so far as the former do provide access to historic data while the latter to current one, which implies a short data gap only (to be eventually bridged over time by accumulating the interim data in a particular apps local cache for example).

An OData endpoint in itself definitely constitutes an API of sorts anyway.

Being part of the API would imply having an 'official' OData endpoint for every (future) Stack Exchange site of course, which would trigger the related question on where to host these ( vs. subdomains odata or odata.api).

What do you think?

share|improve this question

closed as off topic by Kevin Montrose Jun 15 '10 at 12:52

Questions on Stack Apps are expected to relate to Stack Exchange API, app, or script within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

The OData access for the monthly data dumps is not considered part of the API. – Kevin Montrose Jun 15 '10 at 12:52
@Kevin Montrose That answers my question precisely/officially, so thanks! But why didn't you just answer my question then? ;) – Steffen Opel Jun 15 '10 at 22:37

Browse other questions tagged .