encodings doc: need escape character for compact history records

["Gemmill, Craig" <craig.gemmill@tridium.com>]

Hi all-

 

One thing I came across is my comment in the 1.1 doc CompactHistoryRecord section.  We use comma for separating fields in the compact history record string, so we need an escape mechanism for escaping that character if it occurs somewhere else in the fields.  Not a common situation, but if you were logging string information, and the string happened to contain a comma?

 

Anyway, the specific escape character used I think should be a function of the encoding, so it should be included in the encodings doc.  I know that would be a little weird to have one section that addresses a specific item in the core.  Would it be better to just specify a character in the core spec (I’m proposing backslash ‘\’, Unicode 0x5C), and then if needed a specific encoding could override the behavior?

 

-Craig