The analogue of the previous RESTful service access code (for a different example). Again, that’s awfully complex for such a simple task. Yikes.
(link) []
“OnStar is moving its technology platform from Web services to service-oriented architecture (SOA)”. Say what?!
(link) []

Something I wrote in email to an acquaintance regarding abandoning interface/service description languages;

Don’t be afraid if your architecture doesn’t resemble that of CORBA or DCOM.
Via Dilip, a podcast that totally nails JSF using RESTful arguments. Well worth the download.
(link) []

From RFC 2518 (WebDAV);

XML has been chosen because it is a flexible, self-describing, structured data format that supports rich schema definitions, and because of its support for multiple character sets. XML’s self- describing nature allows any property’s value to be extended by adding new elements. Older clients will not break when they encounter extensions because they will still have the data specified in the original schema and will ignore elements they do not understand.

(emphasis mine)

Hey, I wonder where it says that in the XML Rec? 8-)

See also; a presentation of mine which talks about self-descriptively extensible XML.

“It’s so heartening to see the OMG rebuilt from the ground up, but on port 80 with text…” 8-)
(link) []
“While HTML and HTTP have provided consistent standardization for human to computer interaction[…]” #!@%$! HTTP is a standard protocol for the exchange of data and documents. Any data or documents, effectively. Yes, even machine processable ones.
(link) []
XAML for “workflow”? Is this what it sounds like; a hypermedia replacement for BPEL? (oh, and REST-based service support too, *ding*)
(link) []

Nicely said, David;

First and foremost, a loosely coupled architecture allows you to replace components, or change components, without having to make reflective changes to other components in the architecture/systems. This means businesses can change their business systems as needed, with much more agility than if the architecture/systems was more tightly coupled.

Can your SOA do this?

On the Web, it’s a breeze. In fact, you get it for free.

Embrace loose coupling. Embrace the Web.

Wow, that’s pretty complex coding for such a simple task, no? I’d opt for (bugs, quirks, and all), or other Java client HTTP APIs (the two HTTPClient projects come to mind).
(link) []