https://help.etsi.org/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=&size-mode=max&size=0Help - New pages [en]2024-03-19T05:23:24ZFrom HelpMediaWiki 1.39.3https://help.etsi.org/index.php?title=Experts_GuideExperts Guide2024-03-11T15:07:24Z<p>Vantricht: </p>
<hr />
<div>== How to get started with your ETSI drafting ==<br />
This Rapporteur’s guide has been developed to give an overview of what is useful to know when drafting an ETSI Deliverable.<br />
<br />
When new Rapporteurs start working on a draft for ETSI for the first time, it is recommended to read this guide or view the [https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Guides/ETSI_Rapporteurs_guide.mp4 video presentation].<br />
<br />
== Administrative requirements ==<br />
Work can start after the contract (link to https://portal.etsi.org/STF/STFs/Summary/Contract-details_THC) is signed by both parties.<br />
<br />
The initial work plan is agreed during the preparatory meeting.<br />
<br />
Experts can book an office space for the working sessions in ETSI premises as required, with STF/TTF Leader's agreement using the [https://outlook.office365.com/book/Expertsofficesbooking@etsi.org/ Booking application] (click here (https://portal.etsi.org/Portals/0/TBpages/STFs/Docs/User_Guide_Bookings_Application_v0_1.pdf) to access further details).<br />
<br />
After the end of each month, meaning before the 7<sup>th</sup> of the following month, the work done should be confirmed, using the [https://portal.etsi.org/timesheet/login.aspx timesheet declaration] (click [https://portal.etsi.org/Portals/0/TBpages/STFs/Docs/User&#x20;Guide&#x20;-&#x20;Timesheets&#x20;Application&#x20;Management_v2_0.pdf here] to access further details).<br />
<br />
The STF/TTF Leader should review and validate the timesheet declaration of each expert, before the 14<sup>th</sup> of the following month.<br />
<br />
The Funded Activities Team will do the final acceptance of all the timesheets validated by the STF/TTF Leader, starting from the 15th.<br />
<br />
If everybody respects the agreed times and dates, all the work performed will be accounted for in a timely manner.<br />
<br />
= Travels & payments =<br />
The travel costs to attend the Projects working sessions is included in the contractual compensation. A mission travel may be requested to present the results of the Project and/or to attend related events.<br />
<br />
The travellers should prepare a Travel Order on Notilus for the mission travels which will be validated by the STF/TTF leader and by ETSI.<br />
<br />
A travel expense must be prepared also on Notilus with the specific details of the travel organization, to be approved by ETSI. The motivations for exceptions to the [https://portal.etsi.org/STF/STFs/STFwork/Travels/Travelorganisationandreimbursement.aspx ETSI travel rules] must be clearly indicated in the travel order.<br />
<br />
Reimbursement shall be requested, according to the approved travel expense with an invoice from the company with copies of the detailed justification receipts. In the case that unexpected extra costs have been incurred, they should also be clearly indicated in the reimbursement request.<br />
<br />
Regarding payment, FA Team will confirm the achievement of the milestones and provide you with the necessary information to issue the invoice.<br />
<br />
The milestones that must be achieved have been defined in the preparatory meeting (see the meeting minutes) and are part of your contract. Payments will be made upon the achievement of these milestones.<br />
<br />
Requests (for payment) during the duration of the STF/TTF can be sent to [mailto:STFLink@etsi.org STFLink@etsi.org].<br />
<br />
= IT environment =<br />
When working in ETSI, you will have access to a desktop computer, configured with the IT environment. If any special software is required, a request must be made to the ETSI Secretariat.<br />
<br />
editHelp! and the IT services can advise whether the use of this software is compatible with the ETSI IT policy and with the ETSI editing requirements.<br />
<br />
When you are working from your home office, your organization must make available an IT configuration equivalent to the standard ETSI environment, in order to be able to exchange information with the other experts and the ETSI Secretariat.<br />
<br />
This information may be found on the ETSI portal at https://portal.etsi.org/Services/editHelp/How-to-start/Supported&#x20;file&#x20;formats.<br />
<br />
= ETSI DOCBOX =<br />
A document repository area is provided on the [https://docbox.etsi.org/Board/ETSI_Directives ETSI docbox], which is accessible from both inside and outside ETSI. This contains a "Public" area, accessible in read only mode to all ETSI On Line users and a Project [https://docbox.etsi.org/STF/ workarea] to which access is restricted to the experts and can be used to store preliminary drafts and other confidential documents. Before leaving ETSI, you have to move the documents you need to the "docbox" area.<br />
<br />
For each STF/TTF, a dedicated Teams workspace is available for the project members to discuss the drafts and exchange information during the project’s entire lifetime.<br />
<br />
Open WEB pages can also be created on the ETSI Portal to present the activity of the STF/TTF to stakeholders outside ETSI.<br />
<br />
When working in ETSI, documents can be temporarily stored on the local network but will not be accessible from outside ETSI.<br />
<br />
== Drafting your 1<sup>st</sup> deliverable ==<br />
For a 1<sup>st</sup> ETSI Deliverable, it is recommended to read the booklet called Writing World Class Standards available at https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/#p=1.<br />
<br />
This booklet starts with the basics for Rapporteurs who are new to standardization or new to ETSI.<br />
<br />
Guidance follows on how to [https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/ choose the right type of standard], how to [https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/ structure a standard] and draft it, how to [https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/ express the technical requirements] and finally how to [https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/ validate, test and maintain] a standard.<br />
<br />
== Start drafting a revision ==<br />
If it's not a 1<sup>st</sup> publication but a revision of an already published ETSI Deliverable to be produced, it is essential to start working on '''the latest published version'''. In case it is not sure the version you have is the latest version, it is necessary to search in the right place for the proper version.<br />
<br />
[[File:Figure_1_Rap_guide.jpg|frame|center]]<br />
[[File:Figure_2_Rap_guide.jpg|frame|center]]<br />
<br />
= Personal information =<br />
The ETSI Secretariat shall keep the Rapporteur informed all along the process of the development of the ETSI Deliverable. It is essential that all recorded personal details are accurate.<br />
<br />
If not, there is a risk that this could delay the timeline of the work schedule. The name of the Rapporteur should always be provided. Please access personal details by clicking on https://portal.etsi.org/webapp/teldir/PersonalInfo.asp where it is possible to update if needed. If difficulties are experienced when updating these details, just inform the ETSI Secretariat that corrections are needed and the Technical Officer or the Standardization Support Professional or '''''editHelp!''''' can update the information. <br />
<br />
== ETSI skeletons ==<br />
If a new ETSI Deliverable is to be drafted, the best way to start is to download the proper skeleton. These can be downloaded from this page: https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Skeletons.<br />
[[File:Figure_3_Rap_guide.jpg|frame|center]]<br />
<br />
= ETSI skeletons and guide =<br />
At the same time and from the same location, please download the guide named "Principles for drafting an ETSI deliverable with the use of skeletons".<br />
<br />
https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Principles_for_drafting_ETSI_deliverables.pdf. <br />
<br />
This guide contains all the details needed when drafting an ETSI Deliverable. It follows the complete structure of the draft from beginning to end, starting with the cover page and ending with the history box.<br />
<br />
[[File:Figure_4_Rap_guide.jpg|frame|center]]<br />
<br />
For example, it gives guidance on references, terms, symbols, abbreviations and details on ETSI styles on how they are supposed to be used and much more following the skeletons' structure.<br />
<br />
It also explains how to deal with figures, tables, equations, mathematical formulae, supplementary files, etc.<br />
<br />
All the information is summed up in this document to facilitate the drafting from an editing point of view.<br />
<br />
== ETSI videos ==<br />
[[File:Figure_5_Rap_guide.jpg|frame|center]]For a better understanding and a simplified use of the ETSI styles, it is suggested to watch these videos available at https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Styles-toolbar. <br />
<br />
= ETSI Drafting Rules (EDRs) =<br />
In order to draft an ETSI Deliverable, please refer to the ETSI Drafting Rules document - commonly named "EDRs", which is available at https://docbox.etsi.org/Board/ETSI_Directives.<br />
<br />
Every year, the ETSI Secretariat studies the necessity to review these rules.<br />
<br />
It is essential to use the latest updated version of the EDRs when drafting an ETSI deliverable.<br />
<br />
= Set of rules =<br />
These set of rules state what is permitted and what is not when drafting an ETSI Deliverable.<br />
<br />
Whether dealing with normative references or informative references, normative provisions and informative recommendations the rules are not the same depending on the type of ETSI Deliverable worked on.<br />
<br />
European Harmonised Standards have specific rules which are not the same as with Technical Reports.<br />
<br />
It is possible to find all verbal forms for the expression of provisions which are explicitly specified in the EDRs (see clause 3). Depending on the nature of the ETSI Deliverable being drafted – some provisions are not permitted.<br />
<br />
Reproduction of third-party material is allowed only under very strict conditions in ETSI Deliverables, and this is the same with the use of tradenames and trademarks. Some communiqués have been produced to provide more guidance regarding these sensitive topics. All are available by clicking on https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-News. <br />
<br />
= The use of gender-inclusive language guide =<br />
"Using gender-inclusive language means speaking and writing in a way that does not discriminate against a particular sex, social gender or gender identity, and does not perpetuate gender stereotypes. Given the key role of language in shaping cultural and social attitudes, using gender-inclusive language is a powerful way to promote gender equality and eradicate gender bias".<br />
<br />
https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Guides/Use_gender_inclusive_language.pdf<br />
<br />
= Standards’ production time =<br />
How long does it take to get a ETSI Deliverable published?<br />
<br />
This depends on the type of ETSI Deliverable being produced. For example, the process is different if it is a GS or an EN.<br />
<br />
All the details are available by clicking here: https://portal.etsi.org/Resources/Standards-Making-Process/Process.<br />
<br />
= Making a contribution on the ETSI Portal =<br />
Information on how to use the Contribution tool on the ETSI Portal, can be found by clicking here: [[Contributions application|http://help.etsi.org/index.php?title=Contributions_application#WI_Details_tab_-_Creation_of_a_New_Deliverable]].<br />
<br />
= Clean-up service =<br />
It is impossible to publish an ETSI Deliverable which is not compliant with the ETSI Drafting Rules.<br />
<br />
To avoid such a situation, '''''editHelp!''''' proposes a service called "clean-up”, where it is possible to submit a draft once stable enough to be 'cleaned-up' to '''''editHelp!'''''.<br />
<br />
This service is dedicated to prevent any misunderstanding and thus helps raise all blocking issues and offers practical solutions before the approval of the draft.<br />
<br />
All the details are available on the communiqué available at https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/News_from_editHelp/ETSI_clean-up_service.pdf.<br />
<br />
= Editing checklist =<br />
An editing checklist is available at https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/ETSI_editing_checklist.pdf.<br />
<br />
It is recommended to compare the items presented on the list with the content of the ETSI Deliverable to make sure that it is compliant with the EDRs. If doubts subsist, please contact the ETSI Secretariat (either the Technical Officer, the Support Standardization Professional or '''''editHelp!''''') for support and to help solve these issues.<br />
<br />
= Some blocking issues =<br />
A document has been produced which lists the most frequent issues encountered by edithelp! that block the publication of an ETSI Deliverable if not properly addressed beforehand. <br />
<br />
This document can found by clicking on the following link: https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/News_from_editHelp/editHelp_10_most_asked_editing_questions.pdf. <br />
<br />
= FAQ =<br />
If looking for an answer to a specific question, please consult the FAQ, by clicking on https://portal.etsi.org/Services/editHelp/To-help-you-in-your-work/FAQs.<br />
<br />
If the answer cannot be found, it is recommended to contact '''''editHelp!''''' directly (https://portal.etsi.org/Services/editHelp/Contact-Us<nowiki/>)''.'' <br />
<br />
= '''''editHelp'''''! Website https://portal.etsi.org/Services/editHelp =<br />
To know more about '''''editHelp!''''' services, please watch the video tour of the '''''editHelp!''''' website at https://portal.etsi.org/Services/editHelp/How-to-start/editHelp-introduction.<br />
<br />
= All the links provided in this presentation are listed below =<br />
{| class="wikitable"<br />
|+<br />
|'''''editHelp!''''' website<br />
|https://portal.etsi.org/Services/editHelp <br />
|-<br />
|How to use contribution tool on the ETSI Portal<br />
|http://help.etsi.org/index.php?title=Contributions_application <br />
|-<br />
|Frequently Asked Questions (FAQ)<br />
|https://portal.etsi.org/Services/editHelp/To-help-you-in-your-work/FAQs <br />
|-<br />
|How to get in touch with '''''editHelp!'''''<br />
|https://portal.etsi.org/Services/editHelp/Contact-Us <br />
|-<br />
|ETSI booklet on how to draft ETSI Deliverables<br />
|https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile <br />
|-<br />
|Advanced search for ETSI Deliverables<br />
|https://portal.etsi.org/webapp/WorkProgram/Expert/QueryForm.asp <br />
|-<br />
|'''''editHelp!''''' email address<br />
|mailto:editHelp@etsi.org <br />
|-<br />
|Application to update your personal details<br />
|https://portal.etsi.org/webapp/teldir/PersonalInfo.asp <br />
|-<br />
|Find all ETSI skeletons (pre-built deliverables)<br />
|https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Skeletons <br />
|-<br />
|Step by step guide to help you drafting<br />
|https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Principles_for_drafting_ETSI_deliverables.pdf <br />
|-<br />
|Short cut to ETSI styles<br />
|https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Styles-toolbar <br />
|-<br />
|ETSI Drafting Rules<br />
|https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-Rules <br />
|-<br />
|ETSI Directives<br />
|https://docbox.etsi.org/Board/ETSI_Directives/ <br />
|-<br />
|News from '''''editHelp!'''''<br />
|https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-News <br />
|-<br />
|Information on the ETSI Standards Making Process<br />
|https://portal.etsi.org/Resources/Standards-Making-Process/Process <br />
|-<br />
|Clean-up service (information)<br />
|https://portal.etsi.org/Services/editHelp/To-help-you-in-your-work/Services/Clean-ups <br />
|-<br />
|Editing checklist<br />
|https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Editing-checklist<br />
|-<br />
|Question you may ask yourselves when drafting<br />
|https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/10-editing-questions-you-may-be-asked <br />
|}</div>Vantrichthttps://help.etsi.org/index.php?title=Rapporteurs_GuideRapporteurs Guide2024-03-11T14:37:08Z<p>Vantricht: </p>
<hr />
<div>== How to get started with your ETSI drafting ==<br />
This Rapporteur’s guide has been developed to give an overview of what is useful to know when drafting an ETSI Deliverable.<br />
<br />
When new Rapporteurs start working on a draft for ETSI for the first time, it is recommended to read this guide or view the [https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Guides/ETSI_Rapporteurs_guide.mp4 video presentation].<br />
<br />
== Drafting your 1<sup>st</sup> deliverable ==<br />
For a 1<sup>st</sup> ETSI Deliverable, it is recommended to read the booklet called Writing World Class Standards available at https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/#p=1.<br />
<br />
This booklet starts with the basics for Rapporteurs who are new to standardization or new to ETSI.<br />
<br />
Guidance follows on how to [https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/ choose the right type of standard], how to [https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/ structure a standard] and draft it, how to [https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/ express the technical requirements] and finally how to [https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile/ validate, test and maintain] a standard.<br />
<br />
== Start drafting a revision ==<br />
If it's not a 1<sup>st</sup> publication but a revision of an already published ETSI Deliverable to be produced, it is essential to start working on '''the latest published version'''. In case it is not sure the version you have is the latest version, it is necessary to search in the right place for the proper version.<br />
<br />
[[File:Figure_1_Rap_guide.jpg|frame|center]]<br />
[[File:Figure_2_Rap_guide.jpg|frame|center]]<br />
<br />
= Personal information =<br />
The ETSI Secretariat shall keep the Rapporteur informed all along the process of the development of the ETSI Deliverable. It is essential that all recorded personal details are accurate.<br />
<br />
If not, there is a risk that this could delay the timeline of the work schedule. The name of the Rapporteur should always be provided. Please access personal details by clicking on https://portal.etsi.org/webapp/teldir/PersonalInfo.asp where it is possible to update if needed. If difficulties are experienced when updating these details, just inform the ETSI Secretariat that corrections are needed and the Technical Officer or the Standardization Support Professional or '''''editHelp!''''' can update the information. <br />
<br />
== ETSI skeletons ==<br />
If a new ETSI Deliverable is to be drafted, the best way to start is to download the proper skeleton. These can be downloaded from this page: https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Skeletons.<br />
[[File:Figure_3_Rap_guide.jpg|frame|center]]<br />
<br />
= ETSI skeletons and guide =<br />
At the same time and from the same location, please download the guide named "Principles for drafting an ETSI deliverable with the use of skeletons".<br />
<br />
https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Principles_for_drafting_ETSI_deliverables.pdf. <br />
<br />
This guide contains all the details needed when drafting an ETSI Deliverable. It follows the complete structure of the draft from beginning to end, starting with the cover page and ending with the history box.<br />
<br />
[[File:Figure_4_Rap_guide.jpg|frame|center]]<br />
<br />
For example, it gives guidance on references, terms, symbols, abbreviations and details on ETSI styles on how they are supposed to be used and much more following the skeletons' structure.<br />
<br />
It also explains how to deal with figures, tables, equations, mathematical formulae, supplementary files, etc.<br />
<br />
All the information is summed up in this document to facilitate the drafting from an editing point of view.<br />
<br />
== ETSI videos ==<br />
[[File:Figure_5_Rap_guide.jpg|frame|center]]For a better understanding and a simplified use of the ETSI styles, it is suggested to watch these videos available at https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Styles-toolbar. <br />
<br />
= ETSI Drafting Rules (EDRs) =<br />
In order to draft an ETSI Deliverable, please refer to the ETSI Drafting Rules document - commonly named "EDRs", which is available at https://docbox.etsi.org/Board/ETSI_Directives.<br />
<br />
Every year, the ETSI Secretariat studies the necessity to review these rules.<br />
<br />
It is essential to use the latest updated version of the EDRs when drafting an ETSI deliverable.<br />
<br />
= Set of rules =<br />
These set of rules state what is permitted and what is not when drafting an ETSI Deliverable.<br />
<br />
Whether dealing with normative references or informative references, normative provisions and informative recommendations the rules are not the same depending on the type of ETSI Deliverable worked on.<br />
<br />
European Harmonised Standards have specific rules which are not the same as with Technical Reports.<br />
<br />
It is possible to find all verbal forms for the expression of provisions which are explicitly specified in the EDRs (see clause 3). Depending on the nature of the ETSI Deliverable being drafted – some provisions are not permitted.<br />
<br />
Reproduction of third-party material is allowed only under very strict conditions in ETSI Deliverables, and this is the same with the use of tradenames and trademarks. Some communiqués have been produced to provide more guidance regarding these sensitive topics. All are available by clicking on https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-News. <br />
<br />
= The use of gender-inclusive language guide =<br />
"Using gender-inclusive language means speaking and writing in a way that does not discriminate against a particular sex, social gender or gender identity, and does not perpetuate gender stereotypes. Given the key role of language in shaping cultural and social attitudes, using gender-inclusive language is a powerful way to promote gender equality and eradicate gender bias".<br />
<br />
https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Guides/Use_gender_inclusive_language.pdf<br />
<br />
= Standards’ production time =<br />
How long does it take to get a ETSI Deliverable published?<br />
<br />
This depends on the type of ETSI Deliverable being produced. For example, the process is different if it is a GS or an EN.<br />
<br />
All the details are available by clicking here: https://portal.etsi.org/Resources/Standards-Making-Process/Process.<br />
<br />
= Making a contribution on the ETSI Portal =<br />
Information on how to use the Contribution tool on the ETSI Portal, can be found by clicking here: [[Contributions application|http://help.etsi.org/index.php?title=Contributions_application#WI_Details_tab_-_Creation_of_a_New_Deliverable]].<br />
<br />
= Clean-up service =<br />
It is impossible to publish an ETSI Deliverable which is not compliant with the ETSI Drafting Rules.<br />
<br />
To avoid such a situation, '''''editHelp!''''' proposes a service called "clean-up”, where it is possible to submit a draft once stable enough to be 'cleaned-up' to '''''editHelp!'''''.<br />
<br />
This service is dedicated to prevent any misunderstanding and thus helps raise all blocking issues and offers practical solutions before the approval of the draft.<br />
<br />
All the details are available on the communiqué available at https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/News_from_editHelp/ETSI_clean-up_service.pdf.<br />
<br />
= Editing checklist =<br />
An editing checklist is available at https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/ETSI_editing_checklist.pdf.<br />
<br />
It is recommended to compare the items presented on the list with the content of the ETSI Deliverable to make sure that it is compliant with the EDRs. If doubts subsist, please contact the ETSI Secretariat (either the Technical Officer, the Support Standardization Professional or '''''editHelp!''''') for support and to help solve these issues.<br />
<br />
= Some blocking issues =<br />
A document has been produced which lists the most frequent issues encountered by edithelp! that block the publication of an ETSI Deliverable if not properly addressed beforehand. <br />
<br />
This document can found by clicking on the following link: https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/News_from_editHelp/editHelp_10_most_asked_editing_questions.pdf. <br />
<br />
= FAQ =<br />
If looking for an answer to a specific question, please consult the FAQ, by clicking on https://portal.etsi.org/Services/editHelp/To-help-you-in-your-work/FAQs.<br />
<br />
If the answer cannot be found, it is recommended to contact '''''editHelp!''''' directly (https://portal.etsi.org/Services/editHelp/Contact-Us<nowiki/>)''.'' <br />
<br />
= '''''editHelp'''''! Website https://portal.etsi.org/Services/editHelp =<br />
To know more about '''''editHelp!''''' services, please watch the video tour of the '''''editHelp!''''' website at https://portal.etsi.org/Services/editHelp/How-to-start/editHelp-introduction.<br />
<br />
= All the links provided in this presentation are listed below =<br />
{| class="wikitable"<br />
|+<br />
|'''''editHelp!''''' website<br />
|https://portal.etsi.org/Services/editHelp <br />
|-<br />
|How to use contribution tool on the ETSI Portal<br />
|http://help.etsi.org/index.php?title=Contributions_application <br />
|-<br />
|Frequently Asked Questions (FAQ)<br />
|https://portal.etsi.org/Services/editHelp/To-help-you-in-your-work/FAQs <br />
|-<br />
|How to get in touch with '''''editHelp!'''''<br />
|https://portal.etsi.org/Services/editHelp/Contact-Us <br />
|-<br />
|ETSI booklet on how to draft ETSI Deliverables<br />
|https://www.etsi.org/e-brochure/WritingWorldClassStandards/mobile <br />
|-<br />
|Advanced search for ETSI Deliverables<br />
|https://portal.etsi.org/webapp/WorkProgram/Expert/QueryForm.asp <br />
|-<br />
|'''''editHelp!''''' email address<br />
|mailto:editHelp@etsi.org <br />
|-<br />
|Application to update your personal details<br />
|https://portal.etsi.org/webapp/teldir/PersonalInfo.asp <br />
|-<br />
|Find all ETSI skeletons (pre-built deliverables)<br />
|https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Skeletons <br />
|-<br />
|Step by step guide to help you drafting<br />
|https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Principles_for_drafting_ETSI_deliverables.pdf <br />
|-<br />
|Short cut to ETSI styles<br />
|https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Styles-toolbar <br />
|-<br />
|ETSI Drafting Rules<br />
|https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-Rules <br />
|-<br />
|ETSI Directives<br />
|https://docbox.etsi.org/Board/ETSI_Directives/ <br />
|-<br />
|News from '''''editHelp!'''''<br />
|https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-News <br />
|-<br />
|Information on the ETSI Standards Making Process<br />
|https://portal.etsi.org/Resources/Standards-Making-Process/Process <br />
|-<br />
|Clean-up service (information)<br />
|https://portal.etsi.org/Services/editHelp/To-help-you-in-your-work/Services/Clean-ups <br />
|-<br />
|Editing checklist<br />
|https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Editing-checklist<br />
|-<br />
|Question you may ask yourselves when drafting<br />
|https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/10-editing-questions-you-may-be-asked <br />
|}</div>Vantrichthttps://help.etsi.org/index.php?title=NSOs_GuideNSOs Guide2024-02-15T14:06:25Z<p>Raffy: </p>
<hr />
<div>='''Introduction'''=<br />
<br />
This guide provides a step-by-step guidance on the essential elements, most common practices and responsibilities of the National Standards Organizations (NSOs) and National Standardisation Bodies (NSBs).<br />
<br />
An NSO is an organization that develops, maintains and coordinates voluntary standardization activities in a particular country. NSOs typically represent the interests of various stakeholders, including businesses, consumers, academia and government.<br />
<br />
An NSB is an NSO from the European Economic Area and thus from one of the following countries: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, The Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain or Sweden.<br />
<br />
The information contained in this guide is based on the Rules of Procedure (RoP) and Technical Working Procedure (TWP) contained in the [https://portal.etsi.org/Resources/ETSI-Directives ETSI Directives], the European Commission Regulations (EU) [https://eur-lex.europa.eu/legal-content/FR/TXT/?uri=celex%3A32012R1025 N° 1025/2012], and amendment [https://eur-lex.europa.eu/eli/reg/2022/2480/oj N° 2022/2480] and also on the [https://etsisign.eu1.echosign.com/public/esignWidget?wid=CBFCIBAA3AAABLblqZhDi5sRNHpzZXSLmat-YMhP7Ocp_1sEYbdRmsjREUEW8uboWsI-7MWrEIGHdU8UfSXo* ETSI-NSO Agreement].<br />
<br />
='''Roles'''=<br />
==The NSO/NSB Official Contact==<br />
The Official Contact is the person designated by the NSO to be the main contact person between ETSI and the NSO. <br />
There is only one Official Contact per NSO, ensuring that all the contact details within the organization are correctly registered in the ETSI Directory Services application. Contact details can be consulted via the [https://portal.etsi.org/LoginRedirection.aspx?ReturnUrl=%2fwebapp%2fTeldir%2f Directory Services] page.<br />
<br />
[[File:Figure123_NSOs.jpg|frame|center]]<br />
<br />
<br />
The '''NSO Official Contact''' is responsible for the following tasks within the represented country:<br />
<br />
* ensuring that no national standardization activity or publication of any new or revised standard, which could prejudice the preparation of a standard, is undertaken during the Standstill period of a European standard (EN);<br />
* carrying out the Public Enquiry (PE);<br />
* establishing the national position of the represented country;<br />
* ensuring the withdrawal of any conflicting national standards with any recently adopted ENs.<br />
<br />
The '''NSB Official Contact''' has the same responsibilities listed above plus:<br />
<br />
* participating in the EC/EFTA Standardisation Requests (SReq) drafting process;<br />
* participating in the Weighted National Voting procedure to accept SReqs;<br />
* participating in the Weighted National Voting procedure to adopt Work Item(s) identified in the Standardisation Request (WISR); and<br />
* providing ETSI with the title translations into the mandatory official languages via the e Approval application.<br />
<br />
==The NSO/NSB Voting Contact==<br />
The Voting Contact is a person designated by the Official Contact to cast votes during Weighted National Voting procedures and submit comments during Public Enquiries.<br />
<br />
The Official Contact may decide to be also considered as a Voting Contact. It is possible to have several Voting Contacts within the same organization, but only the last vote cast by the Voting Contact of an NSO during a Weighted National Voting procedure will count. It is the responsibility of the NSO to decide which Voting Contact can vote, the ETSI Secretariat has no responsibility in this area.<br />
<br />
In specific conditions, the Weighted National Voting procedure may take place at the ETSI General Assembly level, and in such a case, it is the responsibility of the Head of each National Delegation to cast a vote, after consultation of the relevant NSO.<br />
<br />
==Head of National Delegation (HND)==<br />
The Head of National Delegation is the person appointed by a National Delegation (i.e. the ETSI Full members from the same country) and notified to the Director-General. The Head of National Delegation shall be appointed amongst the representatives of the organizations forming the National Delegation.<br />
<br />
==The ETSI Secretariat Primary Contacts==<br />
The role of the [https://portal.etsi.org/TB-SiteMap/NSO/Contact Primary Contacts] consists in:<br />
* providing meeting facilities and organizing meetings;<br />
* facilitating communication within the groups;<br />
* helping wherever possible the NSOs/NSBs achieving their strategic goals; and<br />
* supporting the NSO/NSB Groups completing their duties using the tools put in place to make their tasks easier.<br />
<br />
='''NSO-ETSI meetings'''=<br />
<br />
The ETSI Director General will have periodic meetings with the NSOs to manage the co operation established in the [https://etsisign.eu1.echosign.com/public/esignWidget?wid=CBFCIBAA3AAABLblqZhDi5sRNHpzZXSLmat-YMhP7Ocp_1sEYbdRmsjREUEW8uboWsI-7MWrEIGHdU8UfSXo* ETSI-NSO Agreement].<br />
<br />
Those meetings may be hybrid (combination of a physical meeting with physical and remote participation via electronic means) or fully held online via electronic means.<br />
<br />
='''Agreements'''=<br />
<br />
==ETSI-NSO Agreement==<br />
<br />
All recognised NSOs/NSBs notified to the ETSI Director-General under Article 13.2 of the Rules of Procedure are entitled to sign the [https://etsisign.eu1.echosign.com/public/esignWidget?wid=CBFCIBAA3AAABLblqZhDi5sRNHpzZXSLmat-YMhP7Ocp_1sEYbdRmsjREUEW8uboWsI-7MWrEIGHdU8UfSXo* ETSI-NSO Agreement].<br />
==Sales Agreement==<br />
ETSI undertakes to give the right of publication to the NSOs/NSBs to sell ETSI Deliverables against payment of royalties.<br />
The Sales Agreement does not supersede the terms of the [https://etsisign.eu1.echosign.com/public/esignWidget?wid=CBFCIBAA3AAABLblqZhDi5sRNHpzZXSLmat-YMhP7Ocp_1sEYbdRmsjREUEW8uboWsI-7MWrEIGHdU8UfSXo* ETSI-NSO Agreement] and is a separate Agreement concerning the Distribution of ETSI Publications. The Legal department is in charge of issuing such agreements ([mailto:legal@etsi.org legal@etsi.org]).<br />
<br />
='''Responsibilities'''=<br />
[[File:Figure4_NSOs.jpg|frame|right]]<br />
<br />
==Standstill==<br />
Standstill is the obligation accepted by the NSOs and the ETSI members not to undertake any national standardization activity which could prejudice the preparation of an EN or a European standardisation deliverable and, not to publish a new or revised standard which is not completely in line with an existing EN or European standardisation deliverable.<br />
Standstill applies to an individual work item leading to an EN or a European standardisation deliverable and accepted by the ETSI General Assembly, with a precise scope and target date. It does not apply to areas or programmes of work as such. General provisions are given in Article 13.3.2 of the Rules of Procedure.<br />
The ETSI Standstill application allows anyone to view the ETSI Work Items under the perspective of the available Standstill information.<br />
<br />
<br />
<br />
===Imposition and release of standstill===<br />
Following the adoption by the responsible Technical Group of a new Work Item (WI) or the endorsement of a new Work Item(s) identified in the Standardisation Request (WISR) intended to result in an EN or a European standardisation deliverable and prior to the drafting of this standard, ETSI shall notify the NSO/NSB as soon as a decision regarding imposition or release of standstill has been made.<br />
Standstill shall start sixty (60) calendar days after the adoption of the Work Item (WI) or Work Item(s) identified in the Standardisation Request (WISR), or at the start of the work, whichever date comes later.<br />
Standstill remains in force until withdrawal of the EN or the European standardisation deliverable, unless it is released by decision of the ETSI General Assembly.<br />
<br />
===Infringement of standstill===<br />
Standstill is not infringed by:<br />
<br />
# the issue by an NSO/NSB of a draft standard for Public Enquiry intended and designated as a contribution to ISO/IEC and/or CEN/CENELEC/ETSI standardisation;<br />
# the publication by an NSO/NSB, within three (3) months of the start of standstill, of a national standard which that NSO/NSB has already approved;<br />
# the publication by an NSO/NSB, after notifying the ETSI Director-General, of a national standard adopting, without change, a published ITU-T or ITU-R Recommendation or a standard in the field of ETSI's interest prepared by the ISO/IEC, where there is neither an EN nor a European standardisation deliverable already in existence.<br />
<br />
In cases 2) and 3) the NSO/NSB commits itself to aligning the national standard with the eventual EN or European standardisation deliverable, when issued.<br />
<br />
==EN Approval Process (ENAP)==<br />
ETSI may elaborate ENs on proposal from at least four (4) Full and/or Associate members in accordance with the provisions of Article 2.2.1 of the Technical Working Procedure.<br />
These ENs shall be adopted by the eligible NSOs through the [https://www.etsi.org/images/articles/SMP/ENAP_EN.gif ENAP] as specified in Article 13.2 of the Rules of Procedure.<br />
<br />
===Participation to the combined Public Enquiry + Weighted National Voting procedure===<br />
An Approval Procedure (AP) is a national consultation undertaken by each NSO in its country to evaluate the likely acceptance of an EN. The AP period (90 calendar days) may be extended by ETSI on receipt of a justified request from an NSO.<br />
<br />
ETSI undertakes to notify all NSOs the start and end of the AP and to provide access to the relevant EN. The comments, if any, resulting from an AP may be of technical or non-technical nature.<br />
<br />
It is necessary to use the ETSI online [https://portal.etsi.org/webapp/EApproval/ e-Approval] application to cast votes and submit comments. If access to the ETSI servers is denied, please apply for an [https://portal.etsi.org/createaccount#/home ETSI EOL account] or contact [mailto:webvote-contact@etsi.org webvote-contact@etsi.org]. <br />
<br />
Comments shall be submitted using the ETSI dedicated [https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fportal.etsi.org%2FPortals%2F0%2FTBpages%2Fedithelp%2FDocs%2FENAP_or_SRdaP_comments%2520and_resolution_reports.docx%3Fver%3DsSfOWonjMgUJERfSm5DLvQ%253d%253d&wdOrigin=BROWSELINK ENAP or SRdAP comments and resolution report template]. The template is available on the online [https://portal.etsi.org/LoginRedirection.aspx?ReturnUrl=%2fwebapp%2fEApproval%2f e-Approval application home page] (see figure 1) or on the ETSI [https://portal.etsi.org/nso.aspx?tbid=590&SubTB=590#/ NSO] or [https://portal.etsi.org/fcga.aspx?tbid=910&SubTB=910#/ NSBG] Portal page. See clause 4.2.3 for more details.<br />
<br />
[[File:Figure5_NSOs.jpg|frame|Figure 1: e-Approval application (home page)|center]]<br />
<br />
===Participation to the 2nd Weighted National Voting procedure===<br />
A Weighted National Vote is the expression of an opinion resulting from of a national consultation undertaken by each NSO to collect all views expressed in its country on the adoption of a European Standard. <br />
A Weighted National Vote shall be carried out over a period of sixty (60) calendar days.<br />
The Weighted National Vote period may be extended by ETSI on receipt of a justified request from a NSO.<br />
ETSI undertakes to notify all NSOs the start and end of the Weighted National Vote and to provide access to the relevant European Standard.<br />
:::IMPORTANT: When a country is represented by more than one NSO, any of the NSOs have the right to vote but only one vote per country shall be counted as vote cast. Votes may be changed by Official or Voting contact of the same country prior to the closing of the vote. Only the last vote casted before the closing of the Weighted National Vote will be considered.<br />
<br />
===How to submit comments and/or cast votes via the e-Approval application===<br />
The NSO undertakes to carry out the public enquiry in its country and to consider all views expressed in its country before deciding how to cast any votes.<br />
It is essential to consolidate all comments received by the set deadline, using the [https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fportal.etsi.org%2FPortals%2F0%2FTBpages%2Fedithelp%2FDocs%2FENAP_or_SRdaP_comments%2520and_resolution_reports.docx%3Fver%3DsSfOWonjMgUJERfSm5DLvQ%253d%253d&wdOrigin=BROWSELINK ENAP or SRdAP comments and resolution report TEMPLATE].<br />
<br />
[[File:Figure6_NSOs.jpg|frame|center]]<br />
<br />
Some advices for the resolution meeting on dealing with comments collected during the Public Enquiry are given in clause 3.7 of the [https://ocgwiki.etsi.org/index.php?title=Chair%27s_Guide#ENAP_Resolution_meetings ETSI Chair's Guide].<br />
When the template has been duly filled in and/or the decision to cast a vote has been taken, it is time to access the voting tool.<br />
All details on how to submit comments and cast votes on ENAP can be consulted by clicking [https://docbox.etsi.org/NSBG/Guidance%20on%20how%20to%20submit%20comments%20and%20cast%20votes%20(ENAP).pdf HERE].<br />
<br />
==Standardisation Request deliverables Approval Process (SRdAP)==<br />
ETSI may elaborate ENs and European standardisation deliverables in response to SReqs to support the European legislation or policies, in accordance with the amended Regulation (EU) No 1025/2012. These deliverables shall be adopted by the eligible NSBs throughout the [https://www.etsi.org/images/articles/SMP/SRdAP_EN_SRdAP_.gif SRdAP].<br />
<br />
===Participation to the Standardisation Request (SReq) drafting process===<br />
The NSBs, the NSOs and the Annex III organizations, are involved in the ETSI process to comment and/or propose modifications to the working draft SReq text as explained in Articles 20.2 to 20.3.3 of the Rules of Procedure. <br />
<br />
The NSB, the NSOs and Annex III organizations will be requested during a meeting organised by the Secretariat, to submit preliminary comments, on the distributed SReq draft. It is possible to invite whomever necessary within a NSB, NSO and Annex III organisation to this meeting. For discussions concerning the distributed SReq draft, managers or policy officers would be more appropriate but since all organizations are different, this depends on the individual structure and organization. <br />
<br />
[[File:Figure7ab_NSOs.jpg|frame|center]]<br />
<br />
===Acceptance of the Standardisation Request (SReq)===<br />
When the draft of a new Standardisation Request (SReq) is finalised, the NSBG members will be asked to accept or reject the submitted Standardisation Request within twenty-five (25) calendar days.<br />
<br />
During these twenty-five (25) calendars days, each NSBG member may receive comments from the Annex III organizations, the BOARD, OCG members and from the Technical Group. The NSB's national position to adopt or reject the proposed SReq will have to be submitted via the [https://portal.etsi.org/webapp/tbdecision3/Menu.asp#/Voting tool].<br />
<br />
Upon the closure of the voting procedure of the NSBG members, and within thirty (30) calendar days following the reception by ETSI of the official Standardisation Request (SReq), the Director-General, in the name of ETSI, shall notify the EC and EFTA, the appropriate Technical Group(s), the NSBG, the Annex III Organizations and the whole ETSI membership on the decision of the NSBG.<br />
<br />
===Adoption of the WISR(s)===<br />
Upon receipt of the Work Item(s) identified in the Standardisation Request (WISR) and created by the responsible Technical Group, each NSB should be able to express the national position to adopt or reject/change/stop the proposed WISR via the ETSI online [https://portal.etsi.org/LoginRedirection.aspx?ReturnUrl=%2fwebapp%2fEApproval%2f e-Approval] application.<br />
<br />
===Participation to the combined Public Enquiry + Weighted National Voting procedure===<br />
<br />
The Enquiry + Vote (EV) comprises a Public Enquiry (see Article 21.4 of the Rules of Procedure) and a Weighted National Voting procedure (see Article 21.5 of the Rules of Procedure) performed in a combined procedure undertaken by each NSB in its own country to evaluate the likely acceptance of a European Standard or a European standardisation deliverable. See Article 21.2.1 of the Rules of Procedure for full details.<br />
<br />
::'''Important:''' The Enquiry + Vote period (90 calendar days) may be extended by ETSI on receipt of a justified request from a NSB.<br />
<br />
ETSI undertakes to notify all NSBs the start and end dates of the Enquiry + Vote and to provide access to relevant European Standard(s) or European standardisation deliverable(s).<br />
<br />
It is important that comments are submitted using the ETSI dedicated [https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fportal.etsi.org%2FPortals%2F0%2FTBpages%2Fedithelp%2FDocs%2FENAP_or_SRdaP_comments%2520and_resolution_reports.docx%3Fver%3DsSfOWonjMgUJERfSm5DLvQ%253d%253d&wdOrigin=BROWSELINK ENAP or SRdAP comments and resolution report template] (see clause 4.3.6).<br />
<br />
The comments, if any, resulting from an Enquiry + Vote may be of '''technical''' or '''non-technical''' nature.<br />
Guidance and instructions on how to submit comments and cast votes are given in clause 4.3.6.<br />
<br />
For all European Harmonised Standards, when submitting comments or casting a vote, a box called "Translated title" is displayed. <br />
It is the exclusive responsibility of each NSB whose official language is listed below to provide ETSI with the '''translation''' into its own language, via the ETSI online [https://portal.etsi.org/webapp/EApproval/ eApproval application].<br />
<br />
List of official languages (25):<br />
Bulgarian, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Icelandic, Italian, Latvian, Lithuanian, Maltese, Norwegian, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish and Swedish. <br />
<br />
::'''Important:''' In order to have an European Harmonised Standards listed in the OJEU, it is mandatory to have its title translated in all the official languages.<br />
<br />
===Participation to the 2nd Weighted National Voting procedure===<br />
A Vote Adoption is the expression of an opinion resulting from a national consultation undertaken by each NSB to collect all views expressed in its country on the adoption of a European Standard or a European standardisation deliverable. <br />
<br />
A Vote Adoption shall be carried out over a period of sixty (60) calendar days.<br />
<br />
The Vote Adoption period may be extended by ETSI on receipt of a justified request from a NSB.<br />
<br />
ETSI undertakes to notify all NSBs at the start and end of the Vote Adoption and to provide access to the relevant a European Standard or a European standardisation deliverable.<br />
<br />
::'''Important:''' When more than one NSB represent a country, any of the NSBs have the right to vote but only one vote per country shall be counted as vote cast. Votes may be changed by any of the NSBs of the same country prior to the closing of the vote. Only the last vote casted before the closing of the Weighted National Vote will be considered.<br />
<br />
===How to submit comments and/or cast votes=== <br />
The NSB undertakes to carry out the public enquiry in its country and to consider all views expressed in its country before deciding how to cast any votes.<br />
<br />
It is essential to consolidate all comments received by the set deadline, using the [https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fportal.etsi.org%2FPortals%2F0%2FTBpages%2Fedithelp%2FDocs%2FENAP_or_SRdaP_comments%2520and_resolution_reports.docx%3Fver%3DsSfOWonjMgUJERfSm5DLvQ%253d%253d&wdOrigin=BROWSELINK ENAP or SRdAP comments and resolution report TEMPLATE] (see TEMPLATE). <br />
Some advices for the resolution meeting on dealing with comments collected during the Public Enquiry are given in clause 3.7 of the [https://ocgwiki.etsi.org/index.php?title=Chair%27s_Guide#ENAP_Resolution_meetings ETSI Chair's Guide].<br />
<br />
When the template has been duly filled in and/or the decision to cast a vote has been taken, it is time to access the voting tool.<br />
All details on how to submit comments and cast votes on SRdAP can be consulted by clicking [https://portal.etsi.org/Portals/0/TBpages/NSBG/Docs/Guidance%20on%20how%20to%20submit%20comments%20and%20vote.pdf HERE].<br />
<br />
='''Transposition'''=<br />
Each NSO shall take measures to ensure the visibility of European Standards or European standardisation deliverables on a national level:<br />
* by publication of an identical text; or<br />
* by publication of an endorsement (i.e. publication of an endorsement sheet or official announcement) within a short time after its publication by ETSI.<br />
<br />
"Publication of an identical text" means identical in technical content and presentation (except translation) and with no restrictions for application.<br />
"Endorsement" means that it shall be stated that the European Standard or European standardisation deliverable has been approved together with the number, title and date, and location from where copies of the text may be obtained.<br />
<br />
European Standards or European standardisation deliverables thus published or endorsed, shall be given the status of national standards.<br />
It is the responsibility of each NSO to update the [https://portal.etsi.org/webapp/Transposition/home.aspx ETSI Transposition and Withdrawal database]. A [https://portal.etsi.org/webapp/Transposition/manual.aspx?topic=Overview user manual guide] is provided via the tool itself.<br />
<br />
='''Translation'''=<br />
Once a European Standard or European standardisation deliverable has been adopted and published in English as an official standard, it may be translated into another language and published equally as an official version of the standard.<br />
<br />
Each NSO is entitled to translate standards into the language(s) of its own country, in accordance with Article 8 of the [https://etsisign.eu1.echosign.com/public/esignWidget?wid=CBFCIBAA3AAABLblqZhDi5sRNHpzZXSLmat-YMhP7Ocp_1sEYbdRmsjREUEW8uboWsI-7MWrEIGHdU8UfSXo* ETSI-NSO Agreement].<br />
<br />
The costs of all translations of standards shall be covered by the parties interested.<br />
<br />
='''Withdrawal of conflicting national standards'''=<br />
<br />
When an EN on a specific matter has been published by ETSI, the NSOs shall ensure that all conflicting national standards on that specific matter are withdrawn on an agreed date set by the General Assembly.<br />
<br />
='''Tools'''=<br />
<br />
==ETSI online e-Approval application==<br />
ETSI NSOs and NSBs are authorized to cast votes and submit comments electronically using the ETSI online [https://portal.etsi.org/webapp/Transposition/manual.aspx?topic=Overview e-Approval] application.<br />
<br />
The ETSI Technical Groups can consult the submitted comments on ETSI European Standards and European standardisation deliverables as soon as an approval procedure is launched. The casted votes are made available at the closure of the approval procedure.<br />
<br />
==ETSI Work Programme==<br />
<br />
The [https://portal.etsi.org/webapp/WorkProgram/SimpleSearch/QueryForm.asp ETSI Work Programme] application is an application which contains all the information needed with regard to the documents’ version number, title, keywords, status and much more.<br />
<br />
It provides an easy way to search for ETSI standards by running dynamic database queries.<br />
To download the document, just click on the corresponding download standard icon (on the top right-hand side). Depending on the status as an ETSI member or non ETSI member, one has the option of downloading either the Word® or the PDF version.<br />
<br />
This application allows to download individual copies of ETSI publications free of charge.<br />
<br />
If further help is needed, please contact us at [mailto:webvote-contact@etsi.org webvote-contact@etsi.org].<br />
<br />
==European Standards compared versions==<br />
<br />
A list can be obtained of the most recent [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Partners/nso/Compared_ENs/AP ENs sent on approval compared] with the previous published version of the same European Standard (if any).<br />
<br />
These documents are made available in order to facilitate the comprehension of the changes made between the two versions.<br />
In the same spirit, a list of the latest versions of published [https://portal.etsi.org/Services/editHelp/To-help-you-in-your-work/Services/HS-compared-versions European Harmonised Standards compared with the previous versions] is made available.<br />
<br />
==Metadata==<br />
<br />
ETSI makes information related to the production of deliverables accessible via its website at [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Metad/ https://docbox.etsi.org/Meta/].<br />
<br />
{|<br />
| • WI number || • Schedule/milestones<br />
|-<br />
| • Type and document number|| • Mandates if any<br />
|-<br />
| • Version number|| • HS or not<br />
|-<br />
| • Procedures/Actions (all)|| • Scope||<br />
|-<br />
| • Title || • Keywords||<br />
|-<br />
| • Technical Body || • Stage codes||<br />
|}<br />
<br />
What is listed above are the weekly collected information of the published ETSI Deliverables, called "metadata", which are made available at [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Metad/Weekly_Pub/ https://docbox.etsi.org/Metad/Weekly_Pub/]. <br />
<br />
They are produced to be imported into electronic tools/applications that any NSOs may wish to develop in order to circulate information in an efficient way, without having to manually record the data for each deliverable recently produced. <br />
<br />
DKE has kindly accepted to share their experience in order to explain how the metadata can be used. DKE uses these metadata to circulate information among their experts in national standardization committees. DKE automatically imports the metadata in their own database every week. Metadata from IEC and CENELEC can also be fed in the same tool. After importing the metadata, deliverables can be found in a personalized display of the application. The documents are already allocated to the national mirror committees. Here is an example of the result where DKE/K 738 is the national mirror to ETSI/ERM TG MARINE. Consequently, EN 300 338-7 Final Draft Version 1.1.0:2022-02 has been circulated in this committee. The external experts can perform a single or group download. Users can also get notification emails which can be customized.<br />
<br />
[[File:Figure8_NSOs.jpg|frame|center]]<br />
<br />
This is the internal view that shows where the circulation is done.<br />
<br />
[[File:Figure9_NSOs.jpg|frame|center]]<br />
<br />
Any tool/application can be automatically fed. To do so, it is necessary to create an automatic bulk download. This is something that needs to be put in place by the NSO IT service. ETSI IT can help if necessary. <br />
These metadata are password protected. For this reason, it is necessary to log in to access the information. If any difficulties are encountered when accessing the file, please contact us at [mailto:webvote-contact@etsi.org webvote-contact@etsi.org].<br />
<br />
='''FAQ - Frequently Asked Questions'''=<br />
==Where can I find the Technical Group resolution report?==<br />
<br />
When an action is closed; the Technical Group Chair shall complete the Technical Group resolution meeting report to identify the decision taken in the Technical Group for each submitted comment. Then the report is uploaded on the ETSI online e Approval application.<br />
<br />
<br />
[[File:Figure10_NSOs.jpg|frame|center]]<br />
<br />
==What does "Under comments assessment" means?==<br />
<br />
When "Under comments assessment" appears when searching for a closed action, it means that comments have been submitted during the approval process, and the Technical Officer has not yet finalised the categorization assessment.<br />
<br />
[[File:Figure11_NSOs.jpg|frame|center]]<br />
<br />
If a comment categorized as "non-technical" implies technical changes, the NSO who has submitted the comment, can be contacted to discuss the nature of the comment. When all comments have been carefully checked by the Technical Officer/Technical Group, the validation is made, and the results are displayed, and all parties are informed.<br />
<br />
==What are the existing mailing lists and what are their purposes?==<br />
<br />
The main mailings list has been made available via the [https://portal.etsi.org/TB-SiteMap/NSO/NSOs-toolkit toolkit] made available on the [https://portal.etsi.org/nso.aspx?tbid=590&SubTB=590#/ NSO] and [https://portal.etsi.org/fcga.aspx?tbid=910&SubTB=910#/ NSBG] home page.<br />
<br />
===ANNEX_III===<br />
<br />
This email distribution list is used by the Secretariat to spread information related to the Standardisation Request deliverable Approval Process (SRdAP) to all Annex III Organisations contacts. This email distribution list is manually maintained. All emails sent to the list are archived and made available [https://list.etsi.org/scripts/wa.exe?A0=ANNEX_III here] (depending on access rights).<br />
<br />
===DELIVERABLE-NOTIFICATIONS===<br />
This email distribution list is used by ETSI Secretariat to weekly send notifications to all NSO Official and Voting Contacts. [https://webapp.etsi.org/deliverables/Subscribe.asp Additional subscription may be done by clicking here]. A link is also provided via the ETSI [https://portal.etsi.org/TB-SiteMap/NSO/NSOs-toolkit NSO toolkit] made available on the [https://portal.etsi.org/nso.aspx?tbid=590&SubTB=590#/ NSO] and [https://portal.etsi.org/fcga.aspx?tbid=910&SubTB=910#/ NSBG] Portal page.<br />
<br />
Notification sent to the list subscribers to inform about the ETSI Deliverables which have been published or sent on procedure during the past week. All emails sent to the list are archived and made available [https://list.etsi.org/scripts/wa.exe?A0=DELIVERABLE-NOTIFICATIONS here].<br />
<br />
===ETSI NSB_INFO===<br />
This email distribution list is used by ETSI Secretariat to spread information to all the NSB Official and Voting Contacts. Any subscribers to this distribution list can also post to the list to share information. This email distribution list is automatically and dynamically updated every day. <br />
<br />
Official and Voting contacts details are taken from the ETSI Directory Services. For the people manually added to the list, a yearly update is launched by the Secretariat. The list can be manually updated on request at any time, when needed. All emails sent to the list are archived and made available [https://list.etsi.org/scripts/wa.exe?A0=NSB_INFO here].<br />
:::NOTE: Should a new name be subscribed to this list please contact [mailto:webvote-contact@etsi.org webvote-contact@etsi.org].<br />
<br />
===ETSI NSO_TRANSLATORS===<br />
This mailing list is used by the Secretariat to inform specific people from the NSB responsible for providing title translations of European Harmonised Standard about the opening of a new Enquiry + Vote (EV) or 2nd Weithed National Vote (VA).<br />
:::NOTE: Should a new name be subscribed to this list please contact [mailto:webvote-contact@etsi.org webvote-contact@etsi.org].<br />
<br />
===Information of ENAP process===<br />
Notifications are sent to the subscribers of this list when an ETSI European Standard is registered by the Secretariat for submission to an approval procedure in the coming weeks.<br />
:::NOTE: Should a new name be subscribed to this list please contact [mailto:webvote-contact@etsi.org webvote-contact@etsi.org].<br />
<br />
===NSB-CONTACTS===<br />
This email distribution list is used by the Secretariat to spread information related to the Standardisation Request deliverable Approval Process (SRdAP) to all the NSBs Official and Voting Contacts. This email distribution list is automatically and dynamically updated every day, with the details contained in the ETSI Directory Services. All emails sent to the list are archived and made available [https://list.etsi.org/scripts/wa.exe?A0=NSB-CONTACTS here] (depending on access rights).<br />
<br />
===NSO-CONTACTS===<br />
This email distribution list is used by the Secretariat to spread information related to the EN Approval Process (ENAP) to all the NSOs Official and Voting Contacts. This email distribution list is automatically and dynamically updated every day, with the details contained in the ETSI Directory Services. All emails sent to the list are archived and made available [https://list.etsi.org/scripts/wa.exe?A0=NSO-CONTACTS here] (depending on access rights).<br />
<br />
='''Definition of terms & abbreviations'''=<br />
<br />
For the purposes of the present document, the following terms and abbreviations apply:<br />
<br />
'''Annex III Organizations:''' the European stakeholder organizations defined in the Annex III of the amended Regulation (EU) No 1025/2012.<br />
<br />
'''Consensus:''' a general agreement, characterized by the absence of sustained opposition to substantial issues by any important part of the concerned interest and by a process that involves seeking to take into account the views of all parties concerned and to reconcile any conflicting arguments. Consensus need not imply unanimity.<br />
<br />
'''EN Approval Process (ENAP):''' the process consisting of a combined Public Enquiry (PE) and, at least, one Weighted National Voting (WNV) procedure performed by the National Standards Organizations (NSOs) in a single process used to adopt a European non-Harmonised Standard.<br />
<br />
'''ETSI Deliverable:''' a document (SR, GR, GS, TR, TS, EG, ES or EN); or, in previous nomenclature, ETS, I ETS, ETR, TBR, TCR-TR or TC-TR) produced by ETSI as the result of an ETSI Work Item (WI).<br />
<br />
'''ETSI Guide (EG):''' an ETSI Deliverable, containing only informative elements, approved for publication by the ETSI members via the MAP.<br />
<br />
'''ETSI-On-Line (EOL) account:''' a set of credentials delivered by ETSI allowing a user to be authenticated to access a number of ETSI IT services. <br />
<br />
'''ETSI Standard (ES):''' an ETSI Deliverable, containing normative provisions, approved for publication by the ETSI members via the ETSI Membership Approval Process (MAP).<br />
:::NOTE: If the ES is elaborated in response to a Standardisation Request (SReq), it is then adopted for publication by the National Standardisation Bodies via the ETSI Standardisation Request deliverable Approval Procedure (SRdAP).<br />
<br />
'''ETSI Partnership Project (EPP): '''an activity established when there is a need to co operate with external bodies and where such co operation cannot be accommodated within an ETSI Project or Technical Committee.<br />
<br />
'''ETSI Project (EP):''' an activity aiming to achieve a well-defined result within a specific time frame, with a set of well-defined resources and focused on a set of ETSI Work Items (WIs). An ETSI Project is relatively self contained and has its own project management. ETSI members only may participate to the activity of an EP.<br />
<br />
'''European Standard (EN): '''an ETSI Deliverable containing normative provisions, approved for publication by the National Standards Organizations (NSOs) by application of the ENAP.<br />
<br />
'''Harmonised Standard (HS):''' a European Standard adopted on the basis of a Standardization Request made by the EC for the application of Union harmonisation legislation, approved for publication by the National Standardisation Bodies (NSBs) by application of the Standardization Request deliverables Approval Procedure (SRdAP).<br />
<br />
:::NOTE: For ETSI Deliverables in previous nomenclatures, consult Annex A.4 of the ETSI Technical Working Procedures (TWP).<br />
<br />
'''European standardisation deliverables: '''any other technical specification than a European standard, adopted by a European standardisation organization for repeated or continuous application and with which compliance is not compulsory.<br />
<br />
'''Gross Domestic Product (GDP):''' sum of gross value added by all resident producers in the economy plus any product taxes and minus any subsidies not included in the value of the products.<br />
<br />
:::NOTE: Definition of the World Bank available from [https://datacatalog.worldbank.org https://datacatalog.worldbank.org].<br />
<br />
'''Group Report (GR):''' an ETSI Deliverable, containing only informative elements, produced and approved for publication by an ISG.<br />
<br />
'''Group Specification (GS):''' an ETSI Deliverable, containing normative provisions, produced and approved for publication by an ISG.<br />
<br />
'''Head of National Delegation:''' person appointed by a National Delegation, and notified to the Director-General, to hold the role. The Head of National Delegation shall be appointed amongst the representatives of the organizations forming the National Delegation.<br />
<br />
'''Industry Specification Group (ISG):''' an activity organized within a specific time frame, around a set of ETSI WIs addressing a specific technology area and supplementing the existing standards development process. ETSI members and non-ETSI members may participate to the activity of an ISG.<br />
<br />
'''Special Report (SR):''' an ETSI Deliverable, containing only informative elements made publicly available for reference purposes.<br />
An SR may be produced and approved respectively by:<br />
* an ETSI Technical Body (TB);<br />
* an ad-hoc group of the General Assembly (GA), Board or Operational Coordination Group (OCG);<br />
* the ETSI Director-General on behalf of the General Assembly, Board or OCG.<br />
<br />
:::NOTE: If the ES is elaborated in response to a Standardisation Request (SReq), it is then adopted for publication by the National Standardisation Bodies Group via the ETSI Standardisation Request deliverable Approval Procedure (SRdAP).<br />
<br />
'''Membership Approval Process (MAP):''' approval process consisting of Weighted Individual Voting by Full and Associate members, used for the approval of an ES or an EG (see Articles 11.2.2, 11.3 and 14 of the Rules of Procedure).<br />
<br />
'''National delegation:''' group formed by representatives of Full member organizations registered in the same country.<br />
<br />
'''National Standards Body (NSB):''' a National Standards Organization (NSO) which is listed by the EC in the OJEU, as per Article 27 of the amended Regulation (EU) No 1025/2012.<br />
<br />
'''National Standards Bodies Group (NSBG):''' the ETSI decision-making body composed of the National Standardisation Bodies (NSOs). The NSB Group is a subset of the National Standards Organization Group (NSOG).<br />
<br />
'''National Standards Organizations (NSO):''' organizations whose function is to carry out at national level the activities related to Standstill, Public Enquiry, establishment of the national position for the vote on draft European Standards as well as the transposition and withdrawal of national standards. These organizations are recognized by their governments as being authorized to make those standards available to the public at the national level.<br />
<br />
'''National Standards Organizations Group (NSOG):''' the ETSI decision-making body composed of the National Standards Organizations (NSOs), from CEPT countries, which have signed the ETSI-NSO Agreement.<br />
<br />
'''Public Enquiry (PE):''' the national consultation undertaken by a National Standards Organization (NSO) to evaluate the likely acceptance or withdrawal of a European Standard (EN).<br />
<br />
'''Standardisation Request (SReq):''' a request (mandate) from the European Commission to the European Standards Organizations (ESOs) to draw up and adopt European Standards or European standardization deliverables in support of European policies and legislation. <br />
<br />
'''Standardization Request deliverable Approval Process (SRdAP):''' the process consisting of a combined Public Enquiry (PE) and, at least, one Weighted National Voting (WNV) procedure performed by the National Standardisation Bodies in a single process used to adopt a European Standard (EN) or a European standardisation deliverable requested by the EC/EFTA SReq.<br />
<br />
'''Technical comment: '''a comment which proposes a technical change in an ETSI Deliverable.<br />
A technical change is one which, implicitly or explicitly, adds, removes or modifies provisions of the deliverable.<br />
<br />
:::NOTE: Technical changes can result in modified behaviour of equipment or systems designed to be conformant to that deliverable.<br />
<br />
'''Technical Committee (TC):''' an activity organized around a set of ETSI WIs addressing a specific technology area that may contribute to more than one Technical Group and which provides continuity. ETSI members only may participate to the activity of a TC.<br />
<br />
'''Technical Group:''' a Technical Committee (TC), an ETSI Project (EP), an ETSI Partnership Project (EPP), a Special Committee (SC) or an Industry Specification Group (ISG).<br />
<br />
'''Technical Report (TR):''' an ETSI Deliverable, containing only informative elements, produced and approved for publication by a TB.<br />
<br />
'''Technical Specification (TS):'''an ETSI Deliverable, containing normative provisions, produced and approved for publication by a TB.<br />
<br />
'''Weighted National Voting (WNV):''' the vote cast to express the national position of a country (following a national consultation) for the adoption or withdrawal of a European Standard or a European standardisation deliverable.<br />
<br />
'''WISR:''' Work Item (WI) created in response to a Standardisation Request.<br />
<br />
'''Work Item (WI):''' a description of a standardization task.<br />
<br />
'''[https://portal.etsi.org/webapp/WorkProgram/Expert/QueryForm.asp ETSI Work Programme (EWP)]''': the complete set of ETSI Work Items.</div>Raffyhttps://help.etsi.org/index.php?title=NSO_GuideNSO Guide2024-02-15T13:57:53Z<p>Raffy: Created page with "='''Introduction'''= This guide provides a step-by-step guidance on the essential elements, most common practices and responsibilities of the National Standards Organizations (NSOs) and National Standardisation Bodies (NSBs). An NSO is an organization that develops, maintains and coordinates voluntary standardization activities in a particular country. NSOs typically represent the interests of various stakeholders, including businesses, consumers, academia and governme..."</p>
<hr />
<div>='''Introduction'''=<br />
<br />
This guide provides a step-by-step guidance on the essential elements, most common practices and responsibilities of the National Standards Organizations (NSOs) and National Standardisation Bodies (NSBs).<br />
<br />
An NSO is an organization that develops, maintains and coordinates voluntary standardization activities in a particular country. NSOs typically represent the interests of various stakeholders, including businesses, consumers, academia and government.<br />
<br />
An NSB is an NSO from the European Economic Area and thus from one of the following countries: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, The Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain or Sweden.<br />
<br />
The information contained in this guide is based on the Rules of Procedure (RoP) and Technical Working Procedure (TWP) contained in the [https://portal.etsi.org/Resources/ETSI-Directives ETSI Directives], the European Commission Regulations (EU) [https://eur-lex.europa.eu/legal-content/FR/TXT/?uri=celex%3A32012R1025 N° 1025/2012], and amendment [https://eur-lex.europa.eu/eli/reg/2022/2480/oj N° 2022/2480] and also on the [https://etsisign.eu1.echosign.com/public/esignWidget?wid=CBFCIBAA3AAABLblqZhDi5sRNHpzZXSLmat-YMhP7Ocp_1sEYbdRmsjREUEW8uboWsI-7MWrEIGHdU8UfSXo* ETSI-NSO Agreement].<br />
<br />
=='''Roles'''==<br />
=The NSO/NSB Official Contact=<br />
The Official Contact is the person designated by the NSO to be the main contact person between ETSI and the NSO. <br />
There is only one Official Contact per NSO, ensuring that all the contact details within the organization are correctly registered in the ETSI Directory Services application. Contact details can be consulted via the [https://portal.etsi.org/LoginRedirection.aspx?ReturnUrl=%2fwebapp%2fTeldir%2f Directory Services] page.<br />
<br />
[[File:Figure1_NSOs.jpeg|left|caption]]<br />
[[File:Figure2_NSOs.jpeg|right|caption]]<br />
[[File:Figure3_NSOs.jpeg|right|caption]]</div>Raffyhttps://help.etsi.org/index.php?title=ETSI_Standards_Making_Process_GuideETSI Standards Making Process Guide2024-02-14T14:24:18Z<p>Raffy: /* Working methods */</p>
<hr />
<div>='''ETSI Deliverables'''=<br />
Work in ETSI is done on the basis of ETSI work items, approved by the Technical Body and adopted by the ETSI membership.<br />
A work item results in one deliverable (sometimes more than one), which can be a European Standard or a Technical Specification, an ETSI Guide or a Technical Report.<br />
ETSI has a suite of specifications, standards and reports that fulfil the various needs of the market:<br />
<br />
* ETSI EN (European Standard) - adopted by ETSI National Standards Organizations (NSOs) (except those elaborated in response to a Standardisation Request (SReq)).<br />
* ETSI European standardisation deliverables – adopted by ETSI National Standardisation Bodies (NSBs).<br />
* ETSI TS (ETSI Technical Specification) and ETSI TR (ETSI Technical Report) - adopted by the responsible Technical Group (except those elaborated in response to a Standardisation Request (SReq)).<br />
* ETSI ES (ETSI Standard) and ETSI EG (ETSI Guide) - adopted by ETSI Members (except those elaborated in response to a Standardisation Request (SReq)).<br />
* ETSI SR (ETSI Special Report) - adopted by the ETSI responsible Technical Group (except those elaborated in response to a Standardisation Request (SReq)).<br />
* ETSI GS (ETSI Group Specification) and GR (ETSI Group Report) - adopted the responsible Industry Specification Group.<br />
<br />
:::NOTE: The skeletons of each specification are available [https://portal.etsi.org/Services/editHelp/Standards-development/Drafting/Skeletons here].<br />
<br />
This suite of deliverables fulfils the needs for:<br />
* Deliverable intended to meet needs specific to Europe and requiring transposition into national standards - ETSI EN.<br />
* Deliverable intended to meet needs specific to the Europe Economic Area (EEA), required under a Standardisation Request (SReq) from the European Commission (EC)/European Free Trade Association (EFTA) – ETSI EN and European standardisation deliverable.<br />
* Deliverable providing technical requirements or explanatory material or both – ETSI GS.<br />
* Deliverable containing only informative elements – ETSI GR.<br />
* High quality specifications delivered early to the market - ETSI TS.<br />
* High quality standards supported by the whole ETSI global membership - ETSI ES.<br />
* Deliverable containing explanatory material – ETSI TR.<br />
* Information document used for various purposes, including giving public availability to information not produced within a Technical Group – ETSI SR.<br />
* Document elaborated by ETSI partners and adopted by ETSI, to become an ETSI Technical Specification (TS) or an ETSI Technical Report (TR) - Publicly Available Specification (PAS).<br />
<br />
:::NOTE: For more information, please read about PASs in our [https://www.etsi.org/about/our-partnerships Partnerships section].<br />
<br />
The numbering convention used by ETSI to link related documents at these various "levels" simplifies their market application.<br />
<br />
='''Process'''=<br />
<br />
<br />
<br />
[[File:Figure1_SMP.jpeg|center|caption]]<br />
<br />
<br />
The Standards Making Process (SMP) is the process applied for the Technical Organization's production of standards and deliverables and the Secretariat's involvement in and interaction with the Technical Organization, the ETSI members and the ETSI National Standards Organizations.<br />
The general conditions for the SMP are defined by the ETSI Directives, in particular the Technical Working Procedures. The Secretariat's tasks and activities in SMP are primarily defined in the Quality Management System (QMS) documentation of ETSI Operations (OPS) Division.<br />
<br />
==Process overview==<br />
''[process - a structured, measured set of activities designed to produce a specified output]''<br />
<br />
The objective of the ETSI Standards Making Process (SMP) is to convert market needs for standardization in the ICT area into ETSI deliverables (specifications, standards, norms, guides, reports) used in the market place.<br />
The input to the process is an existing (as yet known or unknown) market need for standardization. The output is the broad application of the produced deliverables in the market place.<br />
The SMP consists of five main elements, sub-processes, with their own distinct objectives, inputs and outputs. Each sub-process is defined to the level of which operational tasks are performed, and where in the ETSI organization they are performed.<br />
The whole ETSI organization is in one way or the other involved in either operation of the SMP or in direct or indirect support of it. The main technical activities are performed in the Technical Groups of the Technical Organization. The main direct support to those activities is provided by ETSI Operations (OPS) and ETSI Standardization Service (STS) Divisions of the ETSI Secretariat.<br />
The operation of the SMP in the Technical Organization is governed by the ETSI Directives, in particular the Technical Working Procedures, and the ETSI Drafting Rules. The processes, tasks and procedures of the ETSI Secretariat are governed by the Secretariat's Quality Management System documentation, notably that of ETSI Operations (OPS) and ETSI Standardization Service (STS) Divisions.<br />
<br />
==Inception==<br />
''[inception - an act, process, or instance of beginning (as of an institution, organization, or concept)]''<br />
<br />
The times when initiatives to standardization were taken only when products and services were already available are since long gone. This is particularly the case for telecommunications where standardization precedes or goes hand in hand with the design and development processes.<br />
The input to this sub-process is "what's going on in the marketplace", with "marketplace" having a broad interpretation, including development in the research and academic circles.<br />
The output is a new standardization area, given to an existing or a new Technical Group. The formal output is the Terms of Reference (ToR) and/or a Project Requirements Definition (PRD) document, approved by the ETSI Board or, in the case of an ETSI Partnership Project with an external organization, approved by the ETSI General Assembly.<br />
<br />
==The process itself consists, in broad terms, of:==<br />
*Identifying needs for standardization in the subject areas defined by the ETSI Statutes and Rules of Procedure.<br />
*Defining the suitable organization for such standardization within ETSI.<br />
==There are various actors in this process:==<br />
* Experts in the Technical Bodies, Special Committees and ISGs.<br />
* ETSI Members.<br />
* Supported by OPS Technical Officers and staff from Innovation.<br />
<br />
==Conception==<br />
''[conception - the capacity, function, or process of forming ideas or abstractions or of grasping the meaning of symbols representing such ideas or abstractions; an idea or general notion; the originating of something (as an idea or plan) in the mind].''<br />
<br />
The creation of a new standardization area or ISG is manifested by the establishment of the new Technical Group or the amendment of the Terms of Reference of the Project Requirements Definition of an existing.<br />
The identification, definition, approval and adoption of work items are the main elements of the conception phase (even if work items may have been envisaged already during the inception process).<br />
The input is identified standardization needs in the area. These work items may either be entirely new, leading to new deliverables, or a new version of an existing deliverable ("maintenance work item").<br />
The output is a work item, adopted by the ETSI Membership for ETSI deliverables created on proposal for Full or Associate members.<br />
A proposal for a work item may come from inside or outside the Technical Group. The Technical Group may approve the work item, if at least four ETSI Members volunteer to support the work (except those in response to a Standardisation Request (WISR)). The adoption is formally done by the ETSI Membership, except those in response to a Standardisation Request (WISR). The existence of new work items is made known via the ETSI Web site and Members who disagree with the item may within a 30-day period oppose its adoption into the ETSI Work Programme.<br />
ETSI may elaborate European Standards and European standardisation deliverables in response to Standardisation Requests to support the European legislation or policies, in accordance with the amended Regulation (EU) No 1025/2012.<br />
As per Article 20.4 of the Rules of procedure, it is the responsibility of the National Standardisation Bodies (NSB) to adopt a new WISR created by the responsible Technical Group in response to a Standardisation Request (SReq).<br />
For full details see clauses 1.6.3 (Adoption of a Work Item) and 1.7 (Decision-making in a Technical Group of the Technical Working Procedures.<br />
==Drafting==<br />
''[drafting - to make a preliminary or tentative version, sketch, or outline (as of a literary composition or other document)].''<br />
<br />
A work item in the ETSI Work Programme is intended to lead to one (or more) ETSI deliverable(s).<br />
A Technical Group is free to organize its work in any way it wishes, within the rules of the Technical Working Procedures, including create Working Groups to which the tasks of drafting parts of the Technical Group's work programme are given.<br />
The drafting usually takes place in a small team (Rapporteur group) led by a Rapporteur. The work is largely done by "correspondence", i.e. by exchange of documents via the ETSI DocBox server and LISTSERV email exploder facilities.<br />
When the draft by the Rapporteur group is considered ready, the draft deliverable is handed over to the Working Group (when it exists) for approval. The formal approval for further processing or, in the case of ETSI Technical Specifications or ETSI Technical Reports, approval and adoption can only be done by the Technical Group, either at a meeting or by correspondence.<br />
Some drafting activities for a Technical Group are performed by Specialist Task Forces (STF)/Testing Task Forces (TTF) located at the ETSI Secretariat.<br />
The adaptation of specifications from external bodies (Publicly Available Specifications (PAS)) to the ETSI deliverable structure follows the same rules, but will normally be performed by the PAS provider, as defined in the Guidelines for adoption of Publicly Available Specifications.<br />
==Adoption==<br />
''[adoption - the act or process of adopting someone or something, such as: the act or process of giving official acceptance or approval to something]''<br />
<br />
While the drafting process is, in principle, the same for all ETSI deliverables, the process elements of the adoption process depend on the type of deliverable being processed.<br />
<br />
==='''ETSI Group Specification, ETSI Group Report, ETSI Special Report, ETSI Technical Specification and ETSI Technical Report''' ===<br />
*'''For ETSI Group Specification (GS), ETSI Group Report (GR), ETSI Special Report (SR), ETSI Technical Specification (TS) and ETSI Technical Report (TR) elaborated on proposal from Full and Associate members:''' <br />
:The Technical Group draft approval and adoption take place at the same time (one combined decision).<br />
:The Publication process element consists of publishing in PDF format and archiving. The published deliverable will then be made available for distribution via the ETSI Web server.<br />
<br />
[[File:Figure2_SMP.jpeg|center]]<br />
<br />
<br />
:For full details see clauses 2.2.4 (TS and TR approval procedures), 2.2.6 (SR approval procedure) and 2.2.7 (GS and GR approval procedures) of the Technical Working Procedures contained in the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives].<br />
<br />
*'''For ETSI Technical Specifications (TS), ETSI Special Report (SR) and ETSI Technical Reports (TR) elaborated in response to a Standardisation Request (SReq), also called European standardisation deliverables:'''<br />
:They shall be adopted by application of the Standardisation Request deliverables Approval Process (SRdAP) specified in clause 2.2.2.1.1 of the ETSI Technical Working Procedures contained in the ETSI Directives.<br />
:After the Technical Group draft endorsement, the NSBs shall perform a Public Enquiry (see Article 21.4 of the Rules of Procedure) and at least one (1) Weighted National Voting procedure (see Article 21.5 of the Rules of Procedure contained in the ETSI Directives) performed in a combined procedure via a Web browser interface (e-Approval application), over a period of 90 calendar days. If this vote is successful, and if no substantial comments are received as a result of this consultation, the European standardisation deliverable is published. <br />
:The deliverable is adopted if at least 71 % of the weighted NSBs’ votes cast are in favour and at least a quorum of fifty percent (50%) participation of NSBs is reached.<br />
:The Publication process element consists of publishing in PDF format and archiving. The published deliverable will then be made available for distribution via the ETSI Web server.<br />
<br />
[[File:Figure3_SMP.jpeg|center]]<br />
<br />
<br />
<br />
==='''ETSI Standard and ETSI Guide'''===<br />
After Technical Group draft approval, the draft ETSI Standard (ETSI ES) or ETSI Guide (ETSI EG) elaborated on proposal from Full and Associate members is made available to the ETSI Membership (Full and Associate members) for voting in accordance with the Membership Approval Procedure (MAP) defined in clause 2.2.3 (ES – EG approval procedures) of the Technical Working Procedures contained in the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives]. <br />
<br />
Voting is done via a Web browser interface (e-Approval application). The voting period is 60 calendar days (in compliance with World Trade Organization timing requirement). <br />
The deliverable is adopted if at least 71 % of the weighted member votes cast are in favour of the draft (there are no quorum requirements).<br />
The Publication process element consists of publishing in PDF format and archiving. The published deliverable will then be made available for distribution via the ETSI Web server.<br />
<br />
[[File:Figure4_SMP.jpeg|center]]<br />
<br />
<br />
After Technical Group draft approval, the draft ETSI Standard (ETSI ES) or ETSI Guide (ETSI EG) elaborated in response to a Standardisation Request (SReq) is made available to the ETSI Membership (Full and Associate members) for endorsement by ETSI Membership Approval Process (MAP) defined in in clause 2.2.3 Technical Working Procedures contained in the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives]. Voting is done via a Web browser interface (e-Approval application). <br />
The consultation and voting period is 60 calendar days (in compliance with World Trade Organization timing requirement). The deliverable is endorsed if at least 71 % of the weighted member votes cast are in favour of the draft (there are no quorum requirements).<br />
<br />
After the Technical Group draft endorsement, the NSBs shall perform a Public Enquiry (see Article 21.4 of the Rules of Procedure) and at least one (1) Weighted National Voting procedure (see Article 21.5 of the Rules of Procedure contained in the ETSI Directives) performed in a combined procedure via a Web browser interface (e-Approval application), over a period of 90 calendar days. If the vote is successful, and if no substantial comments are received as a result of this consultation, the European standardisation deliverable is published.<br />
<br />
The deliverable is adopted if at least 71 % of the weighted NSBs’ votes cast are in favour and at least a quorum of fifty percent (50%) participation of NSBs is reached.<br />
The Publication process element consists of publishing in PDF format and archiving. The published deliverable will then be made available for distribution via the ETSI Web server.<br />
<br />
==='''ETSI European Standard (EN)'''===<br />
<br />
European Standards (ETSI EN) elaborated on proposal from Full and Associate members, shall be adopted by application of the European Standard Approval Process (ENAP) specified in clause 2.2.1.1.1 of the Technical Working Procedures contained in the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives].<br />
After Technical Group draft approval, the draft ETSI EN is made available to the by the eligible members of the National Standards Organizations Group (NSOG) as per Article 13.2.1 of the Rules of Procedure contained in the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives] for adoption.<br />
<br />
The NSOs shall perform the Public Enquiry (PE) and and at least one (1) Weighted National Voting procedure (see Article 13.4 and 13.5 of the Rules of Procedure contained in the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives]), performed in a combined procedure via a Web browser interface (e-Approval application), over a period of 90 calendar days.<br />
Without any technical comment and after successful Vote (Articles 11.3, 12.2 and 13.5.1 of the Rules of Procedure), the draft is then submitted to the ETSI Secretariat and providing it complies with the ETSI Drafting Rules (EDRs), it is published within 10 calendar days following the Vote.<br />
<br />
In the event that technical comments have been submitted, the result of the Weighted National Voting procedure shall be ignored, and the comments shall be discussed by the responsible Technical Group during the planned resolution meeting, within a period of 30 days. If significant changes have been made, the TG Chair may decide that the revised draft shall be submitted to another Enquiry + Vote procedure, otherwise it may be presented for direct use of a second (2) Weighted National Voting procedure (60 calendar days) of the ENAP. After a successful vote, the Secretariat publishes the standard within 10 calendar days.<br />
<br />
The Publication process element consists of publishing in PDF format and archiving. The published deliverable will then be made available for distribution via the ETSI Web server.<br />
<br />
<br />
[[File:Figure5_SMP.jpeg|center]]<br />
<br />
<br />
European Standards (ETSI EN) '''elaborated in response to a Standardisation Request (SReq)''', shall be adopted by application of the Standardisation Request deliverables Approval Process (SRdAP) specified in Article 2.2.1.1.1 of the Technical Working Procedures contained in the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives]<br />
<br />
After Technical Group draft approval, the draft ETSI EN is made available to the NSBs (National Standardisation Bodies) for adoption.<br />
<br />
The NSBs shall perform the Public Enquiry (PE) and at least one (1) Weighted National Voting procedure (see Articles 21.4 and 21.5 of the Rules of Procedure contained in the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives]), performed in a combined procedure via a Web browser interface (e-Approval application), over a period of 90 calendar days. <br />
<br />
The deliverable is adopted if no technical comments have been submitted, at least 71 % of the weighted NSBs’ votes cast are in favour, and at least a quorum of fifty percent (50%) participation of NSBs is reached (Articles 11.3, 12.2 and 13.5.1 of the Rules of Procedure). The draft is then submitted to the ETSI Secretariat and providing it complies with the ETSI Drafting Rules (EDRs), it is published within 10 calendar days following the Vote.<br />
<br />
If technical comments are received, the Technical Group Chair shall, within a period of 30 days, organize the resolution of the comments received, the preparation of a revised draft, approval of the revised draft at TG level, and submission of the revised draft and resolution report to the ETSI Secretariat. If significant changes have been made, the TB Chair may decide that the revised draft shall be submitted to another Approval Process otherwise it may be presented for direct use of the voting step (60 days) of the SRdAP. After a successful vote, the Secretariat publishes the standard within 10 calendar days.<br />
<br />
The Publication process element consists of publishing in PDF format and archiving. The published deliverable will then be made available for distribution via the ETSI Web server.<br />
<br />
[[File:Figure6_SMP.jpeg|center]]<br />
<br />
In order to make the results of the work of the Technical Group available to the market at an early stage, some of the above processes may be combined in such a way that two deliverables with identical content are processed/published in parallel.<br />
<br />
For example, if the intention is to publish the draft as an ETSI EN, but only after application of the EN Approval Procedure (ENAP) or Standardisation Request deliverables Approval Process (SRdAP), the editing of the ETSI EN (sub-process Editing prior to Public Enquiry) also covers the Publication of an ETSI TS with identical contents.<br />
<br />
Parallel ETSI ES and ETSI TS processing is also possible, but the time gain in this case is less pronounced.<br />
<br />
:::NOTE: Detailed rules for the approval procedures described above may be found in the Technical Working Procedures (TWP).<br />
<br />
='''Promotion'''=<br />
''[promotion - the act of setting up or furthering a business enterprise; active furthering of sale of merchandise through advertising or other publicity]''<br />
<br />
The promotion activities address three main objectives to attract new:<br />
* standardization areas<br />
* work items<br />
* active members<br />
in three main time frames:<br />
* prior to start of standardization work (inception and conception)<br />
* during standardization work (drafting and adoption)<br />
* after publication<br />
<br />
='''Process management'''=<br />
<br />
''[management - the conducting or supervising of something (as business), esp. the executive function of planning, organizing, co-ordinating, directing, controlling, and supervising any industrial or business project or activity with responsibility for results]''<br />
<br />
The operations of ETSI and its bodies are governed by the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives] (containing ETSI Statutes, ETSI Rules of Procedure, ETSI Board Working Procedures, Powers and Functions of the Board, Terms of Reference of the Operational Co-ordination Group, and ETSI Technical Working Procedures).<br />
The processes, tasks and procedures of the ETSI Secretariat are governed by the Secretariat's Quality Management System.<br />
<br />
='''Process performance'''=<br />
<br />
''[performance - the capacity to achieve a desired result]''<br />
<br />
==The main performance characteristics of interest for the Standards Making Process are:==<br />
* timeliness<br />
* deliverable quality<br />
* cost<br />
* production<br />
<br />
==Timeliness addresses mainly two time-to-market aspects:==<br />
<br />
* just-in-time availability, availability of the Technical Body approved deliverable in the optimal moment, not too early, not too late.<br />
* adoption delay, the time it takes to run the deliverable through the approval process.<br />
<br />
The first aspect is difficult to quantify, except when it's too late, and thus difficult to improve.<br />
<br />
The second is within ETSI a matter for continuous follow-up (and improvement). Requirements are given by the Technical Working Procedures, complemented by annually reviewed objectives for the process elements operated by OPS.<br />
<br />
Deliverable quality is a many-faceted concept, ranging from absence of spelling and document layout mistakes to acceptance as a useful standard in the marketplace.<br />
Cost is also difficult to estimate. It is estimated that the total cost for the ETSI standardization activities is of the order of 10 times the budget for the ETSI Secretariat.<br />
Process costs are only followed on the level of OPS activities in relation to the Technical Organization.<br />
<br />
Production, i.e. the process output at three stages in the Adoption process, viz. Publication, Editing prior to Member Voting and Public Enquiry, and Editing prior to Voting (ENAP) is continuously recorded in terms of number of deliverables and size of deliverables (number of pages when the corresponding files are printed).<br />
<br />
Monthly statistics for production (per process stage as indicated above, Technical Body and type of deliverable), adoption delays (moving averages for process cycle (lead) times) for the various types of deliverables, and prediction of the production for the next twelve months is made available to the ETSI membership.<br />
<br />
==Monitoring of the conception, drafting and adoption sub-processes address for the Technical Bodies==<br />
<br />
* composition of the work programme<br />
* production of deliverables (number of deliverables and their size)<br />
* activity level<br />
* delays<br />
* cost elements<br />
<br />
==Process reengineering==<br />
<br />
''[reengineering - the fundamental rethinking and radical redesign of processes to achieve dramatic improvements in critical measures of performance]''<br />
<br />
Reengineering of the processes are either part of a continuous improvement programme (which addresses both changes to the formal procedures as described by the Technical Working Procedures and changes to internal OPS working procedures) or change actions that take place (in OPS Division or in the Technical Organization) when new information tools and technologies are mature for implementation.<br />
<br />
='''Working methods'''=<br />
<br />
The work in the Standards Making Process is governed by the [https://portal.etsi.org/LoginRedirection.aspx?domain=docbox.etsi.org&ReturnUrl=/Board/ETSI_Directives ETSI Directives], which consists of:<br />
<br />
* ETSI Statutes<br />
* ETSI Rules of Procedure<br />
* ETSI Board Powers and Functions, and Working Procedures<br />
* ETSI Technical Working Procedures<br />
* ETSI Drafting rules<br />
* The terms of reference for the operational co-ordination group (OCG) between the Technical Body Chairmen and the Secretariat.<br />
<br />
The Chair of a Technical Body (TB), nominated by the TB and appointed by the Board, is responsible for the overall management of the TB, its working groups and its work programme.<br />
<br />
Representatives of full and associate members can participate in the work of a TB and its working groups. Representatives of non-members may participate on an "exceptional and temporary" basis, if the TB Chair agrees. Working documents are usually available only to members of ETSI (while the resulting TB approved output is available in the public domain, for free of charge [https://www.etsi.org/standards-search#Pre-defined%20Collections download].<br />
<br />
Each TB establishes and maintains a work programme, consisting of Work items. The various TB work programmes together constitute the [https://portal.etsi.org/webapp/WorkProgram/Expert/QueryForm.asp ETSI Work Programme]. The responsibility for a Work item is usually given to small group of experts, chaired by a Rapporteur.<br />
<br />
A work item is approved by the TB and then formally adopted by the whole membership (via a web based procedure).<br />
<br />
Most of the technical work in such Rapporteur groups, in working groups and in the TB as a whole is done via electronic means, email, email exploders, and the ETSI server (ftp or http). TBs and working groups also arrange physical meetings (with a frequency of 2 - 6 meetings per year). Such meetings take place either at the ETSI Secretariat meeting facilities in Sophia Antipolis or are hosted by ETSI members, in the majority of cases in continental Europe.<br />
<br />
Decisions in a TB are taken either by consensus or by a weighted vote (where a proposition passes if at least 71% of the votes cast are in favour).<br />
<br />
The TB approves the output from its work on work item, an ETSI Deliverable. In the case of ETSI Technical Specifications and ETSI Technical Reports, the TB also adopts the deliverable for publication; for the other deliverables adoption takes place after application of the relevant approval [https://portal.etsi.org/Resources/Standards-Making-Process/Process Process].</div>Raffyhttps://help.etsi.org/index.php?title=ETSI_Standards_Making_Process_guideETSI Standards Making Process guide2024-02-14T13:59:57Z<p>Raffy: </p>
<hr />
<div>='''ETSI Deliverables'''=<br />
Work in ETSI is done on the basis of ETSI work items, approved by the Technical Body and adopted by the ETSI membership.<br />
A work item results in one deliverable (sometimes more than one), which can be a European Standard or a Technical Specification, an ETSI Guide or a Technical Report.<br />
ETSI has a suite of specifications, standards and reports that fulfil the various needs of the market:<br />
<br />
* ETSI EN (European Standard) - adopted by ETSI National Standards Organizations (NSOs) (except those elaborated in response to a Standardisation Request (SReq)).<br />
* ETSI European standardisation deliverables – adopted by ETSI National Standardisation Bodies (NSBs)<br />
* ETSI TS (ETSI Technical Specification) and ETSI TR (ETSI Technical Report) - adopted by the responsible Technical Group (except those elaborated in response to a Standardisation Request (SReq)).<br />
* ETSI ES (ETSI Standard) and ETSI EG (ETSI Guide) - adopted by ETSI Members (except those elaborated in response to a Standardisation Request (SReq)).<br />
* ETSI SR (ETSI Special Report) - adopted by the ETSI responsible Technical Group (except those elaborated in response to a Standardisation Request (SReq)).<br />
* ETSI GS (ETSI Group Specification) and GR (ETSI Group Report) - adopted the responsible Industry Specification Group.<br />
<br />
NOTE: The skeletons of each specification are available here.<br />
<br />
This suite of deliverables fulfils the needs for:<br />
* deliverable intended to meet needs specific to Europe and requiring transposition into national standards - ETSI EN<br />
* deliverable intended to meet needs specific to the Europe Economic Area (EEA), required under a Standardisation Request (SReq) from the European Commission (EC)/European Free Trade Association (EFTA) – ETSI EN and European standardisation deliverable.<br />
* deliverable providing technical requirements or explanatory material or both – ETSI GS<br />
* deliverable containing only informative elements – ETSI GR<br />
* high quality specifications delivered early to the market - ETSI TS.<br />
* high quality standards supported by the whole ETSI global membership - ETSI ES.<br />
* deliverable containing explanatory material – ETSI TR.<br />
* information document used for various purposes, including giving public availability to information not produced within a Technical Group – ETSI SR<br />
* document elaborated by ETSI partners and adopted by ETSI, to become an ETSI Technical Specification (TS) or an ETSI Technical Report (TR) - Publicly Available Specification (PAS).<br />
<br />
NOTE: For more information, please read about PASs in our Partnerships section.<br />
<br />
The numbering convention used by ETSI to link related documents at these various "levels" simplifies their market application.<br />
<br />
='''Process'''=<br />
<br />
[[File:Figure1_SMP.jpeg|options|caption]]<br />
<br />
The Standards Making Process (SMP) is the process applied for the Technical Organization's production of standards and deliverables and the Secretariat's involvement in and interaction with the Technical Organization, the ETSI members and the ETSI National Standards Organizations.<br />
The general conditions for the SMP are defined by the ETSI Directives, in particular the Technical Working Procedures. The Secretariat's tasks and activities in SMP are primarily defined in the Quality Management System (QMS) documentation of ETSI Operations (OPS) Division.<br />
<br />
==Process overview==<br />
[process - a structured, measured set of activities designed to produce a specified output]<br />
The objective of the ETSI Standards Making Process (SMP) is to convert market needs for standardization in the ICT area into ETSI deliverables (specifications, standards, norms, guides, reports) used in the market place.<br />
The input to the process is an existing (as yet known or unknown) market need for standardization. The output is the broad application of the produced deliverables in the market place.<br />
The SMP consists of five main elements, sub-processes, with their own distinct objectives, inputs and outputs. Each sub-process is defined to the level of which operational tasks are performed, and where in the ETSI organization they are performed.<br />
The whole ETSI organization is in one way or the other involved in either operation of the SMP or in direct or indirect support of it. The main technical activities are performed in the Technical Groups of the Technical Organization. The main direct support to those activities is provided by ETSI Operations (OPS) and ETSI Standardization Service (STS) Divisions of the ETSI Secretariat.<br />
The operation of the SMP in the Technical Organization is governed by the ETSI Directives, in particular the Technical Working Procedures, and the ETSI Drafting Rules. The processes, tasks and procedures of the ETSI Secretariat are governed by the Secretariat's Quality Management System documentation, notably that of ETSI Operations (OPS) and ETSI Standardization Service (STS) Divisions.<br />
<br />
==Inception==<br />
[inception - an act, process, or instance of beginning (as of an institution, organization, or concept)]<br />
The times when initiatives to standardization were taken only when products and services were already available are since long gone. This is particularly the case for telecommunications where standardization precedes or goes hand in hand with the design and development processes.<br />
The input to this sub-process is "what's going on in the marketplace", with "marketplace" having a broad interpretation, including development in the research and academic circles.<br />
The output is a new standardization area, given to an existing or a new Technical Group. The formal output is the Terms of Reference (ToR) and/or a Project Requirements Definition (PRD) document, approved by the ETSI Board or, in the case of an ETSI Partnership Project with an external organization, approved by the ETSI General Assembly.<br />
<br />
==The process itself consists, in broad terms, of:==<br />
*identifying needs for standardization in the subject areas defined by the ETSI Statutes and Rules of Procedure.<br />
*defining the suitable organization for such standardization within ETSI.<br />
==There are various actors in this process==<br />
* experts in the Technical Bodies, Special Committees and ISGs.<br />
* ETSI Members.<br />
* supported by OPS Technical Officers and staff from Innovation.<br />
==Conception==<br />
[conception - the capacity, function, or process of forming ideas or abstractions or of grasping the meaning of symbols representing such ideas or abstractions; an idea or general notion; the originating of something (as an idea or plan) in the mind].<br />
The creation of a new standardization area or ISG is manifested by the establishment of the new Technical Group or the amendment of the Terms of Reference of the Project Requirements Definition of an existing.<br />
The identification, definition, approval and adoption of work items are the main elements of the conception phase (even if work items may have been envisaged already during the inception process).<br />
The input is identified standardization needs in the area. These work items may either be entirely new, leading to new deliverables, or a new version of an existing deliverable ("maintenance work item").<br />
The output is a work item, adopted by the ETSI Membership for ETSI deliverables created on proposal for Full or Associate members.<br />
A proposal for a work item may come from inside or outside the Technical Group. The Technical Group may approve the work item, if at least four ETSI Members volunteer to support the work (except those in response to a Standardisation Request (WISR)). The adoption is formally done by the ETSI Membership, except those in response to a Standardisation Request (WISR). The existence of new work items is made known via the ETSI Web site and Members who disagree with the item may within a 30-day period oppose its adoption into the ETSI Work Programme.<br />
ETSI may elaborate European Standards and European standardisation deliverables in response to Standardisation Requests to support the European legislation or policies, in accordance with the amended Regulation (EU) No 1025/2012.<br />
As per Article 20.4 of the Rules of procedure, it is the responsibility of the National Standardisation Bodies (NSB) to adopt a new WISR created by the responsible Technical Group in response to a Standardisation Request (SReq).<br />
For full details see clauses 1.6.3 (Adoption of a Work Item) and 1.7 (Decision-making in a Technical Group of the Technical Working Procedures.<br />
==Drafting==<br />
[drafting - to make a preliminary or tentative version, sketch, or outline (as of a literary composition or other document)].<br />
A work item in the ETSI Work Programme is intended to lead to one (or more) ETSI deliverable(s).<br />
A Technical Group is free to organize its work in any way it wishes, within the rules of the Technical Working Procedures, including create Working Groups to which the tasks of drafting parts of the Technical Group's work programme are given.<br />
The drafting usually takes place in a small team (Rapporteur group) led by a Rapporteur. The work is largely done by "correspondence", i.e. by exchange of documents via the ETSI DocBox server and LISTSERV email exploder facilities.<br />
When the draft by the Rapporteur group is considered ready, the draft deliverable is handed over to the Working Group (when it exists) for approval. The formal approval for further processing or, in the case of ETSI Technical Specifications or ETSI Technical Reports, approval and adoption can only be done by the Technical Group, either at a meeting or by correspondence.<br />
Some drafting activities for a Technical Group are performed by Specialist Task Forces (STF)/Testing Task Forces (TTF) located at the ETSI Secretariat.<br />
The adaptation of specifications from external bodies (Publicly Available Specifications (PAS)) to the ETSI deliverable structure follows the same rules, but will normally be performed by the PAS provider, as defined in the Guidelines for adoption of Publicly Available Specifications.<br />
==Adoption==<br />
[adoption - the act or process of adopting someone or something, such as: the act or process of giving official acceptance or approval to something]<br />
While the drafting process is, in principle, the same for all ETSI deliverables, the process elements of the adoption process depend on the type of deliverable being processed.<br />
<br />
='''ETSI Group Specification, ETSI Group Report, ETSI Special Report, ETSI Technical Specification and ETSI Technical Report''' =<br />
For ETSI Group Specification (GS), ETSI Group Report (GR), ETSI Special Report (SR), ETSI Technical Specification (TS) and ETSI Technical Report (TR) elaborated on proposal from Full and Associate members, the Technical Group draft approval and adoption take place at the same time (one combined decision).<br />
The Publication process element consists of publishing in PDF format and archiving. The published deliverable will then be made available for distribution via the ETSI Web server.<br />
[[File:Figure2_SMP.jpeg|options|caption]]</div>Raffyhttps://help.etsi.org/index.php?title=Use_of_gender_inclusive_languageUse of gender inclusive language2024-02-14T13:33:37Z<p>Raffy: /* How do I know if I am using discriminatory language?= */</p>
<hr />
<div>== Introduction == <br />
This guide discusses which language is appropriate for the use in ETSI deliverables and gives examples of how to best avoid common mistakes.<br />
<br />
The ETSI community is diverse and includes all kinds of organisation, from all over the globe. It is therefore important that the way in which ETSI deliverables are phrased is representative of the whole community. This means that ETSI staff and all people working in the different ETSI groups should be conscious about the language they use to not unconsciously leave out or misrepresent parts of the community or society.<br />
This guide focusses in its first release on gender-inclusive language but could be broadened to other aspects in the future.<br />
“Using gender-inclusive language means speaking and writing in a way that does not discriminate against a particular sex, social gender or gender identity, and does not perpetuate gender stereotypes. Given the key role of language in shaping cultural and social attitudes, using gender-inclusive language is a powerful way to promote gender equality and eradicate gender bias.” [statement from the United Nations on gender-inclusive language].<br />
This guide includes a number of recommendations that are a direct copy from the United Nations guidelines on gender-inclusive language, since they are internationally recognised and therefore set a global standard for how to communicate in a gender-inclusive manner.<br />
<br />
This guide focusses on giving guidance on how to communicate using gender-inclusive language in a written form. The aim of this document is to facilitate the development of gender inclusive ETSI deliverables.<br />
<br />
<br />
== When to apply ==<br />
These Guidelines include a number of strategies to help ETSI staff and ETSI community use inclusive language. They may be applied to any type of communication, whether it is oral or written, formal or informal, or addressed to an internal or external audience.<br />
When deciding what strategies to use, ETSI staff and ETSI community should:<br />
* Take into account the type of text/oral communication, the context, the audience and the purpose of the communication.<br />
* Ensure that the text is readable and the text/oral communication clear, fluid and concise.<br />
* Seek to combine different strategies throughout the text/oral communication that allow all categories of the expected audience to be included.<br />
There are different areas that may need extra attention like the use of gender, race, age, cultural background, religion, sexuality etc. Most of these areas may not seem to occur in ETSI documents including standards but being aware of them is important to avoid biased text.<br />
The following chapters give guidance on how to avoid biased text with regard to gender, since this is regarded as the most critical area at the time of the first draft of this guidance.<br />
<br />
== Gender in English ==<br />
In English, there is a difference between “grammatical gender”, “gender as a social construct” (which refers to the roles, behaviours, activities and attributes that a given society at a certain time considers appropriate for men, women or nonbinary people) and “sex” as a biological characteristic of living beings.<br />
English has very few gender markers: the pronouns and possessives (he, she, her, his, they and their); and some nouns and forms of address. Most English nouns do not have grammatical gender forms (teacher, president), whereas a few nouns are specifically masculine or feminine (actor/actress, waiter/waitress). Some nouns that once ended in -man now have neutral equivalents that are used to include all genders (police officer for policeman/policewoman, spokesperson for spokesman, chair/chairperson for chairman, etc.).<br />
A challenge for gender-inclusive communication in English is the use of the masculine form by default. For example, “Every Permanent Representative must submit his credentials to Protocol.”<br />
This is why the following chapter on best practices/strategies provides examples how these types of sentences can be written in a different way to avoid the direct mentioning of one gender only.<br />
<br />
== Best practices/strategies for the use of gender in texts, events ==<br />
A number of strategies can be applied, when speaking or writing in English, to be more gender-inclusive:<br />
==== Forms of address ====<br />
When referring to or addressing specific individuals, use forms of address and pronouns that are consistent with their gender identity (e.g. Ms. for females, Mr. for males). If unsure, use neutral terms like the delegate, the chair, the convenor, etc., or their name (e.g. Robin or Robin Jones) or titles (if appropriate) like Professor Smith.<br />
Alternatively, and if the situation permits, ask the persons addressed or written about what pronoun and form of address should be used for them.<br />
There should also be consistency in the way people are referred to: if one of them is addressed by their name, last name, courtesy title, or profession, the others should be addressed similarly.<br />
<br />
'''Examples'''<br />
<br />
*Less inclusive “Professor Smith (surname and title for a man) and Madeline (first name for a woman) will attend.”<br />
*More inclusive “Professor Smith and Professor Jones will attend (surname and title for both).”<br />
<br />
'''Ms. or Mrs.?'''<br />
<br />
*Care should be taken to use the form of address preferred by each individual. However, when that preference is not known, precedence is given to Ms. over Mrs., as the former is more inclusive and can refer to any woman, regardless of marital status. Note also, but increasingly rare, some will prefer Miss to Ms or Mrs. The use of the non-specific form of address Mx is also available but is not widely used and use should be clarified on an individual basis.<br />
<br />
<br />
'''Use of Chair'''<br />
*<br />
ETSI has adopted the gender-neutral Chair as the expression for the Chair of a meeting. It can be assumed that this can be used as a form of address in oral and written work. It does not however preclude the use of other forms of address where they are generally agreed by the people involved, in particular the person who is the Chair. Such expressions include Madam Chair, Chairperson, Chairman, etc. Formal records of meetings and published documents are expected to use Chair as the term.<br />
<br />
=== Avoid gender-biased expressions or expressions that reinforce gender stereotypes ===<br />
<br />
===='''Discriminatory examples'''====<br />
<br />
*“She throws/runs/fights like a girl.”<br />
*“In a manly way.”<br />
*“Oh, that’s women’s work.”<br />
*“Thank you to the ladies for making the room more beautiful.”<br />
*“Men just don’t understand.”<br />
<br />
'''Examples'''<br />
*Less inclusive: “Guests are cordially invited to attend with their wives.” <br />
*More inclusive: “Guests are cordially invited to attend with their partners.”<br />
*Less inclusive: “Fathers babysit their children.”<br />
*More inclusive: “Fathers care for their children.”<br />
<br />
=== How do I know if I am using discriminatory language?===<br />
Reverse the gender: Would reversing the designation or the term from masculine to feminine or vice versa change the meaning or emphasis of the sentence? Would it make the sentence sound odd?<br />
<br />
'''Examples'''<br />
<br />
*“Women should not seek out leadership positions.”<br />
*“Men cannot do two things at the same time.”<br />
<br />
== Avoid gender-biased presentation that is not relevant (e.g. age) ==<br />
=== Discriminatory example ===<br />
“Anna (34) is an e-Governance expert, e-Estonia Briefing Centre managing director, and TED speaker. Maarten Mes is Managing Director of one2many, a world leader in Cell Broadcast.”<br />
Ask yourself if the added information is relevant for the message of the text.<br />
<br />
== Be open to all forms of gender ==<br />
The concepts of non-binary gender and gender fluidity are now widely understood. There are a range of norms that relate to the treatment of language relating to them, but they are not universally accepted. <br />
Particular treatment is thus not indicated in this document, but it is highlighted as something where sensitivity and tolerance are necessary.<br />
<br />
== Informal terms ==<br />
Informal terms such as “dude”, “mate”, “pal” and “buddy” are often used in conversation amongst friends but should not be used in a professional context. They may also have alternative meanings eg “mate” can be a noun or a verb and should therefore be avoided as far as possible.<br />
<br />
== Terms of endearment ==<br />
Terms of endearment such as “love”, “darling”, “sweetheart”, “gorgeous”, “chick”, “boy”, “girl”, “baby”, “sugar”, “honey” and “sweetness” often make the gender of the speaker sound superior to the gender of the person spoken to in multigender conversations.<br />
Such terms should generally be avoided as far as possible.<br />
<br />
== Make gender visible when it is relevant for communication ==<br />
=== Using several different words ===<br />
In cases in which highlighting gender would make the sentence more inclusive, several separate words can be used. This strategy should be used only when popular beliefs or preconceptions may obscure the presence or action of any gender.<br />
<br />
'''Examples'''<br />
<br />
*“Children should attend the first cooking class with their parents.”<br />
*“All of the soldiers, men, women and non-binary, responded negatively to question 5 in the survey on gender inclusivity.”<br />
<br />
=== Not recommended in general: Using feminine and masculine pronouns ===<br />
“Pairing” is the use of both feminine and masculine forms (he or she; her or his). It is a strategy that may be used when the author/speaker wants to explicitly make both women and men visible. <br />
This guide does not recommend the usage of pairing in general though, because of the following reasons:<br />
*It may be distracting to the reader, in particular in narrative texts. <br />
*Not everyone may consider themselves to fall into one of these two categories.<br />
*It may also create inconsistencies or render the text less accurate - for example, in legal texts.<br />
<br />
== Do not make gender visible when it is not relevant for communication ==<br />
=== Use gender-neutral words ===<br />
*Less inclusive: “Mankind” <br />
*More inclusive: “Humankind”; “humanity”; “human race”<br />
*Less inclusive: “Plans to outsource some 19 services have not proceeded at the anticipated pace, as there are significant manpower shortages.”<br />
*More inclusive: “Plans to outsource some 19 services have not proceeded at the anticipated pace, as there are significant staffing shortages.”<br />
*Less inclusive: “Man-made”<br />
*More inclusive “Artificial”; “human-created”<br />
<br />
=== Using plural pronouns/adjectives ===<br />
<br />
Plural pronouns may be used as a shortcut to ensure gender inclusiveness (words such as they, them, their). Care should be taken to ensure that there is no confusion using a plural pronoun in the singular that there is no confusing plural meaning – especially if there is a legal use of the material.<br />
The plural form is also widely used in speech and would be quite acceptable in meetings and informal conversations at ETSI.<br />
<br />
'''Example'''<br />
<br />
*“Before submitting your document, send it to the focal point for their review; they will return it to you with comments.”<br />
<br />
It is noted that there are several schemes of genderless pronoun. For example, zie for he or she, zim for him/her and zir for his/her. Whilst their use is not precluded in discussions where participants understand those pronouns, it is suggested that they are not used in written correspondence and the plural form or other neutral forms of speech are used as far as possible.<br />
=== Use the pronoun “one”===<br />
<br />
*Less inclusive: “A staff member in Antarctica earns less than he would in New York.”<br />
*More inclusive: “You earn less in Antarctica than New York.” or “A staff member in Antarctica earns less than one in New York.”<br />
<br />
=== Use the relative pronoun “who”===<br />
*Less inclusive: “If a complainant is not satisfied with the board’s decision, he can ask for a rehearing.”<br />
*More inclusive: “A complainant who is not satisfied with the board’s decision can ask for a rehearing.”<br />
<br />
===Use a plural antecedent===<br />
When referring to generic subjects, plural antecedents may be used in order to avoid gendered pronouns.<br />
<br />
*Less inclusive: “A substitute judge must certify that he has familiarized himself with the record of the proceedings.” <br />
*More inclusive: “Substitute judges must certify that they have familiarized themselves with the record of the proceedings.”<br />
=== Omit the gendered word ===<br />
*Less inclusive: “Requests the Emergency Relief Coordinator to continue his/her efforts to strengthen the coordination of humanitarian assistance.”<br />
*More inclusive: “Requests the Emergency Relief Coordinator to continue efforts to strengthen the coordination of humanitarian assistance.”<br />
*Less inclusive: “A person must reside continuously in the Territory for 20 years before he may apply for permanent residence.” <br />
*More inclusive: “A person must reside continuously in the Territory for 20 years before applying for permanent residence.”<br />
=== Use the passive voice ===<br />
The passive voice is not an appropriate option for all sentences in English, as employing the passive voice often changes the emphasis of the sentence. However, it does offer an option for avoiding gendered constructions.<br />
*Less inclusive: “The author of a communication must have direct and reliable evidence of the situation he is describing.” <br />
*Better: “The author of a communication describing a situation must have direct and reliable evidence of the situation being described.”<br />
Note that the original context and emphasis could also be kept using “they are”, as in:<br />
“The author of a communication must have direct and reliable evidence of the situation that they are describing.”</div>Raffyhttps://help.etsi.org/index.php?title=Use_of_gender_inclusive_language_GuideUse of gender inclusive language Guide2024-01-30T14:42:12Z<p>Raffy: /* Best practices/strategies for the use of gender in texts, events: */</p>
<hr />
<div>== Executive summary ==<br />
This guide discusses which language is appropriate for the use in ETSI deliverables and gives examples of how to best avoid common mistakes.<br />
== Introduction == <br />
The ETSI community is diverse and includes all kinds of organisation, from all over the globe. It is therefore important that the way in which ETSI deliverables are phrased is representative of the whole community. This means that ETSI staff and all people working in the different ETSI groups should be conscious about the language they use to not unconsciously leave out or misrepresent parts of the community or society.<br />
This guide focusses in its first release on gender-inclusive language but could be broadened to other aspects in the future.<br />
“Using gender-inclusive language means speaking and writing in a way that does not discriminate against a particular sex, social gender or gender identity, and does not perpetuate gender stereotypes. Given the key role of language in shaping cultural and social attitudes, using gender-inclusive language is a powerful way to promote gender equality and eradicate gender bias.” [statement from the United Nations on gender-inclusive language].<br />
This guide includes a number of recommendations that are a direct copy from the United Nations guidelines on gender-inclusive language, since they are internationally recognised and therefore set a global standard for how to communicate in a gender-inclusive manner.<br />
== Scope ==<br />
The present document focusses on giving guidance on how to communicate using gender-inclusive language in a written form. The aim of this document is to facilitate the development of gender inclusive ETSI deliverables.<br />
<br />
== Guidelines ==<br />
=== When to apply ===<br />
These Guidelines include a number of strategies to help ETSI staff and ETSI community use inclusive language. They may be applied to any type of communication, whether it is oral or written, formal or informal, or addressed to an internal or external audience.<br />
When deciding what strategies to use, ETSI staff and ETSI community should:<br />
* Take into account the type of text/oral communication, the context, the audience and the purpose of the communication.<br />
* Ensure that the text is readable and the text/oral communication clear, fluid and concise.<br />
* Seek to combine different strategies throughout the text/oral communication that allow all categories of the expected audience to be included.<br />
There are different areas that may need extra attention like the use of gender, race, age, cultural background, religion, sexuality etc. Most of these areas may not seem to occur in ETSI documents including standards but being aware of them is important to avoid biased text.<br />
The following chapters give guidance on how to avoid biased text with regard to gender, since this is regarded as the most critical area at the time of the first draft of this guidance.<br />
<br />
=== Gender in English ===<br />
In English, there is a difference between “grammatical gender”, “gender as a social construct” (which refers to the roles, behaviours, activities and attributes that a given society at a certain time considers appropriate for men, women or nonbinary people) and “sex” as a biological characteristic of living beings.<br />
English has very few gender markers: the pronouns and possessives (he, she, her, his, they and their); and some nouns and forms of address. Most English nouns do not have grammatical gender forms (teacher, president), whereas a few nouns are specifically masculine or feminine (actor/actress, waiter/waitress). Some nouns that once ended in -man now have neutral equivalents that are used to include all genders (police officer for policeman/policewoman, spokesperson for spokesman, chair/chairperson for chairman, etc.).<br />
A challenge for gender-inclusive communication in English is the use of the masculine form by default. For example, “Every Permanent Representative must submit his credentials to Protocol.”<br />
This is why the following chapter on best practices/strategies provides examples how these types of sentences can be written in a different way to avoid the direct mentioning of one gender only.<br />
=== Best practices/strategies for the use of gender in texts, events ===<br />
A number of strategies can be applied, when speaking or writing in English, to be more gender-inclusive:<br />
===== Forms of address =====<br />
When referring to or addressing specific individuals, use forms of address and pronouns that are consistent with their gender identity (e.g. Ms. for females, Mr. for males). If unsure, use neutral terms like the delegate, the chair, the convenor, etc., or their name (e.g. Robin or Robin Jones) or titles (if appropriate) like Professor Smith.<br />
Alternatively, and if the situation permits, ask the persons addressed or written about what pronoun and form of address should be used for them.<br />
There should also be consistency in the way people are referred to: if one of them is addressed by their name, last name, courtesy title, or profession, the others should be addressed similarly.<br />
<br />
'''Examples'''<br />
<br />
*Less inclusive “Professor Smith (surname and title for a man) and Madeline (first name for a woman) will attend.”<br />
*More inclusive “Professor Smith and Professor Jones will attend (surname and title for both).”<br />
<br />
'''Ms. or Mrs.?'''<br />
<br />
*Care should be taken to use the form of address preferred by each individual. However, when that preference is not known, precedence is given to Ms. over Mrs., as the former is more inclusive and can refer to any woman, regardless of marital status. Note also, but increasingly rare, some will prefer Miss to Ms or Mrs. The use of the non-specific form of address Mx is also available but is not widely used and use should be clarified on an individual basis.<br />
<br />
<br />
'''Use of Chair'''<br />
*<br />
ETSI has adopted the gender-neutral Chair as the expression for the Chair of a meeting. It can be assumed that this can be used as a form of address in oral and written work. It does not however preclude the use of other forms of address where they are generally agreed by the people involved, in particular the person who is the Chair. Such expressions include Madam Chair, Chairperson, Chairman, etc. Formal records of meetings and published documents are expected to use Chair as the term.<br />
<br />
==== Avoid gender-biased expressions or expressions that reinforce gender stereotypes ====<br />
<br />
====='''Discriminatory examples'''=====<br />
<br />
*“She throws/runs/fights like a girl.”<br />
*“In a manly way.”<br />
*“Oh, that’s women’s work.”<br />
*“Thank you to the ladies for making the room more beautiful.”<br />
*“Men just don’t understand.”<br />
<br />
'''Examples'''<br />
*Less inclusive: “Guests are cordially invited to attend with their wives.” <br />
*More inclusive: “Guests are cordially invited to attend with their partners.”<br />
*Less inclusive: “Fathers babysit their children.”<br />
*More inclusive: “Fathers care for their children.”<br />
<br />
==== How do I know if I am using discriminatory language?====<br />
Reverse the gender: Would reversing the designation or the term from masculine to feminine or vice versa change the meaning or emphasis of the sentence? Would it make the sentence sound odd?<br />
<br />
'''Examples'''<br />
<br />
*“Women should not seek out leadership positions.”<br />
*“Men cannot do two things at the same time.”<br />
<br />
=== Avoid gender-biased presentation that is not relevant (e.g. age) ===<br />
==== Discriminatory example ====<br />
“Anna (34) is an e-Governance expert, e-Estonia Briefing Centre managing director, and TED speaker. Maarten Mes is Managing Director of one2many, a world leader in Cell Broadcast.”<br />
Ask yourself if the added information is relevant for the message of the text.<br />
<br />
=== Be open to all forms of gender ===<br />
The concepts of non-binary gender and gender fluidity are now widely understood. There are a range of norms that relate to the treatment of language relating to them, but they are not universally accepted. <br />
Particular treatment is thus not indicated in this document, but it is highlighted as something where sensitivity and tolerance are necessary.<br />
<br />
=== Informal terms ===<br />
Informal terms such as “dude”, “mate”, “pal” and “buddy” are often used in conversation amongst friends but should not be used in a professional context. They may also have alternative meanings eg “mate” can be a noun or a verb and should therefore be avoided as far as possible.<br />
<br />
=== Terms of endearment ===<br />
Terms of endearment such as “love”, “darling”, “sweetheart”, “gorgeous”, “chick”, “boy”, “girl”, “baby”, “sugar”, “honey” and “sweetness” often make the gender of the speaker sound superior to the gender of the person spoken to in multigender conversations.<br />
Such terms should generally be avoided as far as possible.<br />
<br />
=== Make gender visible when it is relevant for communication ===<br />
==== Using several different words ====<br />
In cases in which highlighting gender would make the sentence more inclusive, several separate words can be used. This strategy should be used only when popular beliefs or preconceptions may obscure the presence or action of any gender.<br />
<br />
'''Examples'''<br />
<br />
*“Children should attend the first cooking class with their parents.”<br />
*“All of the soldiers, men, women and non-binary, responded negatively to question 5 in the survey on gender inclusivity.”<br />
<br />
==== Not recommended in general: Using feminine and masculine pronouns ====<br />
“Pairing” is the use of both feminine and masculine forms (he or she; her or his). It is a strategy that may be used when the author/speaker wants to explicitly make both women and men visible. <br />
This guide does not recommend the usage of pairing in general though, because of the following reasons:<br />
*It may be distracting to the reader, in particular in narrative texts. <br />
*Not everyone may consider themselves to fall into one of these two categories.<br />
*It may also create inconsistencies or render the text less accurate - for example, in legal texts.<br />
<br />
=== Do not make gender visible when it is not relevant for communication ===<br />
==== Use gender-neutral words ====<br />
*Less inclusive: “Mankind” <br />
*More inclusive: “Humankind”; “humanity”; “human race”<br />
*Less inclusive: “Plans to outsource some 19 services have not proceeded at the anticipated pace, as there are significant manpower shortages.”<br />
*More inclusive: “Plans to outsource some 19 services have not proceeded at the anticipated pace, as there are significant staffing shortages.”<br />
*Less inclusive: “Man-made”<br />
*More inclusive “Artificial”; “human-created”<br />
<br />
==== Using plural pronouns/adjectives ====<br />
<br />
Plural pronouns may be used as a shortcut to ensure gender inclusiveness (words such as they, them, their). Care should be taken to ensure that there is no confusion using a plural pronoun in the singular that there is no confusing plural meaning – especially if there is a legal use of the material.<br />
The plural form is also widely used in speech and would be quite acceptable in meetings and informal conversations at ETSI.<br />
<br />
'''Example'''<br />
<br />
*“Before submitting your document, send it to the focal point for their review; they will return it to you with comments.”<br />
<br />
It is noted that there are several schemes of genderless pronoun. For example, zie for he or she, zim for him/her and zir for his/her. Whilst their use is not precluded in discussions where participants understand those pronouns, it is suggested that they are not used in written correspondence and the plural form or other neutral forms of speech are used as far as possible.<br />
==== Use the pronoun “one”====<br />
<br />
*Less inclusive: “A staff member in Antarctica earns less than he would in New York.”<br />
*More inclusive: “You earn less in Antarctica than New York.” or “A staff member in Antarctica earns less than one in New York.”<br />
<br />
==== Use the relative pronoun “who”====<br />
*Less inclusive: “If a complainant is not satisfied with the board’s decision, he can ask for a rehearing.”<br />
*More inclusive: “A complainant who is not satisfied with the board’s decision can ask for a rehearing.”<br />
<br />
====Use a plural antecedent====<br />
When referring to generic subjects, plural antecedents may be used in order to avoid gendered pronouns.<br />
<br />
*Less inclusive: “A substitute judge must certify that he has familiarized himself with the record of the proceedings.” <br />
*More inclusive: “Substitute judges must certify that they have familiarized themselves with the record of the proceedings.”<br />
==== Omit the gendered word ====<br />
*Less inclusive: “Requests the Emergency Relief Coordinator to continue his/her efforts to strengthen the coordination of humanitarian assistance.”<br />
*More inclusive: “Requests the Emergency Relief Coordinator to continue efforts to strengthen the coordination of humanitarian assistance.”<br />
*Less inclusive: “A person must reside continuously in the Territory for 20 years before he may apply for permanent residence.” <br />
*More inclusive: “A person must reside continuously in the Territory for 20 years before applying for permanent residence.”<br />
==== Use the passive voice ====<br />
The passive voice is not an appropriate option for all sentences in English, as employing the passive voice often changes the emphasis of the sentence. However, it does offer an option for avoiding gendered constructions.<br />
*Less inclusive: “The author of a communication must have direct and reliable evidence of the situation he is describing.” <br />
*Better: “The author of a communication describing a situation must have direct and reliable evidence of the situation being described.”<br />
Note that the original context and emphasis could also be kept using “they are”, as in:<br />
“The author of a communication must have direct and reliable evidence of the situation that they are describing.”</div>Raffy