Hi, Could it be you do not use the correct schema when you encode? Maybe the order of events is not following the grammar defined by the schema? I am sorry but I cannot help you - this could be cause by many different things including bug in exip code. // Rumen
Hi, 1. I do not know what is the issue - depends on the schema etc. 2. XML to EXI encoding is not supported - implementing it will not be very easy. You need to understand both XML/EXI standards and exip code base in detail. // Rumen
Hi, As you have seen exipe uses multi schemas in one file "how rule for qname.uri settings?" - Using exip requires gread deal of understanding of the EXI standard itself. If you cannot follow the exipe example then you could read the EXI spec - not the easiest thing to do unfortunately // Rumen
I am sorry I do not understand your question
You would need to preserve namespaces (i.e., include that option in the header) and also encode Namespace (NS) event after SE (start element): EventTypeClass.EVENT_NS_CLASS Check the EXI standard on that: https://www.w3.org/TR/2014/REC-exi-20140211/#encodingEvents // Rumen
Hi, Your usage of exipd looks correct - it supports multiple schema files so this should not be a problem. It could be related to the out of band options "-ops=x%-%-%-%- " that you pass - try decoding v2g_2_encode.exi using some other EXI processor with the same out of band options. If you succeed it is probably some bug or unsupported feature in exip. Best, Rumen
Hi, I understand your question as follow: you have an XML Schema File which is EXI encoded and you are trying to decode it using exip. Moreover the EXI encoded schema file has No EXI options in the header and no out-of-band options as far as you know. Answer: You cannot decode EXI stream if you do not know what options are used during encoding. Tip: Try with some other EXI decoder first. If you succeed with it then you can try with exip. Best, Rumen
Hi Francesc, There are extra requirements for the EXI encoded XSDs (XML Schemas) when used as a source for the grammar generation in exip. The fidelity option Preserve.prefixes must be set in order to decode the QNames in the value items correctly. You need to include the header in the resulting EXI stream Please have a look at "7.2 Converting XML Schema files to EXI" section of the user documentation (http://exip.sourceforge.net/exip-user-guide.pdf) Best regards, Rumen