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

ID | Project | Category | View Status | Date Submitted | Last Update
0007179 | Part 01: TTCN-3 Core Language | Clarification | public | 17-09-2015 08:02 | 14-12-2015 13:56

Reporter | Tomas Urban |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.7.1 (published 2015-06) |
Target Version | v4.8.1 (published 2016-07) | Fixed in Version | v4.8.1 (published 2016-07) |
Clause Reference(s) | 22.2.2
Source (company - Author) | STF 487

Summary | 0007179: Minor issues with restriction on address references in receive operations

Description

The restriction 22.2.2.f states that: "AddressRef for retrieving the sending entity shall be of type address, component or of the type provided in the address declaration of the port type of the port instance referenced in the receive operation. No AddressRef shall contain the special value null at the time of the operation."
There are several problems with this restriction:
1. The term "AddressRef" used in the first sentence is only partially correct. The syntactical description uses the term "VariableRef" for sender redirect assignment and the same term shall be used in the restriction f. The sentence should start this way: "All AddressRef items in the from clause and all VariableRef items in the sender clause shall be of type..."
2. The term "type provided in the address declaration of the port type" is ambiguous. Assuming the address type of the port type PortType is declared as "address integer", the rule requires that reference shall be of an integer type and cannot be of the PortType.address type. This rule is inconsistent with the one used for the global address type (type used to create the global address type cannot be referenced in the sender and from clauses). The specification unfortunately uses both types of references in examples (see example 2 and 3 in the section 6.2.12).
Proposal: Change the term to "address type bound to the port" (see the chapter 6.2.9) and disallow usage of the base type. Update the examples in 6.2.12 accordingly.
3. The sentence "No AddressRef shall contain the special value null at the time of the operation." should contain an explicit reference to the from clause. The rule shall start this way "No AddressRef in the from clause..."

Steps To Reproduce |
Additional Information |
Tags | technically agreed
Relationships |
Attached Files | CR7179_resolution_v1.docx (95,541) 15-10-2015 10:28 http://oldforge.etsi.org/mantis/file_download.php?file_id=3310&type=bug CR7179_resolution_v2.docx (159,549) 15-10-2015 14:26 http://oldforge.etsi.org/mantis/file_download.php?file_id=3323&type=bug CR7179_resolution_v3.docx (155,627) 15-10-2015 14:39 http://oldforge.etsi.org/mantis/file_download.php?file_id=3324&type=bug

Issue History
Date Modified | Username | Field | Change
17-09-2015 08:02 | Tomas Urban | New Issue |
21-09-2015 10:24 | Gyorgy Rethy | Target Version | => v4.8.1 (published 2016-07)
22-09-2015 13:21 | Gyorgy Rethy | Tag Attached: technically agreed |
22-09-2015 13:23 | Gyorgy Rethy | Note Added: 0013240 |
13-10-2015 15:48 | Axel Rennoch | Assigned To | => Axel Rennoch
13-10-2015 15:48 | Axel Rennoch | Status | new => assigned
15-10-2015 10:28 | Axel Rennoch | File Added: CR7179_resolution_v1.docx |
15-10-2015 10:30 | Axel Rennoch | Note Added: 0013391 |
15-10-2015 10:33 | Axel Rennoch | Note Added: 0013392 |
15-10-2015 10:33 | Axel Rennoch | Assigned To | Axel Rennoch => Jacob Wieland - Spirent
15-10-2015 10:33 | Axel Rennoch | Status | assigned => acknowledged
15-10-2015 12:11 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Axel Rennoch
15-10-2015 12:11 | Jacob Wieland - Spirent | Status | acknowledged => assigned
15-10-2015 12:12 | Jacob Wieland - Spirent | Note Added: 0013397 |
15-10-2015 14:26 | Axel Rennoch | File Added: CR7179_resolution_v2.docx |
15-10-2015 14:28 | Axel Rennoch | Note Added: 0013414 |
15-10-2015 14:28 | Axel Rennoch | Assigned To | Axel Rennoch => Jacob Wieland - Spirent
15-10-2015 14:28 | Axel Rennoch | Status | assigned => acknowledged
15-10-2015 14:39 | Jacob Wieland - Spirent | File Added: CR7179_resolution_v3.docx |
15-10-2015 14:40 | Jacob Wieland - Spirent | Note Added: 0013417 |
15-10-2015 14:40 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
15-10-2015 14:40 | Jacob Wieland - Spirent | Status | acknowledged => confirmed
03-11-2015 09:09 | Gyorgy Rethy | Status | confirmed => resolved
03-11-2015 09:09 | Gyorgy Rethy | Fixed in Version | => v4.8.1 (published 2016-07)
03-11-2015 09:09 | Gyorgy Rethy | Resolution | open => fixed
14-12-2015 13:56 | Gyorgy Rethy | Note Added: 0013621 |
14-12-2015 13:56 | Gyorgy Rethy | Status | resolved => closed

Notes

(0013240)
Gyorgy Rethy
22-09-2015 13:23

STF discussion: textual description to be aligned with the syntactical structure part. Also, check the relation of global address type with the port-specific address type.

(0013391)
Axel Rennoch
15-10-2015 10:30

Proposed text and updated examples in uploaded file resolution_v1.

(0013392)
Axel Rennoch
15-10-2015 10:33

Please have a look to the proposed changes.

(0013397)
Jacob Wieland - Spirent
15-10-2015 12:12

proposed change is fine, but needs to be repeated for all communication operations (send, call, reply, raise, trigger, getcall, getreply, catch and check)

(0013414)
Axel Rennoch
15-10-2015 14:28

Resolution v2 now covers all communicatoin ops, please confirm.

(0013417)
Jacob Wieland - Spirent
15-10-2015 14:40

changed cp. to see to be consistent with the rest of the standard. otherwise ok.

(0013621)
Gyorgy Rethy
14-12-2015 13:56

Added to draft V4.7.4