ESP SMP guide

October 2009

ESP support's guide

September 2009 Page 2 of 31

Table of contents Introduction ........................................................................................................................................................................................................................................... 3

ETSI and the ETSI Standardization Project ......................................................................................................................................................................................... 4

What the role of the Technical Officer is in ETSI? ............................................................................................................................................................................... 5 What the role of the Coordinator is in ETSI? ........................................................................................................................................................................................ 6 What the role of the Editor is in ETSI? ................................................................................................................................................................................................. 7

Why does the Officer or the Coordinator contact the rapporteurs or experts? .................................................................................................................................... 9 When does editHelp! contact the rapporteurs or experts? ............................................................................................................................................................... 10

How modifications should be integrated in a document already processed? .................................................................................................................................... 11

How good is the quality of the document received from the rapporteur or expert? ........................................................................................................................... 12

Registration ........................................................................................................................................................................................................................................ 14

Signature ............................................................................................................................................................................................................................................ 18

ETSI and work item numbers ............................................................................................................................................................................................................. 19

Choosing the type of ETSI deliverable (EN, TS, etc) ......................................................................................................................................................................... 20

Membership Approval Procedure, MAP (EG, ES) ............................................................................................................................................................................... 1 Two-step Approval Procedure, TAP (EN) ............................................................................................................................................................................................ 2 One-step Approval Procedure, OAP (EN) ............................................................................................................................................................................................ 3

WPM milestones................................................................................................................................................................................................................................... 4

TB Resolution meeting report ............................................................................................................................................................................................................. 22

Harmonized Standards ....................................................................................................................................................................................................................... 23

Annex 1: Tools, programs and functions ............................................................................................................................................................................................ 25

Annex 2: Definitions ........................................................................................................................................................................................................................... 26

Annex 3: Abbreviations ...................................................................................................................................................................................................................... 27


Introduction The present document will guide you through the various steps required to manage an ETSI document and will show you how to use the tools that are essential for your tasks.

The Technical Officers (TOs), Coordinators and Editors are responsible for the document and its quality. This guide is a tool to help you in improving the quality of the standards for which you are responsible for. It neither replaces the ETSI Drafting Rules (EDRs)(1) nor the ETSI Directives(1) (Rules of Procedure to Technical Working Procedures) but will help to remind you of the most important points.

The information in this Guide is based on the Technical Working Procedures (TWP) and the ETSI Drafting Rules (EDRs), contained in the ETSI Directives.


ETSI and the ETSI Standardization Project ETSI's purpose is to produce and perform the maintenance of the technical standards and other deliverables which are required by its members (Article 2 of the ETSI Statutes - see ETSI Directives).

Like most standards organizations, much of this work is carried out in committees and working groups composed of technical experts from the Institute's member companies and organizations. These committees are often referred to as "Technical Bodies" (TB), and typically meet between two and six times a year, in the ETSI premises or elsewhere. They also rely heavily on electronic communications to help progress the work, especially in-between meetings.

For certain urgent items of work, where this frequency of meeting is not sufficient, ETSI may also convene a Specialist Task Force (STF). STFs are small groups of technical experts usually seconded from ETSI members, to work intensively over a period of time, typically a few months, to accelerate the drafting work. Each STF reports to an ETSI technical body. In addition, ETSI provides a number of other services related to standardization, such as interoperability events (Plugtests™), Testing and interoperability related services and fora hosting.

The work of ETSI, including that of its Technical Bodies and Specialist Task Forces, is governed by the ETSI Directives, a set of documents that define the legal status, purpose, scope, and functional aspects of the Institute. These Directives cover the entire lifecycle of ETSI's standards and other products, from inception, through drafting and approval, to publication, and then subsequent maintenance and finally, where necessary, withdrawal from public availability.

ETSI recognizes four different types of Technical Body (TB): http://www.etsi.org/WebSite/AboutETSI/structure/technicalbodies.aspx.


What the role of the Technical Officer is in ETSI?


What the role of the Coordinator is in ETSI?


What the role of the Editor is in ETSI? The Editor is part or the Editing Document Management (EDM) team which is part of the ETSI Standardization Project (ESP) one. The main task of the Editors is to process the documents to be compliant with the ETSI Drafting Rules (EDRs) which are contained in the ETSI Directives. In case of doubt, the Editor writes under the name of editHelp! the questions in a "ReadMe" file which is sent to the rapporteur.

