The matter is more specific than the article leads to believe. SWIFT is not actually 'moving' it's servers, rather it is adding new servers in Europe. Creating one TransAtlantic zone for messages allowed to reach the US and one Europe zone for messages not allowed to reach the US. The 'National Member Group Chairperson' of each country has specified in which of these zones their traffic should be traveling in, so with some exceptions each country has their own choice. Soon every country which has chosen to will keep their inter-Europe traffic within Europe. (exchanges with American banks obviously have to go to America.) For more information read: http://www.swift.com/solutions/industry_initiatives/distributed_architecture.page And: http://www.swift.com/solutions/industry_initiatives/image_doc/DA_Phase_1_white_paper_200907_1.4.pdf

I think this is a very interesting story. Aside from the technical question raised, I am wondering why the first corporate Wiki wasn't successful. If it failed the first time because the culture isn't right or there wasn't any management support, a second wiki tool - no matter how seamlessly integrated - won't succeed either. Even if you have a company with many different technical domains it's even more reasonable to be able to share information. And an article shouldn't try to be totally comprehensible. You could write a parent page describing the concept, and subpages that are specialised for the different domains. I'd love to discuss this further.