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

ID | Project | Category | View Status | Date Submitted | Last Update
0007503 | Part 01: TTCN-3 Core Language | Clarification | public | 29-09-2016 13:32 | 12-12-2016 10:02

Reporter | Martin Hauch |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.8.1 (published 2016-07) |
Target Version | v4.9.1 (published 2017-05) | Fixed in Version | v4.9.1 (published 2017-05) |
Clause Reference(s) | B.1.3.3
Source (company - Author) | Devoteam - Martin Hauch

Summary | 0007503: allowed elements in a permutation matching-mechanism

Description

Chapter: B.1.3.3 Permutation
As I understand restriction c) and d) in this chapter, elements of a permutation should only be SpecificValue, AnyElement and AnyElementsOrNone.
But in the following examples (from EXAMPLE1:) ValueList is also used as permutation-element.
template integer mw_myInt1 := (1,2,3);
template integer mw_myInt2 := (1,2,?);
template MySequenceOfType mw_myTemplate10 := { permutation (mw_myInt1, 2, 3 ), 5 };
// matches any of the sequences of 4 integers:
// 1,3,2,5; 2,1,3,5; 2,3,1,5; 3,1,2,5; or 3,2,1,5;
// 2,3,2,5; 2,2,3,5; 2,3,2,5; 3,2,2,5; or 3,2,2,5;
// 3,3,2,5; 2,3,3,5; 2,3,3,5; 3,3,2,5; or 3,2,3,5;
template MySequenceOfType mw_myTemplate11 := { permutation (mw_myInt2, 2, 3 ), 5 };
// matches any sequence of 4 integers that ends with 5 and contains 2 and 3 at least once in
// other positions
Please check the restrictions for permutations and the examples above.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |

Attached Files

CR7503_proposal.docx (155,022) 16-11-2016 09:28
http://oldforge.etsi.org/mantis/file_download.php?file_id=3528&type=bug
CR7503_proposal_v2.docx (155,096) 16-11-2016 15:09
http://oldforge.etsi.org/mantis/file_download.php?file_id=3542&type=bug
CR7503_proposal_v3.docx (175,094) 17-11-2016 11:25
http://oldforge.etsi.org/mantis/file_download.php?file_id=3551&type=bug
CR7503_proposal_v4.docx (155,247) 17-11-2016 11:34
http://oldforge.etsi.org/mantis/file_download.php?file_id=3552&type=bug

Issue History
Date Modified | Username | Field | Change
29-09-2016 13:32 | Martin Hauch | New Issue |
14-11-2016 13:31 | Jens Grabowski | Assigned To | => KristÃ³f Szabados
14-11-2016 13:31 | Jens Grabowski | Status | new => assigned
15-11-2016 13:35 | KristÃ³f Szabados | Note Added: 0014250 |
16-11-2016 09:28 | KristÃ³f Szabados | Status | assigned => confirmed
16-11-2016 09:28 | KristÃ³f Szabados | File Added: CR7503_proposal.docx |
16-11-2016 15:09 | KristÃ³f Szabados | File Added: CR7503_proposal_v2.docx |
16-11-2016 15:09 | KristÃ³f Szabados | Note Added: 0014273 |
16-11-2016 16:59 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Tomas Urban
16-11-2016 16:59 | KristÃ³f Szabados | Status | confirmed => assigned
16-11-2016 16:59 | KristÃ³f Szabados | Note Added: 0014284 |
17-11-2016 11:25 | Tomas Urban | File Added: CR7503_proposal_v3.docx |
17-11-2016 11:28 | Tomas Urban | Note Added: 0014296 |
17-11-2016 11:28 | Tomas Urban | Assigned To | Tomas Urban => KristÃ³f Szabados
17-11-2016 11:28 | Tomas Urban | Status | assigned => confirmed
17-11-2016 11:34 | KristÃ³f Szabados | File Added: CR7503_proposal_v4.docx |
17-11-2016 11:35 | KristÃ³f Szabados | Note Added: 0014297 |
17-11-2016 11:38 | KristÃ³f Szabados | Status | confirmed => resolved
17-11-2016 11:38 | KristÃ³f Szabados | Fixed in Version | => v4.10.1 (published 2018-05)
17-11-2016 11:38 | KristÃ³f Szabados | Resolution | open => fixed
17-11-2016 11:38 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Gyorgy Rethy
17-11-2016 14:42 | KristÃ³f Szabados | Note Added: 0014313 |
17-11-2016 14:42 | KristÃ³f Szabados | Status | resolved => feedback
17-11-2016 14:42 | KristÃ³f Szabados | Resolution | fixed => reopened
17-11-2016 14:42 | KristÃ³f Szabados | Status | feedback => resolved
17-11-2016 14:42 | KristÃ³f Szabados | Fixed in Version | v4.10.1 (published 2018-05) => v4.9.1 (published 2017-05)
17-11-2016 14:42 | KristÃ³f Szabados | Resolution | reopened => fixed
12-12-2016 10:02 | Gyorgy Rethy | Status | resolved => closed
12-12-2016 10:02 | Gyorgy Rethy | Target Version | => v4.9.1 (published 2017-05)
12-12-2016 10:02 | Gyorgy Rethy | Note Added: 0014371 |

Notes

(0014250)
KristÃ³f Szabados
15-11-2016 13:35

restriction "d" sounds strange:
- restriction "c" already limits the template referred to in the all from clause and it's elements.
- Expressions, templates and AnyElement and AnyElementsOrNone are allowed as permutation elements.
I believe restriction "d" tried to make sure that the same all from related restrictions are present when the all from is written out directly inside the
permutation and when it would be present in a template that is used in the permutation (so that restriction "c" can not be circumvented by extracting an incorrect all from into template and reference it).
So I propose to change restriction "d" to:
"
For template used as individual members of a permutation and defined using all from, the template in their all from clause shall obey to restriction c) above.
"

(0014273)
KristÃ³f Szabados
16-11-2016 15:09

hopefully simplified wording

(0014284)
KristÃ³f Szabados
16-11-2016 16:59

please check if this restriction wording is good

(0014296)
Tomas Urban
17-11-2016 11:28

According to STF discussion, I removed the restriction on content (all matching mechanisms/templates allowed) and the restriction d). The only restriction that remained is that permutation cannot be present in the template referenced in the all from clause. It is for consistency with all other rules using the all from clause. Please review.

(0014297)
KristÃ³f Szabados
17-11-2016 11:35

removed the void restriction

(0014313)
KristÃ³f Szabados
17-11-2016 14:42

incorrect assignment at resolution

(0014371)
Gyorgy Rethy
12-12-2016 10:02

Added to draft V4.8.2