Questions about discrepancies between WPM and the document are always directed to the Officer.

NOTE: editHelp! has many documents to process, the average is 55 per month (without mentioning 3GPP documents), consequently, there is a delay between registration and the start of processing.

It takes between 2 to 3 weeks before the editing is started.

When the document is ready, the TO responsible for the document has to sign it in the Document Follow-up database so that it can be published or sent on procedure (PE, OAP, etc.).


FAQ: What is the difference between EDM and editHelp!? Editing and Document Management (EDM) is the name of the team providing the editing service. editHelp! is the service provided by EDM to answer the rapporteurs', experts' and officers' questions about the drafting process, the status of the document, the handling of clean-ups, etc.

Feel free to contact editHelp!

Internal extension: 4343 phone: +33 (0)4.92.94.43.43 e-mail: [email protected] website: http://portal.etsi.org/edithelp/home.asp

NOTE: [email protected] is a common mailbox to which all Editors have access, while [email protected] is a mailing list. The message is sent to each individual mailbox of the team members.


Why does the Officer or the Coordinator contact the rapporteurs or experts? To ensure that:

� they work on the correct document (agreed or approved by TB);

� if it is a revision, make sure they work on the latest published document;

� if the document has already been cleaned-up by editHelp!, make sure the rapporteur works on the version editHelp! gave back the rapporteur. Check that "pre-processed by editHelp!" appears in the History box.

Remind the rapporteur to use the ETSI styles;

� How to install the ETSI template toolbar: http://portal.etsi.org/edithelp/pdf/ETSI_toolbar.pdf.

� How to install the ETSI styles: http://portal.etsi.org/edithelp/pdf/ETSI_template.pdf.

Remind them to be careful with references (normative and informative references). Normative references are essential to the document and have to be publicly available;

Provide them with the leaflet for rapporteurs or the experts' one (if not already provided by editHelp!).

NOTE: Do not forget that the TO is responsible for the document and its quality. Feel free to offer to send the rapporteur or expert a first draft of the document for "clean-up" (see page 7).


When does editHelp! contact the rapporteurs or experts? editHelp! contacts each "new" rapporteur or expert when she/he starts to work on a new document (also called draft), to:

� introduce editHelp! and the service it offers;

� provide her/him with the ETSI's pack (how to install the ETSI template, toolbar, skeleton, the editing checklist, where to find the latest version of the EDRs, etc.);

� give useful information concerning the editHelp! website;

� encourage her/him to send her/his first draft for clean-up;

� and a lot more.

When we are dealing with an experienced rapporteur, who is working on a revision, we will:

� make sure she/he works on the latest published document;

� remind her/him to check that the normative references mentioned in clause 2 are publicly available;

� make sure she/he is using the correct template (ETSI styles sheet);

� encourage her/him to use our assistance during the drafting process.

EDM is automatically informed when a WI is created in WPM. For this reason it is essential to create the WI as soon as possible. If it is done when the document has been started or completed all the information sent to the Rapporteur or Expert is useless.


How modifications should be integrated in a document already processed? If several rapporteurs/experts/ETSI editors are involved in the drafting work then clear communication with regard to the drafting work is necessary.

The use of editorial notes and revision marks is recommended, as well as accurate records of the work performed (document history, backup of the different versions, etc.). This will avoid confusion during the exchange of documents between all of the editors.

In the "Reviewing" toolbar under Office 2003 click the down arrow at the right of the icon. Under Office 2007, select the "Review" menu.

Select "Accept All Changes in Document".

All changes made using the "Track Changes" feature will be accepted.

NOTE 1: If the "Reviewing" toolbar does not appear in your Word© document select "View" in the menu bar, then "Toolbars" and tick "Reviewing" in the drop-down list.

NOTE 2: However, it’s important to make sure no old revision marks remain in the document when sending it to the ETSI Secretariat.


How good is the quality of the document received from the rapporteur or expert? You have received the document from the rapporteur/expert - is the quality of the document fully in line with the ETSI requirements?

A quick way to know it is by launching the Quality macro installed on your PC. If it is not, contact the Helpdesk to have it installed.

This macro does not take long to run. It will check if useless page breaks have been inserted, if foreign styles have been used, etc.

Don't worry, this won’t corrupt the document.

At the end a report is generated which tells you what is incorrect. You may decide, depending on the urgency of the deliverable to ask the rapporteur to improve it. Or at least inform them that they did not follow some essential editing rules which may delay the publication of the standard.

