OK - there has been some confusion within our church on exactly what this API will and will not do - the non-technical staff and leaders think that this will be the end of needing ANY custom code to interface with F1 data. As an example an option was brought up to move from an in-house MS Exchange server solution to a hosted Google Mail option (cheaper and perception of easier maintenance). However one of the really highly visible projects on the plate right now is to make all F1 people accessible in Outlook in the global address book WITHOUT ANY INTERFACE FROM USERS/STAFF (i.e., no running of a report and dumping it down to something to import).
Someone called F1 tech support and what was conveyed from the conversation is that if we move to Google Apps/Mail then the API can simply sync up F1 people with the Google Contact list AUTOMATICALLY with NO USER INTERVENTION or THIRD PARTY INTERFACE/ENGINE.
I've contested that there will have to be something in between that is driving this - that Google will not make the calls into F1 and that F1 is not pushing to Google.
I've tried to comminicate that this API is a developer interface into F1 and although it will do a lot of cool things it needs something to drive it.
I did not attend the conference so I was looking for a good layman's description of this to pass on and for clarification as to how and who will use this API.
Thanks.