The representation property is usually put in scope where it produces no warnings. It's only if you put it directly on a string type element that you get this warning.
________________________________ From: Steve Lawrence <[email protected]> Sent: Monday, April 13, 2020 10:17 AM To: [email protected] <[email protected]> Subject: Re: Why does dfdl:representation give a warning message? This warning occurs because for xs:string types the dfdl:representation property is not applicable. xs:string's are assumed to have representation="text", regardless of its value. Because it's not used, we display a warning. Note if you had something like this: <xs:element name="a" type="xs:string" dfdl:representation="binary" /> then one could argue that you do want a warning that the property isn't used. It isn't clear what a binary string would be, so it's probably a mistake. Also note that the same occurs for xs:hexBinary--the representation is always assumed be to "binary", and so the property is ignored. On 4/13/20 8:30 AM, Costello, Roger L. wrote: > Hi Folks, > > I have an element of type string. I put dfdl:representation on the element > declaration. Daffodil gave me this warning: > > [warning] Schema Definition Warning: DFDL property was ignored: > representation="text" > > I object to that warning. > > To my way of thinking, the most fundamental property to document a text data > format is the representation property. To give me a warning that I am clearly > specifying the data format, well, that is not nice. > > I vote that no warning message be generated. > > /Roger >
