Current step is the reverse engineering of a document type definition for the original EDI standard draft. Stabilisation by disscussion and consens about features introduced with 0.5. Portability across networks using SAX may be one concern. This release will try on a smarter DTD called EdiLean. Its important for me that authentication and authorisation will be provided before I call it final 1.0.
Most messages contain viable information for running a bussiness.
Only cryptography on a document level would preserve authentication and authorisation once a message stored on a disk. The beauty of this aproach is, that the secure document is still wellformed and valid of the same document type. I hope that any consens have been found on that road, so the DTDs wont change in further releases. Perl is a perfect language for prototyping, but profiling and using a low level language like C for hot spots, will be necessary to handle large batches. The same is with the text tables produced during Bootstrap.