On Mon, 2009-05-04 at 20:20 -0700, Eric (Google) wrote: > According to the API Terms of Service: > > " 2.1 Permission to Use. You may use: (a) the Health API to access > Google Health, and (b) the Health Service API Specifications for > development for a Health API Client that is designed for usage by > United States users of Google Health. You shall not provide access to > or assign the permission to use the Health API to any third party." > > Eric > -~------~--~---
So, (IANAL) if I read2.1(b) correctly then this means that the Google Health API cannot be included in ANY open source software that may be available for distribution outside of the United States? I would appreciate clarification on this; especially since it was known by yourself and others at Google Health that I planned to include the API in OSHIP. http://launchpad.net/oship From my perspective, I'd like to see this wording changed. The reason being that if Google (probably for legal reasons?) wants to/needs to restrict access to Google Health to US only locations then I am fine with that. However, there are many ways that this can be done and still allow the inclusion of the API in global open source projects. Thanks, Tim -- Timothy Cook, MSc Health Informatics Research & Development Services LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == timothy.cook ************************************************************** *You may get my Public GPG key from popular keyservers or * *from this link http://timothywayne.cook.googlepages.com/home* **************************************************************
signature.asc
Description: This is a digitally signed message part
