Page 155
`ETSI Drafting Rules, 20 May 2014
`ETSI Drafting Rules (EDRs)
`Version adopted by ETSI Director-General
`on 20 May 2014
`
`
`
`
`
`
`
`
`
`
`
`
`Microsoft Corporation
`
`Exhibit 1031-00001
`
`

`

`
`
`Page 156
`ETSI Drafting Rules (EDRs), May 2014
`
`What are the ETSI Drafting Rules?
`The present document specifies rules for the structure and drafting of documents intended to become ETSI
`deliverables. These rules complement the ETSI Technical Working Procedures (TWP)
`(http://portal.etsi.org/directives/home.asp) and are intended to ensure that such documents are drafted in as
`uniform a manner as is practicable, irrespective of the technical content.
`
`NOTE: A free-standing HTML version of the present document is available from editHelp!
`(Download EDRs_Navigator.chm for a more user-friendly version of the ETSI Drafting Rules).
`
`1
`
`ETSI deliverable
`
`All ETSI deliverable types
`1.1
`To draft an ETSI deliverable one of the following type shall be chosen:
`
`•
`
`•
`
`•
`
`•
`
`•
`
`•
`
`•
`
`The European Standard (EN) is the formal output for standardization at the European level and shall be
`chosen when the document is intended to meet needs that are specific to Europe and requires
`transposition into national standards or when the drafting of the document is required under an
`EC/EFTA mandate.
`
`The Technical Specification (TS) is the preferred deliverable when the document contains normative
`provisions and where rapid 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 Guide (EG) shall be chosen when the document contains informative elements providing
`guidance on handling of technical standardization activities in the whole or major parts of the Technical
`Organization.
`
`The ETSI Standard (ES) shall be chosen 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 Technical Report (TR) is the default deliverable when the document contains only informative
`elements.
`
`The Special Report (SR) shall be used for any other kind of document containing informative elements
`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 Group Specification (GS) is an ETSI deliverable, containing either specifications and/or
`information elements, produced by an Industry Specification Group.
`
`ETSI skeletons documents (pre-structured deliverable templates) are available from editHelp! website. Further
`information can be found in ETSI Directives.
`
`Microsoft Corporation
`
`Exhibit 1031-00002
`
`

`

`Page 157
`ETSI Drafting Rules (EDRs), May 2014
`
`
`Objective
`1.2
`The objective of an ETSI deliverable is to define clear and unambiguous provisions in order to facilitate
`international trade and communication. To achieve this objective, the ETSI deliverable shall:
`
`•
`
`•
`
`•
`
`•
`
`be as complete as necessary within the limits specified by its scope;
`
`be consistent, clear and accurate;
`
`provide a framework for future technological development; and
`
`be comprehensible to qualified persons who have not participated in its preparation.
`
`Homogeneity
`1.3
`Uniformity of structure, of style and of terminology shall be maintained not only within each ETSI deliverable,
`but also within a series of associated ETSI deliverables. The structure of associated ETSI deliverables and the
`numbering of their clauses shall, as far as possible, be identical. Analogous wording shall be used to express
`analogous provisions; identical wording shall be used to express identical provisions.
`
`The same term shall be used throughout each ETSI deliverable or series of ETSI deliverables to designate a
`given concept. The use of an alternative term (synonym) for a concept already defined shall be avoided. As far as
`possible, only one meaning shall be attributed to each term chosen.
`
`These requirements are particularly important not only to ensure comprehension of the ETSI deliverable but also
`to derive the maximum benefit available through automated text-processing techniques.
`
`Consistency
`1.4
`In order to achieve the aim of consistency within the complete body of ETSI deliverables, the text of every ETSI
`deliverable shall be in accordance with the relevant provisions of existing basic ETSI deliverables. This relates
`particularly to:
`
`•
`
`•
`
`•
`
`•
`
`•
`
`•
`
`•
`
`standardized terminology;
`
`principles and methods of terminology;
`
`quantities, units and their symbols;
`
`abbreviations;
`
`tables and figures numbering;
`
`bibliographic references; and
`
`graphical symbols.
`
`In addition, for specific technical aspects, the relevant provisions of general ETSI deliverables dealing with the
`following subjects shall be respected:
`
`•
`
`•
`
`•
`
`•
`
`•
`
`limits;
`
`tolerance of dimensions and uncertainty of measurement;
`
`preferred numbers;
`
`statistical methods; and
`
`environmental conditions and associated tests.
`
`Microsoft Corporation
`
`Exhibit 1031-00003
`
`

`

