Great first name! Here goes some rambling... SOA will converge with Business Capability Modeling and Process Modeling built within the scope of business service portfolio management on top of evolving industry and corporate taxonomies through master data management initiatives which will be supported by more targeted technology solutions through "domain driven design" that evolve through the idea of domain-specific languages and the realization of integrated model driven architectures into the software development lifecycle. Software vendors and consulting firms will continue to push proprietary, end-to-end topologies of multiple products as "industry templates" that claim to support open standards. The reality of such solutions claiming support for standards will be that an open standard is selected and extended in an open way, boasting and marketing compatibility with the standard as well as how the solution helped to evolve the standard, but leaving the community with a branched standard that won't play well with others as the primary trunk of the standard continues to grow upward. Ultimately, middle-man software will sit between these products to translate communications and attempt to make enterprise SOA a reality. Everyone will quickly realize (if they haven't already) that enterprise SOA was never about exposing anything and everything across the enterprise in a common format, but completely about streamlining business capabilities/processes across technology solutions to the degree that the supporting technology infrastructure does not "matter", so long as Information Technology exposes the services in a common way (i.e. not necessarily an explicit and exact way, but along a least common denominator). Adaptive industry and business models, evolving technology standards, and the need to sell software as a service will ultimately make "Service Oriented Architecture" a fad of our generation until a new name brings the same light-bulb, "aha" moment of clarity to a new generation and a new maturity of understanding is achieved. Wow do I need a brain break...
Website<Twitter> web = new Website<Twitter>();
web.PukeContent("tweet, tweet. Rockin Robin, tweedle-e-deet.");
//Yes, the web is generic!
I updated Jurgen's ranking to include the number of twitter posts per day using the scores from the popular Twitter tool "Follow Cost". I then took a simple average of the three rankings Follower Rank, Twitters per Day Rank, and Last 100 Twitters per Day Rank and then created a final ranking. Fortunate for Jurgen's position (bumped him up a few rankings).