RE: encodings doc: need escape character for compact history records

How about putting the delimiter in the header of the CompactHistoryRecord?

 

I’m using :::

 

I’m using ,

 

I’m using ^^^^^^

 

Save the heavy escape overhead

 

 

"When one door closes, another opens; but we often look so long and so regretfully upon the closed door that we do not see the one which has opened for us."

-- Alexander Graham Bell

Toby Considine

Chair, OASIS oBIX TC

Editor, OASIS EMIX, Energy Interoperation

Campus Services Information Technology

University of North Carolina

Chapel Hill, NC

  

Email: 
Toby.Considine@ unc.edu

Phone: (919)962-9073 

http://www.oasis-open.org 

http://www.NewDaedalus.com

 

From:  [mailto:]
On Behalf Of Gemmill, Craig

Sent: Thursday, June 13, 2013 3:26 PM

To: 

Subject: [obix] encodings doc: need escape character for compact history records

 

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