[
https://issues.apache.org/jira/browse/DAFFODIL-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Beckerle reassigned DAFFODIL-664:
--------------------------------------
Assignee: (was: Rick)
> schema with no default format that has elements, types, or groups, should
> generate a warning or maybe even an SDE
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DAFFODIL-664
> URL: https://issues.apache.org/jira/browse/DAFFODIL-664
> Project: Daffodil
> Issue Type: Improvement
> Components: Diagnostics, Front End, Usability
> Affects Versions: s9
> Reporter: Mike Beckerle
> Priority: Minor
> Labels: beginner
>
> Because of the way lexical scoping works in DFDL, a schema which doesn't have
> a default format, but which contains anything nested. E.g.,
> {code}
> <complexType name="foo"/>
> <sequence>
> ...
> </sequence>
> </complexType>
> {code}
> That sequence in there. That has no properties at all that apply to it by
> default unless they are in the default format of the containing schema file.
> This characteristic makes a DFDL schema file containing any elements or types
> or groups so useless that we should simply reject it.
> The only DFDL schemas that might not have a default format would be schemas
> that are libraries themselves of just named format definitions. That is, they
> contain only dfdl:defineFormat annotations, or dfdl:defineEscapeSchema
> annotations, and no element, type, or group definitions at all.
> Right now the error you get is about missing leadingSkip property, because
> that's the first property we're looking for. But that is really understating
> the problem, because there are no properties at all!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
