To expect that users, even power users, will be able to build applications that stitch together web services from multiple vendors is a stretch. Teqlo isn’t attempting to build a new development language like Ruby on Rails that dramatically lowers the barrier, what we are doing is essentially reverse programming. We’re treating development as a data flow problem, not a programming flow problem. If there is a core piece of technology that we have invented, it is the routing methodology and not the semantic definition of components; Teqlo takes web services that are wrapped up as components, we call them Teqlets, and determines the optimal sequencing based on the data inputs/outputs of each component. Yeah, it’s hard and there is a lot more to it than I am revealing here, but the point of this post is not to talk about our technology but rather what it means for users.