ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0005964 | Part 01: TTCN-3 Core Language | Editorial | public | 28-11-2011 10:37 | 29-11-2011 10:52

Reporter | Tomas Urban |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | text | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.3.1 (published 2011-06) |
Target Version | v4.4.1 (published 2012-04) | Fixed in Version | v4.4.1 (published 2012-04) |
Clause Reference(s) | 6.2.2
Source (company - Author) | Elvior

Summary | 0005964: Incorrect terminology in definition of the enumerated type

Description

The chapter 6.2.4 of the core language specification contains the following definition: "Enumerated types are used to model types that take only a distinct named set of values. Such distinct values are called enumerations."
In my opinion, the term "enumeration" is used incorrectly. This term is usually used for the whole set of values, not for the individual values inside the enumerated type. See e.g. wikipedia definition of enumeration (http://en.wikipedia.org/wiki/Enumeration [^]) and enumerated type (http://en.wikipedia.org/wiki/Enumerated_type [^]) or definition of C++ enum type in Microsoft online documentation (http://msdn.microsoft.com/en-us/library/2dzy4k6e%28v=VS.100%29.aspx [^])
Proposal:
The correct term for distinct named values declared in the enumerated type shall be one of the following:
- enumerator (that would be my personal pick)
- enumerated/enumeration value (it is already in use in the specification e.g. in chapter 5.2.2)
- enumerated/enumeration item
- enumerated/enumeration member
- enumerated/enumeration element

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | es_20187301v040303_Nov.zip (800,100) 29-11-2011 10:51 http://oldforge.etsi.org/mantis/file_download.php?file_id=2593&type=bug

Issue History
Date Modified | Username | Field | Change
28-11-2011 10:37 | Tomas Urban | New Issue |
28-11-2011 10:37 | Tomas Urban | Clause Reference(s) | => 6.2.2
28-11-2011 10:37 | Tomas Urban | Source (company - Author) | => Elvior
28-11-2011 11:19 | Gyorgy Rethy | Note Added: 0010338 |
28-11-2011 11:20 | Gyorgy Rethy | Target Version | => Edition 4.4.1
28-11-2011 13:42 | Jacob Wieland - Spirent | Note Added: 0010347 |
28-11-2011 14:11 | Gyorgy Rethy | Note Added: 0010352 |
28-11-2011 14:11 | Gyorgy Rethy | Assigned To | => Ina Schieferdecker
28-11-2011 14:11 | Gyorgy Rethy | Status | new => assigned
29-11-2011 10:25 | Ina Schieferdecker | Note Added: 0010377 |
29-11-2011 10:50 | Ina Schieferdecker | Note Added: 0010379 |
29-11-2011 10:51 | Ina Schieferdecker | File Added: es_20187301v040303_Nov.zip |
29-11-2011 10:51 | Ina Schieferdecker | Status | assigned => resolved
29-11-2011 10:51 | Ina Schieferdecker | Resolution | open => fixed
29-11-2011 10:51 | Ina Schieferdecker | Fixed in Version | => Edition 4.4.1
29-11-2011 10:52 | Ina Schieferdecker | Status | resolved => closed

Notes

(0010338)
Gyorgy Rethy
28-11-2011 11:19

To keep the terminology aligned with ASN.1, I propose the term "enumeration item" as this is used in X.680.

(0010347)
Jacob Wieland - Spirent
28-11-2011 13:42

I would stick with stomething that is already used. The occurrences I've found (in order or prominence) are: - enumeration value - enumerated value - enumeration name - enumeration identifier Therefore, I would think we should use enumeration value.

(0010352)
Gyorgy Rethy
28-11-2011 14:11

STF discussion 28/11: use enumerated value consistently throughout the standard.

(0010377)
Ina Schieferdecker
29-11-2011 10:25

Changed to "Enumerated types are used to model types that take only a distinct named set of values. Such distinct values are called enumerated values. Each enumerated value shall have an identifier. ... The identifiers of enumerated values shall be unique within the enumerated type (but do not have to be globally unique) and are consequently visible in the context of the given type only. The identifiers of enumerated values shall only be reused within other structured type definitions and shall not be used for identifiers of local or global visibility at the same or a lower level of the same branch of the scope hierarchy (see scope hierarchy in clause 5.2)."

(0010379)
Ina Schieferdecker
29-11-2011 10:50

Changed to "enumerated value" throughout the master document (see uploaded file, which however also contains numerous other CRs)