[
https://issues.apache.org/jira/browse/DAFFODIL-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868704#comment-16868704
]
Michael Beckerle commented on DAFFODIL-784:
-------------------------------------------
The examples that are portable to IBM DFDL, because they don't use
daffodil-only implemented features, all don't have this problem now.
Schemas like PCAP make use of DFDL features not yet implemented by IBM DFDL.
Such time as we attempt to port these to a future IBM DFDL version, we can
revisit whether they have properties that are missing at that time.
Closing this issue as it is no longer relevant. All the properties mentioned
above are in DFDLGeneralFormat.dfdl.xsd in GeneralFormat.
> 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
> Assignee: 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)
