TOPIC:

Dear all,


the upcoming version for TTCN-3 will be v3.4.1, for which the approval
phase is targetted for June.


The draft versions for part 1, part 4, part 6 and part 10 have been made
available on the ETSI portal server:

TTCN-3 Edition 3.4.1 Core Language
docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3...ts/edition341_prepar
ation/00108-1__TTCN3_ed341__core/00108-1_T3_ed341_corev334__FurtherCRs.z
ip

TTCN-3 Edition 3.4.1 documentation tags
docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3...ts/edition341_prepar
ation/00108-10_TTCN3_ed341__DOC/00108-10_T3_ed341_DOCv330.zip

TTCN-3 Edition 3.4.1 OS
docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3...ts/edition341_prepar
ation/00108-4__TTCN3_ed341__OS/00108-4_T3_ed341_OSv334.zip

TTCN-3 Edition 3.4.1: TCI
docbox.etsi.org/MTS/MTS/07-Drafts/TTCN3_...s/edition341_prepara
tion/00108-6__TTCN3_ed341__TCI/00108-6_T3_ed341_TCIv333__STF349AprilSess
ion.zip


These draft versions implement the CRs as noted at
t-ort.etsi.org/roadmap_page.php

Please consider v3.4.1 for each part in the roadmap.



!!! May we ask you to review those draft versions and let us know your
comments/proposals asap !!!


We plan to have a smooth approval phase and a fast publication, so that
we would like to collect your feedback beforehand.


Thank you in advance and best regards,

Gyorgy, Jens, Thomas and Ina
The TTCN-3 Maintenance Team

Hello all,

Several comments on core language draft:

The description of template(present) (on page 110) should be amended to
the following:
"the template as a whole shall not resolve to the matching mechanisms
*which match* omit"
At the moment, the given definition does not describe the intended meaning.

In the table of template actual parameter/assignment usage (Table 11, on
page 111), it is forbidden to use template(value) actual parameter for a
template(omit) formal parameter. This is an error, I think, as
template(value) is a subset of template(omit).

In the description of the syntactical structure of predefined functions
(16.1.2 on page 116), encode/decode are mentioned, which are otherwise
called encvalue/decvalue.

Also, I found that the standard still mentiones value parameterization
of modules in the chapter about parameterization, but neither
the BNF allows this nor is it mentioned again in the chapter about
module definitions. I think it is a very old remnant and should be removed.

Best regards,

Jacob Wieland

Schieferdecker, Ina wrote:
> Dear all,
>
>
> the upcoming version for TTCN-3 will be v3.4.1, for which the approval
> phase is targetted for June.
>
>
> The draft versions for part 1, part 4, part 6 and part 10 have been made
> available on the ETSI portal server:
>
> TTCN-3 Edition 3.4.1 Core Language
> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3...ts/edition341_prepar
> ation/00108-1__TTCN3_ed341__core/00108-1_T3_ed341_corev334__FurtherCRs.z
> ip
>
> TTCN-3 Edition 3.4.1 documentation tags
> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3...ts/edition341_prepar
> ation/00108-10_TTCN3_ed341__DOC/00108-10_T3_ed341_DOCv330.zip
>
> TTCN-3 Edition 3.4.1 OS
> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3...ts/edition341_prepar
> ation/00108-4__TTCN3_ed341__OS/00108-4_T3_ed341_OSv334.zip
>
> TTCN-3 Edition 3.4.1: TCI
> docbox.etsi.org/MTS/MTS/07-Drafts/TTCN3_...s/edition341_prepara
> tion/00108-6__TTCN3_ed341__TCI/00108-6_T3_ed341_TCIv333__STF349AprilSess
> ion.zip
>
>
> These draft versions implement the CRs as noted at
> t-ort.etsi.org/roadmap_page.php
>
> Please consider v3.4.1 for each part in the roadmap.
>
>
>
> !!! May we ask you to review those draft versions and let us know your
> comments/proposals asap !!!
>
>
> We plan to have a smooth approval phase and a fast publication, so that
> we would like to collect your feedback beforehand.
>
>
> Thank you in advance and best regards,
>
> Gyorgy, Jens, Thomas and Ina
> The TTCN-3 Maintenance Team
>
>


