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

ID | Project | Category | View Status | Date Submitted | Last Update
0006338 | Part 09: Using XML with TTCN-3 | Clarification | public | 30-11-2012 11:02 | 11-12-2012 16:13

Reporter | Gyorgy Rethy |
Assigned To | Gyorgy Rethy |
Priority | normal | Severity | minor | Reproducibility | have not tried
Status | closed | Resolution | won't fix |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.5.1 (published 2013-04) | Fixed in Version | v4.5.1 (published 2013-04) |
Clause Reference(s) | 7.7
For STF discussion |
Source (company - Author) | L.M.Ericsson

Summary | 0006338: Location of definitions and fields generated for wildcards (any element) shall be defined
Description | Location of fields corresponding to anyAttribute is specified but not the order of fields generated for element elements and any elements within the enclosing structured type.
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
30-11-2012 11:02 | Gyorgy Rethy | New Issue |
30-11-2012 11:02 | Gyorgy Rethy | Clause Reference(s) | => 7.7
30-11-2012 11:02 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
10-12-2012 13:43 | Gyorgy Rethy | Status | new => assigned
10-12-2012 13:43 | Gyorgy Rethy | Assigned To | => Gyorgy Rethy
10-12-2012 16:14 | Gyorgy Rethy | Target Version | => Edition 4.5.1
11-12-2012 10:21 | Gyorgy Rethy | File Added: CR6338_resolution_v1.doc |
11-12-2012 10:22 | Gyorgy Rethy | Note Added: 0011215 |
11-12-2012 10:22 | Gyorgy Rethy | Assigned To | Gyorgy Rethy => Tomas Urban
11-12-2012 16:10 | Tomas Urban | Note Added: 0011236 |
11-12-2012 16:10 | Tomas Urban | Assigned To | Tomas Urban => Gyorgy Rethy
11-12-2012 16:11 | Gyorgy Rethy | File Deleted: CR6338_resolution_v1.doc |
11-12-2012 16:12 | Gyorgy Rethy | Note Added: 0011237 |
11-12-2012 16:13 | Gyorgy Rethy | Status | assigned => closed
11-12-2012 16:13 | Gyorgy Rethy | Resolution | open => won't fix
11-12-2012 16:13 | Gyorgy Rethy | Fixed in Version | => Edition 4.5.1

Notes

(0011215)
Gyorgy Rethy
11-12-2012 10:22

Proposed resolultion is in CR6338_resolution_v1.doc, pls. review.

(0011236)
Tomas Urban
11-12-2012 16:10

The position of the any element is significant in case of xsd:sequence. It means that the generated field cannot be at the end of the enframing record, because the codec would not know the insertion point for the any element.
The current specification already contains a sentence: "The XSD any element shall be translated, like other elements, to a field of the enframing record type or field or union field ..." I suppose the sentence can be interpreted in the way that rules for position of the any element are the same as for any other element (because the chapter 7.7.1 doesn't specify otherwise). If it is safe to make such an assumption, I think that actually no change is required in the specification.
Assigned to GyÃ¶rgy to crosscheck.

(0011237)
Gyorgy Rethy
11-12-2012 16:12

Correct, the CR can be closed, no change is needed.