You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2023/06/13 19:48:00 UTC

[jira] [Resolved] (DAFFODIL-2820) GeneralFormatPortable isn't actually portable due to emptyElementParsePolicy

     [ https://issues.apache.org/jira/browse/DAFFODIL-2820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence resolved DAFFODIL-2820.
--------------------------------------
    Resolution: Fixed

Fixed in commit 6c5560758b49ecfd044e2b6320e4d42976f90196

> GeneralFormatPortable isn't actually portable due to emptyElementParsePolicy
> ----------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2820
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2820
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Compatibility
>            Reporter: Steve Lawrence
>            Assignee: Steve Lawrence
>            Priority: Critical
>             Fix For: 3.5.0
>
>
> The DFDLGeneralFormat.dfdl.xsd file defines two formats: GeneralFormat and GeneralFormatPortable. The idea being that GeneralFormatPortable can be used for schemas that want to work in both Daffodil and IBM DFDL.
> However, GeneralFormat defines the extension property emptyElementParsePolicy that IBM DFDL does not allow. Even if a schema only uses GeneralFormatPortable, IBM still sees this invalid property in GeneralFormat and creates an SDE. This means anything using tthe DFDLGeneralFormat.dfdl.xsd file cannot be portable.
> For his to work, the GeneralFormat and GeneralFormatPortable types need to be defined in completely separate files.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)