The state and availability of services are key to the success of SOA. Tim Ewald says Web services consumers should be kept notified about the state of the service they're subscribing to, and has coined a new, mashed-up term for it: "slogging."
Is this an example of Web 2.0 meeting SOA? Ewald writes: "I envision a system based on 'service blogs,' or 'slogs.' A slog conveys information about the state of a service. As a consumer, I want to subscribe to a slog for each service I use. My aggregator becomes a 'dependency dashboard' that tells me about upcoming service news."
I think "slogging" is a pretty clever name for a very useful service, though it evokes images of never-ending messaging... sort of like slogging through 100 e-mails a day.