ITU-T SERIES Z IMP-2016 Specification and Description Language implementer-s guide C Version 3 0 1 (Study Group 17)《语言实现指导的规范与描述–版本3 0 1(研究组17)》.pdf

《ITU-T SERIES Z IMP-2016 Specification and Description Language implementer-s guide C Version 3 0 1 (Study Group 17)《语言实现指导的规范与描述–版本3 0 1(研究组17)》.pdf》由会员分享，可在线阅读，更多相关《ITU-T SERIES Z IMP-2016 Specification and Description Language implementer-s guide C Version 3 0 1 (Study Group 17)《语言实现指导的规范与描述–版本3 0 1(研究组17)》.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Implementers guide TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (March 2016) SERIES Z: LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS Formal description techniques (FDT) Specification and Descriptio

2、n Language (SDL) Specification and Description Language implementers guide Version 3.0.0 This page is intentionally blank. Summary The purpose of this implementers guide is to compile reported defects with resolutions and other agreed changes for the ITU-T Specification and Description Language rela

3、ted ITU-T Recommendations (Z.100, Z.101, Z.102, Z.103, Z.104, Z.105, Z.106, Z.107, Z.109, Z.111 and Z.119) prior to these changes being published in approved Recommendations. This implementers guide includes all changes agreed by Q12/17 to the texts of the relevant Recommendations consented or in-fo

4、rce at the date the guide is approved by SG17 and applies until either the implementers guide is updated to following version or all the changes are incorporated into the relevant Recommendations and the implementers guide is updated to version 3.0.1. It is assumed that consented Recommendations wil

5、l subsequently be approved. Source SDL implementers guide version 3.0.0 was approved on 23 March 2016 by ITU-T Study Group 17 (2013-2016) ITU 2016 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. CONTENTS Page 1

6、 Introduction . 1 1.1 Scope of the Guide . 1 1.2 Approval of the Guide 1 1.3 Distribution of the Guide 1 1.4 Contact 2 2 Error reporting procedure . 3 2.1 Submission of error reports and change requests . 3 2.2 Resolution of errors 3 2.3 Documenting the Resolution of Defects and maintenance changes

7、. 3 Annex A Change Request Form 4 Annex B Master List of Changes 5 B.1 Objectives and scope 5 B.2 Terminology . 5 B.3 Maintenance of Z.100 to Z.109 6 B.4 Z.100 changes . 6 B.5 Z.101 changes . 6 B.6 Z.102 changes . 6 B.7 Z.103 changes . 6 B.8 Z.104 changes . 6 B.9 Z.105 changes . 6 B.10 Z.106 changes

8、 . 6 B.11 Z.107 changes . 6 B.12 Z.109 changes . 6 B.13 Z.111 changes . 6 B.14 Z.119 changes . 6 B.15 List of Open Items 7 B.16 List of Closed items (see B.1 for meaning of a “closed” item) 7 B.16.1 allow algorithmic operators with external data 7 B.16.2 more flexible USE syntax . 7 B.16.3 operators

9、 returning sets of values (multivalued operators) 7 B.16.4 signal priority 7 B.16.5 virtual as default . 7 B.16.6 remote process creation 7 B.16.7 exit connection points for tasks 8 B.16.8 Issues that are closed because no proposals were received over several years 8 Specification and Description La

10、nguage implementers guide Version 3.0.0 1 Introduction This Guide is a compilation of reported defects and maintenance issues with their resolutions for the Specification and Description Language ITU-T Recommendations: Z.100, Z.101, Z.102, Z.103, Z.104, Z.105, Z.106, Z.107, Z.109, Z.111 and Z.119. T

11、he Recommendations ITU-T Z.111 and Z.119 are included in the above list because they are essential normative references. Agreed changes to these documents that have not yet been issued in approved Recommendations are therefore listed here. This Guide is intended to be an additional authoritative sou

12、rce of information for implementers to be read in conjunction with the Recommendations themselves. This Guide itself is not an ITU-T Recommendation. However, it records agreed corrections to reported defects. This Guide is for the SDL-2010 version of the language. The earlier Guide version 1.0.2 was

13、 for the SDL-2000 version of the language and therefore did not include Recs. ITU-T Z.101, Z.102 and Z.103, and included the previous Z.107 (withdrawn in 2008). The changes to SDL-2000 versions of the relevant superseded Recommendations can be found in Annex C of Z.Imp100 (04/15) Version 2.0.2 docum

14、ents and is not repeated in this version. 1.1 Scope of the Guide The Guide records the resolution of defects and maintenance in the following categories as described in Rec. ITU-T Z.100 Appendix II Guidelines for maintenance of the Specification and Description Language: errors open items deficienci

