Their documentation could probably be more complete, but it does say, for example, that they don't support user defined fields on WebDAV requests.
I suppose they could have opted to not mention CardDAV or the other standards and just published an API called GCard or something like that.
They do mention that interoperating with Apple's operating systems is working, so that may be what determined the subset they care about.
> service which when used correctly WILL corrupt users' data
So that comes back to who gets to define what correct use is? If you follow the Google documentation and are losing data, then I agree with you. They should fix the problem or update the documentation.
For one, these aren't security issues.
Also, they do document the parts of the standards that they don't support or adhere to:
https://developers.google.com/google-apps/carddav/
Their documentation could probably be more complete, but it does say, for example, that they don't support user defined fields on WebDAV requests.
I suppose they could have opted to not mention CardDAV or the other standards and just published an API called GCard or something like that.
They do mention that interoperating with Apple's operating systems is working, so that may be what determined the subset they care about.
> service which when used correctly WILL corrupt users' data
So that comes back to who gets to define what correct use is? If you follow the Google documentation and are losing data, then I agree with you. They should fix the problem or update the documentation.