[DFDL-WG] irrelevant properties

It's hard to search for this. Does anyone recall resolution to this? If you specify properties that are clearly mismatched e.g., you specify dfdl:occursCountKind on an element that isn't an array, or you specify dfdl:textStringJustification on a number. Does this generate an error or a warning or nothing? Obviously this doesn't cause any issue if these properties are in scope or referenced from a format annotation. It's only an issue if they are actually written locally in short or long-form annotations right on the point where the incompatibility resides. -- Mike Beckerle | OGF DFDL WG Co-Chair | Tresys Technologies Tel: 781-330-0412