Hi,
I'm working on an implementation of the ONIX standard
http://www.editeur.org/
(international standard for representing and communicating book
industry product information, in XML ).
The ONIX DTD
http://www.editeur.org/onix/2.1/reference/onix-international.dtd
is ambiguous; this feature results in an awkward situation when trying
to use it in XXE:
valid instances of ONIX files parse as valid and load;
invalid instances are duly recognised but the error could (ideally) be
more precisely spotted,
and editing has to be done from the whole set elements from the DTD;
inserting elements from an ambiguous sub-tree (into a valid node) is
simply impossible inside a valid file.
These elements are ignored in the edition elements list.
You can for instance try and build a second <Product> with the same
structure as the first one in the attached file: impossible to append
an <ISBN> element after <NotificationType>.
Is there a (best practice) workaround?
It would anyway be 'cool', for instance, to
1. be warned that the DTD is non-deterministic;
2. be offered the valid choices even in ambiguous nodes;
or to be able to turn off validation in such situations? :-(
Thanks, best regards,
Alain Pierrot
APSED
mailto:apsed.fr at wanadoo.fr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testONIX.xml
Type: application/text
Size: 8753 bytes
Desc: not available
Url :
http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20040610/bdf7ff3e/attachment.bin
-------------- next part --------------