--

---

Jacob Wieland
Software Engineer

Testing Technologies IST GmbH
Michaelkirchstraße 17/18
10179 Berlin, Germany

Phone +49 30 726 19 19 34 Email This email address is being protected from spambots. You need JavaScript enabled to view it.
Fax +49 30 726 19 19 20 Internet www.testingtech.com

---

UPCOMING EVENTS!

May 14-15, IMS Asia, Singapore
www.informatm.com/newt/l/imsvision/asia

May 26-28, Tutorial "Theory & Practice of TTCN-3", Berlin (Germany)
www.testingtech.com/services/ttcn3_tutorial.php

---

Geschäftsführung: Theofanis Vassiliou-Gioles, Stephan Pietsch
Handelsregister HRB 77805, Amtsgericht Charlottenburg
Ust ID Nr.: DE 813 143 070

This e-mail may contain confidential and privileged material for the
sole use of the intended recipient. Any review, use, distribution or
disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), please contact
the sender by reply e-mail and delete all copies of this message.


--

---

Jacob Wieland
Software Engineer

Testing Technologies IST GmbH
Michaelkirchstraße 17/18
10179 Berlin, Germany

Phone +49 30 726 19 19 34 Email This email address is being protected from spambots. You need JavaScript enabled to view it.
Fax +49 30 726 19 19 20 Internet www.testingtech.com

---

UPCOMING EVENTS!

May 14-15, IMS Asia, Singapore
www.informatm.com/newt/l/imsvision/asia

May 26-28, Tutorial "Theory & Practice of TTCN-3", Berlin (Germany)
www.testingtech.com/services/ttcn3_tutorial.php

---

Geschäftsführung: Theofanis Vassiliou-Gioles, Stephan Pietsch
Handelsregister HRB 77805, Amtsgericht Charlottenburg
Ust ID Nr.: DE 813 143 070

This e-mail may contain confidential and privileged material for the
sole use of the intended recipient. Any review, use, distribution or
disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), please contact
the sender by reply e-mail and delete all copies of this message.

Dear Jacob,

Thanks for your comments. Unfortunately, from your mail it was not clear which version you are looking at. E.g. in the latest version(3.3.4, available on the ETSI server at the directory /MTS/MTS/07-Drafts/TTCN3_drafts/edition341_preparation/00108-1__TTCN3_ed341__core/), on page 110 I have the clause 16.1.1 Invoking functions. I think that your first comment is related to clause 15.8 Template restrictions on page 105 instead. To avoid unclarity in the future, I propose to use clause no./paragraph no.(rule no. for the BNF) to identify the locations of the comments.

1) Regarding your first comment: "omit" is a matching mechanism itself. Thus, I rather propose a direct list of forbidden things to avoid further (future) misinterpretations "the template as a whole shall not resolve to the matching mechanisms omit and AnyValueOrNone or the matching attribute ifpresent" (omit cannot match the matching mechanism omit as "omit" itself is a matching mechanism).

2) In the table of template actual parameter/assignment usage (Table 11, on page 111), it is forbidden to use template(value) actual parameter for a template(omit) formal parameter. => I think your comment is correct.

3) (16.1.2 on page 116), encode/decode => your comment is correct.

4) With module parameterization modulepar-s are meant. True, it not like the parameterization of templates, testcases, functions etc., (and in fact are not parameters of the module but of the whole test suite). If you find the current text unclear in this respect, pls. provide a CR.

BR, Gyorgy

>

---

Original Message

---

