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

Glossary


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

XML | SOAP | DOM | WAP
XSLT | XPath | SAX
UDDI | VoiceXML
Base64

New Glossary Words

eCX | XBRL | XQuery




Glossary
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

E

  • ebXML
    ebXML is a joint initiative of the United Nations (UN/CEFACT) and OASIS, developed with global participation for global usage. It 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.

      External link ebXML Web site

  • eCX
    Electronic Catalog XML (eCX) is a data type definition (DTD) that provides a method for electronic catalog interoperability. It is unique because it deals with the difficult problem of dynamic categorization and attributes in electronic catalogs. It also provides a method to "inform" a catalog loading software of actions to take to update a catalog's structure and product information. eCX was developed in the fall of 1998 to address the problem of exchanging product information and catalog structure between different catalog systems. It was developed by Requisite Technology and is used by Requisite and its partners for catalog interoperability.

      External link eCX Web site
      External link Requisite.com

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

      External link XML-EDI Web site

  • E-speak
    E-speak is HP's open software platform for the creation of dynamic, intelligent e-services. E-speak provides dynamic discovery and interaction capabilities. E-speak consists of a Service Framework specification, a set of technical and business conventions based on XML, registry software which allows advertising and dynamic discovery of e-services, and Service Engine which provides the deployment environment for e-services.

      External link http://e-speak.hp.com
      External link http://www.e-speak.net



f

G

H

  • HDML
    Handheld Device Markup Language (HDML) is a language that allows the text portions of Web pages to be presented on cellular telephone and personal digital assistants (PDA) via wireless access. Developed by Unwired Planet, HDML is an open language offered royalty-free. One major difference between HDML and WML is that WML is XML-based, while HDML is not. Another difference between HDML and WML is that HDML does not allow scripting, while WML allows it's own version of JavaScript, called WMLScript. Unwired Planet has changed their name to Phone.com.

      External link Introduction to HDML
      External link Introduction to HDML and ASP



I

  • ICE
    Information & Content Exchange (ICE) is an XML vocabulary that provides an exchange protocol for content on the Web. ICE defines the roles and responsibilities of syndicators (data providers) and subscribers (data consumers). While ICE was initially developed to support commercial publishing applications on the Web, it is expected to prove useful in automating content exchange and reuse in both traditional publishing environments and in business-to-business relationships.

      External link The Information and Content Exchange (ICE) Protocol Specification

J

  • JAXP
    The JAVA API for XML Processing (JAXP) provides 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.

      External link Java Technology and XML

  • JNLP
    Java Network Launching Protocol and API is a specification of protocols and APIs that will enable Java applications to be deployed on the Web. An implementation of this specification will support Web deployed applications by enabling distributing an application on a Web server and launching the application from any Web browser. The JNLP file is an XML document.

      External link Java WebStart

  • 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. A retail chain, for example, could use jUDDI to discover services for its online catalog and then register itself as another service. Using jUDDI, the catalog could discover a service that will ship parcels and perhaps another company's payment web service, creating a web-based store. That store could then also be registered as a web service with UDDI and be "discovered" by other UDDI clients. Companies will eventually create many connections like this, spawning business webs or dynamic collections of on-line businesses, on a massive scale. Bowstreet developed jUDDI as one of the industry's first implementations of UDDI.

      External link jUDDI Web site



K

L

M

  • MathML
    MathML is an application of XML designed to facilitate the use of mathematical expressions in Web pages.

      External link MathML Specification
      External link W3c's Math home page

  • MSXML
    MSXML or MSXML3 is a XML Parser from Microsoft. MSXML3 also implements XSLT, XPath, SAX2 and has very good DOM and namespaces support.

      External link Microsoft MSXML Web site



N

  • .NET
    NET is Microsoft's strategy for delivering software as a service.

      External link Microsoft's .NET web site
      External link MSDN .NET FAQ

  • .NET Framework
    The .NET Framework is an environment 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.

      External link GotDotNet

  • Namespaces
    XML Namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references. XML Namespaces are the solution to the problem of ambiguity and name collisions.

      External link Namespaces in XML

  • NASSL
    Network Accessable Service Specification Language (NASSL) is an Interface Definition Language (IDL), based on XML, that describes the interfaces necessary to access a service. NASSL does not describe the service itself; that responsibility is left to the WDS.

      External link NASSL and WDS



O

  • OPML
    Outline Processor Markup Language, or OPML, is an XML-based format that allows exchange of outline-structured information between applications running on different operating systems and environments.

    Outlines can be used for specifications, legal briefs, product plans, presentations, screenplays, directories, diaries, discussion groups, chat systems and stories. Outliners are programs that allow you to read, edit and reorganize outlines.
      External link OMPL Web site

P

  • Parser
    An XML parser is a processor that reads an XML document and determines the structure and properties of the data. If the parser goes beyond the XML rules for well-formedness and validates the document against an XML DTD, the parser is said to be a "validating" parser.
    List of available Parsers

  • PPML
    PPML (Personalized Print Markup Language) is a brand-new XML-based industry standard printer language for variable data printing defined by PODi, an industry-wide consortium of 13 companies.

    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.

      External link PODi Web site

      External link Introduction to PPML This is a PDF Document

      External link PPML FAQ This is a PDF Document

Q

R

  • RDF
    The Resource Description Framework (RDF) is a general framework for how to describe any Internet resource such as a Web site and its content. An RDF description (such descriptions are often referred to as metadata, or "data about data") can include the authors of the resource, date of creation or updating, the organization of the pages on a site (the sitemap), information that describes content in terms of audience or content rating, key words for search engine data collection, subject categories, and so forth.

      External link RDF Specification

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

      External link Develop a Web Service: Up and Running with the SOAP Toolkit for Visual Studio



Next Page

 

  Contact Us | E-mail Us | Site Guide | About PerfectXML | Advertise ©2004 perfectxml.com. All rights reserved. | Privacy