Monthly Archives: January 2006


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.

Assuming XML extensibility

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.

David Linthicum on Loose Coupling

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.