NOTE: If you have any suggestion to improve this macro, please send an e-mail to editHelp!.


FAQ: What is the difference between "approved", "before TB approval", "clean-up" and "editorial changes"? It is important to know what the differences are between the above mentioned categories. When you register documents you will have to select the correct one.

Approved (by TB) • The document has been approved by the Technical Body and will go through a complete pre-processing from EDM. It should be

published/sent on procedure as soon as possible;

Before TB approval • The document has not yet been approved by the Technical Body. An Editor prepares the document to make sure that as soon as it is

approved it can be published or sent on procedure. This process can significantly improve our production time if well handled (sent for registration at least 3 weeks before approval, no changes made in parallel).

Clean-up • The document could be sent during the drafting stage (e.g. to get a clean version for a meeting). The document will be treated either the day

it was sent or the day after. A quick pre-processing (ETSI styles, figure/table numbering, etc.) is done and all the potential problems are highlighted.

Editorial changes to existing publication • The document is corrected and published straight away. This can only happen when small editorial changes are involved and the

document has been recently published.


Registration Once the quality of the document has been checked, either the Officer or someone from the TB support shall register it in the Document Follow-up database so that it can be processed by and Editor.

Open the Document Follow-Up database from here: Z:\SPA\Private\Common\EDM_Registration\New_document_followup (2007).accdb;

Click Registration: the Registration window opens.

Fill in the new record and click save button to validate: an automatic e-mail pops-up on your screen. The document has to be attached to the e-mail which is sent to editHelp! who will then process the document.

: Make sure the title in the document and the one in WPM correspond as well as the keywords and the work item number. To help you in this matter, a title, keywords and WI number fields are giving you this information which is taken from WPM. Idem for the version number. Don't forget to update WPM if the version in the document is not the correct one and that we should publish with another version number.

If it is urgent, tick the corresponding box.

If something is specific to this document (e.g. keep hyperlink, track changes, etc.) please mention it in your e-mail to editHelp!.


NOTE: Batches of TB approved documents:

After a meeting, editHelp! receives a whole batch of TB approved

documents to process. Moreover several plenary meetings may

take place at the same time. In these cases, editHelp! is likely to

exceed the lead times. A good solution is to provide editHelp!

with the document before the meeting/TB approval.

Publication /

Phase

(MV, PE, V, etc)

no changes

editorial changes

The time between approval

and publication is short,

edithelp! checks only the

modified text.

The time between approval

and publication is very short.

Processing

(+questions for rapporteur/TO)

Registration

WG approval

(Clean-Up)

TB approval

Registration of documents before TB approval

Publication /

Phase (MV, PE, V, etc)

The time between the

approval and publication is

longer than when the

processing has already

been made beforehand.

Processing

(+questions for rapporteur/TO)

WG approval

(Clean Up)

Registration of TB approved documents

TB approval

Registration


FAQ: What is processing? When processing the document, the Editor checks if the document is compliant with the ETSI Drafting Rules (EDRs):

• compliance with WPM (multi-part (if any), procedure, schedule, etc.);

• common text blocks used (IPRs, copyright notification, foreword, references, definitions, abbreviations);

• references (titles, layout, public availability, etc.);

• styles;

• figures and tables;

• numbering (of clauses, figures, tables, annexes, examples, notes, etc.);

• punctuation;

• spell check;

• history box, etc.

It is not the responsibility of the Editor to carry out technical changes. The Editor compiles the questions in a "ReadMe" file and sends it to the rapporteur or expert and copy the Officer and TB support team.

When the rapporteur or expert sends back her/his answers, the changes are incorporated, the Editor then asks the Officer to check and sign off the document so that it can either be published or sent on procedure (MV, V, PE, etc.).


FAQ: What is the difference between "editorial changes" and "technical changes"?

• Technical changes: this type of change must be handled with great care. When you wish to make a change in the document such as the units and values, making technical modifications to the standard, adding a whole paragraph or deleting one. These are considered technical changes and are not under EDM's remit. A technical change may stop the publication of a deliverable until it is confirmed, unlike editorial changes.