`Page 158
`ETSI Drafting Rules (EDRs), May 2014
`
`Equivalence of official language versions
`1.5
`ETSI deliverables shall be in the English language only.
`
`1.6
`
`Fitness for implementation as a national, regional or
`international standard
`The content of an ETSI deliverable shall be drawn up in such a way as to facilitate its direct application and its
`adoption without change as a national, regional or international standard (see ETSI Rules of Procedure,
`article 13.7, in ETSI Directives).
`
`Planning
`1.7
`Rules for the planning of new work items are given in ETSI Technical Working Procedures, annex C (see ETSI
`Directives). When creating a new work item, it is useful to consider whether the end result will be one or more
`ETSI deliverables.
`
`EXAMPLE:
`
`A multi-part deliverable.
`
`In the case where multiple deliverables are expected, some thought should be given to the intended structure and
`any interrelationships between the various components as this facilitates work planning in both the Technical
`Body (TB) and in the ETSI Secretariat.
`
`In the case of a multi-part ETSI deliverable, a list of the intended parts together with their titles should be drawn
`up, (see also clause 1.8 of the present document). The drafting rules given in the present document shall be
`applied from the very beginning of the work and throughout all subsequent stages to avoid delay at any stage.
`
`Subdivision of the subject matter
`1.8
`ETSI deliverables are so diverse that no universally acceptable rules can be established for the subdivision of the
`subject matter.
`
`However, as a general rule, an individual ETSI deliverable shall be prepared for each subject to be standardized
`and published as a complete entity. In specific cases and for practical reasons, for example:
`
`•
`
`•
`
`•
`
`•
`
`the ETSI deliverable is likely to become too voluminous;
`
`subsequent portions of the content are interlinked;
`
`portions of the ETSI deliverable could be referred to in regulations; or
`
`portions of the ETSI deliverable are intended to serve for certification purposes.
`
`The ETSI deliverable may be split into separate parts under the same number. This has the advantage that each
`part can be changed separately when the need arises.
`
`In particular, the aspects of a product which will be of separate interest to different parties (e.g. manufacturers,
`operators, certification bodies, legislative bodies) shall be clearly distinguished, preferably as parts of an ETSI
`deliverable or as separate ETSI deliverables.
`
`Such individual aspects are, for example:
`
`•
`
`performance requirements;
`
`• maintenance and service requirements; and
`
`•
`
`quality assessment.
`
`Microsoft Corporation
`
`Exhibit 1031-00004
`
`

`

`Page 159
`ETSI Drafting Rules (EDRs), May 2014
`
`Subdivision of the subject matter within a series of parts
`1.8.1
`There are two systems in use for subdividing into parts:
`
`a) Each part deals with a specific aspect of the subject and can stand alone.
`
`b) There are both common and specific aspects to the subject. The common aspects shall be given in
`part 1. Specific aspects (which may modify or supplement the common aspects and, therefore, cannot
`stand alone) shall be given in individual parts.
`
`Where the system described in b) is used, care shall be taken that the references from one part to another are
`always to the appropriate version. There are two ways to achieve this:
`
`•
`
`•
`
`If reference is made to a particular element, the reference shall be specific (see clause 2.10.1.3).
`
`Since the complete series of parts is normally under the control of the same Technical Body, the use of
`non-specific references (see clause 2.10.1.4) is permitted, provided that corresponding changes are
`implemented simultaneously in all parts.
`
`The use of non-specific references requires a high degree of discipline by the Technical Body responsible for the
`ETSI deliverable.
`
`Parts and sub-parts
`1.8.2
`The number of a part shall be indicated by Arabic numerals, beginning with 1 (limited to 2 digits), following the
`ETSI deliverable number and preceded by a hyphen, for example:
`
`•
`
`ES 201 999-1, ES 201 999-2, EN 300 356-33, EN 300 356-34.
`
`The number of a sub-part shall be indicated by Arabic numerals, beginning with 1-1 (limited to 2 digits),
`following the ETSI deliverable number and preceded by a hyphen, for example:
`
`•
`
`ES 201 999-1-1, ES 201 999-1-2, EN 300 356-33-10, EN 300 356-33-11.
`
`Legal master of an ETSI deliverable
`1.9
`ETSI deliverables are made publicly available by ETSI in PDF format. Other formats may also be available.
`
`From a legal point of view, the official version of a document is the one which is recognized by the author as
`being the definitive and mature version of his/her work at a certain date. The official version of a document
`constitutes a reference from which it is possible to identify that amendments have been made.
`
`In ETSI, the reference version of an ETSI deliverable (until further amendments are made) is the one that has
`been checked by the Secretariat and incorporates the amendments resulting from the approval process prescribed
`for the ETSI deliverable in the Technical Working Procedures. The reference version of an ETSI deliverable is
`the Portable Document Format (PDF) kept on a specific network drive within the ETSI Secretariat.
`
`Structure of an ETSI deliverable
`2
`An ETSI deliverable need not contain all the normative technical elements shown in table 1 and it may contain
`others than those shown. Both the nature of the normative technical elements and their sequence are determined
`by the nature of the ETSI deliverable in question.
`
`In order to comply with the structure of an ETSI deliverable, the use of the appropriate ETSI "skeleton
`document" is mandatory. Skeletons are available from editHelp! website.
`
`Microsoft Corporation
`
`Exhibit 1031-00005
`
`

