[
https://issues.apache.org/jira/browse/DAFFODIL-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868699#comment-16868699
]
Michael Beckerle commented on DAFFODIL-784:
-------------------------------------------
Updating this. We now include, usually, our own DFDLGeneralFormat.dfdl.xsd
which defines GeneralFormat and GeneralFormatPortable.
Both should have property bindings for all the above mentioned ones that aren't
there.
I'd add to the set also useNilForDefault="no" should be bound as well (if it
isn't)
> Update default properties in examples to have missing required properties for
> portability.
> ------------------------------------------------------------------------------------------
>
> Key: DAFFODIL-784
> URL: https://issues.apache.org/jira/browse/DAFFODIL-784
> Project: Daffodil
> Issue Type: Bug
> Components: Compatibility, DFDL Schemas, QA
> Affects Versions: s10
> Reporter: Michael Beckerle
> Priority: Minor
> Labels: ForInteroperabilityTest
>
> Our friends at IBM fed our PCAP schema to their DFDL implementation.
> It spat out some errors:
> Properties that need a default in scope:
> CTDV1118E : When 'sequenceKind' is 'ordered', DFDL property 'floating' must
> be set.
> CTDV1236E : When number or calendar representation is binary, DFDL property
> 'binaryNumberCheckPolicy' must be set.
> CTDV1263E : For a sequence, DFDL property 'sequenceKind' must be set.
> CTDV1332E : DFDL property 'fillByte' must be set.
> We need to add these properties to all examples so that they will be portable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
