Why are there no web services over packet radio

Approaching the world of ham radio from the perspective of a long time computer software -- and enterprise integration -- point of view, it struck me today: why are there no web services support in amateur packet radio.

Web services are a fancy name for the ability to make a subroutine call across a network (or even on the same computer). They are based in eXtensible Markup Language (XML), which means that the call can pass in and return data of any arbitrary complexity. They are quickly becoming the standard for integration applications across a network, especially in situation where the applications don't normally know about each other.

There are some things about web services that make them a natural for amateur packet networks:

• They are fundamentally half-duplex, like our radio connections: You send in a call (which could be split across packets because of size), and then wait for a response.
• They could allow for a very nice, local front end to traditional applications like bulletin boards, which got killed by not only better connectivity of the internet but, I suspect, nicer web user interfaces.
• They allow for arbitrary experimentation with packet -- no having to come up with a separate KJ4NGS-xx for every application.

It's the last point that seems strongest to me -- the ability to quickly experiment with new services on the packet net.

There's a lot issues to be solved to make this work, but it seems to me to be something that is fundamentally at the heart of what amateur packet should do.