> From: active_ttcn3 : mts stf133 ttcn version 3 - active
> members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Jacob Wieland
> Sent: Tuesday, 13 May, 2008 9:58 AM
> To: This email address is being protected from spambots. You need JavaScript enabled to view it.
> Subject: Re: FYI: TTCN-3 Draft Versions for v3.4.1
>
> Hello all,
>
> Several comments on core language draft:
>
> The description of template(present) (on page 110) should be
> amended to the following:
> "the template as a whole shall not resolve to the matching
> mechanisms *which match* omit"
> At the moment, the given definition does not describe the
> intended meaning.
>
> In the table of template actual parameter/assignment usage
> (Table 11, on page 111), it is forbidden to use
> template(value) actual parameter for a
> template(omit) formal parameter. This is an error, I think, as
> template(value) is a subset of template(omit).
>
> In the description of the syntactical structure of predefined
> functions
> (16.1.2 on page 116), encode/decode are mentioned, which are
> otherwise called encvalue/decvalue.
>
> Also, I found that the standard still mentiones value
> parameterization of modules in the chapter about
> parameterization, but neither the BNF allows this nor is it
> mentioned again in the chapter about module definitions. I
> think it is a very old remnant and should be removed.
>
> Best regards,
>
> Jacob Wieland
>
> Schieferdecker, Ina wrote:
> > Dear all,
> >
> >
> > the upcoming version for TTCN-3 will be v3.4.1, for which
> the approval
> > phase is targetted for June.
> >
> >
> > The draft versions for part 1, part 4, part 6 and part 10 have been
> > made available on the ETSI portal server:
> >
> > TTCN-3 Edition 3.4.1 Core Language
> >
> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition341_prep
> > ar
> >
> ation/00108-1__TTCN3_ed341__core/00108-1_T3_ed341_corev334__FurtherCRs
> > .z
> > ip
> >
> > TTCN-3 Edition 3.4.1 documentation tags
> >
> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition341_prep
> > ar ation/00108-10_TTCN3_ed341__DOC/00108-10_T3_ed341_DOCv330.zip
> >
> > TTCN-3 Edition 3.4.1 OS
> >
> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition341_prep
> > ar ation/00108-4__TTCN3_ed341__OS/00108-4_T3_ed341_OSv334.zip
> >
> > TTCN-3 Edition 3.4.1: TCI
> >
> docbox.etsi.org/MTS/MTS/07-Drafts/TTCN3_drafts/edition341_prepa
> > ra
> >
> tion/00108-6__TTCN3_ed341__TCI/00108-6_T3_ed341_TCIv333__STF349AprilSe
> > ss
> > ion.zip
> >
> >
> > These draft versions implement the CRs as noted at
> > t-ort.etsi.org/roadmap_page.php
> >
> > Please consider v3.4.1 for each part in the roadmap.
> >
> >
> >
> > !!! May we ask you to review those draft versions and let
> us know your
> > comments/proposals asap !!!
> >
> >
> > We plan to have a smooth approval phase and a fast publication, so
> > that we would like to collect your feedback beforehand.
> >
> >
> > Thank you in advance and best regards,
> >
> > Gyorgy, Jens, Thomas and Ina
> > The TTCN-3 Maintenance Team
> >
> >
>
>
> --
>

---

>

---

> Jacob Wieland
> Software Engineer
>
> Testing Technologies IST GmbH
> Michaelkirchstraße 17/18
> 10179 Berlin, Germany
>
> Phone +49 30 726 19 19 34 Email This email address is being protected from spambots. You need JavaScript enabled to view it.
> Fax +49 30 726 19 19 20 Internet www.testingtech.com
>

---

>

---

>
> UPCOMING EVENTS!
>
> May 14-15, IMS Asia, Singapore
> www.informatm.com/newt/l/imsvision/asia
>
> May 26-28, Tutorial "Theory & Practice of TTCN-3", Berlin
> (Germany) www.testingtech.com/services/ttcn3_tutorial.php
>
>

---

>

---

> Geschäftsführung: Theofanis Vassiliou-Gioles, Stephan Pietsch
> Handelsregister HRB 77805, Amtsgericht Charlottenburg Ust ID
> Nr.: DE 813 143 070
>
> This e-mail may contain confidential and privileged material
> for the sole use of the intended recipient. Any review, use,
> distribution or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to
> receive for the recipient), please contact the sender by
> reply e-mail and delete all copies of this message.
>
>
> --
>

