E-envelope Vs EDI/XML

[smartGURL]

salam...dikepilkan bersama pos ini adalah hasil kajian smartGURL dan rakan-rakan berkaitan e-envelope (salah satu teknik penghantaran data-data sensitif dalam e-commerce)

harap ia berguna kepada sesiapa yg ingin mengetahuinya & mengkajinya lebih mendalam. Jgn lupa utk sertakan penulis kertas kerja jika diperlukan utk sebarang penulisan :). selamat membaca... O:O

[smartGURL]

Bermanfaat untuk dilawati extension dr kajian:
http://www.xmledi-group.org/xmledigroup/xmlediindex.htm

Bagaimana ia di implementasikan dlm EDI/XML:
http://www.xmledi-group.org/xmledigroup/Book.htm

[smartGURL]

well...oleh kerana kajian ni agak baru...kami akan present paper ni di UITM conferrence (Shah Alam & Perlis). kemungkinan jika available akan di bentangkan juga di Belanda oleh En. Mohd Taib selaku pensyarah kami :)

kepada sesapa (samada ahli akademik atau penyelidik )yg berminat boleh baca artikel TERBARU/TERKINI kami yg telah di 'up grade' kan dengan menghantar e-mail kepada kami untuk mendapatkan salinan....sebarang komen & pertanyaan bolehlah e-mailkan kepada kami:

Data Transmission In E-Commerce Through EDI Using Electronic Envelope Technique
( Mohd Taib Wahid, Mera Anak Branyai, Nadzirah Abd Ghani, Sarimah Raduan,Suria Firdzaus Jamil )
(taib@fsksm.utm.my, osmiera@lycos.com, nad_z6@hotmail.com, man67@tm.net.my, s_firdaus@email.com)
IS Department, Computer Science & Information Systems Faculty
University Technology of Malaysia
81310 Skudai, Johor

ABSTRACT
Electronic Data Interchange (EDI) is one of particular group of information systems call interorganisational systems that link organizations, such of customers and distributors and passing information between them. It is a set of standardized formats for different types of business documents that allow otherwise incompatible business data processing systems to exchange documents without manual intervention. The company is then able to exchange business documents electronically with any other company that supports EDI. In the environment of EDI, multiple documents can be combined in the same package, requiring additional levels of information for the “electronic envelope”. This is the electronic equivalent of a traditional paper
envelope. Two different EDI standards have evolved to be the most popular which are in the US is the American National Standards Institute (ANSI) x.12 and EDIFACT.

[smartGURL]

antara perkara penting perbandingan antara EDI & XML :


COMPARATIVE STUDY: EDI AND XML

Since EDI started, a newer technology called extensible markup language bloomed rapidly as a standard way for marking up data in a way that is idealized for transporting that data around the Internet. XML is fairly simple and has relatively few rules of grammar to observe. Its syntax is based on a language called Standardized General Markup Language (SGML). The concept is to use a ‘container’ for marking up the ‘content’. Business users can design their own set of documents for exchanging business information between end points.

EDI is usually deployed between two communication end points which transfer data using a Value Added Network (VAN) for a fee. XML was designed to flow over the internet.

XML/EDI - a comparative study chart

XML
· Easy programming
· Many-to-many integration
· Includes small/midsize-trading partners
· Requires standardization
· Web-server
· Man and machine decipherable
· Security measures being standardized
· Transacts over existing internet
· Easier to train & retain staff
EDI
· Complex programming
· Point-to-point integration
· Viable for classified partner networking
· Standardized
· Requires dedicated EDI server
· Machine decipherable
· Highly secure exchange
· High transactional cost






XML provides an ideal methodology for electronic business because:
· XML allows message type creators to clearly identify the role and syntax of each piece of interchanged data using a definition that is both machine processable and human interpretable
· XML allows message type creators to identify the source of each shared structure using an Internet Uniform Resource Locator
· XML allows message type creators to optionally identify which pieces of information should occur in each interchanged set of data and, where relevant, the order in which individual fields should occur in a particular message stream
· XML documents can be given metadata fields that can be used to identify who is responsible for creating, transmitting, receiving and processing each message, and can have built-in facilities for identifying the storage points of programs that should be used to control processes
· XML can make use of facilities provided by the latest version of the Internet HyperText Transfer Protocol (HTTP), which can identify when a message should be moved from one stage of the interchange process to another, and to check that the relevant forms of interchange have taken place.
XML can be integrated with existing EDI systems by:
· providing application-specific forms that users can complete to generate EDI messages
· generating EDI message formats for transmission between computers over the Internet, or through existing value-added networks (VANs)
· allowing data received in EDI format to be interpreted according to sets of predefined rules for display by the receiver on standardized browsers using a user-defined template, rather than having to rely on specially customized display packages.

BENEFIT OF USING E-ENVELOPE
1. It will provide a standard format for common types of data contained in widely differing styles of incoming and outgoing correspondence. This will make it possible to smoothly handle different formats from important information sources unable or unwilling to change their formats.
2. Standardization is achieved without disrupting the styles of different types of correspondence: the envelope is external to the correspondence presentation copy. Therefore, there is little, if any, need to change present styles.
3. Standardization simplifies the development of software to process and communicate a variety of correspondence and communications in different formats. Thus software development costs will be reduced.
4. This approach will automate format rules for different styles of correspondence contained in the department's correspondence handbook. This will simplify secretarial tasks, provide a more rapid and simpler method of implementing these rules, and bring more uniformity and consistency to production of final copy. In effect the correspondence handbook will support drafters and secretaries instead of their being its servants.
5. Because originators will enter basic identifying data, demands will be minimized for human resources in a central organization to reformat documents and input elements of missing data.
6. By treating the envelope and the presentation copy as an integral record, this system will provide a neutral set of information that can be more readily transferred to different systems and processed by different types of database-management software. This will give greater flexibility and longevity to the use of information.