Comment 2449
Accepted (Resolved)
NENA-STA-015.10-201X_DataFormats_PubRvw (Revision 0)
Comment Submitted by
Jerry Eisner-ENP
2017-12-22 12:16:55

In i3, we have run into many issues, specifically in location data fields, where special characters are required and depending on the consuming application, may or not be troublesome.  This effort to deal with the issue should be at least noted if not copied.

Submitter Proposed Solution

Copy i3 language.

Mr. Richard Muscat
2018-02-20 1:25 pm EST

Accepted, by adding the following to the end 3.1:

It should be noted that some things in the past may not have been clearly defined in E9-1-1 (e.g., Customer Name and Street Address fields potentially containing special characters), and this may create additional potential translation complications between E9-1-1 and NG9-1-1, which may also include translation complications for voice-based texting between E9-1-1 and NG9-1-1 (compare, “@” in Real-Time Text (RTT) with “(at)” in TTY).  Going forward in E9-1-1, sensitivity to not unnecessarily increasing these types of data translation complications between E9-1-1 and NG9-1-1 is urged and expected as feasible. 

Mr. Richard Muscat
2018-02-28 4:39 pm EST

From: Jerry Eisner []
Sent: Monday, February 26, 2018 9:46 AM
To: Richard Muscat <>
Subject: RE: Jerry Eisner comments on NENA-STA-015.10-201X_DataFormats_PubRvw

Good morning,

I have been following the KAVI updates.  It’s all good to go as far as I am concerned.