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

ID | Project | Category | View Status | Date Submitted | Last Update
0000403 | Part 01: TTCN-3 Core Language | New Feature | public | 24-11-2006 13:57 | 20-04-2009 11:38

Reporter | Stephan Schulz |
Assigned To | Gyorgy Rethy |
Priority | high | Severity | feature | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v3.1.1 (published 2005-06) |
Target Version | v4.1.1 (published 2009-06) | Fixed in Version | v4.1.1 (published 2009-06) |
Clause Reference(s) | Reference to clause(s) and/or subclause(s) related to CR
Source (company - Author) | Paul Baker, motorola

Summary | 0000403: Port type parameterisation of component types
Description | We would like to extend the parameterisation of component types to allow port types. Thus allowing users to pass ports as parameters during test configuration set-up. This was allowed in TTCN-2 when a PTC was created, but is not currently allowed in TTCN-3.
Steps To Reproduce |

Additional Information

This issue seems to becoming more important (in some cases an issue) for a number of large TTCN-2 user groups that we are migrating to TTCN-3. Most of these groups use TTCN-2 for concurrency, hence, find this parameterisation useful. One case is TTCN-3 / UML 2.0 model co-simulation environments. In this use case we need to route messages from dynamically created UML components, which each have the same port, to TTCN-3 ports. The only way to achieve this currently with TRI is to use an array of ports whose index is defined when the TTCN-3 component is started. This is not very useful!

Tags | No tags attached.

Relationships

related to | 0003011 | closed | Ina Schieferdecker | Remove type parameterization from BNF
related to | 0003955 | closed | Ina Schieferdecker | Text ""TTCN-3 supports value, template, timer and port parameterizationâ€ is misleading
related to | 0004275 | closed | Ina Schieferdecker | New Concepts to be defined via Packages

Attached Files

General_Extension_status_13_08_08_type_parameterization.ppt (40,448) 14-08-2008 12:28
http://oldforge.etsi.org/mantis/file_download.php?file_id=1598&type=bug
CR_403_type_parameters_01.doc (322,560) 16-10-2008 15:20
http://oldforge.etsi.org/mantis/file_download.php?file_id=1706&type=bug
CR_403_type_parameters_02.doc (324,608) 24-11-2008 15:14
http://oldforge.etsi.org/mantis/file_download.php?file_id=1761&type=bug
CR_403_type_parameters_03.doc (312,320) 25-11-2008 07:53
http://oldforge.etsi.org/mantis/file_download.php?file_id=1762&type=bug
CR_403_type_parameters_04.doc (316,416) 27-11-2008 08:36
http://oldforge.etsi.org/mantis/file_download.php?file_id=1809&type=bug
CR_403_type_parameters_05.doc (495,616) 09-12-2008 13:19
http://oldforge.etsi.org/mantis/file_download.php?file_id=1870&type=bug
CR_403_type_parameters_06.doc (496,128) 09-12-2008 15:06
http://oldforge.etsi.org/mantis/file_download.php?file_id=1875&type=bug
CR_403_type_parameters_061.doc (496,640) 15-01-2009 07:07
http://oldforge.etsi.org/mantis/file_download.php?file_id=1954&type=bug
CR_403_type_parameters_062.doc (497,664) 15-01-2009 08:01
http://oldforge.etsi.org/mantis/file_download.php?file_id=1956&type=bug
CR_403_type_parameters_07.doc (325,632) 20-01-2009 07:18
http://oldforge.etsi.org/mantis/file_download.php?file_id=1966&type=bug
CR_403_type_parameters_07_ASN1.doc (99,840) 23-01-2009 14:12
http://oldforge.etsi.org/mantis/file_download.php?file_id=1970&type=bug
CR_403_type_parameters_071.doc (344,064) 23-01-2009 15:22
http://oldforge.etsi.org/mantis/file_download.php?file_id=1973&type=bug
CR_403_type_parameters_08_ASN1.doc (117,760) 23-01-2009 15:33
http://oldforge.etsi.org/mantis/file_download.php?file_id=1975&type=bug
CR_403_type_parameters_081.doc (361,472) 27-01-2009 09:28
http://oldforge.etsi.org/mantis/file_download.php?file_id=1978&type=bug

