The Need for Open (Web) Services
I’ve been looking around the xmethods website looking for web services to interface in VB.NET. There are a few test services, such as the temperature service, but not a whole lot that you can use in a production environment. This made me think about what the BSD/Linux/Open Source solution to web services might be: open services.
Open Services might be something trivial, such as a weather service, stock ticker, or similar service, or it might be something more complex. A provider of an Open Service would (perhaps) unleash the service on the world in an open fashion. He or she might release source code to the service in BSD or *GPL, or they might keep the source private. What they might do next is taking things to their logical conclusion: have a web service running somewhere that is publicly accessible, and point to it for all to use free of charge.
This might not make sense in an economical way, (some would argue that open source software doesn’t make any sense either), but what’s stopping people from doing it anyway? It could be a box in a dorm room, a server connected to cable or dsl, or some spare bandwidth on a colocated box somewhere.
I’d love to see open source software and web services converge. Who knows if it’ll happen. I’ll try to do my part and set up a box, create some services, and unleash them on the world. Perhaps we need a web site to point to these Open Services. Perhaps we need an Open Service License (OSL?). Maybe we need several (GPL-style OSL, BSD-style OSL, etc) I’ll do my best to gather things together in the next couple of days. Looking at the list of web services at xmethods, it appears that many of the published services are homegrown. What’s the next step?
I’d love to hear what people think about this.