15、es clarifications modifications decommitted features extensions NOTE: This Guide addresses proposed changes (extensions, deletions, or modifications) to the Recommendations that are strictly related to maintenance of the Specification and Description Language as described in the Z.100 series. Propos

16、als for new features should be made in the normal way through contributions to ITU-T Study Group 17, but if agreed may result in maintenance changes (extensions, deletions, or modifications). 1.2 Approval of the Guide This Guide is approved by ITU-T Study Group 17. 1.3 Distribution of the Guide This

17、 Guide is available on-line at no charge from the ITU-T at (http:/www.itu.int/rec/T-REC-Z.Imp100/en). 1.4 Contact Any comments should be addressed to the ITU/TSB Secretariat for Study Group 17: Martin Euchner ITU/TSB Place des Nations CH-1211 Geneva 20 Switzerland Tel: +41 22 730 5866 Fax: +41 22 73

18、0 5853 E-mail: tsbsg17itu.int 2 Error reporting procedure 2.1 Submission of error reports and change requests Any implementer of the Specification and Description Language defined in the ITU-T Z.100, Z.101, Z.102, Z.103, Z.104, Z.105, Z.106, Z.107 and Z.109 Recommendations is invited to submit a rep

19、ort using the form found in Appendix II of Z.100 and copied below in Annex A. The report should be submitted to the ITU-T Study Group 17 Secretariat (see clause 1.4). Each form should cover a single error (“error correction“) or proposed change. Where the form reports an error, it is important that

20、the form is completed accurately, especially the sections that relate to the base material against which the error report is being raised. 2.2 Resolution of errors ITU-T Study Group 17 will address the submitted error. Following agreement on a resolution to the error, the proposed resolution will be

21、 approved using the appropriate procedures in ITU-T. Please note that individual responses are not given specifically to those submitting reports, and that the procedure is not intended as a consulting service. 2.3 Documenting the Resolution of Defects and maintenance changes The ITU-T Recommendatio

22、ns that have errors or agreed changes, are recorded in Annex B with defects and their resolutions including the changes, or with the reasons for maintenance and the changes. Annex A Change Request Form Change Request Form Please supply the following details. Type of change: error correction clarific

23、ation (or question) simplification extension modification decommission Short summary of change request Short justification of the change request Is this view shared in your organization? yes no Have you consulted other users? yes no How many users do you represent? 1-5 6-10 11-100 over 100 Your name

24、 and address Please attach further sheets with details if necessary. SDL (ITU-T Z.100) Rapporteur, c/o ITU-T, Place des Nations, CH-1211 Geneva 20, Switzerland. Fax: +41 22 730 5853, e-mail: SDL.rapporteuritu.int. Annex B Master List of Changes This is the master list of changes for the ITU-T Z.100

25、(SDL) series Recommendations for approved by the Working Party 5 of Study Group 17 in 2013 according the rules for maintenance in Rec. ITU-T Z.100 itself. History: The previous version of this list was published in version 2.0.2 of this document, which replaced versions 2.0.0, 1.0.2, 1.0.1 and 1.0 o

26、f this document and the earlier document COM 17-TD 3250 2001-2004 one of the documents of July 2004 WP C/17 meeting. COM 17-TD 3250 2001-2004 records the history up to that point, and there seems to be no benefit repeating that historical information in this document. In accordance with Appendix II

27、to Recommendation ITU-T Z.100, the information in this document is distributed to users by various means including sdlnewssdl-forum.org. B.1 Objectives and scope The purpose of this document is to record agreed changes to SDL Recommendations (ITU-T Z.100 to Z.109) and issues that require study and a

28、re therefore “open“, or have been studied and a decision has been made that the issue is “closed“: that is no further study should be undertaken. The agreed changes come in two categories: a) Correction of errors and clarifications (see definitions below and in Rec. ITU-T Z.100, Appendix II); b) Ext

29、ensions and modifications (see definitions below and in Rec. ITU-T Z.100, Appendix II). The rules for maintenance in an Appendix to Rec. ITU-T Z.100, state that errors and clarifications published in the Master list of changes “come into effect immediately“. Such changes should be published in a Cor

30、rigendum, Addendum or revision of the Recommendation as soon as is practical. Modification and extensions imply some change to SDL. The rule in this case is “Unless there are special circumstances requiring such changes to be implemented as soon as possible, such changes will not be recommended unti

31、l Rec. ITU-T Z.100 is revised.“ B.2 Terminology An error is an inconsistency in one or more Recommendations ITU-T Z.100 to Z.109. A textual correction is a change in the text or diagrams of Recommendations that corrects clerical or typographical errors. An open item is an issue identified but not re