---

>

---

> Jacob Wieland
> Software Engineer
>
> Testing Technologies IST GmbH
> Michaelkirchstraße 17/18
> 10179 Berlin, Germany
>
> Phone +49 30 726 19 19 34 Email This email address is being protected from spambots. You need JavaScript enabled to view it.
> Fax +49 30 726 19 19 20 Internet www.testingtech.com
>

---

>

---

>
> UPCOMING EVENTS!
>
> May 14-15, IMS Asia, Singapore
> www.informatm.com/newt/l/imsvision/asia
>
> May 26-28, Tutorial "Theory & Practice of TTCN-3", Berlin
> (Germany) www.testingtech.com/services/ttcn3_tutorial.php
>
>

---

>

---

> Geschäftsführung: Theofanis Vassiliou-Gioles, Stephan Pietsch
> Handelsregister HRB 77805, Amtsgericht Charlottenburg Ust ID
> Nr.: DE 813 143 070
>
> This e-mail may contain confidential and privileged material
> for the sole use of the intended recipient. Any review, use,
> distribution or disclosure by others is strictly prohibited.
> If you are not the intended recipient (or authorized to
> receive for the recipient), please contact the sender by
> reply e-mail and delete all copies of this message.
>

Hello Gyorgy,

György Réthy wrote:
> Dear Jacob,
>
> Thanks for your comments. Unfortunately, from your mail it was not clear which version you are looking at. E.g. in the latest version(3.3.4, available on the ETSI server at the directory /MTS/MTS/07-Drafts/TTCN3_drafts/edition341_preparation/00108-1__TTCN3_ed341__core/), on page 110 I have the clause 16.1.1 Invoking functions. I think that your first comment is related to clause 15.8 Template restrictions on page 105 instead. To avoid unclarity in the future, I propose to use clause no./paragraph no.(rule no. for the BNF) to identify the locations of the comments.
>
Sorry, I was referencing the draft in the link that Ina sent in the mail
that I answered to. I thought that was clear ;-)
> 1) Regarding your first comment: "omit" is a matching mechanism itself. Thus, I rather propose a direct list of forbidden things to avoid further (future) misinterpretations "the template as a whole shall not resolve to the matching mechanisms omit and AnyValueOrNone or the matching attribute ifpresent" (omit cannot match the matching mechanism omit as "omit" itself is a matching mechanism).
>
I think this is not enough, what about matching mechanisms like "(a, b,
omit)" (i.e. the same as "(a, b) ifpresent"). What about complement()
for optional fields? I think all matching mechanisms which do not match
'omit' is the most concise description. Yes, 'omit' is in itself a kind
of matching mechanism, but so is every value and nobody would have a
qualm with the description of 'no matching mechanism matching value v'.
In my understanding, 'omit' is also both a matching mechanism (which
matches only itself) and a (part of a) value which can only appear in
place of an optional field.

Anyway, as long as it is clear that we mean the same, I'm happy ;-)
> 2) In the table of template actual parameter/assignment usage (Table 11, on page 111), it is forbidden to use template(value) actual parameter for a template(omit) formal parameter. => I think your comment is correct.
>
> 3) (16.1.2 on page 116), encode/decode => your comment is correct.
>
> 4) With module parameterization modulepar-s are meant. True, it not like the parameterization of templates, testcases, functions etc., (and in fact are not parameters of the module but of the whole test suite). If you find the current text unclear in this respect, pls. provide a CR.
>
I'll think about it.

Best regards, Jacob
> BR, Gyorgy
>
>
>>

---

Original Message

---

