I was thinking about how to implement DFDL string literals.<br><br>I went through the spec, and created a diagram which shows in a quasi-UML-class-diagram, what I think is the currently specified behavior of String literals and the properties that have them as their values.<br>
<br>The diagram is attached. If this shows with black or other background instead of white, look for a setting on whatever you are using to view the png file. I had to set mine to white background as the default was an unreadable checkerboard.<br>
<br>Some of the &quot;classes&quot; on here represent combinations of properties e.g., NilKindLiteralValueTextRepSpec means nilKind=&#39;literalValue&#39; and representation=&quot;text&quot;.<br><br>I think it is worth it to review this and see if we agree generally with what is allowed to specify a raw-byte entity and what is not, etc.<br>
<br>Question: Can DFDL Regular Expressions include DFDL Entities? If so which kinds? I would assume (and in the drawing) that is only plain and numeric character entities, not raw bytes, and not character class entities.<br>
<br>...mikeb<br clear="all"><br>-- <br>Mike Beckerle | OGF <span>DFDL</span> WG Co-<span>Chair</span> <br>Tel:  781-330-0412<br><br>