Home ยป B2B eCommerce

Paragraph on B2B eCommerce

In B2B eCommerce, companies exchange electronic business documents (orders, checks, etc. ) and information through Internet frequently between each other. If there is not a common data format for companies to define their data, the exchanges are quite difficult and inefficient. Each company may organise and store data in vastly different styles and formats. It is hard for systems to recognise the information and exchange them with each order.

The others may miss part of the information, or misunderstand the meaning of the documents. Translation software can be used to convert the documents to machine-read formats, and than back to the formats the others prefer. EDI (Electronic Data Interchange) contains this kind translation software, and transfer data over a proprietary network (Kahl and Thomas, 2000). The expenditure of it is high, and it still needs standards in the network.

Without a common data format, it will cost the company a lot of unnecessary money, time and labour. Therefore, the common data format is essential. XML has made the data exchange possible. XML (EXtensible Markup Language) is an extension of the World Wide Web Consortium’s (W3C) Standard Generalized Markup Language, SGML (Greenstein and Vasarhelyi, 2002). Bert Box of the W3C explains that XML is a method for putting structured data in a text file.

XML is a set of rules, guidelines, conventions, whatever you want to call them, for designing text formats for such data, in a way that produces files that are easy to generate and read (by a computer), that are unambiguous, and that avoid common pitfalls, such as lack of extensibility, lack of support for internationalization/localization, and platform dependency (Greenstein and Vasarhelyi, 2002).

The ASC X12 is actively using XML in EDI applications because of its relative ease to translation. XML/EDI provides a standard framework to exchange different kinds of data. The combination of them will benefit companies more (Greenstein and Vasarhelyi, 2002).

References:

Baird, W. (2006). Business Ethics, Privacy and Trust. WMG.

Benatallah, B. (2002). Overview of some patterns for architecting and managing composite web services. ACM SIGecom Exchanges, 3(3), pp. 9-16

Booth, D. et al. (2004). Web Services Architecture. [Online]. (URL http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/). (Accessed 21 July 2006)

Carey, M., et al. (2001). Towards a scalable infrastructure for advanced e-services. Bulletin of the Technical Committee on Data Engineering, 24(1), pp.12-18

Curbera, F. et al. (2002). Unraveling the Web services web: an introduction to SOAP, WSDL, and UDDI. IEEE Internet Computer, 6(2), pp. 86-93

Gottschalk, K. et al. (2002). Introduction to Web Services Architecture. IBM System Journal, 41(2). [Online]. (URL http://researchweb.watson.ibm.com/journal/sj/412/gottschalk.html). (Accessed 21 July 2006).

Gould, J.W. (2006). E-Commerce Security. WMG.

Greenstein, M. and Vasarhelyi, M. (2002). Electronic Commerce: Security, Risk Management, and Control. 2nd ed. New York, London: McGraw – Hill.