Paul, thank you for pointing to XBIS and providing performance results.
I am surprised at the performance of (Fast Schema, X.694) compared to FastInfoSet - I thought run-time conversion from ASN.1 to XML and vice versa using X.694 is more processor intensive than FastInfoSet - a blind conversion from XML to ASN.1 and vice versa.
For (Fast Schema, X.694) there is no conversion from PER to XML it goes straight from PER to Java objects and skips the infoset layer. This is why you can get a 10x increase for certain schema and documents.
If (Fast Schema, X.694) was used to go from PER to XML then element/attribute/prefix/namespaces would all be hardcoded (and String interned automatically in Java, which is good for binding applications like JAXB which require this and Xerces by default interns) but content will not be indexed (as is the case for Fast Infoset). In addition the conversion of PER encoded values of integers etc to characters will affect performance if a suitable API is not available to access content as values other than characters.
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x19219
+353-1-8199219