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

ID | Project | Category | View Status | Date Submitted | Last Update
0006869 | Part 09: Using XML with TTCN-3 | Technical | public | 21-01-2015 13:03 | 04-11-2015 09:45

Reporter | Jacob Wieland - Spirent |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | always
Status | closed | Resolution | no change required |
Platform |  | OS |  | OS Version |
Product Version | v4.5.1 (published 2013-04) |
Target Version | v4.7.1 (published 2016-07) | Fixed in Version | v4.7.1 (published 2016-07) |
Clause Reference(s) | 6.8
For STF discussion |
Source (company - Author) | Testing Technologies - Jacob Wieland

Summary | 0006869: AnyType in XSD module is missing embed_values field

Description

At the moment, it is not possible to model mixed elements with the AnyType type definitoin of the XSD module as it only included attributes and elements but
not the possibly existing contents between the elements.
Therefore, the AnyType definition should be changed to:
type record AnyType {
record length (1 .. infinity) of String attr optional,
record length (1 .. infinity) of String embed_values optional,
record of String elem_list
}
Of course, at the moment, since String can contain anything, the elem_list could be used as a workaround to carry also the other content, but this is inconsistent with other mixed element types and should be avoided.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.

Relationships

duplicate of | 0006685 | closed | Gyorgy Rethy | Splitting rules for xsd:anyType

Attached Files |

Issue History
Date Modified | Username | Field | Change
21-01-2015 13:03 | Jacob Wieland - Spirent | New Issue |
21-01-2015 13:03 | Jacob Wieland - Spirent | Status | new => assigned
21-01-2015 13:03 | Jacob Wieland - Spirent | Assigned To | => Gyorgy Rethy
04-11-2015 09:34 | Gyorgy Rethy | Relationship added | duplicate of 0006685
04-11-2015 09:44 | Gyorgy Rethy | Note Added: 0013482 |
04-11-2015 09:45 | Gyorgy Rethy | Note Edited: 0013482 | bug_revision_view_page.php?bugnote_id=13482#r204
04-11-2015 09:45 | Gyorgy Rethy | Status | assigned => closed
04-11-2015 09:45 | Gyorgy Rethy | Resolution | open => no change required
04-11-2015 09:45 | Gyorgy Rethy | Fixed in Version | => v4.7.1 (published 2016-07)

Notes

(0013482)
Gyorgy Rethy
04-11-2015 09:44 (edited on: 04-11-2015 09:45)

Comment was correct, but as it is related to an earlier version of the standard. The CR was submitted at the time when the new v4.6.1 version was not TB approved yet, but it contained the solution for the problem based on CR 6685. In version v4.6.1 AnyType is changed to:
type record AnyType {
record of XSD.String embed_values optional,
record length (1 .. infinity) of XSD.String attr optional,
record of XSD.String elem_list
}
with {
variant "XSD:anyType";
variant "embedValues";
variant(attr) "anyAttributes";
variant(elem_list) "anyElement";
}
(having embedValues as the first field gives alignment with mixed content's mapping).