Re: The use of ebXML Message Services for ebXML Registry

[duane <duane@xmlglobal.com>]

Yesd - this was resolved.  It is not required to use ebXML trp for
Registry communications

Duane

> "Munter, Joel D" wrote:
> 
> Was this question/issue ever resolved?
> Joel
> 
> -----Original Message-----
> From: Tim McGrath [mailto:tmcgrath@tedis.com.au]
> Sent: Thursday, January 25, 2001 11:14 PM
> To: Bob Sutor; Bill Smith; Ray Walker; knaujok@home.com; 'ebXML
> Coordination'
> Subject: The use of ebXML Message Services for ebXML Registry
> 
> 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
>