Assessing the Impact of XML/EDI with Real Option Valuation

von Dr. Shermin Voshmgir

vorherige Seite | zur Übersichtsseite | folgende Seite

Statistik und Sichtungsnachweis dieser Seite findet sich am Artikelende

[1.] Svr/Fragment 063 01 - Diskussion
Zuletzt bearbeitet: 2020-03-20 23:25:06 [[Benutzer:|]]
Fragment, Gesichtet, Norman 1999, SMWFragment, Schutzlevel sysop, Svr, Verschleierung

Typus
Verschleierung
Bearbeiter
Schumann
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 63, Zeilen: 1 ff. (completely)
Quelle: Norman 1999
Seite(n): 46, 47, 48, Zeilen: 46: 18 ff.; 47: 28 ff.; 48: 1 ff., 8 ff., 14 f.
[Perhaps the retailer's accounting software is tailored to] Internet commerce, and already uses XML formats. In this case, there are utilities for converting one data type definition (DTD) to another, and a generic tool accomplishes the conversion to EDI. The resulting transmission would certainly be more comprehensible to humans, and perhaps even feasible for an employee with a text editor or XML editor to generate. An example of how the sample purchase order might look in an XML rendering of X12 is given in Figure 13. This example is based on the ongoing work of the XML/EDI group. One disadvantage with using XML, as can be seen below, is that the size of the EDI messages gets a lot bigger than the X12 messages. In this example, the XML message is about 8 times bigger than the X12 message.

The idea of XML repositories is to provide a means for industries to store the document-type definitions, that identify the data elements and their relationships exchanged among parties doing business electronically, on the Internet. Repositories contain logic components, such as Java applets, template scripts, forms and object definitions needed to process message components. With common registration procedures for these components, repositories will act as global libraries, and enable industry groups, government agencies, and businesses of all sizes to make their preferred message formats widely available to current and potential trading partners. The intent of the Global Repository is to be a dynamic mechanism that responds through an open Application Programming Interface (API). It is anticipated that fully functional global repositories will evolve in phases:

Phase 1 Limited Intranet implementation, proof of concept, with manual Web interface.

Phase 2 Definition of basic API allows extranet implementations between specific partners.

Phase 3 Definition of full API and available repository products allows full implementations.

Phase 4 DNS style service established and standards bodies adopt support for API and long-term maintenance and alignment.

[page 46]

Perhaps the retailer’s accounting software is tailored to Internet commerce, and already uses XML formats. In this case, there are utilities for converting one data type definition (DTD) to another, and the conversion to EDI might be accomplished by a generic tool. The resulting transmission would certainly be more comprehensible to humans, and perhaps even feasible for an employee with a text editor or XML editor to generate. An example of how the sample purchase order might look in an XML rendering of X12 is given in Listing 3. This example is based on the ongoing work of the XML/EDI group. One disadvantage with using XML, as can be seen below, is that the size of the EDI messages gets a lot bigger than the X12 messages. In this example, the XML message is about 8 times bigger than the X12 message.

[page 47]

XML repositories will provide a means for industries to store on the World Wide Web the document-type definitions that identify the data elements and their relationships exchanged among parties doing business electronically. Repositories will also contain logic components, such as Java applets, template scripts, forms and object definitions needed to process message components.

[page 48]

With common registration procedures for these components, repositories will act as global libraries, and enable industry groups, government agencies, and businesses of all sizes to make their preferred message formats widely available to current and potential trading partners.

[...]

It is anticipated that fully functional global repositories will evolve in phases:

· Phase 1 - Limited Intranet implementation, proof of concept, with manual Web interface.

· Phase 2 - Definition of basic API allows Extranet implementations between specific partners.

· Phase 3 - Definition of full API and available repository products allows full implementations.

· Phase 4 - DNS style service established and standards bodies adopt support for API and long term maintenance and alignment.

[...]

The intent of the Global Repository is to be a dynamic mechanism that responds through an open Application Programming Interface (API).

Anmerkungen

The source is not given.

Sichter
(Schumann), SleepyHollow02



vorherige Seite | zur Übersichtsseite | folgende Seite
Letzte Bearbeitung dieser Seite: durch Benutzer:Schumann, Zeitstempel: 20200320232545
Nutzung von Community-Inhalten gemäß CC-BY-SA, sofern nicht anders angegeben.
… weitere Daten zur Seite „Svr/063
Schumann +
(Schumann) +  und SleepyHollow02 +