formalized communication on the job
Years ago I worked with a company that used an application named The Coordinator,
by Action Technologies Inc. The package defined a protocol for communication,
which included making specific requests for action, accepting or declining
the requests, and declaring the requests complete.
In my opinion, the package supported and worked well in the company's environment.
It encouraged people to be specific and to respond. On the other hand, the
formality of the protocol did not inspire non-request communication, such
as "A note to say hi." or "Here's my idea. What do you think?"
Here are some interesting references:
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL