ETSI's Bug Tracker - Part 09: Using XML with TTCN-3
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006719Part 09: Using XML with TTCN-3Technicalpublic09-04-2014 15:2231-12-2014 11:43
ReporterGyorgy Rethy 
Assigned ToGyorgy Rethy 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versionv4.5.1 (published 2013-04) 
Target Versionv4.6.1 (published 2015-06)Fixed in Versionv4.6.1 (published 2015-06) 
Clause Reference(s)7.1.11
For STF discussion
Source (company - Author)L.M.Ericsson
Summary0006719: Mapping of nillable complex elements is not correct
DescriptionClause 7.1.11 specifies that the whole content of nillable complex elements shall be enframed by an additional "record{...} content optional" plus the useNil instruction construct. However, this is true for the contained elements only: if the complex type has also attributes, these still may be present in the encoded XML. Therefore, the extra record generated for the nillable attribute shall enframe the complex type's elements only and the complex type's attributes shall be outside of the record.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0006721closed Gyorgy Rethy Rules on the use of the ref attribute in element definitions 
Attached Filesdoc CR6719_nillable_Resolution_v1.doc (89,088) 09-04-2014 16:52
http://oldforge.etsi.org/mantis/file_download.php?file_id=2986&type=bug
doc CR6719_nillable_Resolution_v2.doc (90,112) 10-04-2014 09:10
http://oldforge.etsi.org/mantis/file_download.php?file_id=2989&type=bug
doc CR6719_nillable_resolution_v3.doc (92,672) 10-04-2014 15:32
http://oldforge.etsi.org/mantis/file_download.php?file_id=3007&type=bug
Issue History
Date ModifiedUsernameFieldChange
09-04-2014 15:22Gyorgy RethyNew Issue
09-04-2014 16:51Gyorgy RethyAssigned To => Gyorgy Rethy
09-04-2014 16:51Gyorgy RethyStatusnew => assigned
09-04-2014 16:51Gyorgy RethyProduct Version => v4.5.1 (published 2013-04)
09-04-2014 16:51Gyorgy RethyTarget Version => v4.6.1 (published 2015-06)
09-04-2014 16:52Gyorgy RethyFile Added: CR6719_nillable_Resolution_v1.doc
09-04-2014 16:53Gyorgy RethyNote Added: 0011978
09-04-2014 16:54Gyorgy RethyNote Deleted: 0011978
09-04-2014 16:54Gyorgy RethyNote Added: 0011979
09-04-2014 16:54Gyorgy RethyStatusassigned => confirmed
09-04-2014 16:58Gyorgy RethyAssigned ToGyorgy Rethy => Tomas Urban
09-04-2014 16:58Gyorgy RethyStatusconfirmed => assigned
09-04-2014 17:01Gyorgy RethyStatusassigned => confirmed
10-04-2014 09:07Tomas UrbanRelationship addedrelated to 0006721
10-04-2014 09:09Tomas UrbanNote Added: 0011983
10-04-2014 09:10Tomas UrbanFile Added: CR6719_nillable_Resolution_v2.doc
10-04-2014 09:10Tomas UrbanAssigned ToTomas Urban => Gyorgy Rethy
10-04-2014 09:10Tomas UrbanStatusconfirmed => assigned
10-04-2014 10:02Jacob Wieland - SpirentNote Added: 0011985
10-04-2014 11:06Tomas UrbanStatusassigned => confirmed
10-04-2014 15:32Gyorgy RethyNote Added: 0012013
10-04-2014 15:32Gyorgy RethyFile Added: CR6719_nillable_resolution_v3.doc
10-04-2014 15:32Gyorgy RethyAssigned ToGyorgy Rethy => Tomas Urban
10-04-2014 15:32Gyorgy RethyStatusconfirmed => assigned
10-04-2014 15:32Gyorgy RethyStatusassigned => confirmed
11-04-2014 09:24Tomas UrbanNote Added: 0012017
11-04-2014 09:24Tomas UrbanStatusconfirmed => resolved
11-04-2014 09:24Tomas UrbanResolutionopen => fixed
11-04-2014 09:24Tomas UrbanAssigned ToTomas Urban => Gyorgy Rethy
17-06-2014 16:20Gyorgy RethyFixed in Version => v4.6.1 (published 2015-06)
20-06-2014 11:54Gyorgy RethyFixed in Versionv4.6.1 (published 2015-06) =>
31-12-2014 11:43Gyorgy RethyNote Added: 0012595
31-12-2014 11:43Gyorgy RethyStatusresolved => closed
31-12-2014 11:43Gyorgy RethyFixed in Version => v4.6.1 (published 2015-06)

Notes
(0011979)
Gyorgy Rethy   
09-04-2014 16:54   
Proposed resolution is in CR6719_nillable_Resolution_v1.doc. Please review.
(0011983)
Tomas Urban   
10-04-2014 09:09   
Fine by me. I only changed the code generated for the referenced nillable element and added the result of this element transformation (see the related issue for more information).
Please check.
(0011985)
Jacob Wieland - Spirent   
10-04-2014 10:02   
Some more clarification/specification is needed in regard to the relationship between the content-field and the attribute fields, i.e. their order and nameclash-resolution (i.e. what happens if the mangling of attribute-names also yield "content" - which takes precedence?)
(0012013)
Gyorgy Rethy   
10-04-2014 15:32   
In example 2 "UseNil" has to be attached to the top-level record and not to its "content" field: corrected both in the text and in the example.

Handling of possible name clashes has been added to the new paragraph of $7.1.11 and to the text of $B.3.15. Also, an explanatory note is added to B.3.15.

See in CR6719_nillable_resolution_v3.doc.
(0012017)
Tomas Urban   
11-04-2014 09:24   
I have found no issues in the proposed resolution.
The changes can be added to the next version of the standard.
(0012595)
Gyorgy Rethy   
31-12-2014 11:43   
Added to draft V4.5.3