ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0004640 | Part 06: TTCN-3 Control Interface | Technical | public | 23-12-2008 11:50 | 01-09-2010 14:11

Reporter | Andrej Pietschker |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | major | Reproducibility | always
Status | closed | Resolution | won't fix |
Platform |  | OS |  | OS Version |
Product Version | v3.4.1 (published 2008-09) |
Target Version | v4.3.1 (published 2011-06) | Fixed in Version |  |
Clause Reference(s) | 7.2.2.2.
Source (company - Author) | G&D - Andrej Pietschker, Peter Mittermaier

Summary | 0004640: TCI-CD Type interface not complete

Description

In 7.3.2.2.1 the function decode is described and it should retrun the value if it is of a compatible type as the decodingHypothesis, else the distinct value null.
If a type restriction is applied during the definition of a TTCN-3 type this information is not available during decoding.
E.g. type charstring MyString length(3) then decoding "ABCD" as MyString should yield null. However a TCI interface function is missing to query such restrictions such as length, pattern, or value.

Steps To Reproduce |
Additional Information | In the proposal to 4.1.1 a function for arrays is introduced in 7.2.2.2.11: getOffset(). Similar functions are needed for other type restrictions.
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
23-12-2008 11:50 | Andrej Pietschker | New Issue |
23-12-2008 11:50 | Andrej Pietschker | Status | new => assigned
23-12-2008 11:50 | Andrej Pietschker | Assigned To | => Ina Schieferdecker
23-12-2008 11:50 | Andrej Pietschker | Clause Reference(s) | => 7.2.2.2.
23-12-2008 11:50 | Andrej Pietschker | Source (company - Author) | => G&D - Andrej Pietschker, Peter Mittermaier
12-01-2009 17:32 | Ina Schieferdecker | Target Version | => Edition 4.2.1 (not yet published)
09-12-2009 17:11 | Ina Schieferdecker | Note Added: 0009130 |
09-12-2009 17:11 | Ina Schieferdecker | Target Version | Edition 4.2.1 (not yet published) => Edition 5.1.1 (not yet published)
01-09-2010 14:10 | Ina Schieferdecker | Note Added: 0009676 |
01-09-2010 14:11 | Ina Schieferdecker | Status | assigned => closed
01-09-2010 14:11 | Ina Schieferdecker | Resolution | open => won't fix

Notes

(0009130)
Ina Schieferdecker
09-12-2009 17:11

OpenTTCN suggest to base that extension on an existing interface extension they have. If time permits, the TCI extension can be developed in 2010:
> Hello Dr Ina and dear tool smiths,
> > Dear all,
> >
> > we have been asked by Giesecke&Devrient to extend the TCI-CD interface so
> > that an inspection of the type restrictions would be possible at runtime -
> > see http://t-ort.etsi.org/view.php?id=4640 [^]
> OpenTTCN asnwers your questions:
> > May we ask if
> > 1. you have comparable use cases
> yes.
> > 2. you see the need for the described functionality in TCI-CD
> yes.
> > 3. you would welcome a respective interface extension to
> become part of
> > the standard
> yes.
>
> OpenTTCN tool has an interface extension you have described, as our
> extension to TCI-CD API. The documentation of ANSI C version
> of this API
> is publicly available at:
> http://wiki.openttcn.com/docs/2.57.0/sdk4c/api/tci__cons_8h.html [^]
> I think we wanted to make the interface as ANSI TCI-CD like
> as possible.
>
> We are willing to submit a proposal for the interface extension, if
> requested and time permits.
>
> Kind regards,
> Vesa-Matti

(0009676)
Ina Schieferdecker
01-09-2010 14:10

Having reviewed and discussed the responses from the vendors and the OpenTTCN proposal, this CR will be rejected due to the following reasons: - TE as of today handles subtypes - via the decodingHypothesis these constraints are respected - it was discussed that type constraint reflection at CD would be of limited use - constraints can be treated sufficiently via the TE