Forums » #117 - DFDL v1.0 Revision »
Clarify the difference between %ES; and an empty DFDL string literal
Added by Tim Kimber about 9 years ago
Section 6.3.1: I think this wording could be clearer:
"
...
A DFDL string literal is therefore able to describe any arbitrary sequence of bytes and characters.
Empty Strings: Empty string is not allowed as a DFDL string literal value unless explicitly stated otherwise in the description of a property. In this case the use of empty string provides some property specific behavior different from simply using the empty string as a value. When the empty string is to be used as a value, the entity %ES; must be used in the corresponding DFDL string literal."
Replies (5)
RE: Clarify the difference between %ES; and an empty DFDL string literal - Added by Tim Kimber about 9 years ago
Suggested revised wording:
"
...
A DFDL string literal is therefore able to describe any arbitrary sequence of bytes and characters.
The special DFDL entity %ES; is provided for describing an empty string or an empty byte sequence. The %ES; entity is the only way to do this. A DFDL string literal with value "" ( the empty string ) is usually invalid. There are a few properties that explicitly allow an empty DFDL String Literal, and these properties assign a property-specific meaning to the empty string value.
Resolved: Clarify the difference between %ES; and an empty DFDL string literal - Added by Michael Beckerle about 9 years ago
Change per reply above.
Resolved: Clarify the difference between %ES; and an empty DFDL string literal - Added by Steve Hanson over 8 years ago
Updated erratum 2.64 in experience document 1.
DONE - RE: Clarify the difference between %ES; and an empty DFDL string literal - Added by Michael Beckerle over 8 years ago
Change in draft-gwdrp-dfdl-v1.0.4-r06.docx
DONE - RE: Clarify the difference between %ES; and an empty DFDL string literal - Added by Steve Hanson about 8 years ago
(1-5/5)