XML::Edifact - an approach towards XML/EDI as a prototype in perl: Known Bugs

Previous Next Table of Contents

## 4. Known Bugs

## 4.1 Double namespace declarations

Namespace declaration was redefined in January 1999. XML::Edifact 0.30 produced `both` the old and the new declarations. XML::Edifact 0.31 droped the depreciated declartions! If you have an old browser, you may have to download XML::Edifact 0.30 and to edit the actual XML::Edifact. Search for `HERE_` and adopt the headers to your browsers preferences.

## 4.2 Stating level in Syntax identifier.

This has to be parsed. The stating level in EDIFACT speak is called charset encoding in XML speak, and its of course important if you thing about non US/UK products. See un_edifact/unsl.

## 4.3 Explicit Indication of Nesting

This has not been coded yet, as no example messsages are available to me.

## 4.4 XML::Edifact is slow!

The example real life message teleord.edi still needs about 36 seconds on a Sun3/60 running NetBSD. Even as newer computers are faster, XML::Edifact would `not` be able to handle the daily batches of large UN/EDIFACT routers like TeleOdering UK. The solution of this problem will become delayed till version 1.2, when parts of the module will be recoded in C.

Previous Next Table of Contents