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

ID | Project | Category | View Status | Date Submitted | Last Update
0006838 | Part 09: Using XML with TTCN-3 | Technical | public | 08-12-2014 14:59 | 30-12-2014 20:28

Reporter | Tomas Urban |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.5.1 (published 2013-04) |
Target Version | v4.6.1 (published 2015-06) | Fixed in Version | v4.6.1 (published 2015-06) |
Clause Reference(s) | 7.6.8, 7.6.4
For STF discussion |
Source (company - Author) | STF 475

Summary | 0006838: Invalid example 4 in the mixed content section

Description

The example 4 in the chapter 7.6.8 is invalid, because it omits just one field of the record. From the TTCN-3 point of view, it is fine, but the generated XML document won't pass validation (and maybe some codecs won't allow to encode the message too).
The easier fix is just to correct the example. However, it would be worth of considering to change the rules for conversion of the all content (described in 7.6.4) so that this kind of mistake wouldn't be possible, i.e. it would be possible only to omit all or none of the fields of the record that is a result of conversion of the all content with minOccurs=0.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR6838_resolution_v1.doc (102,400) 23-12-2014 16:09 http://oldforge.etsi.org/mantis/file_download.php?file_id=3206&type=bug

Issue History
Date Modified | Username | Field | Change
08-12-2014 14:59 | Tomas Urban | New Issue |
23-12-2014 16:08 | Gyorgy Rethy | Note Added: 0012574 |
23-12-2014 16:08 | Gyorgy Rethy | Assigned To | => Tomas Urban
23-12-2014 16:08 | Gyorgy Rethy | Status | new => confirmed
23-12-2014 16:08 | Gyorgy Rethy | Target Version | => v4.6.1 (published 2015-06)
23-12-2014 16:09 | Gyorgy Rethy | File Added: CR6838_resolution_v1.doc |
29-12-2014 15:02 | Gyorgy Rethy | Assigned To | Tomas Urban => Axel Rennoch
29-12-2014 15:02 | Gyorgy Rethy | Status | confirmed => assigned
29-12-2014 15:02 | Gyorgy Rethy | Status | assigned => confirmed
29-12-2014 15:30 | Axel Rennoch | Note Added: 0012588 |
29-12-2014 15:30 | Axel Rennoch | Note Added: 0012589 |
29-12-2014 15:30 | Axel Rennoch | Assigned To | Axel Rennoch => Gyorgy Rethy
29-12-2014 15:30 | Axel Rennoch | Status | confirmed => acknowledged
30-12-2014 18:25 | Gyorgy Rethy | Status | acknowledged => resolved
30-12-2014 18:25 | Gyorgy Rethy | Fixed in Version | => v4.6.1 (published 2015-06)
30-12-2014 18:25 | Gyorgy Rethy | Resolution | open => fixed
30-12-2014 20:28 | Gyorgy Rethy | Note Added: 0012594 |
30-12-2014 20:28 | Gyorgy Rethy | Status | resolved => closed

Notes

(0012574)
Gyorgy Rethy
23-12-2014 16:08

Example is corrected, pls. cross-check in CR6838_resolution_v1.doc. You are correct, if looking at the TTCN-3 definition only, it is possible to define an XML element, invalid according to the schema. To correct this an alternative "native" mapping to TTCN-3 set could be added, but this would require another CR next year.

(0012588)
Axel Rennoch
29-12-2014 15:30

The modified example in the resolution looks good. However next year we may talk about some conventions about naming of identifiers for templates etc. ;-)

(0012589)
Axel Rennoch
29-12-2014 15:30

you may set the CR to resolved.

(0012594)
Gyorgy Rethy
30-12-2014 20:28

Added to draft V4.5.3