[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[jira] [Closed] (DAFFODIL-1734) base64 encoding and other preprocessing

     [ https://issues.apache.org/jira/browse/DAFFODIL-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Thompson closed DAFFODIL-1734.

Pulled latest updates from incubator-daffodil repository which included specified commit, 1ea2290f28e9ede344cb7d8d06f38a7fe818dfc3.

Verified daffodil successfully builds and executes all sbt tests, including the related test cases.

> base64 encoding and other preprocessing
> ---------------------------------------
>                 Key: DAFFODIL-1734
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1734
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: DFDL Language
>            Reporter: Michael Beckerle
>            Assignee: Michael Beckerle
>            Priority: Major
>             Fix For: 2.2.0
> Many formats have payloads that are embedded base64-encoded data.
> We need a DFDL language feature enabling us to specify that the underlying bytes of an element are base64 encoded. That is, the data stream is base64 encoded, and must be decoded and then parsed, or unparsed and then encoded into base64 text.
> A similar preprocessing should handle compression, as formats like VMF (mil-std-6017) can have compressed payloads.
> In general, we should enable these pre-processing encoder/decoders to be pluggable so the set can be extended easily. 
> This is a form of layering. If we consider just parsing for a moment, this enables one to define an element which is a byte-array or string, and then treat that as the input source for subsequent parsing without having to explicitly do a second pass of calling daffodil to parse the element. You can get Daffodil to do this second pass itself automatically.

This message was sent by Atlassian JIRA