VroniPlag Wiki

This Wiki is best viewed in Firefox with Adblock plus extension.

MEHR ERFAHREN

VroniPlag Wiki
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 035 10 - Diskussion
Zuletzt bearbeitet: 2020-05-21 15:14:14 [[Benutzer:|]]
BauernOpfer, Emmelhainz 1990, Fragment, Gesichtet, SMWFragment, Schutzlevel sysop, Svr

Typus
BauernOpfer
Bearbeiter
SleepyHollow02
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 35, Zeilen: (1-3), 10-17, 30-31
Quelle: Emmelhainz 1990
Seite(n): (14), 16, 80, 89, Zeilen: (14: 31-34); 16: 5 ff.; 80: 28 ff.; 89: 5 ff.
[ ["[...] These rules] of format and syntax provide an accepted way of communicating between business and ensure that the message sent is understood upon receipt. Similar rules of format and syntax exist in the world of EDI" (Emmelhainz 1990: 14).]

[...]

This is where a standard like EDI makes sense. Standards can be either (i) proprietary or (ii) common (open). Proprietary EDI standards are limited to the use of one company and it's trading partners. These are systems in which the organizations have developed a standard format used in communication only with that organization's trading partners on a closed system. While these systems are often referred to as EDI, they do not use common EDI standards. Common EDI standards are guidelines adopted by industry-wide or cross-industry users (Emmelhainz 1990).

[...]

As explained above, EDI standards provide the structure and the common format for electronic messages. However, since no organization has its data file [structured in EDI format, some method of transforming data from a company specific format to the EDI standard format is needed. EDI software performs this function.]


Emmelhainz, M. 1990, Electronic Data Interchange: A total Management Guide. Van Nostrand Reinhold, New York.

[page 14]

[These rules of format and syntax provide an accepted way of communicating between businesses and ensure that the message sent is understood upon receipt.

Similar rules of format and syntax exist in the world of EDI.]

[page 16]

Proprietary Standards As guidelines for formatting and communication, EDI standards can be either proprietary or common. Proprietary EDI standards are formatting and communications guidelines whose use is limited to one organization and its trading partners. [...]

Common EDI Standards Common EDI standards, on the other hand, are guidelines adopted by industry-wide or cross-industry users.

[page 80]

These are systems in which the organization has developed a “standard” format used in communicating only with that organization’s trading partners on a closed system. While these types of systems are often referred to as EDI, they do not use common EDI standards as the format or method of communication.

[page 89]

As explained in Chapter 4, EDI standards provide the structure and the common format for electronic messages. However, since no organization has its data file structured in EDI format, and since manual input of data in EDI format would be tedious and time consuming, some method of transforming data from a company-specific format to the EDI standard format is needed. EDI software performs this function.

Anmerkungen

The source is mentioned twice. At the top of the page there is a passage that is correctly referenced as a literal quote (and therefore only documented here), but it is not made clear that additional passages are also extremely close to the source.

Sichter
(SleepyHollow02) Schumann


[2.] Svr/Fragment 035 20 - Diskussion
Zuletzt bearbeitet: 2020-03-02 15:24:42 [[Benutzer:|]]
BauernOpfer, Fragment, Gesichtet, Parfett 1992, SMWFragment, Schutzlevel sysop, Svr

Typus
BauernOpfer
Bearbeiter
SleepyHollow02
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 35, Zeilen: 9-10, 20-28
Quelle: Parfett 1992
Seite(n): 40, 42, Zeilen: 40: 20 ff.; 42: 6 ff.
The desirable solution for all trading partners is to agree upon common standards from converting data from and into their in-house systems.

[...]

Message refers to a specific Type of EDI dialogue, which is formed to achieve a particular trade function. Functional Groups are groups of messages of the same type, e.g. all purchase orders to one company. Interchange is the envelope that contains the message standards and functional groups thereof. Interchange forms the entirety of an EDI communication between trading partners. Syntax Rules effectively specify the grammar for EDI dialogue. Message Design Guidelines allow groups engaged in designing new messages or modifying existing messages to do so in a consistent manner, which will allow other users to understand them.

The desirable solution is for all trading partners to agree to adopt a common standard for their in-house systems, which would remove any requirement for conversion routines.

[page 42]

A message is a specific type of EDI dialogue which is formed to achieve a particular trade function. [...]

- Functional Groups.

These refer to groups of messages of the same type, eg all purchase orders to one company.

- Interchange.

The interchange forms the entirety of an EDI communication between trading partners. It is the envelope which contains the messages and functional groups thereof.

[...]

- Syntax Rules.

The syntax rules effectively specify the grammar for EDI dialogue. [...]

- Message Design Guidelines.

Message design guidelines allow groups engaged in designing new messages or modifying existing messages to do so in a consistent manner, which will allow other users to understand them.

Anmerkungen

The source is given only for a literal quote top of page that is part of the previous chapter.

Sichter
(SleepyHollow02) Schumann



vorherige Seite | zur Übersichtsseite | folgende Seite
Letzte Bearbeitung dieser Seite: durch Benutzer:Schumann, Zeitstempel: 20200221232652