Forums » #117 - DFDL v1.0 Revision »
Restrictions on delimiters and escape characters unclear
Added by Michael Beckerle about 9 years ago
Sections 12.3.2, or 13.2.1, neither makes clear what are likely requirements.
E.g., the escape character cannot be a prefix of any in-scope terminating delimiter.
Similarly, the escapeBlockStart cannot be a prefix of any in-scope terminating delimiter.
Since the escape character and delimiters can be computed at runtime, this check has to be performed then.
Section 2.3.1 talks about ambiguity of data formats, and if the escape character is the same as a separator, then things are surely ambiguous in some ways, but I dont think this section was about nonsense like the escape character being a prefix of a delimiter, but rather about the cases where different delimiters are the same.
Replies (3)
RE: Restrictions on delimiters and escape characters unclear - Added by Michael Beckerle about 9 years ago
Resolved on 2013-09-24 DFDL Workgroup call
This observation is not right. It is completely reasonable for an escape character to not only be a prefix of a delimiter, but to even be identical to a delimiter. E.g., delimiter "/", and escape char "/", so that an escaped delimiter would be the common "double it" scheme "//".
No change to specification.
Resolved: Restrictions on delimiters and escape characters unclear - Added by Steve Hanson about 9 years ago
Resolved
Closed: Restrictions on delimiters and escape characters unclear - Added by Steve Hanson over 8 years ago
No update to experience documents or specification needed.
(1-3/3)