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

ID | Project | Category | View Status | Date Submitted | Last Update
0007657 | Part 09: Using XML with TTCN-3 | Clarification | public | 24-03-2017 15:01 | 05-01-2018 11:32

Reporter | Gyorgy Rethy |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version | v4.8.1 (published 2017-05) |
Target Version | v4.9.1 (published 2018-05) | Fixed in Version | v4.9.1 (published 2018-05) |
Clause Reference(s) | B.3.2 and B.3.3
For STF discussion |
Source (company - Author) | L.M.Ericsson

Summary | 0007657: Name of anyAttribute and anyElement fields are not encoded

Description

XSD <any> elements are translated in TTCN-3 to one of the
XSD.String elem
anytype elem
record of XSD.String elem_list
record of anytype elem_list
TTCN-3 fields, and the field receives an
variant(elem) "anyElement";
or
variant(elem_list) "anyElement";
encoding instruction.
At encoding this TTCN-3 field in XML, the name of the field (elem or elem_list correspondingly) itself is not encoded, only its content. And similarly, the name elem|elem_list is not expected when decoding an XML document to TTCN-3.
However, this is not explicitly specified at the description of anyElement in clause B.3.2 (implicitly can be assumed as the description talks about the content, still it may leave some ambiguity).
Proposed solution: specify in the description part of clause B.3.2 explicitly that the TTCN-3 field *containing* the "any" element or elements is not encoded, only its content.
----------------------------------------------------------------------------
The same is true for the XSD anyAttribute element and the description of the "anyAttribute" encoding instruction in clause B.3.3.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files | CR7657.docx (155,583) 09-06-2017 10:12 http://oldforge.etsi.org/mantis/file_download.php?file_id=3631&type=bug

Issue History
Date Modified | Username | Field | Change
24-03-2017 15:01 | Gyorgy Rethy | New Issue |
06-06-2017 14:26 | Jens Grabowski | Assigned To | => Tomas Urban
06-06-2017 14:26 | Jens Grabowski | Status | new => assigned
09-06-2017 10:12 | Tomas Urban | File Added: CR7657.docx |
09-06-2017 10:12 | Tomas Urban | Note Added: 0014691 |
09-06-2017 10:12 | Tomas Urban | Assigned To | Tomas Urban => KristÃ³f Szabados
09-06-2017 10:12 | Tomas Urban | Status | assigned => confirmed
09-06-2017 15:07 | KristÃ³f Szabados | Note Added: 0014700 |
09-06-2017 15:07 | KristÃ³f Szabados | Status | confirmed => resolved
09-06-2017 15:07 | KristÃ³f Szabados | Resolution | open => fixed
09-06-2017 15:07 | KristÃ³f Szabados | Assigned To | KristÃ³f Szabados => Gyorgy Rethy
05-01-2018 11:32 | Gyorgy Rethy | Note Added: 0015010 |
05-01-2018 11:32 | Gyorgy Rethy | Status | resolved => closed
05-01-2018 11:32 | Gyorgy Rethy | Fixed in Version | => v4.9.1 (published 2018-05)
05-01-2018 11:32 | Gyorgy Rethy | Target Version | => v4.9.1 (published 2018-05)

Notes

(0014691)
Tomas Urban
09-06-2017 10:12

Resolution proposal uploaded. Please check.

(0014700)
KristÃ³f Szabados
09-06-2017 15:07

The proposal is ready to be added to the next version of the specification.

(0015010)
Gyorgy Rethy
05-01-2018 11:32

Added to draft V4.8.3.