[
https://issues.apache.org/jira/browse/DAFFODIL-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635053#comment-17635053
]
Mike Beckerle commented on DAFFODIL-2750:
-----------------------------------------
Idea: One can tell EXI from XML robustly. Maybe the CLI can auto-sense whether
an incoming unparse infoset is EXI or XML text and automatically handle it the
right way?
Maybe that would eliminate the need for the -I option (xml, exi, or exisa) for
unparsing?
I guess it depends on whether one can robustly distinguish EXI files that are
schema aware from those that are schema-unaware, because a schema-aware EXI
file would require the --schema option. A schema-unware EXI file would not.
> Add option to encode/decode EXI files
> -------------------------------------
>
> Key: DAFFODIL-2750
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2750
> Project: Daffodil
> Issue Type: New Feature
> Components: CLI
> Affects Versions: 3.4.0
> Reporter: Josh Adams
> Assignee: Josh Adams
> Priority: Major
> Fix For: 3.5.0
>
>
> It is rather cumbersome to encode/decode schema aware EXI files as they need
> access to the Daffodil XML resolver in order to import/include schemas
> correctly. Having a simple:
> "daffodil encodeEXI -s /path/to/schema /path/to/file.xml"
> to convert an XML file to an EXI file will be very helpful for testing. A
> decodeEXI command would also be added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
