Advertisement
Promo

Application development Toolkit

Oasis approves Web services 'directory'

Martin LaMonica CNET News

Published: 21 May 2003 10:46 BST

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

A standards body on Tuesday put its stamp of approval on a technology for finding Web services across a network. The Organisation for the Advancement of Structured Information Standards (OASIS) said that an update to the Universal Description, Discovery and Integration (UDDI) specification has been ratified as a standard.

With the ratification of UDDI version 2.0, software companies and individual developers can build software based on the standard and know that their applications will work together.

UDDI acts a registry and locator service for Web services, which are software applications written according to standards that allow them to interact over the Web or a corporate network. The applications access UDDI directories automatically, in the background, to find the information they need to complete transactions.

Although UDDI was introduced nearly three years ago, adoption has been slow compared with that of other Web services standards, such as the Simple Object Access Protocol (SOAP) and Web Services Description Language (WSDL).

Originally, UDDI registries were envisioned as a locator service on the Internet, allowing companies to tap into a broad network of third-party Web services applications. In practice, the directories have been used within corporate networks as a way to store information on available Web services, according to analysts.

Version 2 of UDDI introduces the ability to attach a classification to a Web services directory. This allows a company to identify the contents of UDDI directory to include information such as the company's industry, product categories or geographical information, according to OASIS.

Members of group said that the UDDI technical committee is well on its way to completing the standardisation of a much-anticipated version 3 of the specification. Version 3 introduces the ability to have several interconnected registries and improves the security of UDDI directories with digital signatures.

Ron Schmelzer, an analyst at ZapThink, said that version 3 of UDDI could hasten the adoption of so-called services-oriented architectures, a new way of designing software applications.

In a service-oriented architecture, Web services can share information regardless of the operating system or programming model used to build them. In this way, Web services are "loosely coupled" and link to each other only when required, making a UDDI-like directory more valuable.

"As companies realise that there are significant...benefits in moving to a service-oriented architecture, they will realise that UDDI is no longer an option, but a necessity," Schmelzer said.

OASIS did not give an exact date for the expected standardisation of version 3.


What standards will drive the next wave of Web-based services, and how will they interact? Check out the latest developments on .Net, Java, Liberty Alliance, Passport and other technologies at ZDNet UK's Web Services News Section, including analysis, case studies and management issues.

Let the editors know what you think in the Mailroom.

  • Email
  • Trackback
  • Clip Link
  • Print friendlyPrint with EPSON

Did you find this article useful?
65 out of 115 people found this useful


Full Talkback thread

0 comments


Company/Topic Alerts

Create a new alert from the list below:







Video icon

Video

Discussions

hkommedal hkommedal

It certainly does.

Wednesday 2 December 2009, 12:15 AM

5 comments
CA CA

No, Mr Filesharer, I expect you to die...

Tuesday 1 December 2009, 10:20 PM

4 comments
CA CA

Oh my bad...hkommedal

Tuesday 1 December 2009, 10:19 PM

5 comments

Featured Talkback

In association with Network Liberation Movement
The fact is: Software developers today are really designers and not coders. The reason that business anlaysts exist today to model solutions is because they understand the value of designing software before writing it. All too often developers create code that has little value because they do not understand that business classes interact with other classes within the confines of a working model or pattern.

By: 1000165269

Read full story:
Making sense of agile modelling


Skip Sub Navigation Links to CNET Brand Links

Help

Become part of the ZDNet community.

Newsletters