XML/EDI Components

The XML/EDI specific components are built on top of existing standards for transmitting and processing XML encoded data. These standards define shared features such as:

the standard Internet file storage/naming and data transport mechanisms
file and message transfer formats
the syntax of data coded in XIVIL
the way in which XIVIL files can be validated by an XIVIL parser or document object model generator
the way in which XSL presentation and data evaluation scripts can be associated with parsed objects
the use of rules and data management robots to manage application and repository interfaces.

XIVIL parsers, document browsers, page markup programs and related software functions are available of the shelf today. XML/EDI isn't, therefore, a new standard; it simply provides a framework for using existing standards to tackle existing problems in a new way.

XML/EDI specific components will either manifest themselves as built in components into existing products, plug in programs to existing tools or standalone applications. It is anticipated that new applications will be created from the spark of XML/EDI implementation.

Types of applications

The following examples of the type of facilities that could be built into an XML/EDI implementation is not comprehensive, but a starting place for discussion:

Lexicon Repositories (holding EDIFACT, X12, or BSI dictionaries, DTDs and common business objects)

XML/EDI Data Manipulation Agents (DataBots) which enable rule driven processing

XML/EDI Business Objects (predefined object processors identified by XSL scripts)

XML/EDItors used for the creation and completion of form based EDI messages XML/EDI extensions for message stores

Search Agents which recognize XML/EDI specific tagging and are able to request data from both private and public message stores (e.g. through Web interfacing)

Trading Partner Pages extensions of "yellow pages", but with verified integrity of characteristics.

Domain Name Search