[
https://issues.apache.org/jira/browse/DAFFODIL-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640796#comment-17640796
]
Steve Lawrence commented on DAFFODIL-2752:
------------------------------------------
One potential concern is that the CLI uses the DFDL schema for schema aware
EXI, but that schema will not match the actual SAX events that would be created
with embedded XML. However, it sounds like this might not be an issue (at least
with Exificient) and will just result in a slightly bigger EXI file than if the
correct schema was used.
This could potentially be fixed if the CLI had a way to specify an additional
schema to use for EXI schema-aware. Though, I'm not really sure what such a CLI
flag for that would look like. There are also other bugs that need a feature to
provide infoset specific options (e.g. DAFFODIL-2234) so if we do add something
like this, we should consider a general approach.
Note that this isn't an issue for API users, since they would need to create
the EXIGrammar themselves, and they can make sure to use a different schema for
DFDL vs EXI schema aware.
> SAX to SAX implementation of stringAsXML feature to enable EXI to still work
> ----------------------------------------------------------------------------
>
> Key: DAFFODIL-2752
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2752
> Project: Daffodil
> Issue Type: Improvement
> Components: Performance, SAX
> Affects Versions: 3.4.0
> Reporter: Mike Beckerle
> Priority: Major
>
> The stringAsXML feature is implemented in the XML Text Infoset
> Inputter/Outputter.
> This makes it impossible to use it along with EXI as the Infoset
> representation.
> If this was done as a SAX to SAX transformation instead then it would be
> compatible with EXI.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