`

`
`
`Page 160
`ETSI Drafting Rules (EDRs), May 2014
`
`Table 1: Typical arrangement of elements in an ETSI deliverable
`Legend: Bold type
`= required element
`
`Unbold type (regular) = optional element
`
`Upright type
`= normative element
`
`Italic type
`=
`informative element
`Type of element
`Arrangement of elements
`in an ETSI deliverable
`Cover page
`Table of contents for clauses
`Tables of contents for figures and/or
`tables
`Intellectual Property Rights
`Foreword
`Transposition (ENs only)
`Modal verbs terminology
`Executive summary
`Introduction
`
`Informative preliminary
`
`Reference
`
`clause 2.1
`clause 2.3.1
`clause 2.3.2
`
`clause 2.4
`clause 2.5
`clause 2.5.1
`clause 2.6
`clause 2.7
`clause 2.8
`
`Permitted content of
`element(s) in an ETSI deliverable
`Title
`(generated content)
`(generated content)
`
`Text
`Note(s)
`Table
`Text
`Figure(s)
`Table(s)
`Note(s)
`Text
`Figure(s)
`Table(s)
`Note(s)
`References
`Normative Reference(s)
`Text
`Figure(s)
`Table(s)
`Note(s)
`Text
`Figure(s)
`Table(s
`Note(s)
`Additional informative reading material
`Table
`
`Scope
`Informative Reference(s)
`Definition(s)
`Symbol(s) and abbreviation(s)
`
`Normative References
`Requirements
`
`Normative annex(s)
`
`Informative guidance
`Informative annex(s)
`
`Bibliography
`Change history/Change request
`(history)
`History
`
`Informative general
`
`Normative general
`
`Normative technical
`
`Informative
`supplementary
`
`
`
`clause 2.9
`clause 2.10.2
`clause 2.11.1
`clause 2.11.2
`
`clause 2.10
`clauses 3 and 3.2
`
`clause 2.13.1
`
`clause 2.13.2
`
`clause 2.14
`clause 2.15
`
`clause 2.16
`
`Table
`
`Cover page
`2.1
`The cover page shall contain the title of the ETSI deliverable, together with the version number and the date of
`publication.
`
`The wording of the title shall be established by the Technical Body with the greatest care. While being as
`concise as possible, it shall indicate, without ambiguity, the subject matter of the ETSI deliverable in such a way
`as to distinguish it from that of other ETSI deliverables, without going into unnecessary detail. Any necessary
`additional particulars shall be given in the scope.
`
`The title shall be composed of separate elements, each as short as possible, proceeding from the general to the
`particular. In general, not more than the following three elements should be used:
`
`a)
`
`b)
`
`c)
`
`an introductory element (optional) indicating the general field to which the ETSI deliverable belongs; it
`should not be based on the name of the Technical Body which drafted the deliverable, especially if this
`is too broad to add much value;
`
`a main element (obligatory) indicating the principal subject treated within that general field;
`
`a complementary element (optional) indicating the particular aspect of the principal subject or giving
`details that distinguish the ETSI deliverable from other ETSI deliverables, or other parts of the same
`ETSI deliverable.
`
`The ETSI Secretariat is responsible for the final preparation of the cover page.
`
`Microsoft Corporation
`
`Exhibit 1031-00006
`
`

`

