UDDI as the registry for ebXML components: Typo?

["Chiusano Joseph" <chiusano_joseph@bah.com>]

In the UDDI Technical Note "UDDI as the registry for ebXML components"
[1], the Problem statement (p.3) states:

"This introduces significant concerns of cost and manageability, because
ebXML and Web services impose separate infrastructure requirements and
platform components."

Is this entirely accurate, given that one can register and maintain Web
services in an ebXML Registry? The entire Problem statement is
reproduced below. I wonder if this is a typo.

Joe

1.1 Problem statement
Multiple consortia have initiated pilot projects using the ebXML
framework for business-to-business transactions, while corporations have
also begun adopting ebXML technologies for internal use. At the same
time Web service technologies, which have significant momentum due to
unprecedented industry support, are also being rolled out. This
introduces significant concerns of cost and manageability, because ebXML
and Web services impose separate infrastructure requirements and
platform components.

As a universal technology for publication and discovery of service
metadata, UDDI allows the bridging of the two infrastructures by
accommodating metadata registrations for Web services as well as ebXML
framework components, enabling interoperability among trading partners
using ebXML or Web services. However, a prescribed methodology of
modeling services and components which are conformant to ebXML
specifications is required to make interoperable solutions possible.

[1]
http://www.oasis-open.org/committees/uddi-spec/doc/draft/uddi-spec-tc-tn-uddi-ebxml-20030508.htm
begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard