RE: [ubl-dev] RE: [ebxml-dev] Q: minimum requirement for ebxml?

["J. Dean E. P. Hemopo" <jdeanh@ihug.co.nz>]

david,

go to my website www.archmage.org.nz (its an academics site so it is not
fancy) look under the Phoenix ebXML Registry URL and you will find the tools
i have selected for constructing ebXML services.  i will point you
specifically to Systinet 5.0 C++ Server tool that provides http: server
functionality and SOAP with Attachments functionality.  now as far as i can
see, the core functionality required is HTTP/SMTP/FTP.  i will ratify that
once i have read the spec responsible (i think the answer lies in the
Registry Service spec.

i mention this because providing multiple transport protocols is not
difficult to provide if you go digging for tools to help you along the way.
as a matter of fact, i have just downloaded systinets product as i had the
beta, it is now in full release form.  it is free, but deployed you must pay
royalties (i believe).

have fun digging,

dean hemopo
auckland, new zealand

-----Original Message-----
From: david.lyon@computergrid.net [mailto:david.lyon@computergrid.net]
Sent: Tuesday, 3 August 2004 2:09 p.m.
To: Anthony Ellis
Cc: ubl-dev@lists.oasis-open.org; ebxml-dev@lists.ebxml.org
Subject: [ubl-dev] RE: [ebxml-dev] Q: minimum requirement for ebxml?



I've been doing that. One of the packages that I'm looking at is ebMail from
Hong Kong. It looks very useable and advanced.

Maybe I need a plugin, but it seems to use smtp to transfer data. That would
be
fine as far as I can see for most SMEs.

What is your opinion on using this package for ebxml?

Quoting Anthony Ellis <anthony.ellis@redwahoo.com>:

> What do you mean by ebxmlish?
> For the app to be considered an ebxml compliant messaging service it would
> need to provide all of the 'core' functionality in the ebXML Messaging
> Service Spec.
> Easiest way to test this is to obtain one of the 'available' messaging
> service implementations on the internet and see if your app can
communicate
> with them.
>
> ANTS
>
> -----Original Message-----
> From: david.lyon@computergrid.net [mailto:david.lyon@computergrid.net]
> Sent: Tuesday, August 03, 2004 11:27 AM
> To: ubl-dev@lists.oasis-open.org; ebxml-dev@lists.ebxml.org
> Subject: [ebxml-dev] Q: minimum requirement for ebxml?
>
>
> Q: Say we have an application, and it produces UBL messages and sends them
> via SMTP. Is that ebxmlish enough to be called ebxml. My reading of the
> specs seem to suggest that it might be.
>
> If not, what other things need to be added?
>
> One thing to keep in mind is that the customers are not multi-billion
dollar
> multinationals, but SMEs. They don't have an IT department, don't know
what
> ebxml even is probably aren't that interested.
>
> I'm interested in hearing some different opinions on this. None of the
> specifications that are written really have all that much about doing
ebxml
> within a small or medium sized enterprise. They give the impression of
being
> are primarily focussed on larger organisations.
>
> One possible answer of course is that it is impossible for an sme to use
> ebxml because their business processes don't meet the requirements of
ebxml.
>
> In the first instance, I'm just interested to know if an SMTP app with UBL
> can pass as ebxml.
>
> Regards
>
> David
>
>
> -------------------------------------------------------
>
>
>
>
>




-------------------------------------------------------