[
https://issues.apache.org/jira/browse/DAFFODIL-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276391#comment-17276391
]
Mike Beckerle edited comment on DAFFODIL-913 at 2/1/21, 3:07 PM:
-----------------------------------------------------------------
I believe we can proclaim this to be correct behavior. The primary schema has
to have a global element. I think this is an acceptable constraint and the DFDL
specification is silent on this sort of implementation dependency.
was (Author: mbeckerle):
I believe we can proclaim this to be correct behavior. The primary schema has
to have a global element. I think this is an acceptable constraint and tthe
> A global element is incorrectly required for all schemas
> --------------------------------------------------------
>
> Key: DAFFODIL-913
> URL: https://issues.apache.org/jira/browse/DAFFODIL-913
> Project: Daffodil
> Issue Type: Bug
> Components: Front End
> Reporter: Steve Lawrence
> Priority: Minor
>
> Currently, if you have a schema that only includes complex types which are
> imported and used in other schemas, daffodil fails with an error stating:
> {quote}
> No global elements in foo.xsd
> {quote}
> This restriction should be removed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
