A while ago we (i.e. the developers where I work) thought we would need ebXML to talk to other people in the industry as the XML standard the industry was using apparently used it, now it seems nobody is actually using the XML standard itself for what we need to do, and that it may or may not use ebXML.
With this in mind I am looking to open source the ebXML code we have already written that can ping the Hermes ebXML MSH succesfully, and nearly talk to it with test requests, but still with some bugs to sort out.
I am hoping we can continue putting in some work on the code when time allows and find other interested parties to contribute some developer time and testsing.
So anybody who interested in setting up a website and/or mailing list and CVS should contact me, and we can start getting people involved.
Hopefully I can find the time in the next few weeks to remove anything proprietary, and release what we have to CPAN. Namespace anyone? XML::ebXML or ebXML ?
especially as it is heavily used in governmental and medical circles.
I will probably just use the ebXML namespace, SOAP does - maybe follow that route and put it in ebXML::Lite or something in case somebody else wants to use ebXML::FullyCompliant, etc.
