Basic Search  Advanced Search   
Topics Resources Free Library Software XML News About Us
  You are here: home Info Bank Glossary » Page 4 Thursday, 31 January 2008


A | B | C | D | E

F | G | H | I | J

K | L | M | N | O

P | Q | R | S | T

U | V | WXYZ

Top 10 Glossary Words

XSLT | XPath | SAX

New Glossary Words

eCX | XBRL | XQuery

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | WXYZ

Previous Page


  • WAP
    Wireless Application Protocol, or WAP, is the de facto worldwide standard for providing Internet communications and advanced telephony services on digital mobile phones, pagers, personal digital assistants and other wireless terminals.

    The Wireless Application Protocol is a standard developed by the WAP Forum, a group founded by Nokia, Ericsson, (formerly Unwired Planet), and Motorola. WAP defines a communications protocol as well as an application environment. In essence, it is a standardized technology for cross-platform, distributed computing.

      External link WAP Forum Web site
      External link Introduction to WAP
      External link WAP An Introduction

  • WDDX
    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.

    Allaire created WDDX in order to solve key problems in exchanging data between Web applications. In particular, Simeon Simeonov, Allaire's language technology architect, created WDDX to support problems of distributed computing within ColdFusion. This work was generalized into a cross-language framework, and resulted in the creation of the WDDX SDK and The WDDX SDK was created by Nate Weiss, an independent Web developer, with the support of Allaire and a number of other third parties.

    WDDX is not a formal standard, and it has not been submitted to the W3C or any other standards body. However, WDDX will be freely available for use and redistribution, and is based on open, standards-based technologies such as XML 1.0. Also, it is clear that WDDX represents a significant intellectual and technical contribution to the evolution of distributed Web applications.

      External link

  • Web Service
    Web service is a collection of functions that are packaged as a single entity and published to the network for use by other programs. Web services are building blocks for creating open distributed systems, and allow companies and individuals to quickly and cheaply make their digital assets available worldwide.

      External link The Web service (r)evolution (Part 1)
      External link The Web service (r)evolution (Part 2)

  • Well-formed XML
    XML that meets the requirements listed in the W3C Recommendation for XML 1.0: It contains one or more elements; it has a single document element, with any other elements properly nested under it; each of the parsed entities referenced directly or indirectly within the document is well-formed. A well-formed XML document does not necessarily include a DTD.

  • WML
    WML (Wireless Markup Language), 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,, Motorola, and Ericsson. This specification defines the syntax, variables, and elements used in a valid WML file. WML Resource Page

  • WMLScript
    WMLScript is the WAP corollary to the JavaScript scripting language.

      External link Adding Client-Side Logic To WAP Using WMLScript
      External link Introducing WML and WMLScript
      External link WAPScript tutorial at W3Schools

  • 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.

      External link Web Services Description Language Specification
      External link Using WSDL in SOAP applications

  • WSFL
    The Web services Flow Language (WSFL) Guide describes how Web services may be composed into new Web services to support business processes. Composition comes in two types: The first type allows to specify the logic of a business process; the second type allows to define the mutual exploitation of Web services of participants in a business process. A brief concepts of composition sketch is provided in an introductory chapter of the document. A detailed discussion of the metamodel behind composition follows. The language proper is described and illustrated by code snippets, followed by an XML schema of the 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:
    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
    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

      External link The Web services Flow Language(WSFL) specification This is a PDF Document

  • 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 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.

      External link

  • XBRL
    XBRL (Extensible Business Reporting Language), formerly code named XFRML, is a freely available electronic language for financial reporting. 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 financial statements of publicly held companies and the information they contain. XBRL is not about establishing new accounting standards but enhancing the usability of the ones that we have through the digital language of business. XBRL will not require additional disclosure from companies to outside audiences.

    XBRL, at least at first, will be used to digitally publish financial statements of companies that are issued to external users. An XBRL-based financial statement is a digitally enhanced version of paper-based financial statements, which include the balance sheet, income statement, statement of equity, statement of cash flows, and the notes to the financial statements as well as the accountant's report. "XBRL for Financial Statements" enables a dramatic improvement in the processing of financial reports. XBRL documents can be prepared efficiently, exchanged reliably, published more easily, analyzed quickly, retrieved by investors simply, and enables smarter investments. Potential XBRL applications include XBRL for Financial Statements, XBRL for Taxes, XBRL for Regulatory Filings, XBRL for Accounting and Business Reports, and XBRL for Authoritative Literature.

    XBRL Powerpoint Presentations and other resources External link
    XBRL Essentials External link
    More XBRL Presentations External link
    XBRL Public Discussion Group External link
    MorganStanley XBRL Pages External link
    XBRL Sets Stage for Real-Time Financial Reporting External link
    XBRL demo for MultiMart Web Financials External link
    XBRL Examined in Plain-Speak English External link
    Finally, Business Talks the Same Language: XBRL will make business data easier to access. External link
    The CPA Journal: How XBRL will change your practice External link External link

    As the World Wide Web Consortium (W3C) describes it, XHTML (Extensible Hypertext Markup Language) is "a reformulation of HTML 4.0 as an application of the Extensible Markup Language (XML)." For readers unacquainted with either term, HTML is the set of codes (that's the "markup language") that a writer puts into a document to make it displayable on the World Wide Web. HTML 4 is the current version of it. XML is a structured set of rules for how one might define any kind of data to be shared on the Web. It's called an "extensible" markup language because anyone can invent a particular set of markup for a particular purpose and as long as everyone uses it (the writer and an application program at the receiver's end), it can be adapted and used for many purposes - including, as it happens, describing the appearance of a Web page. That being the case, it seemed desirable to reframe HTML in terms of XML. The result is XHTML, a particular application of XML for "expressing" Web pages.

    XHTML is, in fact, the follow-on version of HTML 4. You could think of it as HTML 5, except that it is called XHTML 1.0. In XHTML, all HTML 4 markup elements and attributes (the language of HTML) will continue to be supported. Unlike HTML, however, XHTML can be extended by anyone that uses it. New elements and attributes can be defined and added to those that already exist, making possible new ways to embed content and programming in a Web page. In appearance, an XHTML file looks like a somewhat more elaborate HTML file.

      External link XHTML Basic Specification

  • XKMS
    XML Key Management Specification (XKMS), uses the relative simplicity of XML to implement two key aspects of secure e-commerce, according to the companies. Microsoft Corp. and VeriSign Inc. will be soon submitting the specification to Web standards bodies for consideration as an open Internet standard. XKMS aims to simplify application building by moving digital-signature handling and encryption out of the applications themselves.

      External link XKMS Specification

  • 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 the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links.

      External link XLink Specification Page's XLink Resource Page

  • XML
    eXtensible Markup Language (XML) is a W3C specification. In it's simplest form, XML is a powerful medium of data exchange. It allows you to create your own meta-language (tags) to represent data and meta-data (data about data). It is different from HTML - HTML has fixed tags and format, XML lets you define your own tags and format (hence eXtensible), HTML tells how the data should "look", whereas XML describes the data and its structure. There are many tools available to create XML documents and again to load, read, validate and parse those documents. This allows applications running on totally different platforms to exchange data - because everybody understands "text" and XML document is another tagged text document.

      External link XML Specification's XML Resource Center

  • XML Data Islands
    XML Data Islands refers to ability of embedding "islands" of data inside HTML pages. These "data islands" are written in XML. Microsoft Internet Explorer 5 introduced <XML> tag which is used to create the Data Islands.

    A data island is an XML document that exists within an HTML page. It allows you to script against the XML document without having to load it through script or through the <OBJECT> tag. Almost anything that can be in a well-formed XML document can be inside a data island.

      External link XML Data Islands
      External link Working with XML in Internet Explorer 5

  • XML Information Set
    The purpose of XML Information Set (Infoset) is to provide a consistent set of definitions for use in other specifications that need to refer to the information in a well-formed XML document. In other words, Infoset provides a common vocabulary to describe the contents of an XML document.

      External link W3c Infoset Specifcation Page

  • XML Fragment Interchange
    XML Fragment Interchange permits part of an XML document together with additional information to be used or interchanged without the rest of the document. The document fragment must be a well balanced subset (has both start and end tags of all the outer elements) of original XML document.

      External link XML Fragment Interchange Specification

  • XMLNews
    XMLNews is a set of specifications for exchanging news and information using open Web and Industry standards. If you are a news provider, the XMLNews specifications let you target more customers and add value to news and information before it goes out the door. If you are a news distributor, either in the new Web media or in the traditional print and broadcast media, the XMLNews specifications can make it easier for you to get the news from the wire to your customers.

      External link XMLNews Technical Overview

    XML-RPC is a specification 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.

      External link XML-RPC Home Page

    XORBA or XML-CORBA Link from Rogue Wave is a web-enabling solution for CORBA-based systems. XORBA extends an ORB's capabilities to the Web by using HTTP communications and XML encoding. XORBA works with multiple ORBs, including Rogue Wave's Nouveau product, to provide a path to the Web for CORBA, COM, and RPC services. XORBA can access any service whose interface is described in IDL, even if the CORBA services being requested are behind a firewall. During design-time, you create a service description document with the help of the XORBA design tool The service description contains an XML representation of your IDL file(s).

      External link XORBA Documentation

  • XP
    The goal of XML Protocol (XP) 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.

      External link W3C XML Protocol Activity Page

  • XPath
    XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer.

      External link W3C XPath Specification Page's XPath Resource Page

  • 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 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.

      External link W3C XPointer Specification Page's XPointer Resource Page

  • XQuery
    XQuery, a query language for XML is designed to be a small, easily implementable 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. XQuery is designed to meet the first of these requirements.

    Microsoft recently announced a prototype to showcase XQuery, click here to visit the prototype Web site. The site allows you to formulate XQueries and a subset of a proposed XQuery-compatible data manipulation language and parse and execute the former, but currently only parse the later. Since it is provided via a Web site, Microsoft provides a set of predefined XML documents and disallow the use of user-specified documents for security reasons. In addition the site offers a set of compliance tests that can be used to check the syntax for the XQuery parser. Since the tests are automatically generated based on the syntax, some of the statements may not have meaningful semantics.

      External link W3C XQuery Specification Page
      External link XML Query Language Demo from Microsoft
      External link XML Query Engine from Fatdog Software

  • XSL
    eXtensible Stylesheet Language (XSL) is a language for expressing stylesheets. It consists of two parts:
    1. XSL Transformations (XSLT): a language for transforming XML documents
    2. 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.

      External link W3C XSL Specification Page's XSL Resource Page

  • XSLT
    XSL Transformations (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.

      External link W3C XSLT Specification Page's XSLT Resource Page

  • XTM
    XML Topic Maps (XTM) is an XML grammar for interchanging Web-based topic maps

      External link XTM Home Page
      External link Getting Topical

  • XUL
    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.

      External link Introduction to XUL
      External link XPToolkit for XUL

End of document. ©

  Contact Us |  | Site Guide | About PerfectXML | Advertise ©2004 All rights reserved. | Privacy