`Page 161
`ETSI Drafting Rules (EDRs), May 2014
`
`
`For multi-part deliverables, all the individual titles in a series of parts shall contain the same introductory
`element (if present) and main element, while the complementary element shall be different in each case in order
`to distinguish the parts from one another. The complementary element shall be preceded in each case by the
`designation "Part …:" and "Sub-part ...:".
`
`For endorsement of documents from other standards organizations, see clause 9.
`
`Second page
`2.2
`The content of the second page is provided by the ETSI Secretariat and shall not be modified. The following
`shall be filled in:
`
`• Work Item number
`
`•
`
`Keywords of the deliverable
`
`2.3
`
`Table of contents
`
`Table of contents for clauses
`2.3.1
`The table of contents shall be generated automatically and shall not be set manually. The title shall be
`"Contents".
`
`•
`
`•
`
`Use TT style for the title.
`
`Use the field {TOC \o\w} for the table itself.
`
`NOTE 1: The ETSI Secretariat is responsible for the final layout of the Table of Contents.
`
`NOTE 2: To unlock the Table of Contents: select the Table of Contents, click simultaneously: Ctrl + Shift +
`F11.
`To lock it: reselect the Table of Contents and then click simultaneously: Ctrl + F11.
`
`Tables of contents for figures and/or tables
`2.3.2
`The tables of contents for figures and/or tables are also allowed. They shall be generated automatically and not
`be set manually. If present, they shall appear after the table of contents for clauses "Contents". The titles shall be
`"List of figures" and/or "List of tables" the clause shall be unnumbered.
`
`•
`
`•
`
`Use TT style for the title.
`
`Use the field {TOC \t "TF" \c} for the list of figures and the field {TOC \t "TH" \c} for the list of
`tables.
`
`Microsoft Corporation
`
`Exhibit 1031-00007
`
`

`

`Page 162
`ETSI Drafting Rules (EDRs), May 2014
`
`Intellectual Property Rights (IPRs)
`2.4
`The "Intellectual Property Rights (IPR)" is the first unnumbered clause. It is a required, informative element.
`
`The content, provided by the ETSI Secretariat, shall not be modified and can be found in the skeleton documents
`available from editHelp! website.
`
`Foreword
`2.5
`The "Foreword" is the second unnumbered clause and on the same page as the IPR clause. It is a required,
`informative element. It shall not contain requirements, figures or tables, except for the transposition table (see
`clause 2.5.1).
`
`It shall always contain a general part, provided by the ETSI Secretariat, giving information on:
`
`•
`
`•
`
`the designation and name of the Technical Body that prepared the ETSI deliverable; and
`
`information regarding the approval of the ETSI deliverable.
`
`Optionally, a specific part of the Foreword may be provided by the Technical Body including as many of the
`following as is appropriate:
`
`•
`
`•
`
`•
`
`•
`
`•
`
`an indication of any other organization that has contributed to the preparation of the ETSI deliverable;
`
`a statement that the ETSI deliverable cancels and replaces other documents in whole or in part;
`
`a statement of significant technical changes from the previous version of the ETSI deliverable;
`
`the relationship of the ETSI deliverable to other ETSI deliverables or other documents;
`
`the existence of an electronic attachment accompanying the ETSI deliverables, if this is not mentioned
`elsewhere.
`
`For multi-part deliverables, there are two options for explaining the relationship between the various parts in the
`series. Either:
`
`a)
`
`b)
`
`the first part shall include in its Foreword an explanation of the intended structure of the series. In the
`"Foreword" of each part belonging to the series, a reference shall be made to the titles of all other parts,
`if they are known;
`
`a specific part (part 1) shall provide an explanation of the intended structure of the series, together with
`details of the titles of the various parts and sub-parts. Each time a new part or sub-part of the
`deliverable is made publicly available, the Secretariat shall publish a new version of part 1 showing the
`details of the new document.
`
`Option b) is the preferred option.
`
`Examples and textblocks to be used can be found in the appropriate skeleton document available from
`editHelp! website.
`
`Transposition table
`2.5.1
`Each European Standard (EN) shall contain a transposition table as the last element in the Foreword. This
`element is provided by the Secretariat and its purpose is described in the ETSI Technical Working Procedures,
`clause 2.4 (see ETSI Directives).
`
`Microsoft Corporation
`
`Exhibit 1031-00008
`
`

