Table of Contents
| Pt. I | Executive Overview of ebXML | 1 |
| 1 | There's No Business Like E-Business | 3 |
| 2 | ebXML in a Nutshell | 47 |
| 3 | ebXML at Work | 77 |
| Pt. II | ebXML Background and Details | 101 |
| 4 | The Promise of XML | 103 |
| 5 | The Road Toward ebXML | 137 |
| 6 | Business Requirements for ebXML | 171 |
| 7 | ebXML and Similar Web Services Specifications | 195 |
| 8 | ebXML Technical Architecture | 219 |
| 9 | Moving from Theory to Practice | 281 |
| Pt. III | Learning More About ebXML | 295 |
| A: Acronyms | 297 |
| B: References | 305 |
| Index | 313 |
Forewords & Introductions
Preface
With this book, Alan Kotok and David Webber have made an important contribution to the understanding of ebXML from both a managerial and technical perspective. ebXML holds great promise for helping to facilitate global e-business for small and large players alike. It may well be the solution the EC community has been seeking for some time.
Traditional EDI has worked well for more than 30 years. In particular, it has worked well for the large hub companies who often coerced their smaller suppliers (known as "spokes") into using EDI if they wanted to keep the hubs as customers. For the hubs, EDI was faster, cheaper, and more accurate than exchanging paper business documents. It proved to be essential for supporting such supply chain partnerships as just in Time manufacturing; Quick Response; and Collaborative Planning, Forecasting, and Replenishment. As evidence of its value, some 95% of the Fortune 1000 companies in the U.S. use EDI. On the other hand, as evidence that small and medium-sized enterprises (SMEs) used it only because of the hubs' insistence, only about 2% of SMEs are traditional EDI users. Traditional EDI can be complicated to set up and administer, and, as practitioners well know, EDI standards are standard in name only.
For some time, the search has been on for a "new EDI," a method of exchanging standard business documents that would be simple and cheap enough that the benefits of EDI would be opened up to large and small companies alike, no matter where in the world they were located.The vision of the new solution was one in which the intelligence needed to interpret electronic business documents could be somehow encapsulated with the documents themselves.This would permit a company to create an electronic purchase order, for example, and send it over the Internet to a company it had never done business with before, and have that purchase order be interpreted and processed at the receiving end. Many schemes have been advanced. Alan and David review most of them in their book. Indeed, they were personally involved with some of the research efforts, as was our Center.
In 1999, for example, one of our graduate students, Rene Kasan, developed a prototype operating environment for XML/EDI under the aegis of the XML/edi Group. David was one of our external advisors on the project. Some elements of that work were carried forward to the ebXML Registry and Repository specifications.
As of this writing, there seems to be a consensus building around ebXML as being the most promising of the candidate solutions. The web site, ebXML.org, describes it as follows:
(A) set of specifications that together enable a modular electronic business framework. The vision of ebXML is to enable a global electronic marketplace where enterprises of any size and in any geographical location can meet and conduct business with each other through the exchange of XML based messages. ebXML is a joint initiative of the United Nations (UN/CEFACT) and OASIS, developed with global participation for global usage.
As with any emerging technology, practitioners need to ask themselves whether ebXML will become a viable option.They also need to determine whether now is the right time to make an investment in learning more about it, developing a pilot installation, and perhaps even becoming involved in the collective effort to help bring it into widespread usage. These are important questions, and this book provides answers.
ebXML could be exactly what the EC community has been waiting for. Alan and David explain it in very clear terms and position it for the reader in its proper historical and technical context. They give us a much-needed platform of understanding of the potential benefits that ebXML can bring to global e-business: a consistent pathway openly supported by the leading vendors in the field.
-Donald j. McCubbrey, Ph.D.
Director, Center for the Study of Electronic Commerce
Daniels College of Business
University of Denver
Denver, Colorado, USA
Read an Excerpt
Chapter 4: The Promise of XML
With this chapter, we begin discussing ebXML's
background and underlying technology, starting with
the
Extensible Markup Language (XML). We will provide
an overview of XML technologies, and discuss
various features related to e-business, as well as its
limitations for business purposes.This chapter is
mostly technical in nature, to explain the raw technology
itself and how the various components relate
together. Our goal is to provide the reader enough of
a sense of XML so that its overall use for business is
clarified.The reader should view this chapter as a
roadmap to the salient features of XML itself; however,
it is not intended to be a tutorial in XML syntax.
What Is XML?
XML makes possible the entire idea of using the
World Wide Web and the Internet for exchanging
business messages. XML is a generic markup language,
which means that it provides instructions that only
define the message or document content, not how
that content is displayed or printed. For example, the
instructions can say, "This block of text contains a
business shipping address."
By focusing on the content and detailing the precise
business context, XML makes it possible for systems
in remote locations to exchange and interpret such
documents without human intervention. This ability to automatically send, retrieve, interpret, transform,
and process the data in electronic messages is of
course critical to the conduct of electronic business
itself.
The World Wide Web Consortium (W3C) developed
XML in 1996–97, and officially released version 1.0
in February 1998.1 While XML is widely recognized
as a technology and the W3C is a highly respected
organization, drawing its membership from both
major software vendors and academic institutions, the
W3C chooses to call its fully approved technical
documents recommendations rather than standards, to
avoid anti-competitive lawsuits in the U.S.
Recommendations represent a consensus within the
W3C as well as the approval of the W3C director,
now Tim Berners-Lee. As recommendations, documents
such as the XML specifications demonstrate
stability and are considered ready for widespread
implementation and business use.2
Markup: Seeing Is Believing
The World Wide Web emerged as a common communications
medium once the
Hypertext Markup
Language (HTML) became available in the early
1990s.
3 HTML is also a recommendation of the
W3C (the latest version is 4.01, December 1999),
and now there is also an XHTML recommendation
(February 2001). HTML provides a good example of
a markup language in wide use, and makes a convincing
case study for the importance of consistent
standards.
You can see HTML markup by opening any web
page with Internet Explorer or Netscape
Communicator. Using the top-level menu in the
browser, select View, Source (Internet Explorer) or
View, Page Source (Netscape).What you see displayed
is the internal HTML syntax that the browser
uses to render the page content you see onscreen.
The familiar web page with its human-readable text
and images are exposed as machine-readable computer
markup code. Notice that the code contains a lot
of instructions in angle brackets, such as <HTML>,
<BODY>, <HEAD>, <TITLE>, <TABLE>, and so on. (See
Listing 4.1 for an example.)
Enclosing the syntax text within angle brackets creates
a tag or element. Close to the top of the web
page's HTML markup source is the tag <HTML>. This
tag tells the web browser that the page is coded in
HTML; the web browser responds by displaying the
information as directed by the rest of the tags on the
page. At the bottom of the page is a similar tag,
</HTML>. The slash after the opening angle bracket in
the tag tells the browser that it has reached the end
of the HTML page. The <HTML>tag is called an open
tag, and the </HTML>tag is a close tag. The markup also
contains other tag pairs: <HEAD>and </HEAD>, <TITLE>
and </TITLE>, <BODY>and </BODY>. These tags define
parts and functions of the HTML document.
Listing 4.1 Sample of HTML Markup
<HTML>
<HEAD>
<TITLE>Dynamiks Research Center News
Homepage</TITLE>
<meta http-equiv="Content-Type"
content="text/html;charset=iso-8859-1">
<meta name="keywords "content="press releases,
wind tunnels,aerospace".>
</HEAD>
<BODY bgcolor="#FFFFFF">
<TABLE width="100%"border="0" cellpadding="0"
cellspacing="0">
</TABLE>
</BODY>
</HTML>
The power of HTML is that it's very simple to use, as
the HTML software excuses most obvious mistakes
by human editors—unclosed tags, orphaned tags,
mistyped tags—by always displaying something, not
just a blank page. This leads to very complex HTML
software, but ease of use for content creators. HTML
has a fixed set of markup tags and most HTML software
readily understands such commonly used tags.
Because HTML is a standard more or less recognized
by the browser manufacturers,4 millions of people
and companies worldwide have found new and innovative
ways of communicating over the web—and in
many cases doing good business—without worrying
about too many technical details....