|1||BEEP||Blocks Extensible Exchange Protocol||BEEP is a new Internet standards-track protocol framework for new Internet applications. APEX is an emerging relaying service for Internet applications. beepcore is a library for developing BEEP-enabled applications. And beepcore.org is the web site for the growing community of BEEP developers. At BEEP's core is a framing mechanism that permits simultaneous and independent exchanges of messages between peers. Messages are arbitrary MIME content, but are usually textual (structured using XML). |
Also see http://ietf.org/rfc/rfc3080.txt.
|2||BPEL4WS||Business Process Execution Language for Web Services||Business processes can be described in two ways. Executable business processes model actual behavior of a participant in a business interaction. Business protocols, in contrast, use process descriptions that specify the mutually visible message exchange behavior of each of the parties involved in the protocol, without revealing their internal behavior. The process descriptions for business protocols are called abstract processes. BPEL4WS is meant to be used to model the behavior of both executable and abstract processes.|
BPEL4WS provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web services interaction model and enables it to support business transactions. BPEL4WS defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intracorporate and the business-to-business spaces.
|3||BSML||Bioinformatic Sequence Markup Language||Bioinformatic Sequence Markup Language (BSML) is an open XML data standard created to facilitate the interchange of data from diverse technologies into a consistent format for more efficient communication within the life sciences community. In 1997 the National Human Genome Research Institute (NHGRI) funded the development of BSML as an evolving public domain standard for the bioinformatics community.|
|4||CML||Chemical Markup Language||CML (Chemical Markup Language) is a new approach to managing molecular information. It has a large scope as it covers disciplines from macromolecular sequences to inorganic molecules and quantum chemistry. CML is new in bringing the power of XML to the management of chemical information. In simple terms it is "HTML for Molecules", but there is a great deal more to it than that. CML and associated tools allows for the conversion of current files without semantic loss into structured documents, including chemical publications, and provides for the precise location of information within files.|
|5||CSS||Cascading Style Sheets||Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g. fonts, colors, spacing) to XML and HTML documents.|
|6||cXML||Commerce XML||cXML (Commerce XML) is very different from most other electronic business protocols. cXML is a streamlined protocol intended for consistent communication of business documents between procurement applications, e-commerce hubs and suppliers. The protocol does not include the full breadth of interactions some parties may wish to communicate. However, through the use of Extrinsic elements and newly-defined domains for various identifiers, it is easily expanded by such applications. This expansion is the limit of point-to-point configurations necessary for communication.|
|7||DIME||Direct Internet Message Encapsulation||Direct Internet Message Encapsulation (DIME) addresses the difficulties involved in embedding binary data into XML documents. DIME is a specification submitted by Microsoft and IBM to IETF, and it defines a lightweight, binary message format that can be used to encapsulate one or more application-defined payloads of arbitrary type and size into a single message construct. Using DIME, a Web service could combine text, image, and video in a single message. Also see: http://www.perfectxml.com/DIME.asp|
|8||DISCO||Discovery||DISCO is a Microsoft® technology for publishing and discovering Web Services. Also see: UDDI.|
|9||DOM||Document Object Model||Document Object Model (DOM) is an abstract API defined by the W3C to process XML documents. It is a language- and platform-independent abstract API that any parser can implement, and it allows applications to create, read, and modify XML documents. |
Using DOM, the parser loads the entire XML document into the memory at once as a tree, providing random access to it for searching and modifying of any element in the document.
|10||DOM4J||DOM for Java||dom4j is an Open Source XML framework for Java. dom4j allows you to read, write, navigate, create and modify XML documents. dom4j integrates with DOM and SAX and is seamlessly integrated with full XPath support. dom4j is a simpler, lightweight API which is optimised for the Java making extensive use of the Java 2 platform such as the Java 2 collections. dom4j was forked from JDOM project fairly early on. dom4j uses interfaces and factory methods rather than concrete classes and constructors.|
|11||DSML||Directory Services Markup Language||The Directory Services Markup Language (DSML) bridges the world of directory services with the world of XML. DSML 1.0 provided a means of representing directory information in XML. This Technical Committee is working on DSML 2.0 which will add support for querying and modifying directories.|
|12||DSSSL||Document Style Semantics and Specification Language||DSSSL is an international standard for associating processing with SGML documents. As you know, SGML itself is intended to allow the complete separation of the content of a document (text, structure, links), from the processing to be associated with it (usually formatting). So where a Word for Windows, Tex, or even LaTeX document would describe what a document looks like (in other words how a printer should "process" it), SGML documents would only describe the structure. Using DSSSL you can describe the processing of documents in a standard way. Since the two most common forms of document processing are formatting and transformation, DSSSL standardised these two processes first. Others may follow as they are needed. The first two are very powerful and many believe that DSSSL will "transform" (sorry) the world of SGML document processing.|
Also see http://www.jclark.com/jade/.
|13||DTD||Document Type Definition||The purpose of a DTD is to define the legal building blocks of an XML document. It defines the document structure with a list of legal elements. A DTD can be declared inline in your XML document, or as an external reference.|
|14||ebXML||Electronic Business using eXtensible Markup Language||ebXML's mission is to provide an open XML-based infrastructure enabling the global use of electronic business information in an interoperable, secure and consistent manner by all parties. ebXML, sponsored by UN/CEFACT and OASIS, is a modular suite of specifications that enables enterprises of any size and in any geographical location to conduct business over the Internet. Using ebXML, companies now have a standard method to exchange business messages, conduct trading relationships, communicate data in common terms and define and register business processes.|
|15||eCX||eCatalog Exchange||eCX was developed in the fall of 1998 to solve the problem of exchanging product information and catalog structure between different catalog systems. The data type definition (DTD) deals exclusively with the description and definition of catalog structure, or schema, and its associated items. eCX is currently used by Requisite Technology and its Partners for eCatalog Exchange.|
|16||EDI||Electronic Data Interchange||EDI (Electronic Data Interchange) is a standard format for exchanging business data. The standard is American National Standards Institute X12 and it was developed by the Data Interchange Standards Association. An EDI message contains a string of data elements, each of which represents a singular fact, such as a price, product model number, and so forth, separated by delimiter. The entire string is called a data segment. One or more data segments framed by a header and trailer form a transaction set, which is the EDI unit of transmission (equivalent to a message). A transaction set often consists of what would usually be contained in a typical business document or form. The parties who exchange EDI transmissions are referred to as trading partners. EDI is the computer-to-computer exchange of business data in standard formats. In EDI, information is organized according to a specified format set by both parties, allowing a "hands-off" computer transaction that requires no human intervention or rekeying on either end. All information contained in an EDI transaction set is, for the most part, the same as on a conventionally printed document. Also see http://www.geocities.com/WallStreet/Floor/5815/|
|17||GXA||Global XML Web Services Architecture||The Microsoft® Global XML Architecture (GXA) is a protocol framework designed to provide a consistent model for building infrastructure-level protocols for Web services and applications. In addition to this underlying protocol framework, GXA defines a family of pluggable infrastructure protocols that provide applications with commonly needed services such as security, reliability, and multi-party agreement. This document describes the basic design principles of GXA and provides a roadmap for understanding how the individual GXA infrastructure-protocols are composed to provide a cohesive platform for Web services and applications.|
|19||HR-XML||Human resources-XML Consortium||The HR-XML Consortium is an independent, non-profit organization dedicated to the development and promotion of a standard suite of XML specifications to enable e-business and the automation of human resources-related data exchanges. The mission of the HR-XML Consortium is to spare employers and vendors the risk and expense of having to negotiate and agree upon data interchange mechanisms on an ad-hoc basis. By developing and publishing open data exchange standards based on Extensible Markup Language ("XML"), the Consortium provides the means for any company to transact with other companies without having to establish, engineer, and implement many separate interchange mechanisms.|
|20||ICE||Information and Content Exchange||The ICE protocol defines the roles and responsibilities of syndicators and subscribers, defines the format and method of content exchange, and provides support for management and control of syndication relationships. ICE is an application of the Extensible Markup Language (XML). Basic concepts in ICE are represented using the element/attribute markup model of XML.|
|21||IFX||Interactive Financial eXchange||The Interactive Financial eXchange (IFX) is a mature, well-designed XML-based, financial messaging protocol, built by financial industry and technology leaders incorporating decades of combined experience and best of breed design principles. |
The Interactive Financial eXchange Forum was formed in 1997 to create a messaging standard for financial services that would address the challenges faced with the advent of network-based computing models. Based on the work previously done by the Open Financial Exchange (OFX) and IBM/Integrion GOLD standard, the Forum proceeded to re-invest all of the knowledge gained from those standards to design a next generation XML standard that would be usable in many types of environments, extensible to cover many types of financial transactions and globally focused in recognition of the increase need to communicate around the world.
|22||JAXB||Java Architecture for XML Binding||JavaTM Architecture for XML Binding (JAXB) provides an API and tools that automate the mapping between XML documents and Java objects.|
JAXB makes XML easy to use by compiling an XML schema into one or more Java technology classes.
|23||JAXM||Java API for XML Messaging||The Java API for XML Messaging (JAXM) Optional Package enables applications to send and receive document oriented XML messages using a pure Java API. JAXM implements Simple Object Access Protocol (SOAP) 1.1 with Attachments messaging so that developers can focus on building, sending, receiving, and decomposing messages for their applications instead of programming low level XML communications routines.|
|24||JAXP||Java API for XML Processing||The Java API for XML Processing (JAXP) supports processing of XML documents using DOM, SAX, and XSLT. JAXP enables applications to parse and transform XML documents independent of a particular XML processing implementation. Depending on the needs of the application, developers have the flexibility to swap between XML processors (such as high performance vs. memory conservative parsers) without making application code changes. Thus, application and tools developers can rapidly and easily XML-enable their Java applications for e-commerce, application integration, and dynamic Web publishing.|
|25||JAX-RPC||Java API for XML-Based RPC||JAX-RPC is the core Web Services API in the Java platform. The Java API for XML-based RPC (JAX-RPC) enables Java technology developers to develop SOAP based interoperable and portable web services. JAX-RPC provides the core API for developing and deploying web services on the Java platform. JAX-RPC is required part of the J2EE 1.4 platform. JAX-RPC web services can also be developed and deployed on J2EE 1.3 containers and Servlet container.|
|26||JDOM||JDOM||JDOM is, quite simply, a Java representation of an XML document. JDOM provides a way to represent that document for easy and efficient reading, manipulation, and writing. It has a straightforward API, is a lightweight and fast, and is optimized for the Java programmer. It's an alternative to DOM and SAX, although it integrates well with both DOM and SAX.|
|27||LegalXML||LegalXML||LegalXML brings legal and technical experts together to create standards for the electronic exchange of legal data.|
LegalXML is a member section within OASIS the not-for-profit, global consortium that drives the development, convergence and adoption of e-business standards. Members themselves set the LegalXML agenda, using the open OASIS technical process expressly designed to promote industry consensus and unite disparate efforts. LegalXML produces standards for electronic court filing, court documents, legal citations, transcripts, criminal justice intelligence systems, and others.
|28||MathML||Mathematical Markup Language||MathML is an XML application for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this functionality for text. See http://www.w3.org/TR/MathML2/|
|29||MISMO||Mortgage Industry Standards Maintenance Organization||Mortgage Industry Standards Maintenance Organization (MISMO) was established by the Mortgage Bankers Association of America (MBA) to coordinate the development and maintenance of Internet based Extensible Markup Language (XML) real estate finance specifications.MISMO utilizes an open and democratic vendor-neutral approach to the development and maintenance of a single real estate finance XML DTD transaction repository. |
MISMO has published specifications that support mortgage insurance application, mortgage insurance loan boarding, secondary, bulk pricing, real estate services, credit reporting and underwriting process areas. The specifications are freely available for industry implementation via the MISMO website.
|30||MSXML||Microsoft XML Core Services||MSXML, now known as Microsoft XML Core Services, is the COM based API to parse and process XML documents. The current release of this free software from Microsoft includes support for DOM Level 2.0, SAX 2.0, XPath, XSLT, and XSD Schemas.|
|31||NewsML||News Markup Language||An XML-based standard to represent and manage news throughout its lifecycle, including production, interchange, and consumer use.|
|32||OASIS||Organization for the Advancement of Structured Information Standards||OASIS is a not-for-profit, global consortium that drives the development, convergence and adoption of e-business standards. Members themselves set the OASIS technical agenda, using a lightweight, open process expressly designed to promote industry consensus and unite disparate efforts. OASIS produces worldwide standards for security, Web services, XML conformance, business transactions, electronic publishing, topic maps and interoperability within and between marketplaces.|
|33||OFX||Open Financial Exchange||Open Financial Exchange is a specification for the electronic exchange of financial data between financial institutions, business and consumers via the Internet. Created by CheckFree, Intuit and Microsoft in early 1997, Open Financial Exchange supports a wide range of financial activities including consumer and small business banking, consumer and small business bill payment, bill presentment, and investments tracking, including stocks, bonds, mutual funds, and 401(k) account details. Since 2000, with the 2.0 specification, OFX has become XML 1.0 compliant and has added 1098, 1099 and W2 tax form download capabilities.|
|34||OPML||Outline Processor Markup Language||OPML an XML-based format that allows exchange of outline-structured information between applications running on different operating systems and environments.|
|35||PPML||Personalized Print Markup Language||PPML is the Personalized Print Markup Language. Developed by the members of PODi, it is an|
XML-based print language whose purpose is to make it much faster to print documents that
have reusable content. While proprietary technologies have provided this ability in the past,
PPML is the first industry standard method. PPML is an open, interoperable, device-independent standard that will enable the widespread use of personalized print applications. It is a standard developed with commercial intent, to create commercial impact - to genuinely change the economics of personalized printing. It will allow personalized print to be more flexible, easier to use and more affordable to produce. It supports a full range of on-demand printing ranging from the office environment to high-speed production environments.
|36||PRISM||Publishing Requirements for Industry Standard Metadata||PRISM is an extensible XML metadata standard for syndicating, aggregating, post-processing and multi-purposing content from magazines, news, catalogs, books and mainstream journals.|
|37||RDDL||Resource Directory Description Language||A RDDL document, called a Resource Directory, provides a package of information about some target, including human-readable descriptive material about the target, and a directory of individual resources related to the target, each directory entry containing descriptive material and linked to the resource in question.|
|38||RDF||Resource Description Framework||The Resource Description Framework (RDF) integrates a variety of applications from library catalogs and world-wide directories to syndication and aggregation of news, software, and content to personal collections of music, photos, and events using XML as an interchange syntax|
|39||REST||Representational State Transfer||REST is an architectural style that models system behavior for network-based applications. When an application on the Web is implemented according to that style, it inherits the interconnectivity characteristics already present in the Web. REST's purpose is to describe the characteristics of the Web such that they can be used to maximum advantage -- it does not need to define them. With this model, instead of using SOAP, the traditional HTTP GET/POST URI based model is used to create and access XML Web Services. For instance, instead of posting SOAP envelop request, we'll simply send a GET request containing method parameters as URL querystrings, and get back the XML result (without the SOAP packaging overhead). Recently, there is a debate going on as to if SOAP offers any additional benefits, and if just the existing Web facilities (HTTP, GET, POST) can be used to build the XML Web service. Also see http://www.xml.com/pub/a/2002/04/24/google.html.|
|40||ROPE||Remote Object Proxy Engine||Remote Object Proxy Engine (ROPE) provides a set of COM components (rope.dll) that assist in building SOAP messaging into your applications. If you were to call a SOAP method without using ROPE you would have to format the SOAP calls into XML, package the call into an HTTP request and send it, receive the HTTP response and parse the returning XML. ROPE takes care of all of that complexity for you. ROPE is not required to use SOAP, but it sure makes things easier. Microsoft's Visual Studio 6.0 SOAP Toolkit contains some helpful information and examples of how to implement ROPE.|
|41||RSS||RDF Site Summary||RDF Site Summary (RSS) is a lightweight multipurpose extensible metadata description and syndication format. RSS is an XML application, conforms to the W3C's RDF Specification and is extensible via XML-namespace and/or RDF based modularization.|
|42||RuleML||The Rule Markup Initiative||Rules in (and for) the Web have become a mainstream topic since inference rules were marked up for E-Commerce and were identified as a Design Issue of the Semantic Web, and since transformation rules were put to practice for document generation from a central XML repository (as used here). Moreover, rules have continued to play an important role in AI shells for knowledge-based systems and in Intelligent Agents, today both needing a Web interchange format, and such XML/RDF-standardized rules are now also usable for the declarative specification of Web Services. |
The Rule Markup Initiative has taken initial steps towards defining a shared Rule Markup Language (RuleML), permitting both forward (bottom-up) and backward (top-down) rules in XML for deduction, rewriting, and further inferential-transformational tasks. The initiative started during PRICAI 2000, as described in the Original RuleML Slide, and was launched in the Internet on 2000-11-10. Besides the previous XML-only RuleML and the current XML/RDF-combining RuleML, there is also an approach towards an RDF-only RuleML. Complementary efforts consist of the development of (Java-based) rule engines such as Mandarax RuleML and XSB-RDF RuleML. There now exists an initial RuleML design and a Version 0.8 system of DTDs for basic RuleML sublanguages.
|43||SAAJ||SOAP with Attachments API for Java||The SOAP with Attachments API for Java (SAAJ) enables developers to produce and consume messages conforming to the SOAP 1.1 specification and SOAP with Attachments note.|
This specification has been derived from the java.xml.soap package originally defined in the JAXM 1.0 specification. The package was moved from the JAXM specification to this document so that other specifications, including JAX-RPC 1.0, can depend on this package without creating a dependency on the rest of the JAXM specification. In the interest of consistency and to simplify the synchronization of the specifications, this first version of the SAAJ specification has been given the number 1.1, same as the corresponding JAXM specification.
|44||SALT||Speech Application Language Tags||Speech Application Language Tags (SALT) are a lightweight set of extensions to existing markup languages, in particular HTML and XHTML that enable multimodal and telephony access to information, applications and Web services from PCs, telephones, tablet PCs and wireless personal digital assistants (PDAs).|
|45||SAML||Security Assertion Markup Language||SAML is an XML-based security standard for exchanging authentication and authorization information.|
|46||SAX||Simple API for XML||SAX, like DOM, defines a set of abstract interfaces for processing XML. It differs from the DOM in that, instead of loading the entire document into memory, SAX follows a streaming model, reading an XML document character by character as a stream, and generating events as each element or attribute is encountered. The SAX-based parser passes these events up to the application through various notification interfaces.|
SAX is an excellent lightweight alternative to DOM for processing XML documents. Unlike DOM, SAX is not a product of the W3C, and was created by the XML-DEV mailing list members, led by David Megginson.
|47||SCOAP||Simple CORBA Object Access Protocol||Simple CORBA Object Access Protocol (SCOAP ) defines CORBA semantics over SOAP and enable native SOAP clients to access CORBA services. There are multiple advantages in using CORBA as a programming model for the|
SOAP protocol domain. These advantages will benefit CORBA as well as SOAP users.
SOAP promises to provide remote procedure call systems with a firewall solution. On
the other hand, SOAP is a maturing technology, and CORBA can provide SOAP users
with already available language bindings and service APIs. Also see ftp://ftp.omg.org/pub/docs/orbos/00-09-07.pdf
|48||SGML||Standard Generalized Markup Language||Conceived notionally in the 1960s - 1970s, the Standard Generalized Markup Language (SGML, ISO 8879:1986) gave birth to a profile/subset called the Extensible Markup Language (XML), published as a W3C Recommendation in 1998. Depending upon your perspective and requirements, the differences between SGML and XML are inconsequential or immense. SGML is more customizable (thus flexible and more "powerful") at the expense of being (much) more expensive to implement.|
|49||SMBXML||Small Business Extensible Markup Language||SMBXML (Small Business Extensible Markup Language) is an open, XML-based standard, designed especially for use by small and medium-sized businesses, that describes a data exchange format for use in common business applications. The SMBXML package includes elements intended primarily for transactions and recordkeeping. Examples include sales records, purchasing records, payroll, tax records, and general banking. Currency exchange rates can be calculated, and conversions can be made, allowing SMBXML to be used in international business operations. The standard can also be applied to general databases, such as employee shift scheduling, vacation scheduling, sick time, and so forth. SMBXML is compatible with most Internet transport and security protocols. Data can be exchanged between consenting parties provided integration agreements are signed.|
|50||SMIL||Synchronized Multimedia Integration Language||Synchronized Multimedia Integration Language (SMIL, pronounced "smile") defines an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL 2.0, an author can describe the temporal behavior of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen. SMIL 2.0 syntax and semantics can be re-used in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL 2.0 components are used for integrating timing into XHTML and into SVG.|
|51||SOAP||Simple Object Access Protocol (With version 1.2, SOAP is no longer an acronym)||SOAP 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 this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework. |
|52||SOM||Schema Object Model||The Schema Object Model (SOM) provides a navigable set of classes that allow access to items in an XML Schema defined using the W3C XML Schema Definition (XSD) specification.|
|53||SQLXML||XML Support in SQL Server 2000||SQLXML enables XML support for your Microsoft SQL Server 2000 Database. It allows developers to bridge the gap between XML and relational data. You can create XML Views of your existing relational data and work with it as if it was an XML file. SQLXML is your solution if you need to |
Query relational database with XPath, Query relational database with SQL and return XML results, Update relational data as if it was XML, Load huge XML files into existing SQL Server 2000 database, converting them to relational data, Query your SQL Server via URLs from your Web Browser of Web application, Access SQL Server XML functionality via OLEDB/ADO, Access SQL Server XML functionality via .NET Managed Classes, and so on.
|54||SVG||Scalable Vector Graphics||SVG is a language for describing two-dimensional graphics in XML. SVG allows for three types of graphic objects: vector graphic shapes (e.g., paths consisting of straight lines and curves), images and text. Graphical objects can be grouped, styled, transformed and composited into previously rendered objects. Text can be in any XML namespace suitable to the appplication, which enhances searchability and accessibility of the SVG graphics. The feature set includes nested transformations, clipping paths, alpha masks, filter effects, template objects and extensibility. |
SVG drawings can be dynamic and interactive. The Document Object Model (DOM) for SVG, which includes the full XML DOM, allows for straightforward and efficient vector graphics animation via scripting. A rich set of event handlers such as onmouseover and onclick can be assigned to any SVG graphical object. Because of its compatibility and leveraging of other Web standards, features like scripting can be done on SVG elements and other XML elements from different namespaces simultaneously within the same Web page. Also see http://www.w3.org/TR/SVG11
|55||SwA||SOAP Messages with Attachments||SwA defines a binding for a SOAP 1.1 message to be carried within a MIME multipart/related message in such a way that the processing rules for the SOAP 1.1 message are preserved. The MIME multipart mechanism for encapsulation of compound documents can be used to bundle entities related to the SOAP 1.1 message such as attachments. Rules for the usage of URI references to refer to entities bundled within the MIME package are specified.|
|56||SyncML||SyncML||SyncML is the common language for synchronizing all devices and applications over any network. SyncML leverages Extensible Markup Language (XML), making SyncML a truly future-proof platform. With SyncML, networked information can be synchronized with any mobile device, and mobile information can be synchronized with any networked applications. With SyncML any personal information, such as email, calendars, to-do lists, contact information and other relevant data, will be consistent, accessible and up to date, no matter where the information is stored. For example, a calendar entry made to a mobile device on a business trip is equally available to a secretary in the network calendar. SyncML is the ultimate choice for remote synchronization. SyncML is designed especially with the wireless world's tight requirements in the mind. SyncML minimizes the use of bandwidth and can deal with special challenges of wireless synchronization like relatively low reliability of the connection and high network latency. In addition to that SyncML enables synchronization over fixed networks, infrared, cable, or Bluetooth. As an open, future-proof standard, SyncML is the synchronization choice for any device or application of the Mobile Information Society!|
|57||TranXML||TranXML||TranXML® , a new extensible markup language (XML) solution, is being proposed as the new industry standard for e-commerce related activities between shippers and carriers. It was created specifically for the procurement and delivery of transportation and logistics services required for supply chain execution. This groundbreaking work to introduce TranXML® to the market was accomplished by Transentric, based on the X.12 and XMLSolutions meta data repository. Transentric 's goal for TranXML® is to remove barriers and to dramatically increase the use of e-Commerce as it relates to transportation and logistics services. The real impact of TranXML® is that it will allow a neutral format that enables both carrier and shipper legacy systems to exchange data.|
|58||UBL||Universal Business Language||The Universal Business Language defines a library of standard electronic business documents, plugs directly into existing traditional business practices, eliminates re-keying of data in existing fax-based supply chains, and fills the “payload” slot in B2B frameworks such as the UN/OASIS ebXML initiative (http://ebxml.org). UBL fulfills the promise of XML for business by defining a standard cross-industry vocabulary. |
UBL envisions a world where all companies, large and small, can interact seamlessly with their
trading partners as if they were part of the same virtual enterprise. It achieves that goal by
standardizing the form of information exchange.
UBL proposes a single ubiquitous language for business communication that takes into account
both the requirements common to all enterprises and the specific needs of companies in
different regions and different vertical industries. Convergence on a single standard will
significantly reduce the cost of integration. By lowering the bar to adoption of e-business
technology, UBL promises to extend the efficiencies of automated ERP systems beyond the
|59||UDDI||Universal Description, Discovery, and Integration||UDDI is the building block that will enable businesses to quickly, easily and dynamically find and transact business with one another.|
The UDDI Community is comprised of more than 300 business and technology leaders working together to enable companies and applications to quickly, easily, and dynamically find, and use Web services. As a cornerstone of the emerging Web services architecture, UDDI will benefit businesses of all sizes by creating an open platform-independent specification. As a part of the UDDI project, a UDDI Business Registry has been established to allow businesses to publish and discover Web services. More information about the UDDI project can be obtained at www.uddi.org.
|60||UIML||User Interface Markup Language||UIML is an XML language for defining user interfaces. UIML is used to define the location, and design of controls. It also defines actions to take when certain events take place.|
|61||VML||Vector Markup Language||VML is an application of Extensible Markup Language (XML) 1.0 which defines a format for the encoding of vector information together with additional markup to describe how that information may be displayed and edited.|
|62||VoiceXML||Voice Extensible Markup Language||VoiceXML is an application of the Extensible Markup Language (XML) which, when combined with voice recognition technology, enables interactive access to the Web through the telephone or a voice-driven browser. An individual session works through a combination of voice recognition and keypad entry. VoiceXML 1.0 was created through a collaboration of AT&T, IBM, Lucent Technologies, and Motorola, who were each working on their own approach but joined forces to create an open standard. Using XML, a programmer can enable voice recognition through the addition of a few simple tag. Also see: http://www.perfectxml.com/learn1.asp|
|63||VRML||Virtual Reality Modeling Language||The Virtual Reality Modeling Language (VRML) is a file format for describing interactive 3D objects and worlds. VRML is designed to be used on the Internet, intranets, and local client systems. VRML is also intended to be a universal interchange format for integrated 3D graphics and multimedia. VRML may be used in a variety of application areas such as engineering and scientific visualization, multimedia presentations, entertainment and educational titles, web pages, and shared virtual worlds.|
|64||VRXML||Vendor Reporting Extensible Markup Language||VRXML is an XML standard for market data billing. See http://www.fisd.net/billing/vrxml.asp|
|65||W3C||World Wide Web Consortium||The World Wide Web Consortium was created in October 1994 to lead the World Wide Web to its full potential by developing common protocols that promote its evolution and ensure its interoperability. W3C has around 500 Member organizations from all over the world and has earned international recognition for its contributions to the growth of the Web.|
|66||WAP||Wireless Application Protocol||The Wireless Application Protocol (WAP) is an open, global specification that empowers mobile users with wireless devices to easily access and interact with information and services instantly.|
Also see: http://www.wapforum.org/what/index.htm
|67||WDDX||Web Distributed Data Exchange||The Web Distributed Data Exchange, or WDDX, is a free, open XML-based technology that allows Web applications created with any platform to easily exchange data with one another over the Web. |
WDDX is an XML-based technology that enables the exchange of complex data between Web programming languages, creating what some refer to as 'Web syndicate networks'. WDDX consists of a language-independent representation of data based on an XML 1.0 DTD, and a set of modules for a wide variety of languages that use WDDX. WDDX can be used with HTTP, SMTP, POP, FTP and other Internet protocols that support transferring textual data.
|68||WML||Wireless Markup Language||WML, formerly called HDML (Handheld Devices Markup Language), is a markup language that is based on XML (eXtensible Markup Language). The official WML specification is developed and maintained by the WAP Forum, an industry-wide consortium founded by Nokia, Phone.com, Motorola, and Ericsson. This specification defines the syntax, variables, and elements used in a valid WML file. Also see http://www.perfectxml.com/WAPWML.asp|
|69||WSDL||Web Services Description Language||WSDL 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, however, the only bindings described in this document describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.|
|70||WSFL||Web Services Flow Language||The Web Services Flow Language (WSFL) is an XML language for the description of Web Services compositions WSFL considers two types of Web Services compositions:|
1. The first type specifies the appropriate usage pattern of a collection of Web
Services,in such a way that the resulting composition describes how to achieve a
particular business goal;typically,the result is a description of a business process
2. The second type specifies the interaction pattern of a collection of Web Services;in
this case,the result is a description of the overall partner interactions
|71||WS-I||Web Services Interoperability Organization||WS-I is an open, industry organization chartered to promote Web services interoperability across platforms, operating systems, and programming languages. The organization works across the industry and standards organizations to respond to customer needs by providing guidance, best practices, and resources for developing Web services solutions. |
WS-I was formed specifically for the creation, promotion, or support of Generic Protocols for Interoperable exchange of messages between services. Generic Protocols are protocols that are independent of any specific action indicated by the message beyond actions necessary for the secure, reliable, or efficient delivery of messages; "Interoperable" means suitable for and capable of being implemented in a neutral manner on multiple operating systems and in multiple programming languages.
|72||WS-Inspection||Web Services Inspection Language||The WS-Inspection specification provides an XML format for assisting in the inspection of a site for available services and a set of rules for how inspection related information should be made available for consumption. A WS-Inspection document provides a means for aggregating references to pre-existing service description documents which have been authored in any number of formats. These inspection documents are then made available at the point-of-offering for the service as well as through references which may be placed within a content medium such as HTML.|
Also see: http://www-106.ibm.com/developerworks/webservices/library/ws-wsilover/
|73||WS-Referral||Web Services Referral Protocol||WS-Referral is a protocol that enables the routing strategies used by SOAP nodes in a message path to be dynamically configured. SOAP itself provides a distributed processing model where SOAP messages can have content destined for specific processing nodes. WS-Routing adds to SOAP the capability of describing the actual message path. WS-Referral provides a mechanism to dynamically configure SOAP nodes in a message path to define how they should handle a SOAP message. It is a configuration protocol that enables SOAP nodes to delegate part or all of their processing responsibility to other SOAP nodes.|
Web Services Referral Protocol (WS-Referral) is a simple SOAP-based protocol for configuring instructions about message paths (routing entries) in SOAP nodes that relay SOAP messages (SOAP routers). WS-Referral is orthogonal to the Web Services Routing Protocol (WS-Routing) in that WS-Referral provides a way to configure how SOAP routers will build a message path, whereas WS-Routing provides a mechanism for describing an actual path of a message.
WS-Referral aids in the configuration of message paths, which in turn enables a variety of services. In addition to relay services such as high performance overlay message delivery or corporate firewall services, SOAP routers can provide Web services like load-balancing, mirroring, caching, and client authentication services. As an example, a Web service may delegate responsibility for some aspects of its service to third parties in a manner that is transparent to users of that service.
|74||WS-Routing||Web Services Routing Protocol||WS-Routing is a simple, stateless, SOAP-based protocol for routing SOAP messages in an asynchronous manner over a variety of transports like TCP, UDP, and HTTP. With WS-Routing, the entire message path for a SOAP message (as well as its return path) can be described directly within the SOAP envelope. It supports one-way messaging, two-way messaging such as request/response and peer-to-peer conversations, and long running dialogs. |
The Web Services Routing Protocol (WS-Routing) defines mechanisms for routing SOAP messages. SOAP is a lightweight wire protocol that defines a serialization mechanism to transport method calls to be used in application layer protocols. SOAP does not actually define a mechanism for sending a message from one party to another, even though it refers to a virtual message path. WS-Routing (formerly known as SOAP-RP) is a stateless protocol that extends SOAP by defining a means to specify an ordered route, or path, from the originator of the message, through intermediaries, to the ultimate message receiver.
|75||WS-Security||Web Services Security||WS-Security describes enhancements to SOAP messaging to provide quality of protection through message integrity, message confidentiality, and single message authentication. These mechanisms can be used to accommodate a wide variety of security models and encryption technologies. |
WS-Security also provides a general-purpose mechanism for associating security tokens with messages. No specific type of security token is required by WS-Security. It is designed to be extensible (e.g. support multiple security token formats). For example, a client might provide proof of identity and proof that they have a particular business certification.
Additionally, WS-Security describes how to encode binary security tokens. Specifically, the specification describes how to encode X.509 certificates and Kerberos tickets as well as how to include opaque encrypted keys. It also includes extensibility mechanisms that can be used to further describe the characteristics of the credentials that are included with a message.
|76||WSXL||Web Services Experience Language||WSXL (Web Services Experience Language) is a Web services centric component model for interactive Web applications, that is, for applications that provide a user experience across the Internet. WSXL is designed to achieve two main goals: enable businesses to deliver interactive Web applications through multiple distribution channels and enable new services or applications to be created by leveraging other interactive applications across the Web. |
To accomplish these goals, all WSXL component services implement a set of base operations for life cycle management, accepting user input, and producing presentation markup. More sophisticated WSXL component services may be specialized to represent data, presentation, and control. WSXL also introduces a new description language to guide the adaptation of user experience to new distribution channels.
User experiences that are implemented using WSXL can be delivered to end users through a diversity of distribution channels - for example, directly to a browser, indirectly through a portal, or by embedding into a third party interactive Web application. In addition, WSXL user experiences can easily be modified, adapted, aggregated, coordinated, synchronized or integrated, often by simple declarative means. New applications can be created by seamlessly combining WSXL applications and adapting them to new uses, to ultimately leverage a worldwide pallet of WSXL component services.
WSXL is built on widely accepted established and emerging open standards, and is designed to be independent of execution platform, browser, and presentation markup.
|77||XACML||Extensible Access Control Markup Language||XACML is an XML specification for expressing policies for information access over the Internet. The motivation behind XACML is to express well-established ideas in the field of access-control policy using an extension language of XML.|
|78||XAML||Transaction Authority Markup Language||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 - the revolutionary new model of Internet-based computing that is now being adopted by all major systems and software vendors. 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.
|79||XBRL||Extensible Business Reporting Language||XBRL (Extensible Business Reporting Language) is an electronic format for simplifying the flow of financial statements, performance reports, accounting records, and other financial information between software programs. This royalty-free, open specification is being developed collaboratively to make it less costly for companies to publish financial information in a format that can be easily viewed and used by management, investors, regulators, and all of the participants in financial markets. It is an XML-based framework that provides the financial community a standards-based method to prepare, publish in a variety of formats, reliably extract and automatically exchange the financial statements of public and private companies, public sector agencies. XBRL enhances the usability and transparency of financial information reported under existing accounting standards, simplifies disclosure, and allows companies to communicate financial information more readily via the Internet.|
|80||XDR||XML-Data Reduced||XML-Data Reduced (XDR) schema is a subset of ideas described in the XML-Data specification, specifically the World Wide Web Consortium (W3C) XML-Data Note (http://www.w3.org/TR/1998/NOTE-XML-data-0105/) and the Document Content Description (DCD) initiative for XML.|
MSXML 2.0 and later provide XDR schema support.
See also: XSD
|81||XForms||XForms||XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three parts—XForms model, instance data, and user interface—it separates presentation from content, allows reuse, gives strong typing—reducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting.|
XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML or SVG.
|82||XHTML||Extensible HyperText Markup Language||XHTML is a family of current and future document types and modules that reproduce, subset, and extend HTML 4. XHTML family document types are XML based, and ultimately are designed to work in conjunction with XML-based user agents. XHTML 2 is a markup language intended for rich, portable web-based applications. While the ancestry of XHTML 2 comes from HTML 4, XHTML 1.0, and XHTML 1.1, it is not intended to be backward compatible with its earlier versions. Application developers familiar with earlier its ancestors will be comfortable working with XHTML 2. |
Also see: http://www.w3.org/TR/xhtml2
|83||X-KISS||XML Key Information Service Specification||The X-KISS specification defines a protocol for a Trust service that resolves public key information contained in XML-SIGelements. The X-KISS protocol allows a client of such a service to delegate part or all of the tasks required to process elements. A key objective of the protocol design is to minimize the complexity of application implementations by allowing them to become clients and thereby to be shielded from the complexity and syntax of the underlying PKI used to establish trust relationships. The underlying PKI may be based upon a different specification such as X.509/PKIX, SPKI or PGP.|
X-KISS is defined in terms of structures expressed in the XML Schema Language, protocols employing the Simple Object Access Protocol (SOAP) v1.1 and relationships among messages defined by the Web Services Definition Language v1.0.
|84||XKMS||XML Key Management Specification||The XML Key Management Specification (XKMS) comprises two parts -- the XML Key Information Service Specification (X-KISS) and the XML Key Registration Service Specification (X-KRSS).|
The X-KISS specification defines a protocol for a Trust service that resolves public key information contained in XML-SIGelements. The X-KISS protocol allows a client of such a service to delegate part or all of the tasks required to process elements. A key objective of the protocol design is to minimize the complexity of application implementations by allowing them to become clients and thereby to be shielded from the complexity and syntax of the underlying PKI used to establish trust relationships. The underlying PKI may be based upon a different specification such as X.509/PKIX, SPKI or PGP.
The X-KRSS specification defines a protocol for a web service that accepts registration of public key information. Once registered, the public key may be used in conjunction with other web services including X-KISS.
Both protocols are defined in terms of structures expressed in the XML Schema Language, protocols employing the Simple Object Access Protocol (SOAP) v1.1 [SOAP] and relationships among messages defined by the Web Services Definition Language v1.0 [WSDL]. Expression of XKMS in other compatible object encoding schemes is also possible.
|85||X-KRSS||XML Key Registration Service Specification||The X-KRSS specification defines a protocol for a web service that accepts registration of public key information. Once registered, the public key may be used in conjunction with other web services including X-KISS.|
X-KRSS is defined in terms of structures expressed in the XML Schema Language, protocols employing the Simple Object Access Protocol (SOAP) v1.1 and relationships among messages defined by the Web Services Definition Language v1.0.
|86||XLANG||XLANG||Automation of business processes based on web services requires a notation for the specification of message exchange behavior among participating web services. XLANG is expected to serve as the basis for automated protocol engines that can track the state of process instances and help enforce protocol correctness in message flows. |
Also see http://www.ebpml.org/xlang.htm
|87||XLink||XML Linking Language||XLink allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links.|
Also see http://www.w3.org/TR/xlink/
|88||XML||Extensible Markup Language||See http://www.perfectxml.com/XML500.asp for details.|
|89||XMLDSIG||XML Digital Signature Syntax and Processing||XMLDSIG specifies XML syntax and processing rules for creating and representing digital signatures. XML Signatures can be applied to any digital content (data object), including XML. An XML Signature may be applied to the content of one or more resources. Enveloped or enveloping signatures are over data within the same XML document as the signature; detached signatures are over data external to the signature element. More specifically, this specification defines an XML signature element type and an XML signature application; conformance requirements for each are specified by way of schema definitions and prose respectively. This specification also includes other useful types that identify methods for referencing collections of resources, algorithms, and keying and management information. |
The XML Signature is a method of associating a key with referenced data (octets); it does not normatively specify how keys are associated with persons or institutions, nor the meaning of the data being referenced and signed. Consequently, while this specification is an important component of secure XML applications, it itself is not sufficient to address all application security/trust concerns, particularly with respect to using signed XML (or other data formats) as a basis of human-to-human communication and agreement. Such an application must specify additional key, algorithm, processing and rendering requirements.
|90||XML-RPC||XML Remote Procedure Call||XML-RPC is 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.
|91||XMP||eXtensible Metadata Platform||The eXtensible Metadata Platform (XMP) provides Adobe applications and workflow partners with a common XML framework that standardizes the creation, processing, and interchange of document metadata across publishing workflows.|
XMP encompasses the following: framework, schema, XMP packet technology, and the XMP Software Development Kit, which is available as an open-source license. XMP is based on the W3C's open standard for metadata, known as the Resource Description Framework (RDF).
XMP embeds metadata inside application files. Because the metadata is enclosed within the file, documents retain their context when they exit their original system or environment. The embedded metadata can include any XML schema, provided it is described in RDF syntax. Extensible, embedded metadata in application files provides significant potential for repurposing, archiving, and automation in publishing workflows.
|92||XMPP||Extensible Messaging and Presence Protocol||XMPP is an open, XML-based protocol for near real-time extensible messaging and presence. It is the core protocol of the Jabber Instant Messaging and Presence technology which is currently deployed on thousands of servers across the Internet and is used by millions of people worldwide. The XMPP working group shall adapt the XMPP for use as an IETF Instant Messaging and Presence technology. Also see http://xml.coverpages.org/xmpp.html|
|93||XPointer||XML Pointer Language||XPointer is the language to be used as the basis for a fragment identifier for any URI reference that locates a resource whose Internet media type is one of text/xml, application/xml, text/xml-external-parsed-entity, or application/xml-external-parsed-entity.|
|94||XQuery||XML Query Language||XQuery facilitates the ability to intelligently query XML data. It is designed to be a language in which queries are concise and easily understood. It is also flexible enough to query a broad spectrum of XML information sources, including both databases and documents. The Query Working Group has identified a requirement for both a human-readable query syntax and an XML-based query syntax.|
|95||XSD||XML Schema Definition||XML Schemas express shared vocabularies and allow machines to carry out rules made by people. They provide a means for defining the structure, content and semantics of XML documents.|
|96||XSL||Extensible Stylesheet Language||XSL is a language for expressing stylesheets. It consists of three parts: XSL Transformations (XSLT): a language for transforming XML documents, the XML Path Language (XPath), an expression language used by XSLT to access or refer to parts of an XML document. (XPath is also used by the XML Linking specification). The third part is XSL Formatting Objects: an XML vocabulary for specifying formatting semantics. 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.|
|97||XSL-FO||XSL Formatting Objects||XSL 1.0 is known as XSL-FO, and it is an XML vocabulary for specifying formatting semantics.|
|98||XSLT||XSL Transformations||XSLT is a language for transforming XML documents into other XML documents.|
|99||XTM||XML Topic Maps||XTM provides a model and grammar for representing the structure of information resources used to define topics, and the associations (relationships) between topics. Names, resources, and relationships are said to be characteristics of abstract subjects, which are called topics. Topics have their characteristics within scopes: i.e. the limited contexts within which the names and resources are regarded as their name, resource, and relationship characteristics. One or more interrelated documents employing this grammar is called a “topic map.”|
|100||XUL||Extensible User-interface Language||XUL (Extensible User-interface Language) is a standard way to exchange data that describes a program's user interface, or at least the portion of it that can be controlled by programming. XUL is a standards-based way to create the user interface for a cross-platform application. It allows you to do with a few lines of markup language what until now took many lines of code. Applications interfaces, with their windows, frames, scroll bars, menus, and toolbars, are created easily -- and just as easily customized by the user.See http://www.oreillynet.com/pub/a/network/2000/03/03/xul.html for more details.|