So is .data just another way of pointing to an API? So if hacker news had an API, you would call up news.ycombinator.data all of the time? It would be awesome if this was the case, but even better if people that had .data domains came to a consensus of how to document their data, eg. www.domain.data/docs and have a common layout among websites to make it easier for programmers and scholars alike to figure out how to access the information they need.
Maybe I misread the article then. If data.google.com, data.google.org makes more sense than google.data (which I agree, it does) then what would the application of .data be? Would google.data be an all-in-one resource for all Google API calls?
I was trying to think of a situation where the various TLDs are owned by different organizations, like woot.com and woot.net or back when whitehouse.com was a porn site.
API is more general term for programming interface whose function is not nessecarilly obtaining data. (it could also be updating or deleting data). this .data TLD as i understand would be just for obtaining data from website in structured way. for example if google had .data domain it would be something like this : you enter google.data?search=lady+gagga and it will return you page in json or some other format for results of that google search.
Yes. Also, almost all APIs are designed around small bits of user or query data, just like your example.
This seems more intended for bulk data, which is likely going to be some pregenerated chunk in the MB, GB, TB range and so less suited to the JSON API call paradigm, and more likely to involve a simple lookup to disk rather than being computed on the fly from some database.
