[
https://issues.apache.org/jira/browse/DAFFODIL-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391651#comment-16391651
]
Michael Beckerle commented on DAFFODIL-1915:
--------------------------------------------
Ah, I forgot.
Much of the implementation is in place for encodingErrorPolicy='error'. in
ByteBufferDataInputStream. But as you point out, since it isn't exercised in
tests the front end rejects encodingErrorPolicy='error' with a
not-yet-implemented SDE.
This is going to be a stumbling block for portability/interoperability with IBM
DFDL, as their implementation does not implement 'replace', only 'error', which
means no schema can be portable if it specifies encodingErrorPolicy. Portable
schemas must not be specifying this property. Since this property was added
fairly late in the DFDL spec development, and there were already existing
implementations (IBM's), this property has a default value and doesn't have to
be specified for Daffodil nor IBM DFDL. This was to prevent breaking working
schemas by requiring a new property be added to all of them.
So at the moment I think portable schemas can't specify this property. Then
Daffodil can take its default, and IBM DFDL can take its default, and so long
as the functioning of the schema is insensitive to this detail, it will be
portable.
I will raise priority of DAFFODIL-935, which is to fix this and implement
'error' for EEP.
> DFDLGeneralFormat - add missing properties to improve portability with IBM
> --------------------------------------------------------------------------
>
> Key: DAFFODIL-1915
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1915
> Project: Daffodil
> Issue Type: Bug
> Components: Front End
> Affects Versions: 2.1.0
> Reporter: Michael Beckerle
> Priority: Major
> Fix For: 2.1.0
>
>
> Steve Hanson of IBM tested some of our schemas on github DFDLSchemas for
> compatibility with IBM DFDL.
> He tested QuasiXML and CSV.
> IBM DFDL does not implement encodingErrorPolicy="replace". We should consider
> whether we can change this to encodingErrorPolicy="error" without breaking
> things, or rather, we should change it, and see if too many things break. It
> would be helpful if every schema trying to be portable did not have to deal
> with this little detail.
> These properties we don't implement yet are required by IBM DFDL, so without
> them defined in DFDLGeneralFormat our schemas can't be immediately portable
> to IBM DFDL even if everything "real" in them is portable. The properties are:
> floating="no"
> textBiDi="no"
> calendarCenturyStart="53"
> calendarObserveDST="yes"
> Daffodil doesn't need these properties yet, but won't reject them I don't
> think, so we should include them to avoid portability hassles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
