When working with and reusing Web services it is good practice to keep and maintain the different parts of services, operations, messages and their contents in separate locations.

Thinking in conventional terms: types and structures are best defined in XSD schema documents; XML documents are a good place to put reusable constants; XSLT documents act as complex assignment or copy methods; WSDLs tie these elements together while encapsulating abstractions of business logic that reasonably belong together. WSDLs declare interfaces and define transport and serialization conventions, as well as where instances can be called.

Understanding services, peers and clients requires users and developers to inspect documents where types and operations are declared and defined. The browse idiom in this console, is therefore extended to these resources.