tag:blogger.com,1999:blog-13490395.post115924953226465431..comments2017-05-30T09:42:16.183-05:00Comments on The Appian Way: Towards an open ChMS marketplaceChuck Russellhttp://www.blogger.com/profile/15429587155202866452noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-13490395.post-1160713402312827012006-10-12T23:23:00.000-05:002006-10-12T23:23:00.000-05:00No, I haven't seen it. Who is behind it?No, I haven't seen it. Who is behind it?Clif Guyhttps://www.blogger.com/profile/03546100664377891125noreply@blogger.comtag:blogger.com,1999:blog-13490395.post-1160691957175779312006-10-12T17:25:00.000-05:002006-10-12T17:25:00.000-05:00Have you seen the http://www.churchdashboard.com/ ...Have you seen the http://www.churchdashboard.com/ project?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13490395.post-1159802061916747492006-10-02T10:14:00.000-05:002006-10-02T10:14:00.000-05:00Hi Clif,You’ve made a great post on such a relevan...Hi Clif,<BR/><BR/>You’ve made a great post on such a relevant topic. It would seem to me that of the three barriers, the common schema would be the point of most discussion. Even so, that doesn’t seem completely unique to a church environment. For example, the exchange of ‘contact’ data certainly happens in other industries aside from our own. Certainly we can expose the requested data in a secure environment. Likewise, a system can only expose as much as it contains. The issue then becomes how we consume that data which is where strong tools come into play. The goal would be to avoid writing and maintaining custom integrations and to instead use such a tool to connect to a data source, format it as needed, and then consume it. It seems like a strong integration tool could almost avoid the requirement for a defined format of data exchange similar to what happened with EDI.<BR/><BR/>Thanks for the great discussion Clif.<BR/><BR/>Garret Schaeffer<BR/>Fellowship of the WoodlandsAnonymousnoreply@blogger.com