Issue History
Date Modified | Username | Field | Change
24-11-2006 13:57 | Stephan Schulz | New Issue |
24-11-2006 13:57 | Stephan Schulz | Clause Reference(s) | => Reference to clause(s) and/or subclause(s) related to CR
24-11-2006 13:57 | Stephan Schulz | Source (company - Author) | => Paul Baker, motorola
24-11-2006 15:04 | Stephan Schulz | Note Added: 0000332 |
15-06-2007 19:13 | Stephan Schulz | Status | new => assigned
15-06-2007 19:13 | Stephan Schulz | Assigned To | => Ina Schieferdecker
13-10-2007 19:29 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Jens Grabowski
15-10-2007 12:19 | Ina Schieferdecker | Note Added: 0003605 |
18-10-2007 14:29 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
18-07-2008 08:56 | Jens Grabowski | Assigned To | Jens Grabowski => Thomas DeiÃŸ
14-08-2008 12:28 | Thomas DeiÃŸ | File Added: General_Extension_status_13_08_08_type_parameterization.ppt |
16-10-2008 15:20 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_01.doc |
24-11-2008 10:54 | Ina Schieferdecker | Relationship added | related to 0003011
24-11-2008 15:14 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_02.doc |
24-11-2008 15:15 | Thomas DeiÃŸ | Note Added: 0007389 |
25-11-2008 07:53 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_03.doc |
25-11-2008 07:54 | Thomas DeiÃŸ | Note Added: 0007393 |
27-11-2008 08:36 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_04.doc |
27-11-2008 08:37 | Thomas DeiÃŸ | Note Added: 0007465 |
28-11-2008 13:47 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Ina Schieferdecker
09-12-2008 10:24 | Ina Schieferdecker | Relationship added | related to 0003955
09-12-2008 13:19 | Ina Schieferdecker | File Added: CR_403_type_parameters_05.doc |
09-12-2008 13:22 | Ina Schieferdecker | Note Added: 0007595 |
09-12-2008 13:22 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Thomas DeiÃŸ
09-12-2008 13:22 | Ina Schieferdecker | Resolution | open => fixed
09-12-2008 14:54 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_06.doc |
09-12-2008 15:05 | Thomas DeiÃŸ | Note Added: 0007601 |
09-12-2008 15:05 | Thomas DeiÃŸ | Assigned To | Thomas DeiÃŸ => Ina Schieferdecker
09-12-2008 15:05 | Thomas DeiÃŸ | File Deleted: CR_403_type_parameters_06.doc |
09-12-2008 15:06 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_06.doc |
09-12-2008 15:49 | Ina Schieferdecker | Note Added: 0007607 |
12-12-2008 09:04 | Ina Schieferdecker | Relationship added | related to 0004275
12-12-2008 09:20 | Ina Schieferdecker | Note Added: 0007668 |
12-12-2008 09:20 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Gyorgy Rethy
15-01-2009 07:07 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_061.doc |
15-01-2009 07:08 | Thomas DeiÃŸ | Note Added: 0007862 |
15-01-2009 08:01 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_062.doc |
15-01-2009 08:02 | Thomas DeiÃŸ | Note Added: 0007864 |
20-01-2009 07:18 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_07.doc |
23-01-2009 13:39 | Gyorgy Rethy | Note Added: 0007921 |
23-01-2009 14:11 | Gyorgy Rethy | Note Edited: 0007921 |
23-01-2009 14:12 | Gyorgy Rethy | File Added: CR_403_type_parameters_07_ASN1.doc |
23-01-2009 14:45 | Gyorgy Rethy | File Added: CR_403_type_parameters_08_ASN1.doc |
23-01-2009 14:46 | Gyorgy Rethy | File Deleted: CR_403_type_parameters_08_ASN1.doc |
23-01-2009 15:22 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_071.doc |
23-01-2009 15:23 | Thomas DeiÃŸ | Note Added: 0007924 |
23-01-2009 15:25 | Gyorgy Rethy | File Added: CR_403_type_parameters_08_ASN1.doc |
23-01-2009 15:29 | Gyorgy Rethy | File Deleted: CR_403_type_parameters_08_ASN1.doc |
23-01-2009 15:33 | Gyorgy Rethy | File Added: CR_403_type_parameters_08_ASN1.doc |
23-01-2009 15:37 | Gyorgy Rethy | Note Added: 0007925 |
27-01-2009 09:28 | Thomas DeiÃŸ | File Added: CR_403_type_parameters_081.doc |
27-01-2009 09:30 | Thomas DeiÃŸ | Note Added: 0007940 |
10-03-2009 10:47 | Ina Schieferdecker | Status | assigned => resolved
10-03-2009 10:47 | Ina Schieferdecker | Fixed in Version | => Edition 4.1.1 (not yet published)
20-04-2009 11:38 | Ina Schieferdecker | Status | resolved => closed

Notes

(0000332)
Stephan Schulz
24-11-2006 15:04

Type parameterization in general shall be discussed; This CR depends on the type parameterization discussion

