Panos,
See comments below.
Panos Georgatsos wrote:
<snip>
> My understanding from reading the ebXML specifications (please correct me if I
> am wrong) is that the two parties exchanging messages are assumed to be servlets
> at known URLs. Therefore, reliable message transfer between
> 'only-Web-browsing-enabled' customers and a server is not cosidered by ebXML
> specs. For this, I said that ebXML is suitable for business-to-business type of
> communication and not so much for customer-to-provider type of communication.
> One might think that in the latter case, reliability is not the issue; however,
> in the case of service negotiation, reliability in message transfer is
> essential, I think.
>
> As I understand it, ebXML is not yet cast in stone, so is it not technically
Is ebXML support part of the charter? As far as I know, it is not.
Not that I am against ebXML, I think it is good initiative. The
thing is if we tie ourselves with ebXML and the standardization
of it takes longer than expected, how would that help SLS?
Also, it may be the case that some vendors see less value in
supporting ebXML but they want to support SLS. For that, I
think the SLS should be as independent from ebXML as possible
but that should not preclude the need for integrating with
ebXML in the foreseeable future.
my 2 cents
regards
Abdallah
This archive was generated by hypermail 2b29 : Tue Apr 10 2001 - 15:58:37 CEST