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

ID | Project | Category | View Status | Date Submitted | Last Update
0005773 | Part 09: Using XML with TTCN-3 | Clarification | public | 29-09-2010 11:22 | 02-12-2010 09:21

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 |  |
Target Version | v4.3.1 (published 2011-06) | Fixed in Version | v4.3.1 (published 2011-06) |
Clause Reference(s) | 7.5.3
For STF discussion |
Source (company - Author) | L.M.Ericsson

Summary | 0005773: Further clarification of decoding union values is needed

Description

Current note in clause 7.5.3 is:
"NOTE 1: XSD requires (see XML Schema Part 2: Datatypes [9], clause 2.5.1.3) that an element or attribute value is validated against the member types in the order in which they appear in the definition until a match is found. A TTCN-3 tool has to use this strategy as well, when decoding an XSD union value."
For further clarification it should be added that "taking into account the xsi:type attribte, if present, and the value in the XML instance"
This note should also be referenced from clause B.3.16 Use Union.

Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
29-09-2010 11:22 | Gyorgy Rethy | New Issue |
29-09-2010 11:22 | Gyorgy Rethy | Clause Reference(s) | => 7.5.3
29-09-2010 11:22 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
29-09-2010 11:23 | Gyorgy Rethy | Description Updated |
29-11-2010 11:24 | Gyorgy Rethy | Note Added: 0009822 |
29-11-2010 11:25 | Gyorgy Rethy | Note Edited: 0009822 |
29-11-2010 11:26 | Gyorgy Rethy | Assigned To | => Jacob Wieland - Spirent
29-11-2010 11:26 | Gyorgy Rethy | Status | new => assigned
29-11-2010 11:26 | Gyorgy Rethy | Target Version | => Edition 4.3.1 (not yet published)
29-11-2010 12:27 | Jacob Wieland - Spirent | Note Added: 0009824 |
29-11-2010 12:28 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Gyorgy Rethy
30-11-2010 15:41 | Gyorgy Rethy | Status | assigned => resolved
30-11-2010 15:41 | Gyorgy Rethy | Resolution | open => fixed
30-11-2010 15:41 | Gyorgy Rethy | Fixed in Version | => Edition 4.3.1 (not yet published)
02-12-2010 09:21 | Gyorgy Rethy | Status | resolved => closed
02-12-2010 09:21 | Gyorgy Rethy | Note Added: 0009915 |

Notes

(0009822)
Gyorgy Rethy
29-11-2010 11:24 (edited on: 29-11-2010 11:25)

Additional clarification: e.g. if the XSD type is
...
<xsd:simpleType>
<xsd:union>
<xsd:simpleType>
<xsd:restriction base="xsd:integer"/>
</xsd:simpleType>
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:union>
</xsd:simpleType>
the XML element
<e21unnamedElement>1</e21unnamedElement>
will be decoded as an integer value, while
<e21unnamedElement xsi:type="xsd:string">1</e21unnamedElement>
will be decoded as a string value
Note 1 is proposed to be extended to:
"NOTE 1: XSD requires (see XML Schema Part 2: Datatypes [9], clause 2.5.1.3) that an element or attribute value of an instance is validated against the member types in the order in which they appear in the XSD definition until a match is found (considering any xsi:type attribute present, see also clause B.3.25). A TTCN-3 tool has to use this strategy as well, when decoding an XSD union value."
Pls. check the proposal

(0009824)
Jacob Wieland - Spirent
29-11-2010 12:27

agreed

(0009915)
Gyorgy Rethy
02-12-2010 09:21

Done