ETSI's Bug Tracker - Part 09: Using XML with TTCN-3
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0007654 | Part 09: Using XML with TTCN-3 | Technical | public | 16-03-2017 14:49 | 05-01-2018 11:28

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 2016-07) |
Target Version | v4.9.1 (published 2018-05) | Fixed in Version | v4.9.1 (published 2018-05) |
Clause Reference(s) | 8.2
For STF discussion |
Source (company - Author) | STF 521

Summary | 0007654: Invalid encoding instruction in the example on type substitution
Description | The union RequestType_derivations contains a variant "name as uncapitalized". However, since the type is a result of type substitution mapping and doesn't constitute an element or attribute, the variant should not be present.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7654-v1.docx (171,200) 25-07-2017 17:11 http://oldforge.etsi.org/mantis/file_download.php?file_id=3657&type=bug

Issue History
Date Modified | Username | Field | Change
16-03-2017 14:49 | Tomas Urban | New Issue |
06-06-2017 14:30 | Jens Grabowski | Assigned To | => KristÃ³f Szabados
06-06-2017 14:30 | Jens Grabowski | Status | new => assigned
09-06-2017 10:17 | KristÃ³f Szabados | Note Added: 0014692 |
09-06-2017 10:17 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Tomas Urban
09-06-2017 10:17 | KristÃ³f Szabados | Status | assigned => feedback
09-06-2017 12:45 | Jacob Wieland - Spirent | Note Added: 0014696 |
25-07-2017 17:07 | Tomas Urban | File Added: CR7654-v1.docx |
25-07-2017 17:09 | Tomas Urban | Note Added: 0014765 |
25-07-2017 17:09 | Tomas Urban | Status | feedback => assigned
25-07-2017 17:09 | Tomas Urban | Assigned To | Tomas Urban => KristÃ³f Szabados
25-07-2017 17:09 | Tomas Urban | Status | assigned => confirmed
25-07-2017 17:11 | Tomas Urban | File Deleted: CR7654-v1.docx |
25-07-2017 17:11 | Tomas Urban | File Added: CR7654-v1.docx |
26-07-2017 09:20 | KristÃ³f Szabados | Note Added: 0014773 |
26-07-2017 09:20 | KristÃ³f Szabados | Status | confirmed => resolved
26-07-2017 09:20 | KristÃ³f Szabados | Resolution | open => fixed
26-07-2017 09:20 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Gyorgy Rethy
05-01-2018 11:28 | Gyorgy Rethy | Note Added: 0015009 |
05-01-2018 11:28 | Gyorgy Rethy | Status | resolved => closed
05-01-2018 11:28 | Gyorgy Rethy | Fixed in Version | => v4.9.1 (published 2018-05)
05-01-2018 11:28 | Gyorgy Rethy | Target Version | => v4.9.1 (published 2018-05)

Notes

(0014692)
KristÃ³f Szabados
09-06-2017 10:17

According to 5.2.2 f), on page 17: "if a character string that is to be used as a name of a TTCN-3 type starts with a lower-case letter, the first letter shall be capitalized (converted to upper-case);"
The variant seems to be fine.
According to 5.2.2 f) (on page 17) the name of the TTCN-3 type to be generated is capitalized ... and according to 5.2.2 a) (on page 20) if the name of the generated TTCN-3 is different from the original name only in the first letter the "name as uncapitalized" variant attribute shall be used.
In this case we start from "requestType" add the "_derivations" because of the type substitution; according to 5.2.2 in the generated TTCN-3 this has to be "RequestType_derivations" and so also have the variant attribute to note the change in the first letter.

(0014696)
Jacob Wieland - Spirent
09-06-2017 12:45

but what does the variant attribute accomplish? The name of the type will never appear in an XML, so the codec does not need to know whether the type name was capitalized or not.

(0014765)
Tomas Urban
25-07-2017 17:09

The rule 5.2.2.a (on page 20) cannot be applied in this case, because it works only for "an element declaration, attribute declaration, top-level complex type definition or user-defined top-level simple type definition if the type definition name generated is different from the value of the name attribute of the corresponding schema component".
The mentioned type is neither of those and it is not present in the schema. Besides as Jacob said, it doesn't make much sense to generate the instruction.
I uploaded a resolution proposal which simply removes the attributes from the examples. Please check.

(0014773)
KristÃ³f Szabados
26-07-2017 09:20

Looks good by me. Ready to be added to the next version of the core language specification.

(0015009)
Gyorgy Rethy
05-01-2018 11:28

Implemented in draft V4.8.3.