NENA ISSUE SUBMISSION & CHARTER FORM - NENA-ADM-003

Instructions for NENA ISSUE SUBMISSION FORM:

1.  The Originator completes Section 1 and e-mails the form to the NENA Committee Resource Manager (CRM) at .

2.  Upon approval of the DSC Co-Chairs & HQ Staff[1], the CRM publishes the form for 10-day review.

3.  The Development Steering Council (DSC) reviews Section 1 along with comments received during the 10-day review and decides whether to accept the Issue according to the criteria described in NENA ADM-002. Acceptance of the Issue does not necessarily include acceptance of the “Requested Outcome or Proposed Solution”. If the Issue is accepted and assigned to a Committee, the CRM fills out Section 2 based on DSC instructions.

4.  The Committee Co-Chair(s) and all Subcommittee/Working Group Chairs complete Section 3 (the Working Group Charter) and emails the form to the CRM.

5.  The DSC approves the Working Group Charter and the CRM enters the approval date in Section 2.

6.  The CRM sends a copy of the updated form to the Originator.

7.  The CRM updates Section 2 when the Issue status changes.

NOTE: Some fields on this form will be used to populate the Charter if this Issue is accepted and assigned by the DSC.

Section 1 - Issue Details
To Be Completed by the Originator
Please provide input for all fields
Short title (what the Issue may easily be referred to by)
Change Web Services Interfaces from SOAP/XML to REST/json / Date Submitted:
10/07/2015
Originator Name / Brian Rosen
Originator Organization / Neustar
Originator Email /
Originator Phone / 724 382 1051
Description of Problem or Opportunity (Provide detailed and clear information. If this is time sensitive or critical provide an explanation.
NENA has lagged the industry in interface standards. New web services are defined using json object serialization and REST interface descriptions. SOAP/XML is functionally obsolete for new interfaces.
Requested Outcome/Proposed Solution (Provide detailed and clear information):
Note: The final resolution and disposition of this issue may not conform precisely to the Requested Outcome or Proposed Solution. The Working Group consensus will determine the actual means used to accomplish the intent of the Requested Outcome or Proposed Solution.
Direct STA-010.3 and the new NG-PSAP STA to use json/REST interfaces. In V3 of STA-010, retain existing SOAP/XML interfaces for backwards compatibility to V2 implementations with notice that SOAP/XML will be deprecated completely by V4.
Section 2 – DSC Tracking
To be Completed by NENA DSC
Issue Number / 20151007
Date Published for 10-Day Review / Thu 10/22/2015 5:53 PM
Review Comments / 12/08/2015
Date and Reasons for Rejection by the DSC / n/a
Date Assigned by DSC / 12/15/2015
Submit PINS to ANSI? / ☐ Yes ☒ No Date PINS Submitted:______
Referred To - Who will receive the Issue?:
If applicable, which NENA Committee will own this Issue?
☐ Accessibility ☐ Agency Systems ☐ Data Management ☒ Data Structures
☐ Interconnection & Security ☐ NGTPC ☐ PSAP Operations ☐ Public Education & PSAP Training
Or specify the internal NENA owner of this Issue ______
********************************************************************************************
Or specify which external entity it was referred to:
☐ APCO ☐ ATIS-ESIF ☐ ATIS-PTSC ☐ ATIS-WTSC ☐ IEEE ☐ IETF ☐ NFPA
OTHER ______
Working Group Assigned To
(If applicable) / XML Working Group
Estimated/Requested Completion Date of draft (if applicable)
DSC Instructions to the Working Group (includes supplements or modifications to the Originator’s Requested Outcome) / Requested outcome modified by DSC to reflect:
·  Investigate ALL new STAs to use JsonREST interfaces.
·  This would need to be a NENA policy decision across all standards as the current policy is NIEM compliance. Should both SOAP/XML and JsonREST be required for some time?
·  Part of the analysis should be communication with NIEM as to their support for JsonREST.
Date the Charter is due back to DSC / 02/12/2015 – extended due date to include JCM discussion.
Date Working Group Charter Approved
Actual Completion Date
(to be completed later)
Status Updates: link to Scopes & Goals
Resolution: (a brief explanation of how the Issue was resolved for closure)
Section 3 – Working Group Charter
To Be Completed by the Committee Co-Chairs & all Subcommittee/Working Group Co-Chairs, and approved by the DSC.
Assigned Committee Working Group (should be based on the name used in the Issue Submission form, and include the Parent Committee name.)
Data Structures Committee, XML Schema Development Working Group / Issue Number
(from above)
20151007 / Date WG Created
(if it is a new WG)
Goal/Objective/Deliverable (Describe each goal/objective/deliverable and provide detailed and clear information, based on the accepted Issue.)
#1 goal/objective/deliverable: An informal whitepaper that lists pros and cons of adopting REST web services within NENA, instead of SOAP web services, along with shifting from XML to JSON. ______
#2 goal/objective/deliverable: Included in the whitepaper, an exploration of JSON NIEM conformance. The whitepaper must describe how JSON can conform to NIEM, if it can, and what impacts NIEM conformance may have on JSON data structures within NENA.______
#3 goal/objective/deliverable: Included in the whitepaper, a recommendation on the adoption of REST for NENA web services and JSON for data structures. If the working group recommends migrating to REST and JSON, the working group must include a recommended migration plan. The whitepaper and its recommendations will be delievered to the NENA DSC and NENA staff, who will make the final decision on whether or not to migrate from SOAP and XML to REST and JSON. ______
Importance (Rank each goal/objective/deliverable as Essential, Important, or Desirable as follows;
·  Essential – required for something else to succeed
·  Important – helpful toward the success of another work effort
·  Desirable – asset for other reasons
#1 goal/objective/deliverable is ranked: Essential :
#2 goal/objective/deliverable is ranked: Essential
#3 goal/objective/deliverable is ranked: Essential
Schedule (Considering the Estimated Completion Date for the Issue, establish when each goal/objective/deliverable should be met or accomplished, and provide detailed and clear information, based on the accepted Issue.
If applicable, list any intermediate schedule milestones, e.g., “Outline complete”, “First draft complete”.)
#1 goal/objective/deliverable: No later than 6 months after the workgroup conducts its first meeting.______
#2 goal/objective/deliverable: No later than 6 months after the workgroup conducts its first meeting.______
#3 goal/objective/deliverable: No later than 6 months after the workgroup conducts its first meeting.______
Dependencies (Identify all known dependencies for achieving success, e.g., completion of work in other committees or other organizations outside of NENA.)
Chair(s) (Who will serve as the Chair(s) for the group performing this work? Provide name, phone and email.)
Jason Horning, Brian Rosen
Editor(s) (Who will serve as the Editor(s) for the group performing this work? Provide name, phone and email.)
Participating Organizations (Identify all outside organizations that will be needed for success of the identified goals/objectives/deliverables, e.g., APCO, ATIS, NEIM, IHIS, etc.)
Subject Matter Expertise Needed (Identify the types of SMEs needed to achieve success.)
NIEM, JSON, and REST
Required Resources (Identify the types of non-human resources needed to achieve success, e.g., list server, web site, etc.)
Initial Work Schedule Plan (Identify the initial call & meeting schedule, e.g., every Tuesday at 10am EASTERN.)
Status Reporting Schedule (The Charter serves as the guiding document to drive work activities toward established goals. Additionally, it serves as a tool to ensure timely status reports to the DSC throughout the work interval. Depending on the nature of the work, and its impact on other work, the timing of status reports may differ among WG activities.
This field is to be used by the DSC to establish the timing of WG status reports to the DSC or designated Project Mgr(s).)
Measurement (How will each goal/objective/deliverable be evaluated? Use quantitative and/or qualitative measures which are descriptive of the measurement criteria)
#1 goal/objective/deliverable: ______
#2 goal/objective/deliverable: ______
Other?

NENA ADM-003, 07/28/2015 Page 5 of 5

[1] See ADM-002 for details surrounding Issue acceptance.