>> From: active_ttcn3 : mts stf133 ttcn version 3 - active
>> members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Jacob Wieland
>> Sent: Tuesday, 13 May, 2008 9:58 AM
>> To: This email address is being protected from spambots. You need JavaScript enabled to view it.
>> Subject: Re: FYI: TTCN-3 Draft Versions for v3.4.1
>>
>> Hello all,
>>
>> Several comments on core language draft:
>>
>> The description of template(present) (on page 110) should be
>> amended to the following:
>> "the template as a whole shall not resolve to the matching
>> mechanisms *which match* omit"
>> At the moment, the given definition does not describe the
>> intended meaning.
>>
>> In the table of template actual parameter/assignment usage
>> (Table 11, on page 111), it is forbidden to use
>> template(value) actual parameter for a
>> template(omit) formal parameter. This is an error, I think, as
>> template(value) is a subset of template(omit).
>>
>> In the description of the syntactical structure of predefined
>> functions
>> (16.1.2 on page 116), encode/decode are mentioned, which are
>> otherwise called encvalue/decvalue.
>>
>> Also, I found that the standard still mentiones value
>> parameterization of modules in the chapter about
>> parameterization, but neither the BNF allows this nor is it
>> mentioned again in the chapter about module definitions. I
>> think it is a very old remnant and should be removed.
>>
>> Best regards,
>>
>> Jacob Wieland
>>
>> Schieferdecker, Ina wrote:
>>
>>> Dear all,
>>>
>>>
>>> the upcoming version for TTCN-3 will be v3.4.1, for which
>>>
>> the approval
>>
>>> phase is targetted for June.
>>>
>>>
>>> The draft versions for part 1, part 4, part 6 and part 10 have been
>>> made available on the ETSI portal server:
>>>
>>> TTCN-3 Edition 3.4.1 Core Language
>>>
>>>
>> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition341_prep
>>
>>> ar
>>>
>>>
>> ation/00108-1__TTCN3_ed341__core/00108-1_T3_ed341_corev334__FurtherCRs
>>
>>> .z
>>> ip
>>>
>>> TTCN-3 Edition 3.4.1 documentation tags
>>>
>>>
>> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition341_prep
>>
>>> ar ation/00108-10_TTCN3_ed341__DOC/00108-10_T3_ed341_DOCv330.zip
>>>
>>> TTCN-3 Edition 3.4.1 OS
>>>
>>>
>> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition341_prep
>>
>>> ar ation/00108-4__TTCN3_ed341__OS/00108-4_T3_ed341_OSv334.zip
>>>
>>> TTCN-3 Edition 3.4.1: TCI
>>>
>>>
>> docbox.etsi.org/MTS/MTS/07-Drafts/TTCN3_drafts/edition341_prepa
>>
>>> ra
>>>
>>>
>> tion/00108-6__TTCN3_ed341__TCI/00108-6_T3_ed341_TCIv333__STF349AprilSe
>>
>>> ss
>>> ion.zip
>>>
>>>
>>> These draft versions implement the CRs as noted at
>>> t-ort.etsi.org/roadmap_page.php
>>>
>>> Please consider v3.4.1 for each part in the roadmap.
>>>
>>>
>>>
>>> !!! May we ask you to review those draft versions and let
>>>
>> us know your
>>
>>> comments/proposals asap !!!
>>>
>>>
>>> We plan to have a smooth approval phase and a fast publication, so
>>> that we would like to collect your feedback beforehand.
>>>
>>>
>>> Thank you in advance and best regards,
>>>
>>> Gyorgy, Jens, Thomas and Ina
>>> The TTCN-3 Maintenance Team
>>>
>>>
>>>
>> --
>>

---

>>

---

>> Jacob Wieland
>> Software Engineer
>>
>> Testing Technologies IST GmbH
>> Michaelkirchstraße 17/18
>> 10179 Berlin, Germany
>>
>> Phone +49 30 726 19 19 34 Email This email address is being protected from spambots. You need JavaScript enabled to view it.
>> Fax +49 30 726 19 19 20 Internet www.testingtech.com
>>

---

>>

---

>>
>> UPCOMING EVENTS!
>>
>> May 14-15, IMS Asia, Singapore
>> www.informatm.com/newt/l/imsvision/asia
>>
>> May 26-28, Tutorial "Theory & Practice of TTCN-3", Berlin
>> (Germany) www.testingtech.com/services/ttcn3_tutorial.php
>>
>>

