Hi all,
I'm looking into integrating Apache Daffodil into our product and have
several questions for which I could not find answers in the
documentation or issues.

1. Is it currently possible to extend Daffodil with custom types? For
example, could I create a custom field type for a field compressed with
a custom compression and have Daffodil call my own code for further
parsing of the original field value?
2. The DFDL spec states that additional implementation-defined encoding
names can be defined. How would a custom encoding be defined in the
DFDL specification?
3. Is it currently possible to parse a input stream but output only a
set of field from the specification? For example, could an XPath be
specified to determine which nodes in the specification Daffodil will
output?
4. Is there a recommended way of dynamically creating a DFDL
specification XSD? or should I just use general tooling?

Any pointers and help would be much appreciated.
Thanks!

Roded

Reply via email to