[
https://issues.apache.org/jira/browse/DAFFODIL-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence resolved DAFFODIL-1915.
--------------------------------------
Resolution: Fixed
Assignee: Dave Thompson (was: Michael Beckerle)
Fixed in 300b444de58a2e5f68e8285c6ad9efef4b54be8e
> 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
> Assignee: Dave Thompson
> 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)