---

>>

---

>> Geschäftsführung: Theofanis Vassiliou-Gioles, Stephan Pietsch
>> Handelsregister HRB 77805, Amtsgericht Charlottenburg Ust ID
>> Nr.: DE 813 143 070
>>
>> This e-mail may contain confidential and privileged material
>> for the sole use of the intended recipient. Any review, use,
>> distribution or disclosure by others is strictly prohibited.
>> If you are not the intended recipient (or authorized to
>> receive for the recipient), please contact the sender by
>> reply e-mail and delete all copies of this message.
>>
>>
>> --
>>

---

>>

---

>> Jacob Wieland
>> Software Engineer
>>
>> Testing Technologies IST GmbH
>> Michaelkirchstraße 17/18
>> 10179 Berlin, Germany
>>
>> Phone +49 30 726 19 19 34 Email This email address is being protected from spambots. You need JavaScript enabled to view it.
>> Fax +49 30 726 19 19 20 Internet www.testingtech.com
>>

---

>>

---

>>
>> UPCOMING EVENTS!
>>
>> May 14-15, IMS Asia, Singapore
>> www.informatm.com/newt/l/imsvision/asia
>>
>> May 26-28, Tutorial "Theory & Practice of TTCN-3", Berlin
>> (Germany) www.testingtech.com/services/ttcn3_tutorial.php
>>
>>

---

>>

---

>> Geschäftsführung: Theofanis Vassiliou-Gioles, Stephan Pietsch
>> Handelsregister HRB 77805, Amtsgericht Charlottenburg Ust ID
>> Nr.: DE 813 143 070
>>
>> This e-mail may contain confidential and privileged material
>> for the sole use of the intended recipient. Any review, use,
>> distribution or disclosure by others is strictly prohibited.
>> If you are not the intended recipient (or authorized to
>> receive for the recipient), please contact the sender by
>> reply e-mail and delete all copies of this message.
>>
>>
>
>


--

---

Jacob Wieland
Software Engineer

Testing Technologies IST GmbH
Michaelkirchstraße 17/18
10179 Berlin, Germany

Phone +49 30 726 19 19 34 Email This email address is being protected from spambots. You need JavaScript enabled to view it.
Fax +49 30 726 19 19 20 Internet www.testingtech.com

---

UPCOMING EVENTS!

May 14-15, IMS Asia, Singapore
www.informatm.com/newt/l/imsvision/asia

May 26-28, Tutorial "Theory & Practice of TTCN-3", Berlin (Germany)
www.testingtech.com/services/ttcn3_tutorial.php

---

Geschäftsführung: Theofanis Vassiliou-Gioles, Stephan Pietsch
Handelsregister HRB 77805, Amtsgericht Charlottenburg
Ust ID Nr.: DE 813 143 070

This e-mail may contain confidential and privileged material for the
sole use of the intended recipient. Any review, use, distribution or
disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), please contact
the sender by reply e-mail and delete all copies of this message.

Hello Jacob,

Please find my comments inserted below. Anyway, thanks for your careful reading and your hints. I'll make sure that the corresponding changes are incorporated to part1.

Best regards

Thomas

>

---

Original Message

---

