to LooselyCoupled.com homepage
 Weekly emails: how to  

 

> weblog > archive > June 2002


June 23rd-29th, 2002

You know how to WSDL, don't you?

Building applications that are web services-ready sounds like good advice, but how do you do that when the web services ...

Putting the whizz into web services

Those in the know pronounce certain web services standards as words rather than spelling out the letters in the ...

WSCI sours for ebXML as BPML opens 1.0

BPMI.org yesterday published BPML 1.0, the first public draft for release 1.0 of the Business Process Modeling ...

The A in EBITDA

I've often wondered what the A in EBITDA stands for. Now I think I've got it: Earnings Before Interest, Taxes, ...

Gaps for startups in web services management

Small firms will be the main drivers of innovation in web services, even though all the media focus is on what big ...

Platforms by stealth: Macromedia, Progress

How can an up-and-coming vendor win market share for its platform against the big guys? The trick is to sell the ...


June 16th-22nd, 2002

Digital identity is not a two-horse race

Smaller players could gain ground in digital identity while the market waits to see more substance emerge from ...

Loose coupling, good or bad?

A welcome debate has been launched by Jon Udell's article last week about loose coupling. Patrick Logan points out that ...

Keep standards simple

Creating ever-more-complex web services standards will hinder adoption, warns Blue Titan Software's chief architect ...

Hard-wired applications and the EAI scam

Hearing the founders of Cape Clear and Bowstreet on successive evenings is bound to give plenty of food for thought, ...


June 9th-15th, 2002

Why loosely coupled?

If you ever wondered why loose coupling is such an important concept in web services, this InfoWorld article by Jon ...

Why not aggregate collectively?

RSS newsfeeds make it possible to read multiple news sources at once, and now that many weblogs publish an RSS feed of ...

Giving the Web a human face

"Where are the business advantages in becoming a 'faceless third party'? Even if you're the most reliable faceless ...

Understanding orchestration

Today, we have applications. In the future, all we will have is orchestration. Today's applications will have atomized ...

Putting UDDI into context

People have wrongly perceived UDDI as the Google of web services discovery, writes Doug Kaye. A closer analogy might be ...

So tell me again, how do we make money from this?

At last, someone has noticed the missing ingredient in the web services stack: billing. Everyone has been talking about ...


June 2nd-8th, 2002

Web-native application services flourish

Adopting a componentized software architecture is one of the key success factors identified by IDC in its latest survey ...

Web services in a nutshell

Keeping it to less than a dozen words is a good rule of thumb for an elevator pitch. The essentials are captured ...

UDDI is not enough

A groundswell of dissatisfaction has been rising against UDDI, and not before time. A very thorough article in this ...

Embracing and extending the desktop

Networked services add to, rather than eliminating, client functionality. This is in contrast to the early beliefs of ...

The secret of integration is separation

"Modularization of applications, and their delivery as a service, is the biggest change that web services will create ...


previous month | next month

Assembling on-demand web services to automate business, commerce, and the sharing of knowledge

read an RSS feed from this weblog

current


archives

 
 


Copyright © 2002-2010, Procullux Media Ltd. All Rights Reserved.