Web Services Glossary
API (Application Program Interface)—A set of programs or interfaces for developers to interact with the network or operating system.
AUP (Acceptable Use Policy)—A policy defined by the network providers to be followed by users using that network.
B2B (Business-to-Business)—Provides information exchange and other services between businesses.
Binding—Associating an interface, a valid data format, and a protocol to ensure smooth message transmission.
BTP (Business Transaction Protocol)—A protocol used to exchange messages in XML between businesses in a set of B2B transactions over the Internet.
CC/PP (Composite Capability/Preference Profiles)—A set of the user's or user agent's preferences and capabilities.
Client—In any client/server system, the software requesting services or information from the server.
COM (Component Object Model)—A software architecture developed by Microsoft to develop applications from binary software components.
CORBA (Common Object Request Broker Architecture)—Generic interface developed by the Object Management Group (OMG) allowing objects to communicate with each other in a network, irrespective of their language and operating system.
CPA (Collaboration Protocol Agreement)—Rules of interaction between two parties dealing electronically, and a list of their IT capabilities.
CPP (Colloboration Protocol Profile)—Profile of a company with a description of its capabilities (Information Technology-related).
DCOM (Distributed Component Object Model)—Architecture developed by Microsoft to extend COM, thus enabling objects located on different LANs, WANs, or on the Internet to communicate with each other.
DOM (Document Object Model)—A generic interface (platform- and language-neutral) that allows external programs to edit a document's contents, structure, and style.
DTD (Document Type Definition)—A document defining the format of the contents present between the tags in an XML or SGML document, and the way they should be interpreted by the application reading the XML or SGML document.
ebXML (electronic business XML)—A set of specifications defined to enable businesses to communicate with each other, irrespective of their location and domain, over the Internet, exchanging messages in an XML format.
ebXML Messaging Service Protocol—With ebXML Message Handler independent of both, the network protocol (FTP, SMTP, and HTTP) and business processes used for the secure transmission of messages over any kind of network.
HTTP (Hyper Text Transfer Protocol)—A protocol defining how messages should be formatted and what action servers have to take on them. For Web-based messages.
JAXP (Java API for XML Processing)—Converts XML into a format independent of any particular business implementation.
Message—The basic unit of communication containing the data to be transmitted between the client and server.
P2P (Peer to Peer)—Allows a group of programs having similar attributes to communicate with each other.
Service—A facility or application offered by an organization.
SOAP (Simple Object Access Protocol)—A lightweight, XML-based messaging protocol that contains an envelope, header, and body, designed to exchange information in a decentralized, distributed environment.
UDDI (Universal Description, Discovery, and Integration)—An XML-based lookup service for locating Web Services in an Internet scenario.
Web service—An application capable of being defined, located via the Internet protocol, and interacting with other software applications, identified by a Uniform Resouce Identity.
WSDL (Web Services Definition Language)—An XML-based language used to give a description about the Web Services available in a UDDI.
Xinclude—Provides a simple way of including an XML file into an existing XML document.
Xlink (XML Linking Language)—Provides a framework to link all the XML resources together.
XML (eXtensible Markup Language)—A language specialized for Web documents, enabling the creation of tags customized to the company's needs and business logic. It not only has data but also contains metadata. It uses DTD and SCHEMA to describe the data.
XML Encoding—Used to support foreign languages.
XML Namespaces—It is possible for documents to have elements with the same name. XML namespaces are used to differentiate between them to avoid element name conflict.
Xpath—Used to define the parts of an XML document, using path expressions.
Xpointer (XML Pointer Language)—Provides a framework for addressing internal structures of XML documents, such as elements, attributes, and content.
Xquery—Provides functionality to query an XML document.
XSD (XML Schema Definition)—Describes a well-structured XML document.
XSL (eXtensible Stylesheet Language)—A language created for describing stylesheets for XML documents. Consists of XSLT, XPath, and XML Formatting Objects.
XSLT (eXtensible Stylesheet Language Transformation)—Language to transform the format of XML data into data of other formats, on the basis of a set of well-defined rules.