Glossary
This glossary is currently being updated. You'll find additional Web service terms described here.
A B C D E
F G H I J K
L M N O P Q
R S T U V W
X Y Z
Suggest/submit a glossary entry
A [ Top ]
ACID
ACID is an for the four properties guaranteed by transactions: atomicity, consistency, isolation, and durability.
An atomic transaction is the smallest indivisible unit of acceptable change. Consistency means that
the transaction correctly transforms the system state. Isolation ensures that no other transaction can see
a transaction in an incomplete state. A durable transaction is one that's capable of surviving system failures
intact. A transaction should be able to survive all failures, including server, process, communication, and media
failures.
Actor
An actor is an attribute defined by the SOAP 1.1 specifications. It's presence on a child element of the Header element identifies the endpoint for which this element was intended.
See SOAP.
B [
Top ]
Bean
A reusable software component. Beans can be combined to create an application.
See also EJB, JavaBeans
Biztalk
BizTalk is an industry initiative started by Microsoft and supported by a wide range of organizations like SAP,
CommerceOne and Ariba. This initiative is establishing a set of guidelines for how to publish schemas in XML and
how to use XML messages to easily integrate software programs together in order to build rich new solutions.
See also Biztalk Framework and Biztalk Server.
More at http://www.biztalk.org
Biztalk Framework
The BizTalk Framework addresses issues of XML-based information exchange between third-party or custom-developed
applications in a platform- and technology-neutral manner. It provides specifications for the design and development
of XML-based messaging solutions for communication between applications and organizations. This specification builds
upon standard and emerging Internet technologies such as Hypertext Transfer Protocol (HTTP), Multipurpose Internet
Mail Extensions (MIME), Extensible Markup Language (XML), and Simple Object Access Protocol (SOAP).
See also ebXML, Biztalk, Biztalk Server.
More at http://www.microsoft.com/biztalk/techinfo/framework20.htm
Biztalk Server
A product from Microsoft conforming to the Biztalk framework. The BizTalk Server 2000 unites, in a single product,
enterprise application integration (EAI), business-to-business integration, and the advanced BizTalk Orchestration
technology to allow developers, IT professionals, and business analysts to easily build dynamic business processes
that span applications, platforms, and businesses over the Internet.
See also Biztalk and Biztalk Framework.
More at http://www.microsoft.com/biztalk/
Brazil Toolkit
The Brazil project is a web-based infrastructure from Sun Microsystems that links people securely to information, computers and other devices leveraging existing standards and protocols.
The framework enables stand-alone systems to work together within the Web space. A strong authentication architecture allows extranets to access intranets in an open environment without compromising security. The Brazil project's approach extends the endpoints of a network to new applications and smaller devices. At the same time it can incorporate legacy applications into the system.
More at http://www.sun.com/research/features/brazil/.
C [
Top ]
C#
C# (pronounced C-sharp) is a new object oriented language from Microsoft and is derived from C and C++. It also
borrows a lot of concepts from Java too including garbage collection.
More at http://msdn.microsoft.com/vstudio/nextgen/technology/csharpintro.asp,
http://msdn.microsoft.com/library/default.asp?URL=/library/dotnet/csspec/vclrfcsharpspec_Start.htm
and http://msdn.microsoft.com/vstudio/nextgen/technology/csharpdownload.asp
CORBA
CORBA or the Common Object Request Broker Architecture is a language independent, distributed object model specified
by the Object Management Group (OMG).
More at http://www.corba.org
Crimson
Crimson is a XML parser from the Apache group which supports XML 1.0. It is based on the Sun Project X parser.
More at http://xml.apache.org/crimson/index.html
See also Xerces
D [
Top
]
DOM
DOM or Document Object Model is a platform- and language-neutral interface that will allow programs and scripts
to dynamically access and update the content, structure and style of documents. The document can be further processed
and the results of that processing can be incorporated back into the presented page. DOM provides a standard set
of objects for representing HTML and XML documents, a standard model of how these objects can be combined, and
a standard interface for accessing and manipulating them. Vendors can support the DOM as an interface to their
proprietary data structures and APIs, and content authors can write to the standard DOM interfaces rather than
product-specific APIs, thus increasing interoperability on the Web.
More at http://www.w3.org/DOM/, http://www.oasis-open.org/cover/dom.html
See also SAX
Digital certificates
Digital certificates are electronic files that are used to uniquely identify people and resources over networks
such as the Internet. They are based on public-key cryptography, which uses a pair of keys (private and public
key) for encryption and decryption.
DISCO
DISCO or "Discovery of Web Services" is a draft protocol for discovery of services proposed by Microsoft.
It assumes that Web Services are described using SCL (SOAP Contract Language) documents. Hence, it proposes how
SCL documents can be retrieved for a resource or a collection of resources, i.e. how information about a service
is discovered. It is not limited to discovering information about Web Services, it can be used to find metadata
for any resource. The discovery itself can be of two types
- Discovering endpoints for a service
- Discovering orchestration for a service i.e. the when and how messages are sent from endpoint to endpoint.
See also RDF, SCL.
More at http://msdn.microsoft.com/xml/general/disco.asp
DTD
DTD or Document Type Definition is a description of the structure and properties of a class of XML files.
E [ Top ]
ebXML
ebXML is a set of specifications that together enable a modular electronic business framework. The vision of ebXML
is to enable a global electronic marketplace where enterprises of any size and in any geographical location can
meet and conduct business with each other through the exchange of XML based messages. ebXML is a joint initiative
of the United Nations (UN/CEFACT) and OASIS, developed with global participation for global usage.
ebXML is similar in intent to Biztalk, however it is a much more expansive framework than BizTalk that not only
defines processes for exchanging business documents, but also for dealing with various reliability, legal and international
issues involved with exchanging documents. Sun Microsystems is a strong supporter of ebXML, whereas Microsoft is
promoting Biztalk.
See also Biztalk
More at http://www.ebxml.org
EJB
EJB or Enterprise Java Beans is a component architecture for the development and deployment of object-oriented,
distributed, enterprise-level applications. Applications written using the Enterprise JavaBeans architecture are
scalable, transactional, and multi-user and secure. The enterprise bean is a component that implements a business
task or business entity and is of two types- entity bean or a session bean.
See also Bean, Entity bean, Session bean
More at http://java.sun.com/products/ejb/
Entity bean
An enterprise bean that represents persistent data maintained in a database. An entity bean can manage its
own persistence or it can delegate this function to its container. An entity bean is identified by a primary key.
If the container in which an entity bean is hosted crashes, the entity bean, its primary key, and any remote references
survive the crash.
See also EJB
More at http://java.sun.com/products/ejb/
E-SPEAK
E-speak is HP's open software platform for the creation of dynamic, intelligent e-services. The e-speak services
defines a uniform services interface (API's) and uniform services interaction (e-speak engine) that allows e-services
to dynamically interact to discover, negotiate, broker and compose themselves to solve a business to business or
business to consumer service request.
It has a strong security component and fine grained security model for the services based on SPKI (Simple Public
Key Infrastructure). It has recently added support for SOAP.
More at http://www.e-speak.net and http://e-speak.hp.com
F [ Top
]
G [ Top ]
H [ Top ]
I [ Top ]
IIOP
IIOP or Internet Inter-ORB Protocol is a transport protocol used for communication between CORBA object request brokers.
.
See also CORBA.
J [ Top ]
JavaBeans
Javabeans is a a portable, platform-independent reusable component model written in Java.
See also beans.
More at http://java.sun.com/products/javabeans/
JDBC
JDBC or Java Database Connectivity is a standard for database-independent connectivity between the Java platform
and a wide range of databases. The JDBC interface provides a call-level API for SQL-based database access.
More at http://java.sun.com/products/jdbc/
JAXB
Also called as Project Adelard and XML/Java Binding. This is proposed specification from Javasoft
that will define an XML data-binding facility for the Java Platform. Such a facility compiles an XML schema into
one or more Java classes. These automatically-generated classes handle the translation between XML documents that
follow the schema and interrelated instances of the derived classes. They also ensure that the constraints expressed
in the schema are maintained as instances of the classes are manipulated.
More at http://java.sun.com/xml/
JAXP
JAXP or Java API for XML Parsing is an optional API provided by Javasoft. It provides basic functionality for reading,
manipulating, and generating XML documents through pure Java APIs. It is a thin and lightweight API that provides
a standard way to seamlessly integrate any XML-compliant parser with a Java application.
More at http://java.sun.com/xml/
JAXM
JAXM or Java API for XML Messaging is an optional API provided by Javasoft. The overall goal is to provide a messaging
system for use in B2B systems. These B2B scenarios are generally conceived of as involving two or more business
entities communicating via the Internet (TCP/IP). In particular, a Java application developer should be able to
easily communicate with other business entities which have agreed to adhere to specifications which the ebXML initiative
has put forth by working with a set of simple Java interfaces. JAXM is generic API for XML messaging- it can be
used as a Java interface to any XML messaging system, such as ebXML MS, SOAP, W3C XML Protocol. Sun is developing an implementation
of the JAXM API for ebXML MS (code name "M Project").
See also SOAP, M project
More at http://java.sun.com/xml/ and http://developer.java.sun.com/developer/earlyAccess/mproject/
JAXR
JAXR or Java API for XML Registries provides an API for a set of distributed Registry Services that enables business-to-business integration between business enterprises, using the protocols being defined by ebXML.org, Oasis, ISO 11179.
More at http://java.sun.com/aboutJava/communityprocess/jsr/jsr_093_jaxr.html
Jini
Jini network technology provides a simple infrastructure for delivering services in a network and for creating
spontaneous interaction between programs that use these services regardless of their hardware/software implementation.
More at http://www.sun.com/jini/, http://www.jini.org/
JSEE
JSEE or Java Secure Socket Extension is a Java package that enables secure Internet communications. It implements
a Java version of SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols and includes functionality
for data encryption, server authentication, message integrity, and optional client authentication. Using JSSE,
developers can provide for the secure passage of data between a client and a server running any application protocol
(such as HTTP, Telnet, NNTP, and FTP) over TCP/IP.
See also SSL
More at http://java.sun.com/products/jsse/
JSP
JSEE or Java Server Pages is an extension of the Java Servlet technology. It allows for java code to be embedded
in HTML pages. JSP pages use XML tags and scriptlets written in the Java programming language to encapsulate the
logic that generates the content for the page. It passes any formatting (HTML or XML) tags directly back to the
response page. In this way, JSP pages separate the page logic from its design and display .
See also taglibs
More at http://java.sun.com/products/jsp/
jUDDI
jUDDI (pronounced "Judy") is an open source Java-based implementation of a UDDI registry and a toolkit
for developers to build access to UDDI registries within their own applications. jUDDI has been architected to
allow it to act as the UDDI front-end on top of existing directories and databases. jUDDI-enabled applications
can look up services in the UDDI registry and then proceed to "call" those web services directly. It
is developed by Bowstreet.
See also UDDI
More at http://www.juddi.org
K [ Top ]
L [ Top
]
M [ Top
]
M Project, The
See JAXM.
mustUnderstand
mustUnderstand is an attribute defined by the SOAP 1.1 specification. It's presence on a child element of the Header element indicates that any endpoint processing the Header must either recognize the element or return the appropriate SOAP Fault, containing the faultcode MustUnderstand.
See SOAP.
N [ Top ]
NASSL
NASSL or the Network Accessable Service Specification Language was an IDL language for SOAP proposed by IBM. It seems to have been superceeded by WSDL.
See also WSDL, SCL and SDL.
.NET
.NET is Microsoft's strategy for delivering software as a service. It includes .NET infrastructure and tools to
build and operate a new generation of services, .NET user experience to enable rich clients, .NET building block
services and .NET device software to enable a new generation of smart Internet devices.
See also .NET framework, Visual Studio .NET
More at http://msdn.microsoft.com/net/
.NET framework
The .NET Framework is an environment from Microsoft for building, deploying, and running Web Services and other
applications. It consists of three main parts: the Common Language Runtime, the Framework classes, and ASP.NET.
See also .NET framework, Visual Studio .NET
More at http://msdn.microsoft.com/net/
O [ Top ]
ORB
ORB or Object Request Broker is library than enables CORBA objects to locate and communicate with one another.
See also CORBA.
OTS
OTS or Object Transaction Service is a definition of the interfaces that permit CORBA objects to participate in
transactions.
See also CORBA.
P [ Top
]
pocketSOAP
pocketSOAP is a COM-based client SOAP toolkit with versions available for most Windows platforms, including Windows CE.
More at http://www.pocketsoap.com
PKI
PKI or the Public Key Infrastructure is the use of public key cryptography and X.509 certificates in a
distributed server system to establish secure domains and trusted relationships.
See also SPKI
More at http://www.pki-page.org
Project Adelard
See JAXB
Q [ Top ]
R [ Top
]
RDF
RDF--the Resource Description Framework-- is a framework for metadata; it provides interoperability between applications
that exchange machine-understandable information on the Web. RDF emphasizes facilities to enable automated processing
of Web resources. RDF metadata can be used in a variety of application areas; for example: in resource discovery
to provide better search engine capabilities; in cataloging for describing the content and content relationships
available at a particular Web site, page, or digital library; by intelligent software agents to facilitate knowledge
sharing and exchange; in content rating; in describing collections of pages that represent a single logical "document";
for describing intellectual property rights of Web pages, and in many others. RDF with digital signatures will
be key to building the "Web of Trust" for electronic commerce, collaboration, and other applications.
More at http://www.w3.org/RDF/
RMI
RMI or Remote Method Invocation enables the programmer to create distributed Java based applications, in which
the methods of remote Java objects can be invoked from other Java virtual machines, possibly on different hosts.
A Java program can make a call on a remote object once it obtains a reference to the remote object, either by looking
up the remote object in the bootstrap naming service provided by RMI or by receiving the reference as an argument
or a return value
More at http://java.sun.com/products/jdk/rmi/
ROPE
ROPE or Remote Object Proxy Engine is a set of COM components (rope.dll) that assist in building SOAP messaging
into applications.
More at http://msdn.microsoft.com/library/periodic/period00/webservice.htm
RosettaNet PIP
A RosettaNet PIP (Partner Interface Processes) is an XML specification designed to align a specific business process
between supply chain partners.
This initial test of a PIP, completed by IBM and Microsoft, allows manufacturers to seamlessly add new products
-- including standardized technical specifications and part numbers -- into their partners' catalogs. RosettaNet
develops PIPs through extensive process modeling to determine how partners (manufacturers, distributors, resellers,
carriers and end-users) in the IT supply chain interact with each other as they carry out day-to-day business activities
in each of six high-level business process areas -- Partner/Product Review, Product Introduction, Order Management,
Inventory Management, Marketing Information Management, and Service and Support.
More at http://www.rosettanet.org/
S [ Top ]
SAX
SAX or Simple API for XML is an event-driven, serial-access mechanism for accessing XML documents. .
More at http://www.megginson.com/SAX/
See also DOM
S2ML
S2ML or Security Services Markup Language is an industry standard for enabling secure e-commerce transactions
through eXtensible Markup Language
(XML). S2ML was developed to provide a common language for the sharing of security services between companies engaged
in B2B and B2C business transactions. It has been supported by a number of vendors including Sun, Bowstreet and
Verisign. S2ML is a set of two XML schemas (Name Assertion and Entitlement) and an XML-based request / response
protocol for two services (Authentication and Authorization) designed to provide a framework for sharing security
objects on the Internet.
More at http://www.s2ml.org/
SCOAP
SCOAP or the Simple CORBA Object Access protocol aims to define CORBA semantics over SOAP and enable native SOAP
clients to access CORBA services.
See also SOAP
More at ftp://ftp.omg.org/pub/docs/orbos/00-09-07.pdf
and ftp://ftp.omg.org/pub/docs/orbos/00-09-03.pdf
SCL
SCL or the SOAP Contract Language SCL, describes contracts between a set of endpoints exchanging messages. It was
proposed by Microsoft and is used to describe Web Services.
See also WSDL
More at http://msdn.microsoft.com/xml/general/disco.asp
SDL
SDL or the Service Description Language. This is a standard proposed by Microsoft and has since been superceeded
by WSDL.
See also WSDL
SKPI
SKPI or Simple Public Key Infrastructure SPKI is an Internet draft standard that defines public-key certificates
for access control. It emphasizes decentralization and uses largely the public keys of entities instead of their
names. The certificates are mainly used in access control. SPKI avoids using globally unique names for entities.
See also PKI
More at http://www.ietf.org/html.charters/spki-charter.html,
http://world.std.com/~cme/html/spki.html
SOUP
The Simple Object Update Protocol (SOUP) specifies an content-transfer model for digital "appliances"
like cameras, printers, scanners,
picture frames, personal digital assistants, cell phones, machine control systems, and so on. SOUP standardizes
simple but important communications
between content-rich devices. It uses Simple Object Access Protocol (SOAP) messages to push content from one device
into another. The approach resembles
the way web browsers pull content from web servers.
More at http://www.hpl.hp.com/personal/John_Barton/HTTP-A/SOUP.htm
SOAP
SOAP or the Simple Object Access protocol, is a lightweight protocol for exchange of information in a decentralized,
distributed environment. It is an
XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in
a message and how to process it, a set of
encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote
procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however,
the only bindings defined in in the standard describe how to use SOAP in combination with HTTP and HTTP Extension
Framework.
See also JAXM, XML-RPC, XML Protocol
More at http://www.w3.org/TR/SOAP and http://www.soaprpc.com
SOAP body
The SOAP Body element provides a simple mechanism for exchanging mandatory information intended for the ultimate
recipient of the message. Typical uses of the Body element include marshalling RPC calls and error reporting. All
immediate child elements of the Body element are called body entries and each body entry is encoded as an independent
element within the SOAP Body element.
See also SOAP
More at http://www.w3.org/TR/SOAP
SOAP detail element
The detail element is intended for carrying application specific error information related to the Body element.
It MUST be present if the contents of the Body element could not be successfully processed. It MUST NOT be used
to carry information about error information belonging to header entries. Detailed error information belonging
to header entries MUST be carried within header entries. The absence of the detail element in the Fault element
indicates that the fault is not related to processing of the Body element. This can be used to distinguish whether
the Body element was processed or not in case of a fault situation. All immediate child elements of the detail
element are called detail entries and each detail entry is encoded as an independent element within the detail
element.
See also SOAP
More at http://www.w3.org/TR/SOAP
SOAP envelope
The Envelope is the top element of the XML document representing the message. The element MAY contain namespace
declarations as well as additional attributes. If present, such additional attributes MUST be namespace-qualified.
Similarly, the element MAY contain additional sub elements. If present these elements MUST be namespace-qualified
and MUST follow the SOAP Body element.
See also SOAP
More at http://www.w3.org/TR/SOAP.
SOAP fault
The SOAP Fault element is used to carry error and/or status information within a SOAP message. If present, the
SOAP Fault element MUST appear as a body entry and MUST NOT appear more than once within a Body element. See
also SOAP
More at http://www.w3.org/TR/SOAP
SOAP faultactor
The faultactor element is intended to provide information about who caused the fault to happen within the message
path. It is similar to the SOAP actor attribute but instead of indicating the destination of the header entry,
it indicates the source of the fault. The value of the faultactor attribute is a URI identifying the source. Applications
that do not act as the ultimate destination of the SOAP message MUST include the faultactor element in a SOAP Fault
element. The ultimate destination of a message MAY use the faultactor element to indicate explicitly that it generated
the fault
See also SOAP
More at http://www.w3.org/TR/SOAP
SOAP faultcode The faultcode element is intended for use by software to provide an algorithmic mechanism
for identifying the fault. The faultcode MUST be present in a SOAP Fault element and the faultcode value MUST be
a qualified name. SOAP defines a small set of SOAP fault codes covering basic SOAP faults
See also SOAP
More at http://www.w3.org/TR/SOAP
SOAP faultstring The faultstring element is intended to provide a human readable explanation of the fault
and is not intended for algorithmic processing. The faultstring element is similar to the 'Reason-Phrase' defined
by HTTP. It MUST be present in a SOAP Fault element and SHOULD provide at least some information explaining the
nature of the fault.
See also SOAP
More at http://www.w3.org/TR/SOAP
SOAP header The Header element is encoded as the first immediate child element of the SOAP Envelope XML
element. All immediate child elements of the Header element are called header entries.
See also SOAP
More at http://www.w3.org/TR/SOAP
SSL
SSL or secure socket layer is a security protocol. It is the standard for securing communications and transactions
across the Internet and is supported by most browsers and webservers. It uses digital certificates to create a
secure, confidential
communications "pipe" between two entities.
See also JSSE
More at http://www.openssl.org, http://home.netscape.com/eng/ssl3/
Sun ONE
Sun ONE or Sun Open Net Environment is suite of software from Sun Microsystems for creating, assembling and deploying Web Services. The two main tools are Sun's Forte for Java product family and the iPlanet Process Manager. Forte for Java software is designed for the rapid building and combining of software components that may be accessed as services. iPlanet Process Manager is a graphical service creation environment tuned to the needs of business professionals.
More at http://www.sun.com/sunone
T [
Top ]
taglibs
taglibs or JSP tag libraries define declarative, modular functionality that can be reused by any JSP page. Tag
libraries reduce the necessity to embed large amounts of Java code in JSP pages by moving the functionality provided
by the tags into tag implementation classes. In doing so, tag libraries makes authoring JSP pages easier -- both
for the Web page author and for tools that expose the functionality encapsulated by the library to the author.
See also JSP
More at http://java.sun.com/products/jsp/taglibraries.html
U [ Top
]
UDDI
UDDI or Universal Description, Discovery and Integration is a standard proposed by Microsoft, IBM and Ariba. The
UDDI specifications define a way to publish and discover information about Web Services. The term "web service"
describes specific business functionality exposed by a company, usually through an Internet connection, for the
purpose of providing a way for another company or software program to use the service. The core component of the
UDDI project is the UDDI business registration, an XML file used to describe a business entity and its Web Services.
Conceptually, the information provided in a UDDI business registration
consists of three components: "white pages" including address, contact, and known identifiers; "yellow
pages" including industrial categorizations based on standard taxonomies; and "green pages", the
technical information about services that are exposed by the business. Green pages include references to specifications
for Web Services, as well as support for pointers to various file and URL based discovery mechanisms if required.
More at http://www.uddi.org, http://uddi.microsoft.com/
and http://www-3.ibm.com/services/uddi/index.html
V [ Top ]
Visual Studio .NET
This is a new release of the Visual Studio product from Microsoft with a lot of support for XML technolgies for
building Web Services. It also has
a new programming language- C#.
See also C#
More at http://msdn.microsoft.com/vstudio/nextgen/beta.asp
W [ Top
]
W3C
W3C or the World Wide Web Consortium is a organization with a mission to develop interoperable technologies (specifications, guidelines, software, and tools) to lead the Web to its full potential as a forum for information, commerce, communication, and collective understanding.
More at http://www.w3.org/
WSDL
WSDL or Web Services Description Language is an XML format for describing network services as a set of endpoints
operating on messages containing either
document-oriented or procedure-oriented information. The operations and messages are described abstractly, and
then bound to a concrete network protocol and
message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services).
WSDL is extensible to allow description of
endpoints and their messages regardless of what message formats or network protocols are used to communicate. It
consolidates earlier proposals in this area include NASSL, SCL and SDL.
See also NASSL, SCL and SDL.
More at http://www-106.ibm.com/developerworks/library/w-wsdl.html
WSFL
WSFL or Web Services Flow Language is an XML language for the description of
Web Services compositions.
More at http://www-4.ibm.com/software/solutions/webservices/pdf/WSFL.pdf
X [ Top ]
XAML
Transaction Authority Markup Language (XAML) is a vendor-neutral standard that enables the coordination and processing
of online transactions in the
rapidly emerging world of XML web services. XAML is intended to be a completely open standard for web-based business
transactions. The standard defines a set of XML message formats and interaction models that web services can use
in order to provide business-level transactions that span multiple parties across the Internet. It is supported
by a number of vendors, including Bowstreet, Hewlett-Packard Company, IBM, Oracle and Sun Microsystems.
More at http://www.xaml.org
Xerces
Xerces is an Open source XML Parser from the Apache group. It is available for Java, C++ and Perl.
More at http://xml.apache.org
See also Crimson and JAXP
XHTML
XHTML or EXtensible HyperText Markup Language is a reformulation of HTML in XML. It can be considered as a stricter
and cleaner version of HTML.
More at http://www.w3.org/TR/xhtml1/, http://www.w3.org/TR/xhtml-basic/
XIDL
XIDL was an interface defination language for SOAP RPC proposed by IBM. It was superceeded by NASSL, which seems
to have been superceeded by WSDL.
See also NASSL, SCL and SDL
XML
XML stands for eXtensible Markup Language. It is an extensible document language for specifying document content
(i.e. data). XML is not a single, predefined markup language: it's a metalanguage -- a language for describing
other languages -- which lets you design your own markup. A predefined markup language like HTML defines a way
to describe information in one specific class of documents only: XML lets you define your own customized markup
languages for limitless different classes of document. It can do this because it's written in SGML, the international
standard metalanguage for text markup systems.
More at http://www.w3.org/XML, http://www.xml.org
and http://www.xml.com
XML-RPC
XMLRPC is a predecessor of SOAP. It's a spec and a set of implementations that allow software running on disparate
operating systems, running in different environments to make procedure calls over the Internet. It's remote procedure
calling using HTTP as the transport and XML as the encoding. XML-RPC is designed to be as simple as possible, while
allowing complex data structures to be transmitted, processed and returned.
See also SOAP.
More at http://www.xmlrpc.com
XML/Java Binding
See JAXB
XMLP
See XML Protocol
XML Protocol
The goal of XMLP (XML Protocol) is to develop technologies which allow two or more peers to communicate in a distributed
environment, using XML as its
encapsulation language. Solutions developed by this activity allow a layered architecture on top of an extensible
and simple messaging format, which provides robustness, simplicity, reusability and interoperability.
See also SOAP
More at http://www.w3.org/2000/xp/
XP
Stands for either XML Protocol or extreme programming.
More at http://www.extremeprogramming.org/.
See also XML Protocol
XPath
XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer.
See also XPointer, XSLT
More at http://www.w3.org/TR/xpath
XPointer
XPointer is the language to be used as the basis for a fragment identifier for any URI reference that locates a resource of Internet media type text/xml or application/xml.
XPointer, which is based on the XML Path Language (XPath), supports addressing into the internal structures of XML documents. It allows for examination of a hierarchical document structure and choice of its internal parts based on various properties, such as element types, attribute values, character content, and relative position.
More at http://www.w3.org/TR/xptr
XSL
XSL is a language for expressing stylesheets. It consists of two parts:
- XSL Transformations (XSLT): a language for transforming XML documents
- An XML vocabulary for specifying formatting semantics (XSL Formatting Objects)
An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary.
See also
XSLT
More at
http://www.w3.org/Style/XSL/,
http://www.w3.org/TR/xsl/
XSLT
XSLT is a language for transforming XML documents into other XML documents. XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL
includes an XML vocabulary for specifying formatting. XSL specifies the styling of an XML document by using
XSLT to describe how the document is transformed into another XML document that uses the formatting
vocabulary.
XSLT is also designed to be used independently of XSL. However, XSLT is not intended as a completely
general-purpose XML transformation language. Rather it is designed primarily for the kinds of transformations
that are needed when XSLT is used as part of XSL.
See also XSL
More at http://www.w3.org/TR/xslt
Y [
Top ]
Z [ Top ]
Date: Mar 1, 2001
Version: 1.6
Author: Vivek Chopra
URL: http://www.SoapRPC.com/faqs/glossary.html