The use of ebXML Message Services for ebXML Registry

[Tim McGrath <tmcgrath@tedis.com.au>]

During the recent Quality Review of the Registry Services specification,
an issue arose which we would like to bring to the attention of the Executive
(possibly for tabling to the Steering Committee).

We would like clarification on the position of ebXML with respect to the exclusive use of TRP Message Services for all Registry Services communications.

This has been stated in both the TA and the Registry Services specifications:

> Technical Architecture v1.0 (lines 874-875) states:
> "The ebXML Messaging Service serves as the transport mechanism for
> all communications into and out of the Registry."

> Registry Services v0.83 (lines 243-244) states:
> "All interactions between the clients of the ebXML Registry and the
> ebXML Registry will be conducted using ebXML Messaging Service."
This requirement does not appear in the ebXML Requirements document. 
The QR team would like to know if the intention of ebXML is for "exclusive"
or just "mandatory" support for ebXML Message Services?
.

--
regards
tim mcgrath
TEDIS   fremantle  western australia 6160
phone: +618 93352228  fax: +618 93352142
 

begin:vcard 
n:McGrath;Tim
tel;pager:+61(0)299633829
tel;cell:+61 (0)438352228
tel;fax:+61(0)893352142
tel;work:+61(0)893352228
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:tmcgrath@tedis.com.au 
x-mozilla-cpt:;-23520
fn:tim mcgrath
end:vcard