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 060 02 - Diskussion
Zuletzt bearbeitet: 2020-02-04 23:50:37 [[Benutzer:|]]
Fragment, Gesichtet, Johnson 1999, SMWFragment, Schutzlevel sysop, Svr, Verschleierung

Typus
Verschleierung
Bearbeiter
Klgn
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 60, Zeilen: 2-6
Quelle: Johnson 1999
Seite(n): 80, Zeilen: third col. 5 ff.; right col. 6 f.
Overall response time of XML applications slows as the data store grows larger. Object databases, which store XML content, are not as highly tuned as standard SQLbased relational database management systems. Using XML is not necessarily proven in terms of performance. Many believe that these problems will disappear as XML settles in. Then, too, says Klein, overall response time of XML applications slows as the data store grows larger. Object databases, which store XML content, aren’t as highly tuned as standard SQL-based relational database management systems. “Using XML is not necessarily proven in terms of performance,” he says. [...]

Most say these problems will disappear as XML settles in.

Anmerkungen

No source is given.

Sichter
(Klgn) Schumann


[2.] Svr/Fragment 060 07 - Diskussion
Zuletzt bearbeitet: 2020-03-18 21:15:35 [[Benutzer:|]]
Fragment, Gesichtet, KomplettPlagiat, Norman 1999, SMWFragment, Schutzlevel sysop, Svr

Typus
KomplettPlagiat
Bearbeiter
Schumann
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 60, Zeilen: 7-19, 27-32
Quelle: Norman 1999
Seite(n): 44, 47, 48, Zeilen: 44: 7 ff.; 47: 2 ff.; 48: last paragraph
The XML/EDI groups are working to define XML namespaces and DTDs equal to the EDIFACT standard to support commercial usage of EDI over XML. Even though most organizations agree that EDI using XML is a good idea some are still skeptical. This is due to the fact that they think that EDI is too complex to be dealt with easily. In the health care industry alone, there are 400 different formats for a claim. One of the key issues will be how compatible the new implementations of EDI will be to the old ones; currently there is no answer to this question.

Furthermore a big debate is going on between the different XML/EDI groups on what the structure of the XML tags should be. Some advocate the use of the full description in the tag and others the use of the ANSI element number as the tag name. Others want to use a unique number that would include the standard version of the directory, the segment it resides in and the data-element it represents.

[...]

[4.4. XML/EDI Example]

EDI is quite different from sending electronic mail messages or sharing files through a network, a modem, or a bulletin board. The straight transfer of computer files requires that the computer applications of both the sender and receiver (referred to as "trading partners") agree upon the format of the document. The sender must use an application that creates a file format identical to the receiver’s computer application.

[page 48]

The XML/EDI group [1] is working to define XML namespaces and DTDs equal to the EDIFACT standard to support commercial usage of EDI over XML. Even though most organizations agree that EDI using XML is a good idea some are still skeptical. This is due to the fact that they think that EDI is too complex to be dealt with easily. In the health care industry alone, there are 400 different formats for a claim. One of the key issues will be how compatible the new implementations of EDI will be to the old ones; currently there is no answer to this question.

[page 47]

Currently a big debate is going on between the different XML-EDI groups on what the structure of the XML tags should be. Some advocate the use of the full description in the tag and others the use of the ANSI element number as the tag name. Others want to use a unique number that would include the standard version of the directory, the segment it resides in and the data-element it represents.

[page 44]

EDI is quite different from sending electronic mail messages or sharing files through a network, a modem, or a bulletin board. The straight transfer of computer files requires that the computer applications of both the sender and receiver (referred to as "trading partners") agree upon the format of the document. The sender must use an application that creates a file format identical to the receiver’s computer application.

Anmerkungen

The source is not given.

Sichter
(Schumann), WiseWoman


[3.] Svr/Fragment 060 22 - Diskussion
Zuletzt bearbeitet: 2020-01-22 21:51:02 [[Benutzer:|]]
BauernOpfer, Dumbill 2001, Fragment, Gesichtet, SMWFragment, Schutzlevel sysop, Svr

Typus
BauernOpfer
Bearbeiter
SleepyHollow02
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 60, Zeilen: 22-25
Quelle: Dumbill 2001
Seite(n): online, Zeilen: 0
[Concerning the current developments in the ebXML area: “None of the vendors quite knows where we are running to, but they are running faster and harder than before to get there before their rivals” (Dumbill 2001).] Vendors claim to be cooperating on specifications, but compete on implementations. Despite vendor assurance, it seems plain that the race to compete on implementation puts the viability of multivendor institutions at risk.

Dumbill, E. 2001, XML hype down but not out in New York [Online]. Available: http://www.xml.com/lpt/a/2001/04/11/xmldevcon.html
Accessed: April 12, 2001

None of the vendors quite knows where we're running to, but they're running faster and harder than before to get there before their rivals. IBM, Microsoft, and Sun's latest mantra is to "cooperate on specifications, but compete on implementations"; and competing they are. [...]

Despite vendor assurances, it seems plain that the race to compete on implementation puts the viability of multivendor institutions like OASIS at risk.

Anmerkungen

The source is given for literal quote, but is not made clear that the copying continues after the reference.

Sichter
(SleepyHollow02) Schumann



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