32、solved. A deficiency is an issue identified where the semantics of SDL are not clearly defined in the Recommendations. A clarification is a change to the text (or diagrams) in a Recommendation that does not (intentionally) change the meaning of SDL, but is intended to make the Recommendations less a

33、mbiguous or easier to understand. A modification changes the semantics of SDL. An extension is a new feature that does not change the semantics of SDL defined in the approved Recommendations for SDL. B.3 Maintenance of Z.100 to Z.109 A Rec. ITU-T Z.100 Appendix documents the procedure to be followed

34、 for the maintenance of Recommendations ITU-T Z.100, Z.101, Z.102, Z.103, Z.104, Z.105, Z.106, Z.107 and Z.109. This procedure requires error corrections, proposed modifications and extensions to be widely publicized and a Master list of changes to be maintained. Clarifications or corrections for er

35、rors and deficiencies in the list of changes come into effect “immediately“ (that is as soon as the Working Party or Study Group approves the list). Other changes take effect only when the relevant Recommendation is updated. B.4 Z.100 changes None. B.5 Z.101 changes None. B.6 Z.102 changes None. B.7

36、 Z.103 changes None. B.8 Z.104 changes None. B.9 Z.105 changes None. B.10 Z.106 changes None. B.11 Z.107 changes None. B.12 Z.109 changes None. B.13 Z.111 changes None. B.14 Z.119 changes None. B.15 List of Open Items The following is a list of issues classified as open items according to the rules

37、for maintenance for SDL. It was agreed in September 2015 that each item on the list at that time should be progressed and removed from this list once the item has been included in the revised SDL-2010. B.16 List of Closed items (see B.1 for meaning of a “closed” item) To facilitate the tracking of i

38、tems each item uses the identifier of the form (month/year). given when the item was first put onto the open item list. For example “(04/97).3”. If the items were never on the open item list, the numbers are consecutive to the open items for the meeting at which the closed item is identified. B.16.1

39、 allow algorithmic operators with external data This was listed as an item in COM-10-1 in 1997 but the requirement is not clear. B.16.2 more flexible USE syntax Originally listed as item (04/97).25 of Q.6/10 (SDL) Meeting, 29 April 05 May 1997. The proposal was to use p1, p2, p3; instead of use p1;

40、use p2; use p3; to use packages p1, p2 and p3. A has an optional after the package name and is a comma separated list of names, so that allowing list of comma separated package names would lead to syntactic ambiguity. Therefore the proposed change has no benefit. B.16.3 operators returning sets of v

41、alues (multivalued operators) This issue was originally listed as item (10/96).13 of COM-10-1 1997. This is adequately be handled by struct. B.16.4 signal priority Originally listed as item (04/97).18 in the Q.6/10 (SDL) Meeting, 29 April 05 May 1997 report. The concept is to give signals a (possibl

42、y dynamic) priority. The selection signals for consumption is already relatively complex and a fundamental part of SDL-2010. In SDL-2010 it is possible to state the availability time for signals determined by the sending agent. Signals are not available to be consumed from the input port of the reci

43、pient until the specified time has been reached. Two or more signals that become available at the same time are ordered according to a priority specified by the senders. In SDL-2010 which available signal instance is selected for consumption depends on the current state, the priority of the input fo

44、r the signal in that state and the order of the signals in the input port. B.16.5 virtual as default Originally listed as item (04/97).31 in the Q.6/10 (SDL) Meeting, 29 April 05 May 1997 report. In SDL-2010 (and SDL-2000 and SDL-92) a type in which is omitted treated as finalized. This had been ext

45、ensively discussed (and virtual as default rejected) when SDL-92 was formulated, and has implications on the use of constraints. B.16.6 remote process creation Originally listed as item (04/97).31 in the Q.6/10 meeting 21-25 September 1998 report. The need is satisfied by remote procedure in the sta

46、te machine of an agent, and it was decided an additional construct made the language too complex. B.16.7 exit connection points for tasks Listed as an issue (06/00).1 in the Report of Q.6/10 meeting Oslo 8-9 June 2000, 6.6. The issue is whether to allow a statement in a textual algorithm in a task s

47、ymbol to transfer control to an additional exit point from the task symbol. The following diagram gives an outline example where g is an exit connection point. This issue is considered closed. There should only be one exit point from a task symbol. B.16.8 Issues that are closed because no proposals

48、were received over several years These items had been listed as additional open items in Z.Imp100 for a considerable time, but no proposals were received. It was decided in September 2015 to close these items. Data type library extensions (predefined object types, Standard Template Library analogue) Memory management issues Instance sets vs. container types and navigation into composite agents Broadcast mechanisms Interrupts _ if (b ) continue g;g