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

ID | Project | Category | View Status | Date Submitted | Last Update
0004230 | Part 09: Using XML with TTCN-3 | Technical | public | 02-10-2008 07:13 | 18-10-2008 16:01

Reporter | Gyorgy Rethy |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | always
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.1.1 (published 2009-06) | Fixed in Version | v4.1.1 (published 2009-06) |
Clause Reference(s) | 7.6.1.1
For STF discussion |
Source (company - Author) | L.M.Ericsson

Summary | 0004230: Clarify text on mapping of complexType containing extended simpleContent is unclear

Description

The text of the clause is:
"When extending simpleContent further attributes may be added to the original type. The example below extends a built-in type by adding an attribute. The mapping result of an extended simpleContent type with added attributes is always a record containing the base type as a field referenced by the reserved name base.
EXAMPLE:
..."
It is unclear what the mapping rule is. It is proposed:
"When extending XSD simpleContent, further XSD attributes may be added to the original type. The base type of the extended simpleContent and the extension XSD attributes shall be mapped as individual fields of the TTCN-3 record type, generated for the enclosing XSD complexType. First the fields corresponding to the extension XSD attributes shall be generated in the order of their occurance in the XSD, followed by the field generated for the extended XSD base type. The field name of the latter shall be "base".
EXAMPLE: The example below extends a built-in type by adding an XSD attribute
..."

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

Issue History
Date Modified | Username | Field | Change
02-10-2008 07:13 | Gyorgy Rethy | New Issue |
02-10-2008 07:13 | Gyorgy Rethy | Status | new => assigned
02-10-2008 07:13 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
02-10-2008 07:13 | Gyorgy Rethy | Clause Reference(s) | => 7.6.1.1
02-10-2008 07:13 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
13-10-2008 09:31 | Gyorgy Rethy | Summary | Mapping of complexType containing extended simpleContent is unclear => Clarify text on mapping of complexType containing extended simpleContent is unclear
15-10-2008 10:02 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Ina Schieferdecker
15-10-2008 14:19 | Ina Schieferdecker | Note Added: 0007071 |
15-10-2008 14:19 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Gyorgy Rethy
15-10-2008 14:19 | Ina Schieferdecker | Resolution | open => fixed
15-10-2008 14:19 | Ina Schieferdecker | Target Version | => Edition 4.1.1 (not yet published)
18-10-2008 16:01 | Gyorgy Rethy | Status | assigned => closed
18-10-2008 16:01 | Gyorgy Rethy | Note Added: 0007120 |
18-10-2008 16:01 | Gyorgy Rethy | Fixed in Version | => Edition 4.1.1 (not yet published)

Notes

(0007071)
Ina Schieferdecker
15-10-2008 14:19

The proposed solution is ok - just a bit of rewording:
"When extending XSD simpleContent, further XSD attributes may be added to the original type. The base type of the extended simpleContent and the additional XSD attributes shall be mapped to fields of the TTCN-3 record type, which is generated for the enclosing XSD complexType. At first, the fields corresponding to the additional XSD attributes shall be generated in the order of their occurance in the enclosing XSD complexType definition, followed by the field generated for the original type. The field name of the latter shall be "base".
EXAMPLE: ..."

(0007120)
Gyorgy Rethy
18-10-2008 16:01

Text including changes from Ina is implemented in master copy.