>From: active_ttcn3 : mts stf133 ttcn version 3 - active
>members only [This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of ext
>Jacob Wieland
>Sent: Tuesday, 13. May 2008 09:58
>To: This email address is being protected from spambots. You need JavaScript enabled to view it.
>Subject: Re: FYI: TTCN-3 Draft Versions for v3.4.1
>
>Hello all,
>
>Several comments on core language draft:
>
>The description of template(present) (on page 110) should be
>amended to the following:
>"the template as a whole shall not resolve to the matching
>mechanisms *which match* omit"
>At the moment, the given definition does not describe the
>intended meaning.

TD: You are right, it's not only omit. But also AnyValueOrNone and ifpresent that must not be used. I suggest to follow Jacob's suggestion: clause 15.8, semantic description of (present): "... shall not resolve to matching mechanisms that match omit ..."

>
>In the table of template actual parameter/assignment usage
>(Table 11, on page 111), it is forbidden to use
>template(value) actual parameter for a
>template(omit) formal parameter. This is an error, I think, as
>template(value) is a subset of template(omit).

TD: You are also right. So in the row 'template(omit)', column 'template(value)' there should also be a 'Yes'.

>
>In the description of the syntactical structure of predefined functions
>(16.1.2 on page 116), encode/decode are mentioned, which are
>otherwise called encvalue/decvalue.

TD: you are also right.

>
>Also, I found that the standard still mentiones value
>parameterization of modules in the chapter about
>parameterization, but neither the BNF allows this nor is it
>mentioned again in the chapter about module definitions. I
>think it is a very old remnant and should be removed.
>
>Best regards,
>
>Jacob Wieland
>
>Schieferdecker, Ina wrote:
>> Dear all,
>>
>>
>> the upcoming version for TTCN-3 will be v3.4.1, for which
>the approval
>> phase is targetted for June.
>>
>>
>> The draft versions for part 1, part 4, part 6 and part 10 have been
>> made available on the ETSI portal server:
>>
>> TTCN-3 Edition 3.4.1 Core Language
>>
>docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition341_prep
>> ar
>>
>ation/00108-1__TTCN3_ed341__core/00108-1_T3_ed341_corev334__FurtherCRs
>> .z
>> ip
>>
>> TTCN-3 Edition 3.4.1 documentation tags
>>
>docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition341_prep
>> ar ation/00108-10_TTCN3_ed341__DOC/00108-10_T3_ed341_DOCv330.zip
>>
>> TTCN-3 Edition 3.4.1 OS
>>
>docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition341_prep
>> ar ation/00108-4__TTCN3_ed341__OS/00108-4_T3_ed341_OSv334.zip
>>
>> TTCN-3 Edition 3.4.1: TCI
>>
>docbox.etsi.org/MTS/MTS/07-Drafts/TTCN3_drafts/edition341_prepa
>> ra
>>
>tion/00108-6__TTCN3_ed341__TCI/00108-6_T3_ed341_TCIv333__STF349AprilSe
>> ss
>> ion.zip
>>
>>
>> These draft versions implement the CRs as noted at
>> t-ort.etsi.org/roadmap_page.php
>>
>> Please consider v3.4.1 for each part in the roadmap.
>>
>>
>>
>> !!! May we ask you to review those draft versions and let us
>know your
>> comments/proposals asap !!!
>>
>>
>> We plan to have a smooth approval phase and a fast publication, so
>> that we would like to collect your feedback beforehand.
>>
>>
>> Thank you in advance and best regards,
>>
>> Gyorgy, Jens, Thomas and Ina
>> The TTCN-3 Maintenance Team
>>
>>
>
>
>--
>

---

>

---

>Jacob Wieland
>Software Engineer
>
>Testing Technologies IST GmbH
>Michaelkirchstraße 17/18
>10179 Berlin, Germany
>
>Phone +49 30 726 19 19 34 Email This email address is being protected from spambots. You need JavaScript enabled to view it.
>Fax +49 30 726 19 19 20 Internet www.testingtech.com
>

---

>

---

>
>UPCOMING EVENTS!
>
>May 14-15, IMS Asia, Singapore
>www.informatm.com/newt/l/imsvision/asia
>
>May 26-28, Tutorial "Theory & Practice of TTCN-3", Berlin
>(Germany) www.testingtech.com/services/ttcn3_tutorial.php
>
>

---

>

---

>Geschäftsführung: Theofanis Vassiliou-Gioles, Stephan Pietsch
>Handelsregister HRB 77805, Amtsgericht Charlottenburg Ust ID
>Nr.: DE 813 143 070
>
>This e-mail may contain confidential and privileged material
>for the sole use of the intended recipient. Any review, use,
>distribution or disclosure by others is strictly prohibited.
>If you are not the intended recipient (or authorized to
>receive for the recipient), please contact the sender by reply
>e-mail and delete all copies of this message.
>
>
>--
>

---

>

---

>Jacob Wieland
>Software Engineer
>
>Testing Technologies IST GmbH
>Michaelkirchstraße 17/18
>10179 Berlin, Germany
>
>Phone +49 30 726 19 19 34 Email This email address is being protected from spambots. You need JavaScript enabled to view it.
>Fax +49 30 726 19 19 20 Internet www.testingtech.com
>

---

>

---

>
>UPCOMING EVENTS!
>
>May 14-15, IMS Asia, Singapore
>www.informatm.com/newt/l/imsvision/asia
>
>May 26-28, Tutorial "Theory & Practice of TTCN-3", Berlin
>(Germany) www.testingtech.com/services/ttcn3_tutorial.php
>
>

---

>

---

>Geschäftsführung: Theofanis Vassiliou-Gioles, Stephan Pietsch
>Handelsregister HRB 77805, Amtsgericht Charlottenburg Ust ID
>Nr.: DE 813 143 070
>
>This e-mail may contain confidential and privileged material
>for the sole use of the intended recipient. Any review, use,
>distribution or disclosure by others is strictly prohibited.
>If you are not the intended recipient (or authorized to
>receive for the recipient), please contact the sender by reply
>e-mail and delete all copies of this message.
>

Dear all,

thank you for the comments received so far. We have uploaded a revised
draft version v3.3.5 at
portal.etsi.org/docbox/MTS/MTS/07-Drafts...3_drafts/edition341_
preparation/00108-1__TTCN3_ed341__core/

Please revise this document.

Looking forward your comments.

With best regards,

Ina on behalf of the TTCN-3 maintenance team

>

---

Original Message

---

> From: Schieferdecker, Ina
> Sent: Friday, May 09, 2008 11:38 AM
> To: 'active_ttcn3 : mts stf133 ttcn version 3 - active
> members only'; 'This email address is being protected from spambots. You need JavaScript enabled to view it.'
> Subject: FYI: TTCN-3 Draft Versions for v3.4.1
>
> Dear all,
>
>
> the upcoming version for TTCN-3 will be v3.4.1, for which the
> approval phase is targetted for June.
>
>
> The draft versions for part 1, part 4, part 6 and part 10
> have been made available on the ETSI portal server:
>
> TTCN-3 Edition 3.4.1 Core Language
> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition
> 341_preparation/00108-1__TTCN3_ed341__core/00108-1_T3_ed341_co
> rev334__FurtherCRs.zip
>
> TTCN-3 Edition 3.4.1 documentation tags
> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition
> 341_preparation/00108-10_TTCN3_ed341__DOC/00108-10_T3_ed341_DO
> Cv330.zip
>
> TTCN-3 Edition 3.4.1 OS
> docbox.etsi.org/MTS/MTS/07-Drafts//TTCN3_drafts/edition
> 341_preparation/00108-4__TTCN3_ed341__OS/00108-4_T3_ed341_OSv334.zip
>
> TTCN-3 Edition 3.4.1: TCI
> docbox.etsi.org/MTS/MTS/07-Drafts/TTCN3_drafts/edition3
> 41_preparation/00108-6__TTCN3_ed341__TCI/00108-6_T3_ed341_TCIv
> 333__STF349AprilSession.zip
>
>
> These draft versions implement the CRs as noted at
> t-ort.etsi.org/roadmap_page.php
>
> Please consider v3.4.1 for each part in the roadmap.
>
>
>
> !!! May we ask you to review those draft versions and let us
> know your comments/proposals asap !!!
>
>
> We plan to have a smooth approval phase and a fast
> publication, so that we would like to collect your feedback
> beforehand.
>
>
> Thank you in advance and best regards,
>
> Gyorgy, Jens, Thomas and Ina
> The TTCN-3 Maintenance Team
>
>