Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Web Services Metadata Exchange

Contributors:  IBM, BEA Systems, Microsoft, SAP AG, Computer Associates, Sun Microsystems, webMethods

Summary:  This specification explains how the Web Services MetadataExchange Framework is structured and how it operates. It is an update to the version previous published on September 1, 2004.

Date:  16 Aug 2006 (Published 01 Mar 2004)
Level:  Advanced

Activity:  5808 views
Comments:  

This specification explains how the Web Services MetadataExchange Framework is structured and how it operates. It is an update to the version previous published on September 1, 2004.

Web services use metadata to describe what other endpoints need to know to interact with them. For example, WS-Policy describes the capabilities, requirements, and general characteristics of Web services; WSDL describes abstract message operations, concrete network protocols, and endpoint addresses used by Web services; XML Schema describes the structure and contents of XML-based messages received and sent by Web services.

To bootstrap communication with a Web service, this specification defines how an endpoint can request the various types of metadata it may need to effectively communicate with the Web service. In response to the request, this specification defines an encapsulation that contains the three different ways the metadata may be returned. First, the metadata itself may be simply included in the response. Second, a URI may be returned, to which an HTTP GET can then be sent to retrieve the metadata from that location. And third, a WS-Addressing Endpoint Reference of a WS-Transfer Metadata Resource may be returned, to which a WS-Transfer Get may be issued to retrieve the metadata. This specification also defines how a WS-Addressing Endpoint Reference can be modified to include this encapsulation.

Get the specifications and related material

DescriptionDateAccess method
WS-MetadataExchange specification (PDF, 236KB)August 2006HTTP download
WS-MetadataExchange WSDL (4KB)August 2006HTTP download
WS-MetadataExchange XSD (4KB)August 2006HTTP download

If you would like to contribute technical comments on this specification, please do so through our Feedback page.

Previous versions of this specification:


Resources

  • Web Services Policy Framework defines how to apply policies to control individual services behavior.

  • Web Services Trust Language is a related protocol for how trust relationships can be shared between services.

  • Web Services Transfer describes a general SOAP-based protocol for accessing XML representations of Web service-based resources.

  • Web Services Security and Web Services Security Addendum describe enhancements to SOAP to provide quality of protection through message integrity, confidentiality, and authentication.

  • WS-SecureConversation defines extensions that build on WS-Security to provide secure communication.

  • WS-SecurityPolicy is a building block that is used in conjunction with other Web service and application-specific protocols to accommodate a wide variety of security models.

  • SOAP 1.1 is the basic messaging transport for all Web services while SOAP 1.2 offers enhancements to the message framework.

  • WSDL 1.1 is the current standard language for services description.

  • XML Schema, Part 1 and Part 2 are specifications that explain how schemas are organized in XML documents.

Comments



Help: Update or add to My dW interests

What's this?

This little timesaver lets you update your My developerWorks profile with just one click! The general subject of this content (AIX and UNIX, Information Management, Lotus, Rational, Tivoli, WebSphere, Java, Linux, Open source, SOA and Web services, Web development, or XML) will be added to the interests section of your profile, if it's not there already. You only need to be logged in to My developerWorks.

And what's the point of adding your interests to your profile? That's how you find other users with the same interests as yours, and see what they're reading and contributing to the community. Your interests also help us recommend relevant developerWorks content to you.

View your My developerWorks profile

Return from help

Help: Remove from My dW interests

What's this?

Removing this interest does not alter your profile, but rather removes this piece of content from a list of all content for which you've indicated interest. In a future enhancement to My developerWorks, you'll be able to see a record of that content.

View your My developerWorks profile

Return from help

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=SOA and web services
ArticleID=153068
SummaryTitle=Web Services Metadata Exchange
publish-date=08162006