16 ms·

If you throw out all the 'tit-for-tat' assumptions, it really makes sense. Google has an API for nearly everything. I could easily see this as a standardizati

If you throw out all the 'tit-for-tat' assumptions, it really makes sense. Google has an API for nearly everything. I could easily see this as a standardization approach. Personally, I'm not effected at all between using the Google calendar website and my android based phone. I think Google's goal is to push everyone to use the API for their calander in future apps. I don't mind doing that for what they provide. I could easily imagine that use of their API could allow for better data gathering than using the open standard.

sangnoir 14y ago
Microsoft recently filed an amicus brief supporting Oracle's position on API copyright. I wouldn't speculate that this is the motive, but it would be interesting if Microsoft is pressured into using Google APIs
cube13 14y ago
> If you throw out all the 'tit-for-tat' assumptions, it really makes sense. Google has an API for nearly everything. I could easily see this as a standardization approach. Except caldav is just a protocol. It's not an API. Google could have made an API that supports the caldav protocol, but chose not to. This also effects me a lot, personally, because I have a Kindle Fire and an iPhone, and I use my Google calendar to sync up everything between the two.
- Selfcommit 14y ago
  So then the Google calander API has always been used, but the data is delivered in CalDev format? This move would then represent Google refusing to accept that format? I didn't read things that way. It makes good business sense - look at Maps API. You can get X number of free calls, but if you go over a certain limit you need to pay (That limit is pretty high if I recall) So now fast forward to Microsoft and Others incorporating that API into their products - am I understanding correctly Google could charge for API calls similarly?

16 ms·

If you throw out all the 'tit-for-tat' assumptions, it really makes sense. Google has an API for nearly everything. I could easily see this as a standardizati

by Selfcommit 14y ago

sangnoir 14y ago
Microsoft recently filed an amicus brief supporting Oracle's position on API copyright. I wouldn't speculate that this is the motive, but it would be interesting if Microsoft is pressured into using Google APIs
cube13 14y ago
> If you throw out all the 'tit-for-tat' assumptions, it really makes sense. Google has an API for nearly everything. I could easily see this as a standardization approach. Except caldav is just a protocol. It's not an API. Google could have made an API that supports the caldav protocol, but chose not to. This also effects me a lot, personally, because I have a Kindle Fire and an iPhone, and I use my Google calendar to sync up everything between the two.
- Selfcommit 14y ago
  So then the Google calander API has always been used, but the data is delivered in CalDev format? This move would then represent Google refusing to accept that format? I didn't read things that way. It makes good business sense - look at Maps API. You can get X number of free calls, but if you go over a certain limit you need to pay (That limit is pretty high if I recall) So now fast forward to Microsoft and Others incorporating that API into their products - am I understanding correctly Google could charge for API calls similarly?