1、 ETSI TR 102 317 V1.1.1 (2004-06)Technical Report Electronic Signatures and Infrastructures (ESI);Process and tools for maintenance of ETSI deliverablesETSI ETSI TR 102 317 V1.1.1 (2004-06) 2 Reference DTR/ESI-000029 Keywords e-commerce, electronic signature, security ETSI 650 Route des Lucioles F-0
2、6921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.et
3、si.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing o
4、n ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal
5、.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telec
6、ommunications Standards Institute 2004. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI
7、 registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 317 V1.1.1 (2004-06) 3 Contents Intellectual Property Rights5 Foreword.5 Introduction 5 1 Scope 6 2 References 6 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .7 4 Maintenance
8、activity 7 4.1 History of the TC ESI maintenance activity.7 4.2 Revised maintenance process .7 4.2.1 General description.7 4.2.2 Tracking stage.8 4.2.3 Pre-processing stage .8 4.2.4 Processing stage8 4.3 Maintenance report.9 4.3.1 Maintenance report and its role in the maintenance process.9 4.3.2 St
9、ructure of the maintenance report9 4.3.2.1 General structure .9 4.3.2.2 Clause 5: fields and structure 9 4.3.2.3 Annex A: fields and structure10 5 Maintenance tools 11 5.1 Description of the tools 11 5.2 Requirements12 5.3 How to install the tools.12 5.4 How to use the tools .13 5.4.1 Maintenance pr
10、ocess and general instructions13 5.4.2 Inserting the elementary comments into the database.13 5.4.3 Creating the body of the maintenance report 15 5.4.4 Finishing the maintenance report17 5.5 How the tools work 17 5.5.1 Mail Merge database.17 5.5.2 Mail Merge Word feature and template18 5.5.3 Macro
11、producing the maintenance report target file .18 5.6 Generalized use of the maintenance tools 18 6 Tools improvements.19 6.1 Adding some automatic formatting capabilities .19 6.2 Improving the database structure19 6.3 Improving the database insertion form.19 6.4 Making the tools corporate.19 Annex A
12、: Database structure20 A.1 Tables .20 A.1.1 Table “tComments“ 20 A.1.1.1 Columns20 A.1.2 Table “tCommentType“20 A.1.2.1 Columns20 A.1.2.2 Predefined records 20 A.1.3 Table “tResolutionStatus“ 21 A.1.3.1 Columns21 A.1.3.2 Predefined records 21 ETSI ETSI TR 102 317 V1.1.1 (2004-06) 4 A.2 Relationships
13、 diagram .21 A.3 Queries .22 Annex B: MS Word global template: macros VBA sources and forms.23 B.1 VBA sources 23 B.1.1 Module “modCode“23 B.1.2 Module “frmMenu“ 27 B.1.3 Module “frmInfo“.29 B.2 VBA forms .30 B.2.1 Form “frmMenu“30 B.2.2 Form “frmInfo“.30 Annex C: How to recreate the tools31 C.1 Int
14、roduction 31 C.2 Procedures for maintenance tools recreation31 C.2.1 Mail Merge database 31 C.2.2 VBA macros.31 C.2.3 Mail Merge template 32 Annex D: Mail Merge template and maintenance report samples 33 D.1 Sample of Mail Merge template.33 D.2 Sample of clause 5 of the maintenance report base file
15、.34 D.3 Samples of elementary comments within clause 5 of the maintenance report.34 D.3.1 Introduction 34 D.3.2 Example n. 1.35 D.3.3 Example n. 2.36 D.4 Samples of contribution with metadata within annex A of the maintenance report.36 D.4.1 Introduction 36 D.4.2 Example n. 1.37 D.4.3 Example n. 2.3
16、8 History 39 ETSI ETSI TR 102 317 V1.1.1 (2004-06) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and ca
17、n be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursu
18、ant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present docu
19、ment. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Electronic Signatures and Infrastructures (ESI). Introduction The ETSI Technical Committee on Electronic Signatures and Infrastructures (TC ESI) has a significant number of technical specifications that need to b
20、e maintained. This maintenance activity includes: tracking all comments received; resolving a certain number of comments; issuing a new revision of selected deliverables; and updating the maintenance report that documents the whole activity. In order to facilitate and speed-up its maintenance activi
21、ty some tools have been developed. Even though they were developed to support maintenance of technical specifications within TC ESI, they are considered have wider applicability. Therefore TC ESI decided to document them in the present document. These tools provide ability to track the elementary co
22、mments on several technical specifications (keeping also many details called “metadata“ as the reference to the original contributions) and record their final resolution. Starting from the elementary comments stored in a database, these tools can automatically produce the body of an ETSI Technical R
23、eport that documents the current status of comments on the TC ESI deliverables. These tools can be used to: report to the working group; input to experts working on revising specifications; publish a report that identifies the status of maintenance activities on ETSI specifications. ETSI ETSI TR 102
24、 317 V1.1.1 (2004-06) 6 1 Scope The present document describes the maintenance activity as performed by TC ESI, the maintenance report and the tools developed to simplify and speed-up the maintenance tasks. The core of the present document is the description of the various aspects of these tools: ho
25、w to install and use them, how they work and what can be done in order to improve them. Clause 4 contains the explanation of the maintenance process as performed by TC ESI and describes the maintenance report; clause 5 describes the tools developed by TC ESI in order to simplify the management of th
26、e maintenance tasks. Clause 6 describes further development of the maintenance tools that can be pursued. Annex A describes the database structure, annex B contains the source code of the developed macros and the pictures of the forms and annex C includes a sample of Mail Merge template, a sample of
27、 the core of the maintenance report base file and two examples of tables generated with the tools described in the present document and to be inserted in the maintenance report. Annex D describes how to re-create the tools having only the present document. 2 References For the purposes of this Techn
28、ical Report (TR) the following references apply: 1 ETSI TR 102 046 (V1.1.1): “Electronic Signatures and Infrastructures (ESI); Maintenance Report“. 2 ETSI TR 102 046 (V1.2.1): “Electronic Signatures and Infrastructures (ESI); Maintenance Report“. 3 ETSI SR 001 262 (V1.8.1): “ETSI drafting rules“. 3
29、Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: contribution: every block of comments (at least one comment) received as a whole, related to only one deliverable and identified by a unique code; it can be a complex co
30、mment or a set of comments elementary comment: one of the atomic comments obtained by splitting a contribution during the pre-processing stage; it could coincide with the contribution Mail Merge: MS Word feature that performs the mail merge operation Mail Merge database: MS Access database containin
31、g the elementary comments; it serves as data source for the Mail Merge operation Mail Merge template: MS Word file containing the template; it includes the Mail merge fields as available from the Mail Merge database properly formatted within a table maintenance activity phase: historical round of th
32、e maintenance activity as performed by TC ESI maintenance process stage: part of the revised maintenance process as improved by TC ESI during the second maintenance activity phase maintenance report: report covering the status of maintenance activity; it can be published as an ETSI Technical Report
33、(as done by TC ESI) maintenance report base file: file containing the maintenance report except for the clause collecting the elementary comments: this clause includes the placeholders for the tables collecting the elementary comments for each deliverable ETSI ETSI TR 102 317 V1.1.1 (2004-06) 7 main
34、tenance report target file: file containing the complete maintenance report after having launched the Mail Merge operation and the ETSI maintenance tools 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: HTML HyperText Markup Language SQL Structured Query
35、 LanguageSTF Specialist Task Force VBA Visual Basic for Applications 4 Maintenance activity 4.1 History of the TC ESI maintenance activity After having developed the first set of deliverables, TC ESI started the maintenance activity collecting all the comments received on the published deliverables,
36、 both from inside and outside. The results of this earlier maintenance activity resulted in a previous version of the maintenance report being published without the use of any supporting tools (TR 102 046 1). This document simply collects all the comments received keeping them in their original form
37、at. Later, a second maintenance phase has been started. In this phase it was decided to improve the maintenance process making it more structured and to support this improved process by producing some helpful tools. The outcomes of this second phase are: a revision of the maintenance process; the ET
38、SI maintenance tools developed in order to support the revised maintenance report, simplifying and speeding-up it; a new and completely restructured version of TR 102 046 2 (described in clause 4.3), the TC ESI maintenance report that includes the output of the first phase of the maintenance activit
39、y; this maintenance report serves as tool for the maintenance process (TC ESI internal purpose) and as public documentation of the TC ESI maintenance activity (public purpose). Even if the mentioned outcomes are related to the TC ESI maintenance activity, an aim of this technical committee was to sh
40、are this work with other technical committees and bodies involved in the maintenance of their deliverables. For this purpose TC ESI decided to document its maintenance activity and tools in an ETSI Technical Report that is constituted by the present document. 4.2 Revised maintenance process 4.2.1 Ge
41、neral description The maintenance process, as revised during the second maintenance activity phase, includes many stages starting from receiving the comments to approving and publishing the new version of the deliverables. The purpose of the maintenance report and of the tools described in this docu
42、ment is helping the people involved in the maintenance process by covering its first three phases: tracking, pre-processing and processing the comments received. For the purposes of this document and of the maintenance report, every block of comments received as a whole (at least one comment but it
43、can be a complex comment or a set of comments), related to only one deliverable and identified by a unique code is “contribution“. ETSI ETSI TR 102 317 V1.1.1 (2004-06) 8 There are different subjects involved in the maintenance process: the STF in charge to receive the contribution and to maintain t
44、he maintenance report: - the general maintenance STF; the STF in charge to produce a new version of a well defined set of deliverables: - the maintenance STF specific for a (set of) deliverable(s); members of the TC ESI. It is possible that one ETSI STF acts both as general maintenance STF and speci
45、fic maintenance STF. 4.2.2 Tracking stage This stage is to record the contributions received from any source, keeping them in their original format. This stage is accomplished by the general maintenance STF. 4.2.3 Pre-processing stage A single contribution may be constituted by a set of comments or
46、a complex comment and these comments may refer to a single deliverable or many deliverables; it is impossible to know in advance how a contribution can be structured. This stage is to transform the contributions from an unstructured form to a structured set of elementary comments: each elementary co
47、mment is a single and simple comment with some metadata attached to. The outcome of this stage is a collection of elementary comments grouped by deliverable; each elementary comment is ready to be processed independently of the others in the next stage. This stage is accomplished by the general main
48、tenance STF. 4.2.4 Processing stage This stage is to resolve comments. This might be done separately for each elementary comment. However it is suggested to operate this stage activity on a set of elementary comments all related to a single deliverable; the comment resolution for each comment set re
49、lated to one deliverable may be operated separately. Hence starting from this point it is assumed that each set of elementary comments related to a single deliverable will be better treated as a whole block; therefore and the maintenance report has been structured and the maintenance tools have been developed to fully support this assumption. For each set of elementary comments related to a single deliverable, this stage activity can be done in different ways and by different subjects: by the general maintenance STF; by the general and s
