few questions about COM pattern; getting the terms right; comparison to Android binders

A bit of context: I am currently finding my way around Modo's (which is a 3D graphics package) C++ API for plugins. According to the docs it's built on COM architecture, so want it or not I'm having to learn some COM basics (even though I'm not a OS programmer by any stretch).

I've read the API docs, the WIKI on COM and this link: Newbie questions about COM I've also worked a bit in Android (some of this concept seems to appear there as well, read below). I still would like some things clarified:

0) is there a canonical understanding of COM, a set of rules that don't differ by implementation?

1) in the light of 0) which of these words should be synonymous: "server", "service", "interface", "remote object's method", "remote object" - or does it just differ (e.g. there may be many interfaces per server, there may not; there may be many interfaces per local object; etc.)

2) is Android Binder pattern also an example of COM? I've worked with it, briefly, and the picture shows how I understand it (presented with with my line of thinking on untangling name confusion) - would this be a correct interpretation?

Many thanks,