You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2020/01/15 13:56:00 UTC

[jira] [Commented] (DAFFODIL-1959) EXIficient Inputter and outputter for XML EXI representation

    [ https://issues.apache.org/jira/browse/DAFFODIL-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016002#comment-17016002 ] 

Mike Beckerle commented on DAFFODIL-1959:
-----------------------------------------

Re: testing this feature - we need this to work with other EXI tools.

EXI is pointless if users can't choose to decode the EXI we create with their choice of EXI library.

There are other EXI libraries that we should probably evaluate and test against to be sure they can create infosets we can unparse, and can consume EXI streams we create from parsing.

One such commercial library is from AgileDelta.

> EXIficient Inputter and outputter for XML EXI representation
> ------------------------------------------------------------
>
>                 Key: DAFFODIL-1959
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1959
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Back End
>    Affects Versions: 2.1.0
>            Reporter: Mike Beckerle
>            Priority: Major
>              Labels: beginner
>
> Create EXI (dense binary XML) representation using an EXI-specific InfosetInputter and InfosetOutputter.
> These would be very similar to the XML InfosetInputter and Outputter - as EXI libraries such as EXIfficient https://github.com/EXIficient/exificient already have SAX/StAX, APIs, etc. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)