|
Do not create acronyms or abbreviations unless necessary. If there is an abbreviation that is specific only to your document, instead of creating yet another abbreviation, just spell it out.
====Early Notification Process For New Terms or Definitions ====
When a Working GroupsGroup developdevelops a new term that they believe may be used by other Working Groups, this process is the method with which the proposednew term andor definition canmay be sharedsubmitted within the NDG groupan leadersISF before the document approvalcontaining processthe hasterm or new definition is approved and begunpublished.
'''Early Notification Resources:'''
*A folder in “00. All Group Leaders” on NWS is dedicated to this purpose.
The name of that folder is “Proposed MG Terms.” https://dev.nena.org/kws/groups/all-group-leaders/documents?folder_id=1928
*That NWS Folder is where proposals to add/modify/delete terms in the MG will be stored for sharing and approval, way ahead of when they would have otherwise been seen by anyone outside of the WG that came up with them.
*The [https://dev.nena.org/higherlogic/ws/groups/ed9b432e-644e-48be-ab9f-c8cffce3a079/documents?folder_id=130 NENA-ADM-008] Agenda & Notes template includes a reminder line that will encourage meeting hosts to look to see if there’s anything in that folder that needs their attention. There is a link to the folder where such information would be if it existed. This ‘reminder’ step is similar to the Agenda line item that exists now to remind them to ask if there are any known conflicts.
'''How It Works:'''
*A WG Co-Chair or assigned delegate will send the proposed MG term change (add/change/delete) to the CRM via email. The email should be in the following format:
Subject: MG Proposal-Term (Abbreviation if applicable)
Email Body: The XXXXX WG is proposing to add/change/delete (select one) the following term from the MG:
TERM:
ABBREVIATION (if applicable):
PROPOSED DEFINITION:
Submitters Name, Email & Contact Number
*CRM receives the email and creates a document for uploading to NWS to be filed in “00. All Group Leaders” under the folder named “Proposed MG Terms.”
*This folder contains proposed MG terms that may affect other working group's document.
*The CRM will try to ensure the “Document Title” field is short enough that a quick glance by WG Co-Chairs will let them know if a term is applicable to their work or not.
When the file is uploaded by the CRM, a copy of the text will also be copied in the “Submitter Note” field. By doing this, the recipient will not be required to open the actual document, but they will be able to reply to the all-group-leaders@dev.nena.org NWS distribution list. When replying, DO NOT CHANGE THE SUBJECT as NWS will create a discussion list of all emails related to the subject term.
*The WG Co-Chairs will check the link when preparing the agenda and determine if any terms affect the group’s work.
*It remains possible that any proposed MG change could be reversed during the document’s approval cycles. This early notification concept simply meets the goal that was put forth during the 2017 JCM, to speed up the process of sharing proposed MG changes ahead of the formal approval cycles.
*The MG won’t be changed until the associated document is approved for publication by the Executive Board. But the WG that requested the change will know that there weren’t any objections from other WGs, and other WGs will know about the pending change, and can make use of it in their own work, if applicable.
*Once a new MG is published the draft proposed documents will be archived or deleted from the folder. The folder will only contain terms that are in documents that are being drafted.
===Conducting Document Reviews & Comment Resolution===
| 