• Editorial changes: these changes mostly concern the styles used in the document and general appearance of ETSI deliverables, but they also include English grammar, punctuation, etc. (see the ETSI Drafting Rules (EDRs): http://portal.etsi.org/Directives/home.asp). Editorial changes constitute the essence of EDM's work and are also very important, as the more editorial changes there are to be made, the longer it will take for EDM to process the document and in the end to publish it.


Signature When the Editor has finished with the processing of the document, an e-mail is sent (via editHelp!) to inform you that the document is ready to be signed off.

Open and check the document in Z:\SPA\Private\Standin\...; (the e-mail will containt the information where to find the document).

Open the Document Follow-Up from here: Z:\SPA\Private\Common\EDM_Registration\New_document_followup (2007).accdb.

Click "Electronic signature": the signature window opens.

Select your name, the TB and the document from the list, the date of signature and click "Save" button.

The document is electronically signed.

An automatic e-mail pops up on your screen and is to be sent to editHelp!.


ETSI and work item numbers The ETSI work item is the description of a standardization task approved by a TB. ETSI deliverables (SR, TR, TS, ES, EG, GS or EN) are produced as the result of an ETSI work item.


Choosing the type of ETSI deliverable (EN, TS, etc)

- The European Standard (EN): when the document is intended to meet needs specific to Europe and requires transposition into national standards or when the drafting of the document is required under an EC (European Commission)/EFTA (European Free Trade Association) mandate.

- The ETSI Standard (ES): when the document contains normative provisions and it is considered preferable or necessary that the document be submitted to the whole ETSI membership for its approval.

- The ETSI Guide (EG): when the document contains guidance on handling of technical standardization activities in the whole or major parts of the Technical Organization.

- The ETSI Technical Report (TR) is the default deliverable when the document contains mainly informative elements.

- The ETSI Technical Specification (TS) is the preferred deliverable when the document contains normative provisions and requires a short time to "market", validation and maintenance are essential. A TS may later be converted to an ES or an EN, or be used to publish the contents of a draft ES being sent for vote or a draft EN being sent for Public Enquiry or vote.

- The ETSI Special Report (SR): used for any other kind of document containing information of general ETSI member or public interest. The SR is also the appropriate deliverable type for a deliverable with dynamic content generated by a software application on the ETSI web site on the basis of database content.

- The ETSI Groups Specification (GS): when the document contains either specifications and/or information elements, produced by an Industry Specification Group.


ETSI acronyms

Deliverable types / Is the deliverable normative or informative

Who approves the

deliverables Specificities of the deliverable types

EN European Standard / Harmonized telecommunications series (normative provisions

National Standards

Organizations

document intended to meet needs specific to Europe (requires transposition into national standards).

EN HS. Document for which drafting is required under a European mandate.

EG ETSI Guide (normative and/or informative elements)

ETSI Members

guidance for example on implementing systems according to technical standards.

ES ETSI Standard (normative provisions) document whose submission to the whole ETSI membership is preferable or necessary.

TS Technical Specification (normative provisions)

Technical Body

document which provides short time to "market". Validation and maintenance are essential.

TR Technical Report (informative elements) use for feasibility studies, market reports, explanatory information, etc.

SR Special Report (informative document) Various purposes: - giving public availability to information; - being "virtual" documents, etc.

GS Group Specification

(normative provisions) ISG Members document intended to meet needs specific to an Industry Specification Group.

October 2009

Membership Approval Procedure, MAP (EG, ES) The process consists of weighted individual voting by ETSI full and associate members.

30 days15

days60 days

ETSI processETSI

process

15days

30 daysTB drafting

ETSI Membership Approval Process (MAP)TB process

Publication The Publication process consists of final editing of the Word version of the adopted GS, TS, TR or SR, archiving, and publication in PDF format. The published deliverable will then be made available via the PDA and constitutes a part of the ETSI Documentation Service (EDS).

Publication


Two-step Approval Procedure, TAP (EN) The process consists of a Public Enquiry followed by weighted national vote.

NOTE: Any comments and proposals received by the National Standards Organizations (NSOs) are consolidated and forwarded to the ETSI Secretariat and then to TB officials at the end of the Public Enquiry. Idem for Vote.

60 days 60 days

ETSI process

ETSI process

ETSI process

TB drafting15

days120 days

15days

15days

30 daysprocess

30 days 30 days

NSOs’ processNSOs’ process

TB process

TB review


One-step Approval Procedure, OAP (EN) The process consists of One-step Approval Procedure and weighted national voting which are combined in one phase.

NOTE: Any comments and proposals received by the National Standards Organizations (NSOs) are consolidated and forwarded to the ETSI Secretariat and then to TB officials at the end of the Public Enquiry. Idem for Vote.

TB drafting 30 days 15 days 15 days

ETSI process

120 days30 days

ETSI process TB process NSOs’ process


WPM milestones The status code indicates the stage in a standard's life cycle. There is a general progression from lower (0) to higher (12+) numbers.

Status code

Description Status code



Description

0 Creation of WI by WG/TB 7A Start of TB approval process 9 DaA Start of TB approval process 11 WI Waiting - see "Remarks"

0 a TB adoption of WI 7AA Start of pre-processing 9 DaB End of TB approval process 12 Publication

1 Start of work 7AB End of pre-processing 9 E Draft receipt by ETSI Secretariat 12 V Delivery to the EC

2 Early draft 7B End of TB approval process 9 WE Waiting - see "Remarks" 12 W Citation in the OJ

4 Stable draft 8 TB approval 10AA Start of pre-processing 13 TB decision to make document historical

5AA Start of pre-processing 8 A Draft receipt by ETSI Secretariat 10AB End of pre-processing 30 Withdrawal proposal verified

5AB End of pre-processing 8 WA Waiting - see "Remarks" 10 F Start of Vote 35 Withdrawal proposal TB approved

5 P Suspendend work 9AA Start of pre-processing 10 FM Start of Membership Vote 40 Start of Membership Withdrawal Vote

5 Q Resume work 9AB End of pre-processing 10 G End of OAP 40 Start of Withdrawal Vote

5S <to be defined> 9 B Start of OAP 10 G End of Vote 45 End of Membership Withdrawal Vote

6 Final draft for approval 9 B Start of Public Enquiry 10 GM End of Membership Vote 45 End of Withdrawal Vote

6 AA Start of pre-processing 9 C End of Public Enquiry 10 H Vote result determination (rejected) 50 Withdrawn

6 AB End of pre-processing 9 D Start of TB review of PE comments 10 J TB chairman informed

7 WG approval 9 Da TB approval 11 Vote result determination (adopted)

NOTE: Letter suffixes indicate "minor" steps through a single numeric status value.


TB Resolution meeting report

When a procedure is closed, the TB' officials have to download the TB resolution meeting report template from the e-Approval application (see picture).

Then when the report is completed, it has to be uploaded via the same application. The closed procedure and the correct document have to be selected.

Click on "upload TB resolution meeting report" in order to upload your report.


Harmonized Standards An EN (telecommunications series) the drafting of which has been entrusted to ETSI by a mandate from the European Commission under European Directive 98/48/EC (latest amendment to Directive 83/189/EEC) and has been drafted taking into account the applicable essential requirements of the "New Approach" Directive and whose reference has subsequently been announced in the Official Journal of the European Communities.

Foreword

The Foreword of an Harmonized Standard needs to be based on the skeleton document and shall contain specific text blocks which are mandatory and can be found in the skeleton document (http://portal.etsi.org/edithelp/zip/ETSI_HS_EN_skeleton.zip).

To check or write the Foreword of an Harmonized Standard:

Open the skeleton document.

Look in the Foreword section: you will find several text blocks (in normal font) and guidelines for when to use these text blocks (in blue font).

Scroll down to "Text to be used in Harmonized ENs", and check or copy the text block(s) you need according to your document's Technical Body and with regard to other factors (such as document with attachments or not, etc.).


dow (date of withdrawal) dates After the Foreword of all Harmonized Standards there shall be a table which should look like this:

Proposed national transposition dates

Date of latest announcement of this EN (doa): 3 months after ETSI publication

Date of latest publication of new National Standard or endorsement of this EN (dop/e):

6 months after doa

Date of withdrawal of any conflicting National Standard (dow): 18 months after doa

The two first lines of the table never change, as the date of latest announcement (doa) is always three months after ETSI publication and the date of latest publication (dop) is always six months after doa. However the date of withdrawal (dow) is more tricky: it can be either 6, 18, 24 or 36 months after doa. It is your responsibility to make sure that the dates are correct.

NOTE: Each time an editor is working on an Harmonized Standard, he or she will ask you to confirm that the dow date is correct.

Annex A (normative): HS Requirements and conformance Test specifications Table (HS-RTT)

This annex is mandatory for HSs related to article 3.2 of the R&TTE Directive. It should always be the first annex.

Annex <B> (informative): The EN title in the official languages Prior to publication in the Official Journal of the EU, the title of an Harmonized Standard has to be available in all of the official languages listed in this annex.

NOTE: For more information on Harmonized Standards' text blocks and more: http://portal.etsi.org/edithelp/guides.asp#Harmonized


Annex 1: Tools, programs and functions To do this, you will use several tools, programs and functions to help you in your work.

EWP: ETSI Work Programme is an application which contains all the information you may need with regard to your document's version number, title, keywords, status and much more.

PDA: Publication Download Area provides an easy way to search the ETSI publications catalogue, by running dynamic database queries.

e-Approval: This application provides an easy way to consult comments and/or results on ETSI Standards, ETSI Guides, ETSI European Standards and ETSI Harmonized European Standards, by running dynamic database queries.

Word functions: Microsoft Word® contains many features which are useful (and sometimes mandatory) for document editing such as revision marks, headers and footers, etc.

ETSI skeletons: Specific ETSI documents which contain the text blocks and styles used for each type of ETSI standards (EG, EN, TR, TS, etc.).

ETSI toolbar: All the ETSI styles pre-defined and applicable in one click, available under word.

ETSI template: A file that contains the ETSI structure and tools for shaping such elements as the style and page layout of finished files.

ReadMe file: Document produced by the editing team (editHelp!) to highlight all the potential problems which may occur in the document. This file is sent to you (also copied to the ETSI Technical Officer (TO)) to collect your answers which are then implemented.

Rapporteurs' pack: Contains sets of useful information and tools for drafting.

Editing checklist: To finally check that your draft complies with the EDRs.


Annex 2: Definitions

The technical organization of ETSI comprises the three types of Technical Bodies, designated either as an ETSI Project, a Technical Committee or an ETSI Partnership Project. They provide the forum for technical discussion and have as their main tasks the preparation of work programmes and ETSI deliverables.

ETSI deliverable: document (GS, TS, TR, SR, ES, EG or EN (telecommunications series), etc. produced as the result of an ETSI Work Item (WI).

ETSI Partnership Project (EPP): is an activity established when there is a need to co-operate with external bodies and where such co-operation cannot be accommodated within an EP or TC. [TWP 1.1.3].

ETSI Project (EP): is 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 WIs. An ETSI Project is relatively self-contained and has its own project management. [TWP 1.1.1].

ETSI standards: shall mean any standard adopted by ETSI including options therein or amended versions and shall include European Standards (ENs) (telecommunications series), ETSI Standards (ESs), Common Technical Regulations (CTRs) which are taken from ENs (telecommunications series) and including drafts of any of the foregoing, and documents made under the previous nomenclature, including ETSs, I-ETSs, parts of NETs and TBRs, the technical specifications of which are available to all MEMBERS, but not including any standards, or parts thereof, not made by ETSI. [RoP 15].

Technical Body (TB): is the primary decision making centre for all matters that fall within its ToR. It may establish WGs, if required. When this is the case, the TB shall decide on the rules for the WG, within the scope of the ETSI RoP and these ETSI TWPs. The TB shall retain responsibility.

Technical Committee (TC): supported by Working Groups where appropriate, is an activity organized around a set of ETSI WIs addressing a specific technology area that may contribute to more than one Technical Body and which provides continuity. [TWP 1.1.2].

Working Group: is established by TB if required. The TB shall retain responsibility for it. It may support TC where appropriate.

Work Item (WI): description of a standardization task approved by a Technical Body according to the procedures in clause 1.6.3 and adopted by the ETSI members. [TWP, annex A].

National Standards Organization: is a standards organization 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 in the telecommunication series as well as the transposition and withdrawal of national standards; and which is normally recognized by its Government as being authorized to make them available to the public at the national level.


Annex 3: Abbreviations For the purposes of the present document, the following abbreviations apply:

EDRs ETSI Drafting Rules EG ETSI Guide EN European Standard EP ETSI Project EPP ETSI Partnership Project ES ETSI Specification EWP ETSI Work Programme GS Group Specification IPR Intellectual Property Right ISG Industry Specification Group MAP Membership Approval Procedure NSO National Standards Organisation OAP One-step Approval Procedure OJEU Official Journal of the European Union PDA Publication Download Area SMP Standard Making Process SR Special Report STF Special Task Force TAP Two-step Approval Procedure TB Technical Body TC Technical Committee TG Task Group

Documents

ESP SMP guide