[
https://issues.apache.org/jira/browse/DAFFODIL-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729114#comment-16729114
]
Michael Beckerle commented on DAFFODIL-35:
------------------------------------------
Of the other properties mentioned here, the only ones that might not have
sufficient checking are:
textStandardBase
useNilForDefault
choiceLengthKind
choiceLength
occursStopValue
documentFinalTerminatorCanBeMissing
All of these above should at least be detected, and if they have an
unimplemented value, should error or at least warn.
(See code for the dfdl:floating property for example of what to do)
They should error out, but for compatibility reasons we will want to provide a
flag.
> Daffodil must recognize unimplemented annotations
> -------------------------------------------------
>
> Key: DAFFODIL-35
> URL: https://issues.apache.org/jira/browse/DAFFODIL-35
> Project: Daffodil
> Issue Type: Bug
> Components: Front End
> Reporter: Joe Futrelle
> Priority: Minor
>
> The DFDL spec states:
> "In order to provide portability of a DFDL schema, a minimal or extended
> conforming processor must ensure that all the required properties, as
> defined in the property precedence sections, are present in a schema, even
> when those properties are not implemented. For example if the bi-directional
> text feature is not implemented, it is still a schema definition error if
> dfdl:textBiDi is not set to 'no' [on] an xs:string element."
> Whereas Daffodil will currently fail if certain annotations are present at
> all, even if they would not trigger unimplemented behavior. For instance
> dfdl:lengthUnits must be supported, but dfdl:lengthUnits='bits' is optional.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
