Page 44 - GAO-02-327 Electronic Government: Challenges to Effective Adoption of the Extensible Markup Language
P. 44
Chapter 2: A Comprehensive Set of Standards
for Implementing XML Is Only Partially in
Place
describing what specific functions are available and how they can be
accessed.
RosettaNet Funded by a consortium of more than 400 companies, including
corporations such as IBM, Cisco, and Dell, RosettaNet began as an effort
to create XML standards for the IT supply chain but has expanded to
include electronic components and semiconductor manufacturing.
RosettaNet has developed three dictionaries: a business dictionary, e-
commerce dictionary, and IT technical dictionary. Its business dictionary
designates the properties used in basic business activities, and its
technical dictionaries provide the properties for defining products. In
addition, RosettaNet has developed electronic business guidelines in the
form of partner interface process specifications, which include business
models, impact and benefit analyses for implementing the business
models, technical software designs, and implementation guides.
RosettaNet has developed partner interface process specifications for
administration, product and service review, product information, order
management, inventory management, marketing information management,
service and support, and manufacturing. Even though RosettaNet
standards were designed for the electronics industry, they offer an
approach for defining and modeling business processes that others may
follow.
Based on discussions with industry experts and Web documentation, these
standards are in different stages of development and acceptance.
RosettaNet appears to be the most fully developed business standard, but
it is not endorsed by any internationally recognized standards
organization. EbXML has the advantage of the formal backing of
UN/CEFACT and OASIS, but its suite of specifications is not yet complete.
For example, the majority of ebXML’s initial efforts focused on
establishing the underlying rules for data dictionaries rather than
developing the dictionaries themselves. Development began only in
October 2001 for a common library of business documents for ebXML that
will enable trading partners to unambiguously identify and exchange
4
business information. Without these tools, data that are exchanged
between organizations may not be interpreted and validated consistently.
4
In October 2001, OASIS formed the OASIS Universal Business Language (UBL) Technical
Committee to define a common XML business document library.
Page 40 GAO-02-327 Electronic Government

