[
https://issues.apache.org/jira/browse/DAFFODIL-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774028#comment-17774028
]
Steve Lawrence commented on DAFFODIL-2850:
------------------------------------------
Maybe a duplicate of DAFFODIL-2810? Instead of escalating just this warning to
an error, I would suggest we do what DAFFODIL-2810 suggests and have a way to
escalate *all* warnings as errors. And if there is a particular warning that a
user doesn't want to cause an error then it should be suppressed with the
"suppressSchemaDefinitionWarnings" tunable.
> Way to escalate some warnings to errors (ex: incompatibility with JSON)
> -----------------------------------------------------------------------
>
> Key: DAFFODIL-2850
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2850
> Project: Daffodil
> Issue Type: Improvement
> Components: Front End
> Affects Versions: 3.5.0
> Reporter: Mike Beckerle
> Priority: Major
>
> JSON format is becoming much more important.
> Recent work on some well-known and used schemas such as mil-std-2045, shows
> that they are not JSON compatible. They have duplicate field names (multiple
> children elements with the same name and type).
> We need a way to avoid this by escalating the warning about this to an error.
> This should be settable by way of some sort of ~/.daffodil.properties file
> that a user can set in their home directory, or in a per-project properties
> or config file.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