`

`Page 163
`ETSI Drafting Rules (EDRs), May 2014
`
`Modal verbs terminology
`2.6
`The "Modal verbs terminology" appears after the "Foreword", it shall not be numbered. It is a required
`informative element.
`
`The "Modal verbs terminology" specifies how the modal verbs shall be used within the ETSI deliverable (see
`also clause 3.2).
`
`The content, provided by the ETSI Secretariat, shall not be modified and can be found in the skeleton documents
`available from editHelp! website.
`
`Executive summary
`2.7
`The "Executive summary" appears after the "Modal verbs terminology" and before the "Introduction" and shall
`not be numbered. It is an optional informative element and shall not contain requirements.
`
`The "Executive summary" is used, if required, to summarize the ETSI deliverable. It contains enough
`information for the readers to become acquainted with the full document without reading it. It is usually one
`page or shorter.
`
`Introduction
`2.8
`The "Introduction" shall appear after the "Executive summary" (if present). It is an optional informative and
`shall not contain requirements.
`
`The "Introduction" is used, if required, to give specific information or commentary about the technical content of
`the ETSI deliverable, and about the reasons prompting its preparation.
`
`It shall not be numbered unless there is a need to create numbered subdivisions. In this case, it shall be numbered
`0 with clauses being numbered 0.1, 0.2, etc. Any numbered figure, table or displayed formula shall be numbered
`normally beginning with 1 (see also clause 2.12.1).
`
`Scope
`2.9
`The "Scope" shall start on a new page and be clause number 1 of each ETSI deliverable. It is a required
`informative element and shall not contain requirements.
`
`The "Scope" defines without ambiguity the subject of the ETSI deliverable and the aspect(s) covered, thereby
`indicating the limits of applicability of the ETSI deliverable or particular parts of it.
`
`In deliverables that are subdivided into part, the scope of each part shall define the subject of that part of the
`deliverable only.
`
`The "Scope" shall be succinct so that it can be used as a summary for bibliographic purposes.
`
`This element shall be worded as a series of statements of fact.
`
`Forms of expression such as the following shall be used:
`
`"The present document
`
`•
`
`specify:
`
`the functional requirements for …"
`
`a method of …"
`
`the characteristics of …";
`
`•
`
`establishes
`
`a system for …"
`
`
`
`general principles for …";
`
`Microsoft Corporation
`
`Exhibit 1031-00009
`
`

`

`Page 164
`ETSI Drafting Rules (EDRs), May 2014
`
`gives guidelines for …";
`
`gives terms and definitions …".
`
`
`
`•
`
`•
`
`Statements of applicability of the ETSI deliverable shall be introduced by the following wording:
`
`•
`
`"The present document is applicable to …".
`
`2.10 References
`"References" shall be clause number 2 of each ETSI deliverable.It is a required element and shall not contain
`requirements.
`
`The "References" clause lists the documents referred to in the body of the ETSI deliverable. It consists of
`clause 2.1 "Normative references" and clause 2.2 "Informative references.
`
`ETSI deliverables may include references to ETSI documents and also to documents of non-ETSI organizations .
`In the second case it shall be ensured that implementers and evaluators of deliverables standardized by ETSI, and
`other interested parties, have access to all materials needed to implement those deliverables. These rules apply to
`documents that are produced in accordance with the ETSI Rules of Procedures but also to any deliverables that
`are developed elsewhere that are sent to ETSI to be standardized.
`
`These rules are pointed toward normative references because they are functionally a part of the ETSI deliverable
`itself. It is best practice to follow these principles for informative references as well, but more flexibility is
`permitted for informative references because these documents are not strictly necessary for the implementation
`of an ETSI deliverable.
`
`Reproduction of elements from other documents is deprecated (i.e. referencing is the preferred method in ETSI).
`
`The textblock to be used for the "References" clause can be found in the appropriate skeleton document available
`from editHelp! website.
`
`2.10.1 Normative references
`The "Normative References" clause is numbered 2.1and lists references to documents to which conformance is
`necessary to claim compliance to the ETSI deliverable containing the reference. Normative references are
`mentioned in the body of the ETSI deliverable and shall be indicated by an appropriate wording which
`underlines the normative impact of the reference within the document.
`
`EXAMPLE:
`
`"the test method shall be as described in Recommendation ITU-T M.50",
`Recommendation ITU-T M.50 is a normative reference.
`
`In considering whether a normative reference to a document should be included in an ETSI deliverable,
`preference should be given to standards and specifications by recognized standards development organizations
`and to the directives of the European Union.
`
`Normative referencing of documents under the possession of other organizations is allowed where the use of
`such normative references has been justified by the Technical Body in charge of development of the ETSI
`deliverable containing the reference. Where an objection to the use of a normative reference has been raised
`within Technical Body discussion, this shall be noted in the minutes or some other record that will be available
`to ETSI Members.
`
`Normative references list shall contain:
`
`•
`
`•
`
`•
`
`•
`
`the issuing organization;
`
`the document identity;
`
`the edition or version number or date of publication (for Harmonized Standards, see clause 8.4);
`
`the title.
`
`Microsoft Corporation
`
`Exhibit 1031-00010
`
`

`

`
`The list shall not include:
`
`Page 165
`ETSI Drafting Rules (EDRs), May 2014
`
`•
`
`•
`
`•
`
`•
`
`•
`
`referenced documents which are not publicly available (see clause 2.10.1.1);
`
`referenced documents which are only cited in an informative manner (such references shall be listed in
`clause 2.2 "Informative references");
`
`other reading material not explicitly referred to in the body of the ETSI deliverable (such publications
`have to be listed in an informative annex entitled "Bibliography" see clause 2.14);
`
`referenced documents not available in English language.
`
`Use the EX style, enclose the number in square brackets and separate it from the title with a tab (you
`may use sequence fields for automatically numbering references, see clause 6.9.2. (See example).
`
`EXAMPLE:
`
`[1]
`
`[2]
`
`ETSI EN 301 025-3: "Electromagnetic compatibility and Radio spectrum Matters (ERM);
`VHF radiotelephone equipment for general communications and associated equipment for
`Class "D" Digital Selective Calling (DSC); Part 3: Harmonized EN under article 3.3 (e) of
`the R&TTE Directive".
`
`ETSI EN 300 163: "Television systems; NICAM 728: transmission of two-channel digital
`sound with terrestrial television systems B, G, H, I, K1 and L".
`
`Public availability of the normative references
`2.10.1.1
`A normative reference shall be publicly available in English language during the approval phases, at the time of
`publication and for the duration of the expected lifespan of the ETSI deliverable. If public availability cannot be
`guaranteed after publication of the ETSI deliverable has occurred, the originating body of the document shall be
`requested to provide ETSI with the right to make available the text; the ETSI Secretariat shall establish and
`maintain a list of the referenced documents and the relevant external bodies, for document tracking and cross-
`referencing purposes, and keep the necessary liaison with the originating body.
`
`If normative references in an ETSI deliverable are not publicly available during the drafting stage, the
`deliverable shall not be submitted to an approval procedure until the reference is publicly available or the text
`shall be made available to be held by ETSI.
`
`For online referenced documents, information sufficient to identify and locate the source shall be provided.
`Preferably, the primary source of the referenced document should be cited, in order to ensure traceability.
`Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The
`reference shall include the method of access to the referenced document and the full network address, with the
`same punctuation and use of upper case and lower case letters.
`
`Test suites availability
`2.10.1.2
`If conformance with a specification that includes normative references requires the use of a test suite, the test
`suite for the normatively referenced part should also be made publicly available. Any such test suite should be
`usable by potential implementers on terms at least as favourable as those contained in ETSI Rules of Procedure,
`annex 6 (see ETSI Directives).
`
`Specific normative references
`2.10.1.3
`A "specific" reference is a reference to the particular revision or version of the normatively referenced document.
`Specific references are favoured because they lead to permanence and stability in ETSI deliverables. Normative
`references generally should be limited to documents that are finally approved by the organizations responsible
`for issuing them.
`
`Unlike ETSI, many other Standards bodies, (e.g. ISO, CEN, CENELEC, etc.) have a policy of regularly
`reviewing/maintaining their deliverables. Their procedures also involve the automatic withdrawal of the previous
`version. It therefore follows that any ETSI deliverable making specific references to such documents will need to
`be revised.
`
`Microsoft Corporation
`
`Exhibit 1031-00011
`
`

`

`Page 166
`ETSI Drafting Rules (EDRs), May 2014
`
`
`Non-specific normative references
`2.10.1.4
`A "non-specific" reference is a reference to a deliverable that will apply to all future revisions and versions of the
`originally referenced document. Non-specific references require additional procedures to ensure that any
`revisions made necessary to the ETSI deliverable by virtue of revisions made to the normatively referenced
`materials are considered by the appropriate Technical Body in charge of the ETSI deliverable.
`
`If a normative reference is non-specific, the Technical Body in charge of the ETSI deliverable should establish a
`process for gaining access to all future revisions and versions of the normatively referenced material. In addition,
`the Technical Body should establish a work plan for ensuring that any such new revisions and versions of the
`normatively referenced material do not require a substantive amendment to the ETSI deliverable referencing that
`document or, alternatively, for ensuring that any such needed amendments are made and approved appropriately.
`Any future versions incorporated by reference shall meet with the requirements for public availability and
`Intellectual Property.
`
`It may, therefore, be appropriate that an ETSI deliverable contain non-specific references, provided that the
`following requirements can be fulfilled:
`
`•
`
`•
`
`it is accepted that it will be possible to use future versions of the document referred to for the purposes
`of the referring ETSI deliverable;
`
`it is granted that the structure of the document referred to will not change for the specific areas which
`are used by the referring ETSI deliverable (e.g. the referred to document is controlled by the same
`Technical Body as the referring one).
`
`Referring to specific or non-specific references
`2.10.1.5
`The following form shall be used consistently throughout the deliverable:
`
`•
`
`" … in accordance with ES 201 001 [n], clause 3, … ".
`
`ETSI Intellectual Property Rights (IPRs) policy for normative references
`2.10.1.6
`ETSI promotes a policy that any essential Intellectual Property Rights (IPRs) embodied in normatively
`referenced documents be available for use in ETSI deliverables on licensing and disclosure terms that do not
`materially differ from the terms defined in the ETSI IPR Policy. This normative reference policy, however, does
`not imply any obligation on the Technical Body, ETSI members or Technical Body members to investigate or
`ensure the availability of any essential normatively referenced IPRs, under any specific licensing and disclosure
`terms, at the time a normative reference is provided, explicitly or implicitly, within an ETSI deliverable.
`
`Informative references
`2.10.2
`The "Informative references" clause is numbered 2.2 and lists references to documents that may be useful in
`implementing an ETSI deliverable or add to the reader's understanding but which are not required for
`conformance to the ETSI deliverable. Informative references are mentioned in the body of the ETSI deliverable
`and are indicated by an appropriate wording which does not imply normative impact (claim of conformity) of
`the reference within the document.
`
`EXAMPLE:
`
`"the test method is described in Recommendation ITU-T M.50",
`Recommendation ITU-T M.50 is an informative reference.
`
`Informative references should be publicly available (but no check will be made by the ETSI Secretariat).
`
`•
`
`Use the EX style, add the letter "i" (for informative) before the number (which shall be in square
`brackets) and separate this from the title with a tab (you may use sequence fields for automatically
`numbering references, see clause 6.9.2. (See example).
`
`Microsoft Corporation
`
`Exhibit 1031-00012
`
`

`

`
`
`EXAMPLE:
`
`[i.1]
`
`[i.2]
`
`Page 167
`ETSI Drafting Rules (EDRs), May 2014
`
`ETSI TR 102 473: "Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Use
`Cases and Services".
`
`ETSI TR 102 469: "Digital Video Broadcasting (DVB); IP Datacast over DVB-H:
`Architecture".
`
`Informative references not mentioned in the body of the document will be listed in the Bibliography annex, see
`clause 2.14.
`
`2.10.3 Reference