(0003605)
Ina Schieferdecker
15-10-2007 12:19

This should be considered in the larger context of type parameterization for TTCN-3 and is therefore deferred to the STF in 2008

(0007389)
Thomas DeiÃŸ
24-11-2008 15:15

typo corrected. small extension on semantics. version 02 uploaded.

(0007393)
Thomas DeiÃŸ
25-11-2008 07:54

editorial corrections. Formal type parameters of nested type definitions removed for the sake of simplicity.

(0007465)
Thomas DeiÃŸ
27-11-2008 08:37

restriction for default values of parameters added. In this case the type must not be a type parameter. v04 uploaded

(0007595)
Ina Schieferdecker
09-12-2008 13:22

Added the C++ mapping part. Moved the annexes to the respective parts of TTCN-3. Did some rewording and reformatting. Please check.

(0007601)
Thomas DeiÃŸ
09-12-2008 15:05

C++ mapping not checked.
Issue whether all or known types can be used as actual parameters.
Actually this is not quite clear to me: "Any compatible type known in a module can be passed as actual parameter, i.e. actual type parameters are not limited to those types only known in the module containing the type parameterized definition itself"
Which module is considered here: Is it the module where the actual parameters are provided, or is it the module containing the type parameterized definition? On first reading I thought it is the second one, which would lead to similar restrictions as in the use of the anytype. But on second reading, the actual intention might be that the really the known types of the module where the actual parameters are provided can be used. Maybe I had problems with this because this is somehow obvious: only what is known in a module can be provided as actual parameter. The usage of 'compatible' type is blurring the difference further.
May I suggest to remove the 'known in a module' from the beginning of the first sentence: "Any compatible type can be passed as actual parameter, i.e. actual type parameters are not limited to those types only known in the module containing the type parameterized definition itself"

(0007607)
Ina Schieferdecker
09-12-2008 15:49

fine with me.

(0007668)
Ina Schieferdecker
12-12-2008 09:20

Please check.

(0007862)
Thomas DeiÃŸ
15-01-2009 07:08

language tag added, document numbers added.

(0007864)
Thomas DeiÃŸ
15-01-2009 08:02

tag corrected

(0007921)
Gyorgy Rethy
23-01-2009 13:39 (edited on: 23-01-2009 14:11)

I have the following comments:
1) type compatibility
Real type compatibility is defined for component types only (and there are two rules for component types), therefore to say in general, that the actual type shall be compatible with the formal type parameter is ambiguous. possible solutions:
- allow type compatibility for component types only, runson compatibility rule only (Part-1 $6.3.3 item 2). This is mentioned, without the precise reference, in clause 5.4.1.5 restriction c), but not consistently required through the whole text. This would mean, that the formal type parameter name shall always be a component type.
- In addition to component type names allow as formal type parameters built-in simple types In this case the actual type parameter simply has to be the same root type as the formal parameter. In case of structured types all fields of the formal type parameter shall resolve to built-in types (i.e. not constrained) and the actual type shall be type compatible acc. to part-1 6.3.2.2 and all fields shall resolve to the same root type as the correcponding field of the formal type parameter.
I would go for the simpler solution at this stage, i.e. formal type parameter shall be either "type" or a component type name, and rather come back to the data type compatibility later, if a CR requires it.
2) editorial
$6.4 end of 2nd paragraph: *Part-1* clause 10.
3)
The package has also effect on ASN.1 to TTCN-3 mapping as allows importing ASN.1 definitions with value formal parameters. I uploaded a proposed text in CR_403_type_parameters_07_ASN1.doc
4) In the header of table A.1 in clause 9.2 (new clause no 10.2 in the uploaded file) "Constants (TTCN 3 and external)" shall be "Constants" as external constants are deleted in Part-1.

(0007924)
Thomas DeiÃŸ
23-01-2009 15:23

Comments by Gyorgy and Jacob Wieland included. (Jacob commented on a few inconsistencies in the BNF)

(0007925)
Gyorgy Rethy
23-01-2009 15:37

New updated additions on importing ASN.1 parameterization is uploaded in CR_403_type_parameters_08_ASN1.doc. This new version aligns the structure between the 201 873 parts and the pparameterization package, namely importing ASN.1 parameterized definitions is moved to the package from Part-7.

(0007940)
Thomas DeiÃŸ
27-01-2009 09:30

Updated ASN clause from Gyorgy added. Comment by Jacob Wieland on usage of actual parameters in extended field reference. These make sense only when refering alternatives in a union (anytype). The BNF rule ExtendedFieldReference was changes accordingly. version 081 uploaded.