The popularity of widgets these days has brought to attention the need for
interoperability, i.e. for widgets developed for one site or platform to be
able to run in other sites and widgets developed by different people to be
able to work with each other.
So much so that I know of at least 3 somewhat competing specifications for
There's the gadget portion of the OpenSocial specs which was adopted from the
Google Gadgets work. Then there's OpenAjax which is more broadly focused on
Ajax interoperability but has a lot of pieces geared towards widget
And finally there's the W3C's Widgets 1.0 Family of Specifications. Based on
a preliminary analysis, the OpenAjax specs appear to be the most
comprehensive for widget interoperability issues but OpenSocial seems to have
gained more adoption.
The W3C work appears to be moving very slowly (no surp... (more)
Over the past few years I’ve been helping a lot of government clients
design and implement architectures for information-sharing. When it comes
to information-sharing one of the most important aspects is the relationships
in the data being shared because it’s those relationships that provide the
context to help you understand and utilize the information better. Within
an enterprise, key data types are often dispersed across multiple systems so
a lot of the things we did included implementing data services (i.e.
SOAP/WSDL-based Web Services) on top of each of these systems to pr... (more)
The adoption of Service Oriented Architecture (SOA) promises to further
decouple monolithic applications by decomposing business functions and
processes into discrete services. While this makes enterprise computing
assets more accessible and reusable, SOA implementation patterns are
primarily an iteration over previous application development models. Like
most application development evolutions, SOA approaches inject more layers
and flexibility into the application tier, but have often neglected the most
fundamental building block of all applications: the underlying data.
Typically when we think about security for a Web service, our focus is on how
to protect it from unauthorized and malicious users. Thus, we tend to
concentrate on such things as authentication of the requestor, checking to
see that the requestor is authorized to access the service, validation of the
request message, and so forth - all things that happen on the way in or
during a request for the service. However, there is an equally important set
of security functions that need to occur on the way out or after the service
has finished processing the request.
Because these securit... (more)
Enterprise information integration (EII) is getting a lot of hype these days,
and the vendors are giving you very compelling reasons for why you need an
enterprise data access layer based on their EII product. However, a lot of
the scenarios and case studies they present are very targeted or are simple
examples of how their product works that don't delve into the complexities of
a real-world environment. This article presents some of those complexities
and demonstrates how some of the EII products may not provide adequate
functionality for an environment with such complexities.